Leture-w1-2

Leture-w1-2 - SE 210: Software Specification and Design I...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
SE 210: Software Specification and Design I Fall 2008 Lecture 2 on Wed., Sept. 24, 2008
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 Last Lecture 1 team project: 4 weighted assignments. Have you started choosing  your project? your teammates? Hand in the assignment0 on Mon., Sept. 29, 2008 (Next  Monday!)
Background image of page 2
3 The Requirements Problem The goal of software development: To develop quality software  on time  and  on budget  and  meets customers’  real needs . The reality:  quite different customers  many software development projects failed.  The Standish Group research [1994] shows in United States: 31%  of projects will be cancelled before they are get completed. 52.7%  project will cost 189% of their original estimates.
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 The Root Causes of Project Failure The three most commonly cited factors: Lack of user input : 13% of all projects Incomplete requirements and specifications:  12% of all  projects. Changing requirements and specifications:  12% of all projects. At least a third of development projects run into trouble  due to requirements gathering, documentation, and management. 
Background image of page 4
5 The Root Cause for Project Success Projects delivered on time and on budget: 9% of the projects in large companies.  16% of the projects in small companies. Three most important factors: User involvement : 16% of all successful projects. Executive management support : 14% of all successful projects. Clear statement requirements : 12% of all successful projects.
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
6 The High Cost of Requirements Errors .1-.2 .5 1 2 5 20 Requirements time Design Coding Unit Test Acceptance test Maintenance
Background image of page 6
7 Reasons for the High Cost of Requirements Errors Respecification Redesign Recoding Retesting Change orders (telling users to replace a defective version of the system with a 
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 10/14/2008 for the course SE 210 taught by Professor An during the Fall '08 term at Drexel.

Page1 / 23

Leture-w1-2 - SE 210: Software Specification and Design I...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online