Software Engineering: (LECT 1)
Software Engineering: (LECT 1)
Software Engineering: (LECT 1)
(LECT 1)
1
Organization of this
Lecture:
What is Software Engineering?
Programs vs. Software Products
Evolution of Software Engineering
Notable Changes In Software
Development Practices
Introduction to Life Cycle Models
Summary
2
What is Software
Engineering?
Engineering approach to develop
software.
Building Construction Analogy.
Systematic collection of past
experience:
techniques,
methodologies,
guidelines.
3
Engineering Practice
Technology
Esoteric Past
Craft Systematic Use of Past
Experience Experience and Scientific Basis
Unorganized Use of
Past Experience
Art
Time
5
Why Study Software Engineering?
(1)
6
Why Study Software Engineering?
(2)
To acquire skills to be a
better programmer:
Higher Productivity
Better Quality Programs
8
Software Crisis
Software products:
fail to meet user requirements.
frequently crash.
expensive.
difficult to alter, debug, and
enhance.
often delivered late.
use resources non-optimally.
9
Software Crisis (cont.)
Hw cost
Sw cost
1960 Year
1999
Relative Cost of Hardware and Software
10
Factors contributing to the
software crisis
Larger problems,
Lack of adequate training in
software engineering,
Increasing skill shortage,
Low productivity improvements.
11
Programs versus Software
Products
12
Computer Systems
Engineering
Computer systems engineering:
encompasses software
engineering.
Many products require
development of software as well
as specific hardware to run it:
a coffee vending machine,
a mobile communication
product, etc.
13
Computer Systems
Engineering
14
Computer Systems
Engineering (CONT.)
15
Computer Systems
Engineering (CONT.)
Feasibility
Study
Requirements
Analysis and
Specification Hardware
Development
Hardware
Software
Partitioning
Software
Development Integration
and Testing
Project Management
16
Emergence of Software
Engineering
18
High-Level Language
Programming (Early 60s)
19
High-Level Language
Programming (Early 60s)
20
Control Flow-Based Design
(late 60s)
Programmers found:
programs written by others very
difficult to understand and maintain.
To cope up with this problem,
experienced programmers
advised: ``Pay particular attention
to the design of the program's
control structure.'’
22
Control Flow-Based Design (late 60s)
60s)
111 25
Control Flow-Based Design (Late
60s)
It was found:
GO TO statements makes control
structure of a program messy
GO TO statements alter the flow
of control arbitrarily.
The need to restrict use of GO TO
statements was recognized.
26
Control Flow-Based Design (Late
60s)
28
Control Flow-Based Design (Late
60s)
29
Control Flow-Based Design (Late
60s)
Everyone accepted:
it is possible to solve any
programming problem without
using GO TO statements.
This formed the basis of
Structured Programming
methodology.
31
Structured Programming
32
Structured programs
33
Structured programs
34
Structured programs
35
Structured Programming
Research experience
shows:
programmers commit less
number of errors
while using structured if-then-
else and do-while statements
compared to test-and-branch
constructs. 36
Data Structure-Oriented
Design (Early 70s)
37
Data Structure-Oriented
Design (Early 70s)
Techniques which
emphasize designing the
data structure:
derive program structure from
it:
are called data
structure-oriented
38
Data Structure Oriented
Design (Early 70s)
JSP technique:
program code structure
should correspond to the
data structure.
40
Data Structure Oriented
Design (Early 70s)
In JSP methodology:
a program's data structures are
first designed using notations for
sequence, selection, and iteration.
Then data structure design is
used :
to derive the program structure.
41
Data Structure Oriented
Design (Early 70s)
42
Data Flow-Oriented Design (Late
70s)
Data flow-oriented
techniques advocate:
the data items input to a system
must first be identified,
processing required on the data
items to produce the required
outputs should be determined.
43
Data Flow-Oriented Design (Late
70s)
46
Object-Oriented Design (80s)
Object-oriented technique:
an intuitively appealing design
approach:
natural objects (such as
employees, pay-roll-register, etc.)
occurring in a problem are first
identified.
47
Object-Oriented Design (80s)
48
Object-Oriented Design (80s)
Object-Oriented Techniques
have gained wide acceptance:
Simplicity
Reuse possibilities
Lower development time and cost
More robust code
Easy maintenance
49
Evolution of Design
Techniques
Object-Oriented
Data flow-based
Data structure-
based
Control flow-
based
Ad hoc
50
Evolution of Other Software
Engineering Techniques
51
Evolution of Other Software
Engineering Techniques
life cycle models,
specification techniques,
project management techniques,
testing techniques,
debugging techniques,
quality assurance techniques,
software measurement
techniques,
CASE tools, etc.
52
Differences between the exploratory
style and modern software
development practices
In exploratory style,
errors are detected only during
testing,
Now,
focus is on detecting as many
errors as possible in each
phase of development.
55
Differences between the exploratory
style and modern software
development practices (CONT.)
In exploratory style,
coding is synonymous with
program development.
Now,
coding is considered only a
small part of program
development effort.
56
Differences between the exploratory
style and modern software
development practices (CONT.)
57
Differences between the exploratory
style and modern software
development practices (CONT.)
During all stages of
development process:
Periodic reviews are being carried
out
Software testing has become
systematic:
standard testing techniques are
available.
58
Differences between the exploratory
style and modern software
development practices (CONT.)
59
Differences between the exploratory
style and modern software
development practices (CONT.)
60
Differences between the exploratory
style and modern software
development practices (CONT.)
61
Software Life Cycle
Software life cycle (or software
process):
series of identifiable stages
that a software product
undergoes during its life time:
Feasibility study
requirements analysis and specification,
design,
coding,
testing
62
Life Cycle Model
A software life cycle model (or
process model):
a descriptive and diagrammatic model
of software life cycle:
identifies all the activities required for
product development,
establishes a precedence ordering among
the different activities,
Divides life cycle into phases.
63
Life Cycle Model (CONT.)
64
Why Model Life Cycle ?
A written description:
forms a common understanding of
activities among the software
developers.
helps in identifying inconsistencies,
redundancies, and omissions in the
development process.
Helps in tailoring a process model for
specific projects.
65
Why Model Life Cycle ?
66
Life Cycle Model (CONT.)
67
Life Cycle Model (CONT.)
68
Life Cycle Model (CONT.)
69
Life Cycle Model (CONT.)
71
Life Cycle Model (CONT.)
72
Life Cycle Model (CONT.)
73
Life Cycle Model (CONT.)
75
Life Cycle Model (CONT.)
77
Summary
78
Summary
Adherence to a software life cycle
model:
helps to do various development
activities in a systematic and
disciplined manner.
also makes it easier to manage a
software development effort.
79
Reference
80