Professional Documents
Culture Documents
Engineering
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide1
Objectives
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide2
Topics covered
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide3
Software engineering
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide4
Software costs
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide5
What is software?
What is software engineering?
What is the difference between software
engineering and computer science?
What is the difference between software
engineering and system engineering?
What is a software process?
What is a software process model?
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide6
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide7
What is software?
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide8
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide9
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide10
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide11
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide12
Waterfall;
Iterative development;
Component-based software engineering.
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide13
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide14
W
a
er
fall
t
mod
0
2
5
5
0
1
0
0
7
5
Specific
Design
Devel
Integ
ratio
It
erative
0
2
5
5
0
7
5
1
0
0
Specific
Iterativ
S
y
ste
Compon
ineerin
0
2
5
5
0
1
0
0
7
5
Specific
Develo
Integ
ratio
Develop
ems
0
1
0
2
0
0
40
3
S
ystem
d
S
ystem
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide15
0
2
5
5
0
1
0
7
5
Specifi
Devel
S
yst
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide16
Rules
Recommendations
Process guidance
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide17
Lower-CASE
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide18
Dependability
Efficiency
Acceptability
Software must accepted by the users for which it was designed. This
means it must be understandable, usable and compatible with other
systems.
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide19
Delivery
Trust
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide20
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide21
Confidentiality
Competence
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide22
Computer misuse
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide23
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide24
Preamble
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide25
PUBLIC
PRODUCT
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide26
JUDGMENT
MANAGEMENT
PROFESSION
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide27
COLLEAGUES
SELF
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide28
Ethical dilemmas
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide29
Key points
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide30
Key points
IanSommerville2004
SoftwareEngineering,7thedition.Chapter1
Slide31