Skip to main content

Chapter-5 Requirements Life Cycle Management.

Requirement Life Cycle Management.

The knowledge area which depicts the jobs that B.A's undertook in order to manage, organize and maintain requirements and designs information from inception to retirement.

These jobs maintains meaningful relationships between connected requirements and designs.

The purpose of Requirement Life Cycle Management is to make sure that the business, stakeholder, and solution requirements and designs aligned to each other and that the solution implements them. It also helps to ensure that business analysis is available for future use. 

The Requirements Life Cycle:


  • Starts with representation of a business need as a requirement.
  • Continue through the development of a solution.
  • Ends when a solution and the requirements that represent it are retired.
The management of requirements does not end once a solution is implemented. Throughout the life of a solution, requirements continue to provide importance when they are managed appropriately also requirements may be in multiple states at one time.
The Requirements Life Cycle Management knowledge areas include following tasks:

Trace Requirements: analyzes and maintains the relationships between
requirements, designs, solution components, and other work products for
impact analysis, coverage, and allocation.

• Maintain Requirements: make sure that requirements and designs are
accurate and current throughout the life cycle and facilitates reuse where
needed.

• Prioritize Requirements: assesses the value, urgency, and risks associated
with particular requirements and designs to ensure that analysis and/or
delivery work is done on the most important ones at any given time.

• Assess Requirements Changes: evaluates new and changing stakeholder
requirements to determine if they need to be acted on within the scope of a
change.

• Approve Requirements: works with stakeholders involved in the
governance process to reach approval and agreement on requirements and
designs.

Core Concepts Model in Requirements Life Cycle Management



Trace Requirements

Purpose: The purpose of Trace Requirements is to make sure that needs and designs at different levels are aligned to each other, and to manage the effects of change to one level on related requirements.

Description: Requirements tractability identifies and documents the lineage of each
requirement, including its backward tractability, its forward tractability, and its
relationship to other requirements.

Trace ability enables:
• Faster and simpler impact analysis.
• More dependable discovery of inconsistencies and gaps in needs.
• Deeper insights into the scope and complexity of a change. 
• Reliable assessment of which needs have been addressed and which
have not.

Labels:

Comments

  1. AMANPREET KAURFebruary 4, 2020 at 8:55 PM

    Requirement life-cycle involves many phases and sometimes times it is really complicated process. Each phase have different requirements. However, with the BABOK and the content above has really made it helpful to understand what a Business Analyst needs to do for Requirement life-cycle management and how the process can be traced.

    ReplyDelete
  2. Gurvinder SinghFebruary 4, 2020 at 9:00 PM

    Life cycle management is a business management approach that can be used by all types of small and big businesses to improve their sustainability performance. Its purpose is to ensure more sustainable value chain management. LCM is useful for the organisation to target, organize, analyze and manage product-related information and activity.

    ReplyDelete
  3. Mir MD Abir ShafayetFebruary 24, 2020 at 1:48 PM

    Requirement life-cycle represent a business need according to requirement, as well as it helps through the development of a solution. Requirement life cycle management works through Trace requirement, maintain requirement, prioritize requirement, assess requirements changes and approve requirements.

    ReplyDelete

Post a Comment

Popular posts from this blog

Chapter 4 - Elicitation and Collaboration

 Elicitation and Collaboration Elicitation with the engagement of stakeholders are the tasks that Business Analysts perform to get information from stakeholders or other sources and confirm the results obtained. Elicitation and collaboration is never a 'phase' in Business analysis, rather it goes on until the Business Analyst finishes his/her work. Elicitation and collaboration can be planned, unplanned, or both. The Elicitation and Collaboration knowledge area is composed of the following tasks: • Prepare for Elicitation • Conduct Elicitation • Confirm Elicitation Results • Communicate Business Analysis Information  • Manage Stakeholder Collaboration The Core Concept Model in Elicitation and Collaboration: Prepare for Elicitation: This task involves clarifying the scope of the selected elicitation techniques, collecting the required information and making schedules.  Business analysts prepare for elicitation by defining the desired ...
3 comments
Read more

Chapter 1- Introduction to Business Analysis

Purpose of B.A.BOK ? The original purpose of BABOK Guide is to define the working of Business Analysis and provides  a collection of commonly accepted practices. It helps a business analyst define and discuss the required skills important to perform business analysis work. It also helps to understand the people who work with business analyst to know the skill set required by the person they are hiring. This guide is a common structure for all perspective, defining B.A. tasks that are conducted to properly analyze a change or evaluate the required for a change. Six knowledge areas of BABOK Business Analysis Planning and Monitoring : It is start the process of project with analyzing the information without the concern about ending the project. Elicitation and Collaboration: It is practice of research and discovering the requirement from users customers and stakeholders. Requirements life-cycle management : In order to manage and maintain requirements and design inf...
4 comments
Read more

Chapter 6 - Strategy Analysis

Strategy Analysis Strategy is a  plan of action or policy that deigned to work in the most effective way to apply the capabilities of an enterprise in order to reach a desire set of goals and objectives. On the other hand, strategy analysis refers to the process of conducting research on a company and its environment to formulate a strategy  that  must be performed to collaborate with stakeholders in order to identify a need of  strategic or tactical importance (the business need), enable the enterprise to  address that need, and align the resulting strategy for the change with higher and  lower-level strategies. The Strategy Analysis knowledge area includes the following tasks: • Analyze Current State :   C urrent state analysis  is a process management strategy that identifies and evaluates a business's current  processes and  understands the business need and how it relates  to the way the enterprise functions ...
3 comments
Read more