1. Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis

2. What is Requirements Analysis? A Knowledge Area that describes the tasks and techniques used by a business analyst to analyze stated requirements in order to define what is required.

3. Requirements Analysis Tasks Prioritize Organize Specify and Model Define Assumptions and Constraints Verify Validate

4. What is Prioritization? A decision process used to determine the relative importance of requirements

5. Why Prioritize? To ensure that analysis and implementation efforts focus on the most critical requirements first

6. How to decide on Priority? Evaluate the business value Business or Technical Risk Implementation Difficulty * Likelihood of Success Regulatory or Policy Compliance Relationship to Other Requirements Stakeholder Agreement * Urgency

7. Techniques Decision Analysis Risk Analysis MoSCoW Analysis Timeboxing/Budgeting Voting

8. Output A prioritized requirement with an attribute that describes its relative importance to stakeholders and the organization

9. Requirements Analysis Tasks Prioritize Organize Specify and Model Define Assumptions and Constraints Verify Validate

10. What is Organization? Present requirements in structured views in order to...

11. Why Organize? Show: Different stakeholder perspectives Analyst and stakeholders where to find a specific requirement Interrelationships and dependencies between requirements

12. How to Organize? Who needs what? What as opposed to How?

13. Example Techniques Business Rules Process and Data Diagrams Functional Break down Use Cases

14. Output Structured requirements and documentation of the relationships between them

15. Requirements Analysis Tasks Prioritize Organize Specify and Model Define Assumptions and Constraints Verify Validate

16. What is Specify and Model? Analyze expressed stakeholder desires and/or the current state of the organization using a combination of textual statements, matrices, and diagrams Models

17. Why Specify and Model? Analyze the functioning of an organization and provide insight into opportunities for improvement

18. How to Specify and Model? Statements Matrix Documentation Diagrams Capture Requirements Attributes

19. Techniques Including but not limited to: – Business Rules Analysis – Non-functional requirements analysis – State Diagrams – User Stories – Prototyping – Data Flow Diagrams – Data Modeling – Functional Decomposition – Sequence Diagrams

20. Output Analyzed, Specified Requirements Possibly models

21. Requirements Analysis Tasks Prioritize Organize Specify and Model Define Assumptions and Constraints Verify Validate

22. What are Assumptions and Constraints? Assumptions are factors believed to be true, but not yet confirmed. Constraints are restrictions or limitations on possible solutions.

23. Why Define Assumptions and Constraints? Identify factors other than requirements that may affect which solutions are feasible

24. How to Define Assumptions and Constraints? Document unconfirmed facts Business Constraints Technical Constraints

25. Techniques Problem Tracking Risk Analysis

26. Output monitoredupdated List of monitored and updated Assumptions and Constraints

27. Requirements Analysis Tasks Prioritize Organize Specify and Model Define Assumptions and Constraints Verify Validate

28. What is Verification? Final check by the business analyst and key stakeholders to determine that requirements: – Are ready for formal review and validation by customers and users – Provide all information needed for further work

29. Why Verify? To ensure that requirements have been defined correctly and are of acceptable quality

30. How to decide on Verification? Characteristics of Requirements Quality Verification Activities

31. Techniques Acceptance and Evaluation Criteria Problem Tracking Structured Walkthrough

32. Output Verified Requirements of sufficient quality to allow further work

33. Requirements Analysis Tasks Prioritize Organize Specify and Model Define Assumptions and Constraints Verify Validate

34. What is Validation? Ongoing Ongoing process to ensure that stakeholder, solution, and transition requirements align to business requirements

35. Why Validate? To ensure that all requirements support the delivery of value to the business, fulfill its goals and objectives, and meet a stakeholder need

36. How to decide on Validation? Identify Assumptions Define Measurable Evaluation Criteria Determine business value Evaluate Alignment with Business Need

37. Example Techniques Acceptance and Evaluation Criteria Definition Prototyping Structured Walkthrough

38. Output Validated Requirements demonstrated to deliver value to stakeholders and are aligned with the business goals and objectives

39. Requirements Analysis Tasks Prioritize Organize Specify and Model Define Assumptions and Constraints Verify Validate

40. I am done for today! Any Questions?