BABOK-3---Requirements-life-cycle-management

1. Requirements lifecycle Management IIBA BABOK v3

2. Requirements Life cycle Management • RLCM refers to the activities associated with complete life cycle of requirements, from inception to the retirement. • Requirements lifecycle management: • begins with the representation of a business need as a requirement, • continues through the development of a solution, and • ends when a solution and the requirements that represent it are retired

3. Requirements Life cycle Management

4. Requirements Life cycle Management BABOK v3 Book

5. 5.1 Trace Requirements • Tracing of requirements is conducted for the following reasons: • to ensure that requirements and designs at different levels are aligned to one another • to manage the effects of change to one level on related requirements. • To achieve the objectives of this task, we need: • To maintain forward traceability • To maintain the backward traceability • To maintain the relationships amongst requirements • Requirements Lifecycle is different from software development lifecycle

6. 5.1 Trace Requirements Elements Techniques Level of Formality Business Rules Analysis Relationships Functional Decomposition Traceability Repository Process Modelling Scope Modelling

7. Traceability Relationships • A number of relationships can be considered for managing the traceability . • These relationships are as follows: • Derive: When a requirement is derived (or gets generated) from the other. It’s a parent-child relationship. • Depends: When a requirement is dependent on the other for its completion. Depends has two types of association: • Necessity: When completion of one requirement is required only if other one is done. • Effort: When implementation of one req. makes it easier to implement other, effort wise.

8. Traceability Relationships • The requirements are associated with each other in the following ways • Satisfy: When one requirement is going to be fulfilled using another element, not necessarily a requirement. E.g. A login screen can fulfil the requirement of “allowing authorized login into the system”. • Validate: A relationship for showing how it’s going to be validated? E.g. a test case is associated with a requirement and it can be used to validate the requirement.

9. 5.2 Maintain Requirements • The purpose of this task is to keep the requirements well maintained. • This task may involve • To retain accuracy of requirements • To retain consistency of requirements throughout the lifecycle, with or without changes • To support re-use of requirements in other solutions

10. 5.2 Maintain Requirements Elements Techniques Business Rules Analysis Maintain Requirements Functional Decomposition Maintain Attributes Process Modelling Reusing Requirements Data Flow Diagrams Data Modelling Use case & Scenarios User Stories Requirements Traceability Table

11. Forward traceability • Alignment of requirements with design elements, test cases etc. • Used to validate implementation of every requirement in the software application • Artefact used to maintain the forward traceability – Requirements traceability table (RTT) or Backlogs

12. Backward traceability • Ensuring that every solution and testing element is created to meet a requirement • For example, each test case must get mapped to one or more requirements • Artefact used to maintain the forward traceability –Requirements traceability table (RTT) or Backlogs

13. Section Quiz

14. Quiz #1 • Which one is not achieved through the task “Tracing of requirements? • more reliable discovery of inconsistencies and gaps in requirements • faster and simpler impact analysis • Status of completion of requirements • Estimation of each task to track its completion status

15. Quiz #2 • Which of the following does not represent requirement life cycle management? • Waterfall Model • Setting up relationship amongst requirements • Maintaining the status of each requirement

16. Requirement Traceability Table (RTT) • One of the techniques to trace requirements is Requirement Traceability Table (RTT) • RTT captures the following along with their relationships: • Requirements • Priority • Relationship amongst requirements • Design • Coding Unit • Test Cases • UAT test cases etc.

17. RTT Snapshot

18. Requirement Traceability Table

19. Requirements Baselining • Baseline A reviewed, approved, and agreed-upon set of requirements committed to a specific product release. • Once the baseline has been established, new requirements can be more easily identified and managed. • A request for a new requirement can be compared against the existing baseline to see where it will fit in and whether it will create a conflict with any other requirements.

20. Baselining & Version Management Requirement Sign-off Version 1.0 Impact Analysis Customers Asks for Changes Changed Requirements Version 1.1 Requirements Added/Deleted Updated Requirements Version 1.2

21. Version Management Software • Efficient way of managing versions and maintaining requirements (or any other artefact) is a version management software • Commercial and open source software are available • Team Foundation Server (Microsoft), SVN, CVS, GIT etc

