Software and Software Engineering

1
Software and Software Engineering

• Lecture 1

2
Motivation

• What does software engineering provide?
• Why do we need software engineering?

3
What is Software Engineering

• Engineering Discipline
• Systematic and Standardized Approach to Software
  Development using
• Processes (Methodologies)
• Sequence of steps from project start to end
• Architectures
• Common skeleton solutions (structure)
• Principles
• Guidelines and good practices
• Models

4
Project Success and Failure Rates

• 1998
• 26 Successful
• 28 Failed
• 46 Challenged
• 2000
• 28 Successful
• 23 Failed
• 49 Challenged

Larman, Craig, Agile and Iterative Development, A
Managers Guide, Addison-Wesley, 2004, page 101.
5
Costs

• Costs are high (70) for the on-going operation
  of the software system over its life cycle

6
Project Success
Larman, Craig, Agile and Iterative Development, A
Managers Guide, Addison-Wesley, 2004, page 71.
7
Change
Larman, Craig, Agile and Iterative Development, A
Managers Guide, Addison-Wesley, 2004, page 73.
8
Factors on Challenged Projects
Larman, Craig, Agile and Iterative Development, A
Managers Guide, Addison-Wesley, 2004, page 56.
9
Actual Use of Requested Features
Larman, Craig, Agile and Iterative Development, A
Managers Guide, Addison-Wesley, 2004, page 57.
10
Chapter 1

11
Software Failures over Time
12
Myths

• Standards and procedures everything you need to
  know to build software
• Behind schedule -gt add more programmers
• Outsource -gt Relax
• Start writing programs -gt Fill in details later
• Change is easily accommodated
• Done when code is written
• No way to access quality until code is running
• Only deliverable is code
• Documentation slows us down