Software Evolution & Impact of

Software Engineering

Presentation by Mahesh Raina

Contents:

 History Of Software Engineering

 Evolution Of software Engineering : Throughout the history how Software Engineering has
been evolved
 Age of Internet
 Impact on software and Software Engineering because of Evolution
 Future of Software and Software Engineering
 History Of Software Engineering

 Alan Turing is credited with being the first person to come up with a theory for software
in 1935, which led to the two academic fields of computer science and
software engineering.
 21 June 1948, The very first time a stored-program computer held a piece of software in
electronic memory and executed it successfully, was 11 am 21 June 1948, at the University of
Manchester, on the Manchester Baby computer. It was written by Tom Kilburn, and calculated
the highest factor of the integer 2^18 = 262,144
 Margaret H. Hamilton is the person who came up with the idea of naming the
discipline, software engineering, as a way of giving it legitimacy during the
development of the Apollo Guidance Computer.[9][10]
 Evolution Of software Engineering: From an Art To
Engineering Discipline
 In the 1960s and 1970s, the field of software engineering began to take shape. Researchers and practitioners
began to develop formal methods for software design and development, such as structured programming and the
use of flowcharts to represent algorithms. In 1968, a conference on software engineering was held, and the term
“software engineering” was officially coined.
 Is Software Engineering A Science Or An Art?
software engineering has evolved from an art to a
discipline with its own set of best practices,
methodologies, and tools. The field has grown
and matured over time, with new technologies
And approaches being developed to improve
the design and development of software.
Lehman’s laws of software evolution
These laws, were first published in 1974

S-type (specified) programs are derivable

from a static specification and can be
formally proven as correct or not.

P-type (problem-solving) programs attempt

to solve problems that can be formulated
formally, but which are not computationally
affordable. Therefore, the program must be
based on heuristics or approximations to
the theoretical problem.

E-type (evolutionary) programs are

reflections of human processes or of a part
of the real world. These kinds of
programs try to solve an activity that
somehow involves people or the real world.
 1965 to 1985: The software crisis

 Software engineering was spurred by the so-called software crisis of the 1960s, 1970s, and
1980s, which identified many of the problems of software development. Many projects ran over
budget and schedule. Some projects caused property damage. A few projects caused loss of
life. The software crisis was originally defined in terms of productivity, but evolved to
emphasize quality . Some used the term software crisis to refer to their inability to hire enough
qualified programmers.

 Cost and Budget Overruns: The OS/360 operating system was a classic example. This decade-
long project from the 1960s eventually produced one of the most complex software systems at
the time. OS/360 was one of the first large (1000 programmers) software projects. Fred Brooks
claims in The Mythical Man-Month that he made a multimillion-dollar mistake of not
developing a coherent architecture before starting development
 Age of Internet
 The rise of the Internet led to very rapid growth in the demand for international information display/e-mail
systems on the World Wide Web. Programmers were required to handle illustrations, maps, photographs, and
other images, plus simple animation, at a rate never before seen, with few well-known methods to optimize
image display/storage
Impact on software and Software Engineering because of Evolution