BTS330: Business Requirements Analysis using OO

1. BTS330: Business Requirements Analysis using OO Requirements Development: Vision and Scope

2. Agenda • Vision and Scope • <Clinic Name> Exercise

3. Re-evaluate Clarify Rewrite Correct and close gaps Requirements Development Elicitation Analysis Specification Validation Text, p. 59

4. Agenda • Revisit the requirements development cycle • Revisit the requirements development process • Vision and Scope • <Clinic Name> Exercise

5. Process (Iterative!) • Define Vision/Scope • Identify users/stakeholders: classes, reps, decision makers • Select elicitation techniques • Identify, prioritize and develop use cases • Some modeling here (e.g. user interfaces) • Includes business rules

6. Process (Iterative!) • Specify quality attributes • Derive/create requirements specification • Including external interfaces? Constraints? • Model • Review • Prototype

7. Process (Iterative!) • Develop/evolve Architecture • Allocate requirements to (software) components • Develop test cases • Validate

8. Agenda • Revisit the requirements development cycle • Revisit the requirements development process • Vision and Scope • <Clinic Name> Exercise

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

10. <Clinic Name> Vision and Scope Product Vision Scope forBusiness Area 1 Scope forBusiness Area 2 And so on… These might be different releases

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

12. Documenting Scope • Features • Key Stakeholders • Operating Environment • Use Case Diagram

13. Scope: Features • 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. Scope: Stakeholders • Key Stakeholders • Who needs to be part of the development? • Who will use the system and how?

15. Scope: Operating Environment • Operating Environment • Physical environment • Distribution? • Locations? • Availability/Performance/Integrity requirements

16. Agenda • Revisit the requirements development cycle • Revisit the requirements development process • Vision and Scope • <Clinic Name> Exercise

17. Exercise: Part 1 • In Your Group • Create a vision statement for the entire <Clinic Name> system

18. Exercise: Part 2 In Your Group • Identify the Business Areas of the <Clinic Name> that must interface with each other and decide how

19. Exercise: Part 2 • Define initial scope for each business area within <Clinic Name> • Create a description of major system features • If you finish then: • Identify key stakeholders • Define operating environment