Chapter 5 - Requirement Life Cycle Management

The Requirements Life Cycle Management Area is defined as the tasks that a business analysts do to maintain order to manage requirements and design information from the start up to its conclusion.

And its purpose according to BABOK is, to ensure that business, stakeholder, and solution requirements and designs are aligned to one another and that solution implements them.

It will involve control over the desired requirements and how this requirement will be implemented to the solution on how it would be constructed and delivered.

Here are some steps of the requirements life cycle:

  • begins with the representation of a business to determine its needs as a requirement;
  • continues through the development of a solution, and
  • ends when a solution and the requirements that represent it are retired.

The Requirement Life Cycle Management knowledge area as defined by the table above includes this tasks according to BABOK Guide:
  • 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.

Sources used: 
  • BABOK Guide version 3
  • https://medium.com/swlh/managing-business-analysis-information-into-requirements-lifecycle-3254ee85ae96

Comments

  1. Harleen Virk2 October 2019 at 18:07

    TRACE REQUIREMENT:
    The cause of Trace Requirements is to ensure that necessities and designs at extraordinary stages are aligned to each other, and to manage the results of trade to at least one degree on associated necessities.

    Traceability allows:

    • Quicker and simpler impact analysis.
    • Extra dependable discovery of inconsistencies and gaps in requirements.
    • Deeper insights into the scope and complexity of an alternate.
    • Reliable assessment of which requirements were addressed and that have no longer.

    It is regularly hard to appropriately represent desires and answers without deliberating the relationships that exist between them. While traceability is valuable, the business analyst balances the number of relationship types with the benefit received through representing them. Traceability also supports each requirements allocation and release planning via supplying an immediate line of sight from requirement to expressed want.

    ReplyDelete
  2. Parminder Singh2 October 2019 at 18:21

    There are situations in which requirements can be reused.
    Requirements that are candidates for long-term use by the organization are identified, clearly named, defined, and stored in a manner that makes them easily retrievable by other stakeholders.
    Depending on the level of abstraction and intended need being addressed, requirements can be reused:

    • Within the current initiative
    • Within similar initiatives
    • Within similar departments
    • Throughout the entire organization.

    Requirements at high levels of abstraction may be written with limited reference to specific solutions. Requirements that are represented in a general manner, without direct ties to a particular tool or organizational structure, tend to be more reusable. These requirements are also less subject to revision during a change. As requirements are expressed in more detail, they become more tightly associated with a specific solution or solution option. Specific references to applications or departments limit the reuse of requirements and designs across an organization. Requirements that are intended for reuse reflect the current state of the organization. Stakeholders validate the proposed requirements for reuse before they can be accepted into a change
    Resources: BABOK_guide book from page number- 95

    ReplyDelete
  3. Mariane7 October 2019 at 15:13

    Currently in Great-West Life there is a position open for Business Systems Analyst.

    Among the role requirements, the function specifies: "Expertise in creating business process maps, end to end process steps and Business Requirements Documentation".

    The job role also states that two of the responsibilities will be:
    • Create detailed Process Definition and Requirements Documentation that is required for Developer to build an automated solution which includes alternate process scenarios and expected outcomes
    • Validate the automated activities with SME’s during Verification and User Acceptance Testing to ensure the automated solution has met the requirements

    Source: https://gwlcareers-greatwestlife.icims.com/jobs/18336/business-systems-analyst/job
    Accessed on: Sept. 07, 2019

    ReplyDelete

Post a Comment

Popular posts from this blog

Chapter 1 - What is Business Analysis?

Hello! Welcome to our Business Analysis blog.  We are Mariane, Harleen, Kent and Parminder, and we are Business Technology Management students at Red River College.  Throughout our Fall term we will be using this blog to share some important concepts regarding Business Analysis.  For our first post, we will start with the basics, and define exactly what is Business Analysis, and other important concepts related to it. According to BABOK, " Business analysis is the practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders. Business analysis enables an enterprise to articulate needs and the rationale for change, and to design and describe solutions that can deliver value. "  Business analysis cannot work without having a representative to intermediate these practices within an enterprise. This professional is called a Business Analyst who is responsible for putting in practice the tasks desc...
Read more

Chapter-12 Fit Criteria and Rationale

Image
FORMALITY GUIDE Horse ventures need to have an exact and effectively shareable comprehension of the significance of necessities. It has been our experience that when the task has numerous partners—which is the standard for horse ventures—various partners relegate various implications to prerequisites. Including a reason and a fit basis to every necessity implies it is for all intents and purposes inconceivable for errors to happen. We prescribe that pony ventures incorporate both of these in their necessities. Elephant ventures must utilize methods of reasoning and fit criteria. These tasks are compelled to deliver a composed determination to be given on to some other gathering, either another piece of the association or an outsourcer. Having a detail containing just unambiguous, testable necessities is pivotal to elephant ventures on the off chance that the other party is to comprehend and, at that point convey the right item Scale of Measurement Any prerequisite can be ...
Read more

Chapter 5 - Investigating the Work

The starting point for any product that will be built is the owner's work.  The book mentions that business analysts go "trawling" after business requirements.  The first task in the business requirements gathering process is to understand and investigate the work that is being done. Once that's understood, then the "essence needs to be understood, that is the clean picture of the business, without technology.  In this chapter the "Brown Cow Model" is also introduced. Which is divided into 4 parts:  How-Now: shows the implementation of the work as it currently exists, including physical artifacts, people and processors to do the work.   What-Now: shows the real business policy (essence). No machines, people, or organizational departments. Future-What: shows the business as your owner wants to have it, but still with no technology applies to it. Future-How: shows the idealized future business policy, augmented with the technology and people ...
Read more