CHAPTER 5-Requirements Life Cycle Management
Requirements Life Cycle Management
What the
Requirements Life Cycle Management describes?
It is one of
the primary phases of the requirement gathering process commonly known as
Requirement extraction. Once the requirement is gathered, it can be organized
in folders logically as per requirements. These requirements are analyzed
further to prepare facts and figures for a business analyst to track possible
result based on analysis. This procedure is referred as Impact Assessment. It describes the tasks that business
analysts perform in order to manage and maintain requirements and design
information from inception to retirement.
This cycle
helps to maintain a meaningful relationship between related requirements and
designs, assessing changes and analyzing and gaining consensus on changes. The
purpose of this management is to ensure that business, stakeholder, and
solution requirements and designs are aligned to one another and that the
solution implements them. It involves a control over requirements and how these
requirements will be implemented in the actual solution to be constructed and
delivered. This management makes sure that business analysis information is
available to use in future.
How the
requirements life cycle management woks?
The requirements
life cycle: -
Ø
Begins
as a representation of business need as requirement
Ø
Continues
through the development of solution
Ø
Ends
when both solution and requirements are retired.
This management
does not end after the implementation of solution. Throughout the life of a solution,
requirements continue to provide value when they are managed appropriately.
Life cycle refers to the existence of various phases or states that
requirements pass through as part of any change. Requirements may be in
multiple states at one time. So, the solution is always implemented according
to the requirement.
What are the
main tasks in the knowledge area of The Requirements Life Cycle Management?
The
Requirements Life Cycle Management has five main tasks as described below: -
Ø
Trace
Requirements: - The management analyzes and maintains a meaningful relationship
between requirements, designs, solutions components, and some other products
including analysis, coverage and allocation.
Ø
Maintain Requirements: - It makes sure that
both the requirements and the designs are accurate and facilitates reuse when
needed.
Ø
Prioritize
Requirements: - It assesses the value, urgency, and risks associated with
particular requirements and designs to ensure that analysis and delivery work
is done on the most important ones at any given time.
Ø
Assess
Requirements Changes: - it works on analysing the changing stakeholder
requirements to determine if they need any change.
Ø
Approve
Requirements: - it works with the stakeholders to reach approval and agreement
on their designs and requirements.
This management
cycle also works in “Skip the Dishes”. In “Skip the Dishes”, they also have to
make changes according to the requirements. They even keep updating their app
every month in order to meet the requirements.
Elements: -
ReplyDelete* Gain Consensus
Business analysts are in charge of guaranteeing that the partners with endorsement
authority comprehend and acknowledge the necessities. Endorsement may affirm that
partners accept that adequate worth will be made for the association to
legitimize interest in an answer. Business analysts get endorsement by looking into the
necessities or changes to prerequisites with the responsible people or
gatherings and mentioning that they endorse, demonstrating their concurrence with the
arrangement or structures portrayed.
Utilizing the techniques and means built up in the undertakings Plan Business Analysis
Administration (p. 37) and Communicate Business Analysis Information (p. 67)
business analysts present the necessities to partners for endorsement. Business
analysts encourage this endorsement procedure by tending to any inquiries or giving
extra data when mentioned.
Complete understanding may not be vital for a fruitful change, yet in the event that there is
an absence of understanding, the related dangers are to be distinguished and overseen
appropriately. (BABOK, pg.97)
Prioritization in business
ReplyDeleteThe reason for Prioritize Requirements is to rank necessities in the request for relative significance. It is the basic step to determine the relative importance to stakeholders. It can refer to the relative value of a requirement, or to the sequence in which it will be implemented. Prioritization is an ongoing process, with priorities changing as the context changes.
Typical factors that influence prioritization include:
*Benefit,Penalty,Cost, Risk,Dependencies,Time Sensitivity,Stability and Regulatory or Policy Compliance.
Challenges of Prioritization
Stakeholders may likewise experience issues portraying any prerequisite as a lower need, and this may affect the capacity to make fundamental exchange offs. Also, stakeholders may (deliberately or accidentally) demonstrate need to impact the outcome to their ideal result.
Continual Prioritization
Firstly, prioritization is done at a higher level of abstraction As the essentials are furthermore refined, prioritization is done at a continuously granular level and will merge additional bases for prioritization as they become appropriate.
Access requirements changes
ReplyDeleteIt is a task taken under consideration when new expectations or demands are identified. This may or may not change the current the strategy and scope as the scope is dependent on the demands.
The potential impacts needs to be taken under consideration as the demands will have huge effect on the current process of the business. It should not side track the scope totally, hence accessing the requirement changes task needs to be done with care. Analyst also needs to take the opportunities, limitation and the risk with all the new changes made to the current strategy.
A mapping of all the changes in the current process will give a better picture on which aspects is the business will running ahead. The input/output diagram below will help the analyst where all changes can be made.
Some techniques to apply these changes effectively:
-Document analysis: Any existing documents that facilitates the understanding of the impact of certain changes.
-Interviews: The impact pf the changes needs to get opinion of the stakeholders in order to work upon with everyone's' consent.
-Risk analysis: To evaluate the risk which can be accrued by applying the changes needs to be done accurately.
-Item Tracking: To track any conflicts or issues discovered during the impact.
Th design of the new changes to be implemented should be have approval of all the stakeholders and resources should be available to start the new change in process.