1. 1 Scope CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute October 11, 2004

2. 2 Project Scope Resources Time Deadline

3. 3 The Shape of Scope Resources Time Deadline Time Resources

4. 4 Brooks' Law Adding labor to a late project makes it later Why?

5. 5 Requirements Baseline Itemized list of features intended for a given release Must be acceptable to customer Must have reasonable probability of success

6. 6 Setting Priorities Customers should decide priorities. Why?

7. 7 Example Priorities #FeaturePriority 1External RDB supportCritical 4Portability to a new OSCritical 3Ability to clone new projectImportant 5New project wizardImportant 2Implementation of tool tipsUseful

8. 8 Assessing Effort Developers should estimate effort. Why?

9. 9 Example Effort #FeaturePriorityEffort 1External RDB supportCriticalMedium 4Portability to a new OSCriticalHigh 3Ability to clone new projectImportantLow 5New project wizardImportantLow 2Implementation of tool tipsUsefulLow

10. 10 Setting the Baseline Include all "Critical" items Can you deliver those items on time? Add some "Important" items as budget allows

11. 11 Example Baseline #FeaturePriorityEffort 1External RDB supportCriticalMedium 4Portability to a new OSCriticalHigh 3Ability to clone new projectImportantLow Baseline 5New project wizardImportantLow 2Implementation of tool tipsUsefulLow

12. 12 Managing the Customer Include customer in decisions about scope reduction Negotiate changes to requirements Give yourself some slack Avoid "feature creep"