Professional Documents
Culture Documents
Based on
6/6/01
6/6/01
Whats Needed?
6/6/01
6/6/01
6/6/01
IMPROVEMENT
Productivity Increase
202%
46%
Defect Reduction
90%
76%
Data derived from an SEI Technical Report, Benefits of CMM-Based Software Process Improvement,
CMU/SEI-94-TR-13, August 1994.
6/6/01
6/6/01
6/6/01
Informing the
enterprise
User
requirements
System
requirements
Supplier
work
Architectural
design
Customer work
Defining
results
for users
Defining what
the system
must do
Optimizing
the costbenefits
Amount of effort
Detailed
design &
component
development
Storing
knowledge from
previous projects
Provisional
& final
acceptance
Deciding
Linking
Qualifying
Verifying
on potential deliverables
the
& validating
changes to requirements design
the product
6/6/01
10
6/6/01
What do we mean
by real requirements?
11
6/6/01
Characteristics of a Good
Requirement
Each individual requirement should be:
12
6/6/01
Effective Communication
13
6/6/01
14
6/6/01
15
6/6/01
EFFECTIVENESS
Very High
COSTS
High
Defect Estimation
Very High
Low
Defect Tracking
High
Low
Formal Testing
High
High
QA Organization
High
High
Independent audits
High
High
High
Low
Prototyping
High
Low
High
Medium
Change Tracking
High
Medium
Informal Walkthroughs
Moderate
Medium
Informal Testing
Moderate
Medium
TQM
Moderate
Medium
ISO 9000-9004
Marginal
High
16