Scope

1
Scope

• CSSE 371 Software Requirements and Specification
  Mark Ardis, Rose-Hulman InstituteOctober 11,
  2004

2
Project Scope
Resources
Time
Deadline
3
The Shape of Scope
Resources
Resources
Time
Time
4
Brooks' Law

• Adding labor to a late project makes it later
• Why?

5
Requirements Baseline

• Itemized list of features intended for a given
  release
• Must be acceptable to customer
• Must have reasonable probability of success

6
Setting Priorities

• Customers should decide priorities.
• Why?

7
Example Priorities
Feature Priority
1 External RDB support Critical
4 Portability to a new OS Critical
3 Ability to clone new project Important
5 New project wizard Important
2 Implementation of tool tips Useful
8
Assessing Effort

• Developers should estimate effort.
• Why?

9
Example Effort
Feature Priority Effort
1 External RDB support Critical Medium
4 Portability to a new OS Critical High
3 Ability to clone new project Important Low
5 New project wizard Important Low
2 Implementation of tool tips Useful Low
10
Setting the Baseline

• Include all "Critical" items
• Can you deliver those items on time?
• Add some "Important" items as budget allows

11
Example Baseline
Feature Priority Effort
1 External RDB support Critical Medium
4 Portability to a new OS Critical High
3 Ability to clone new project Important Low
Baseline
5 New project wizard Important Low
2 Implementation of tool tips Useful Low
12
Managing the Customer

• Include customer in decisions about scope
  reduction
• Negotiate changes to requirements
• Give yourself some slack
• Avoid "feature creep"