22. 5.3 Prioritize Requirements • The purpose of this task is to categorize requirements in the order of delivery priority. • Stakeholders are the primary source of prioritization. • Technique 10.33 in BABOK Guide

23. 5.3 Prioritize Requirements Techniques Elements Backlog Management Business Cases Decision Analysis Basis of prioritization Estimation Challenges of prioritization Financial Analysis Continual prioritization Interviews Item Tracking Prioritization Risk Analysis & Mgmt Workshops

24. Basis of Prioritization • Benefits to stakeholders • Penalty for not implementing requirements • Cost (Cost-benefit analysis) • Risk (Not able to deliver anticipated value, technology risk) • Requirements dependencies • Time Sensitivity (When is to be delivered, the best time) • Stability • Regulatory or other compliances resulting in penalty

25. Prioritization Techniques • MoSCoW technique • Ranking Technique • Kano Analysis • Voting Technique • Hundred Dollar Method • Analytic Hierarchy Method (AHD) • Prioritization Based on Value, Cost, and Risk & Many more…..

26. MoSCoW Prioritization Matrix • Must Have: The requirement is essential, key stakeholder needs will not be satisfied if this requirement is not delivered • Should Have: Important requirement but work around is possible • Could Have: This is a ‘nice to have’ requirement; • Won't Have: The full name of this category is ‘Would like to have but Won’t Have during this version’;

27. Voting/Ranking/Grouping • Requirements are grouped and categorized as high, medium and low or assigned numeric value from 1 to 10 • Simple to use and implement technique • Suitable for small group of stakeholders with clarity on business priorities

28. Challenges of Prioritization • Challenges associated with prioritization • Stakeholders individually may have differing priorities and business priorities are overlooked • Stakeholders can’t decide because of ego clashes • Every requirement is high priority • Large number of stakeholders

29. Section Quiz

30. Quiz #1 • Why it’s important to prepare a list of prioritized requirements during requirements development phase • It’s part of the requirements development phase • Customer stakeholders have conflicting requirements • It helps in managing cost, schedule & resources constraints • None of these

31. Quiz #2 • Select the best options for the provided information. You need to answer the question – top challenges in prioritization of requirements? A. Stakeholder’s conflicting Requirements B. Budget C. Quality D. Domain E. Technology • A, B & D • A, B & C • A & B • All of these

32. 5.4 Assess Requirements Changes • The purpose of this task is to evaluate the impact of proposed changes to the requirements and designs • Also known as Impact Analysis

33. 5.4 Assess Requirements Change Techniques Elements Business Cases Impact Analysis Parameters Business Rule Analysis Assessment Formality Decision Analysis Impact Analysis Document Analysis Impact Resolution Estimation Financial Analysis Interface Analysis Cost Benefit Interviews Schedule Impact Item Tracking Urgency Risk Analysis & Mgmt Workshops

34. Change Request Form Change Request Log

35. 5.5 Approve Requirements • Purpose of this task is to obtain agreement on the requirements to proceed further • Approval can be formal or informal • In Agile methodologies, the approval of requirements is collaborative and can be managed during the iteration review meetings or backlog grooming meetings • Use of various techniques is common to seek approval like demonstrations, prototyping etc

36. 5.5 Approve Requirements Techniques Elements Acceptance & evaluation criteria Understand Stakeholders Roles Decision Analysis Conflict & Issue Management Item Tracking Gain Consensus Reviews Track & Communicate approval Workshops

37. Case Study BABOK Knowledge Areas Requirements Life Cycle Management

38. Mobile Banking System • How will the requirements Traceability Table look like for Mobile Banking System? • How do we conduct impact Analysis for the following change: • Include contact number and Email ID for every Payee • Add the ability to schedule the Payment at a later date

39. Mobile Banking System • Requirements Traceability Table for MBS • Assessing Requirements Change • Is an alternative available? Is it a change or a defect? • Is it an independent requirement or it affects other requirements? • What will be the effect? Will those screen(s) will also change? • What’s the overall effort estimation and cost? How much time will it take?

40. THANKS! Any questions? You can contact us at info@techcanvass.com 022-40155 175 7738 7731 08 www.techcanvass.com