VANCOUVER Chapter Study Group. BABOK Chapter 6 Requirements Analysis

Size: px
Start display at page:

Download "VANCOUVER Chapter Study Group. BABOK Chapter 6 Requirements Analysis"

Transcription

1 VANCOUVER Chapter Study Group BABOK Chapter 6 Requirements Analysis February 24, 2016 Hossam Saleh, CBAP

2 Introduction PD Hours Presentation and quizzes at IIBA Vancouver Chapter website Certification Update CBAP Location Jan-2016 Current Notes All BC Victoria and Burnaby CCBA Location Jan-2016 Current Notes All BC Victoria Hossam Saleh 2

3 Agenda Chapter 6 Requirements Analysis (one hour) 6 tasks Techniques Pop quiz Break Chapter 7 Solution Assessment & Validation (one hour) 5 tasks Techniques Pop quiz 3

4 Chapter 6 Requirements Analysis 5

5 Chapter 6 Requirements Analysis Tasks 1. Prioritize Requirements 2. Organize Requirements 3. Specify and Model Requirements 4. Define Assumptions & Constraints 5. Verify Requirements 6. Validate Requirements POMAVV ( Poam a Vee Vee ) 6

6 Requirements Analysis Input and Output Diagram 7

7 Intro (1/2) What criteria have you used to prioritize and organize requirements? In your organization, how do you decide which models to use when analyzing requirements? In your experience, what are the best models you have used for analyzing requirements? Please share your experience with requirement walk through. Why bother? 8

8 Intro (2/2) Analyze stated requirements to define the required capabilities of a potential solution that will fulfill stakeholder needs. Water fall vs. Agile how does requirement analysis differ? 9

9 6.1 Prioritize Requirements 10

10 6.1 Prioritize Requirements Basis for prioritization Business value Business or technical risks Challenges Non-negotiable demands Unrealistic trade offs Implementation difficulty Likelihood for success Regulatory or policy compliance Stakeholder agreement Relationship to other requirements Urgency 11

11 6.2 Organize Requirements 12

12 6.2 Organize Requirements 6.2 Elements Level of Abstraction What vs. how High-level vs. low level Methodology Model Selection (Model- simplify reality) Use classes, profiles or roles Concepts & relationships Events Processes Rules 13

13 6.3 Specify and model requirements 14

14 6.3 Specify and model requirements Elements Text Matrix documentations Models Modeling formats Notations Formal vs. informal models Capture requirements attributes Improvement opportunities 15

15 6.3 Specify and model requirements Improvement Opportunities Automate or simplify work people perform Improve access to information Reduce complexity of interfaces Increase consistency of behaviour Eliminate redundancy 16

16 6.3 Specify and model requirements Techniques Acceptance and evaluation criteria Business rules analysis Data dictionary and glossary Data flow diagram Functional decomposition Interface analysis Metrics and key performance indicators Non-functional requirements analysis Organization modeling Process modeling Prototyping Scenarios and use cases Sequence diagrams State diagrams User Stories 17

17 6.4 Define Assumptions & Constraints 18

18 6.4 Define Assumptions & Constraints Assumptions Anything believed to be true but not verified Source of potential project risk Business Constraints Budgetary, time, resource, skills, organizational limits Technical Constraints Architecture design, development language, hardware & software platforms, application limits Resource utilization, message size & timing, size of software, file records, data elements 19

19 6.4 Define Assumptions & Constraints Stakeholders Implementation SME Project Manager All stakeholders Techniques Problem tracking Risk analysis 20

20 6.5 Verify Requirements 21

21 6.5 Verify Requirements Elements Characteristics of requirements quality Cohesive Complete Consistent Correct Feasible Modifiable Unambiguous Testable 22

22 6.5 Verify Requirements Elements of Verifying Requirements Verification activities Check for completeness Compare requirements with others, updated consistently All variations of processes documented Triggers/outcomes Consistent terminology Use of examples 23

23 6.5 Verify Requirements Stakeholders All stakeholders Techniques General technique Acceptance and evaluation criteria Problem tracking Structured walk through Check list 24

24 6.6 Validate Requirements 25

25 6.6 Validate Requirements Elements Identify Assumptions Define Measurable Evaluation Criteria Determine Business Value Determine Dependencies for Benefits Realization Evaluate Alignment with business case and opportunity cost 26

26 6.6 Validate Requirements Elements Identify Assumptions Define Measurable Evaluation Criteria Determine Business Value Determine Dependencies for Benefits Realization Evaluate Alignment with business case and opportunity cost 27

27 6.6 Validate Requirements Stakeholders All stakeholders Techniques Acceptance and evaluation criteria Matrices and key performance indicators Prototyping Risk Analysis Structured Walkthrough 28

28 Requirements States Stated 3.3 Confirmed 3.4 Traced 4.2 Communicated 4.5 Approved Prioritized 6.1 Specified / Modeled Analyzed 6.3 Verified 6.5 Validated

29 Chapter 6 Requirements Analysis Pop Quiz 30