1. Lecture: Requirements Development - Vision and Scope

2.  A Project is a sequence of unique, complex, and connected activities having one goal or purpose and that must be completed by a specific time, within budget, and according to specification. ( p. 65)

3. Elicitation AnalysisSpecificationValidation Clarify Correct and close gaps Rewrite Re-evaluate Text, p. 59

4.  Revisit the requirements development cycle  Revisit the requirements development process  Vision and Scope  Exercise

5. 1. Define Vision/Scope 2. Identify users/stakeholders: classes, reps, decision makers 3. Select elicitation techniques 4. Identify, prioritize and develop use cases  Some modeling here (e.g. user interfaces)  Includes business rules

6. 5. Specify quality attributes 6. Derive/create requirements specification  Including external interfaces? Constraints? 7. Model 8. Review 9. Prototype

7. 10. Develop/evolve Architecture 11. Allocate requirements to (software) components 12. Develop test cases 13. Validate

8.  Revisit the requirements development cycle  Revisit the requirements development process  Vision and Scope  Exercise

9.  Common understanding of business requirements  Provides boundary  Vision: whole “product”  Scope: particular project or iteration or...

10. Product Vision Scope for Business Area 1 Scope for Business Area 2 And so on… These might be different releases

11.  For.. (target)..who.. (need).. the.. (product).. is.. (category).. that.. (key benefit).. unlike.. (current or competitor).. our product.. (advantages)  Text, (p.85)

12.  Features  Key Stakeholders  Operating Environment  Use Case Diagram

13.  Major Features  Describe functionality of each feature (include as much as you know!)  E.g. ▪ Payroll Creation: The payroll creation feature will allow the client to set up and execute a regularly scheduled process to calculate employee wages owing for a specific time period, to make appropriate deductions, and to generate an electronic deposit to each employee’s bank account. A pay slip will also be printed for each employee.

14.  Key Stakeholders  Who needs to be part of the development?  Who will use the system and how?

15.  Operating Environment  Physical environment ▪ Distribution? ▪ Locations?  Availability/Performance/Integrity requirements

16.  Revisit the requirements development cycle  Revisit the requirements development process  Vision and Scope  Exercise

17.  In Your Group  Create a vision statement for the entire system

18. In Your Group  Identify the Business Areas of the that must interface with each other and decide how

19.  Define initial scope for each business area within ▪ Create a description of major system features ▪ If you finish then: ▪ Identify key stakeholders ▪ Define operating environment