Requirement Life Cycle Management
The Requirements Life Cycle Management knowledge area describes the tasks
that business analysts perform in order to manage and maintain requirements
and design information from inception to retirement. These tasks describe
establishing meaningful relationships between related requirements and designs,
assessing changes to requirements and designs when changes are proposed, and
analyzing and gaining consensus on changes.
The requirements life cycle:
• 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.
------------------------------------------------------
---------------------------------------------------------
The Requirements Life Cycle Management knowledge area includes the 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: ensures that requirements and designs are
accurate and current throughout the life cycle and facilitates reuse where
appropriate.
• 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.
-----------------------------------------------------------
Elements :-
1. Level of Formality
2. Relationships
3. Traceability Repository
------------------------------------------------------------
Techniques :-
• Business Rules Analysis: used to trace business rules to requirements that
they support, or rules that support requirements.
• Functional Decomposition: used to break down solution scope into smaller
components for allocation, as well as to trace high-level concepts to low-level
concepts.
• Process Modelling: used to visually show the future state process, as well as
tracing requirements to the future state process.
• Scope Modelling: used to visually depict scope, as well as trace requirements
to the area of scope the requirement supports.
-------------------------------------------------------------
------------------------------------------------------------
When considering changes or additions to existing requirements, business
analysts assess the impact of the proposed change by considering:
• Benefit: the benefit that will be gained by accepting the change.
• Cost: the total cost to implement the change including the cost to make
the change, the cost of associated rework, and the opportunity costs such
as the number of other features that may need to be sacrificed or deferred
if the change is approved.
• Impact: the number of customers or business processes affected if the
change is accepted.
• Schedule: the impact to the existing delivery commitments if the change is
approved.
• Urgency: the level of importance including the factors which drive
necessity such as regulator or safety issues.
-------------------------------------------------------------
Approve Requirements
Purpose
The purpose of Approve Requirements is to obtain agreement on and approval of
requirements and designs for business analysis work to continue and/or solution
construction to proceed.
Description
Business analysts are responsible for ensuring clear communication of
requirements, designs, and other business analysis information to the key
stakeholders responsible for approving that information.
Unlike most companies, Microsoft has expanded the cycle. Where most have plan, execute, finish, Microsoft has it laid out in more detail. They start by initializing the process and getting permission to accept the project. Then they plan and receive the requirements from the client. Third, they begin the process of building the product. During this phase they also have regular stops to test and check if it still matches the original requirements. Finally, they evaluate their performance and find out if there is any parts of the job that could have been done better. This is the complete Microsoft cycle.
ReplyDeleteIt is one of the primary phases of the requirement gathering process commonly known as Requirement extraction.The requirement validation phase in microsoft includes analyzing the needs or conditions required to meet a new or altered product(Windows, Word, Excel Ppt, OneDrive) considering needs of the various stakeholders. In third phase they start to construct new product. In Microsoft, there are requirement validation tools that do validation with very less human intervention. Requirement Management process includes planning, monitoring, analyzing, communicating and managing of those requirements need in the organization.
ReplyDeleteIn the life cycle of management knowledge, there are various phases and complicated process. There are different tasks to do in life cycle management knowledge area such as trace requirements refers to maintain the designs as working in Microsoft. They can maintain requirements regarding the current life cycle of Microsoft company. In Microsoft, the person prioritise the requirements in which they assesses the risks with specific design to analyse the work done. Apart from it, they can assess the requirement change that indicates the changes in new and changing requirements according to need.
ReplyDelete