Chapter 5 Requirements Life Cycle Management - Business Analysis

                                        Chapter 5


1) TRACE REQUIREMENT  -  analyzes and maintains the relationships between requirements, designs, solution components, and other work products for impact analysis, coverage, and allocation.
    PURPOSE - the purpose of trace requirement is to ensure the designs and requirements at different levels are aligned to one another.
   TECHNIQUES -  Business Rules Analysis
                                Functional Decomposition
                                Process Modelling
                                Scope Modelling

2) MAINTAIN REQUIREMENT -  ensures that requirements and designs are current  and efficient throughout the life cycle and facilitates reuse where appropriate.
    PURPOSE - it maintains the consistency and accuracy of the requirement throughout the life cycle.
    TECHNIQUES -  Business Rules Analysis
                                 Data Flow Diagrams
                                 Data Modelling
                                 Document Analysis
                                 Functional Decomposition

3) PRIORITIZE REQUIREMENT - it ensure the value, risk associated with particular requirement and design to analyse it.
    PURPOSE - its purpose is on the basis of relative importance it prioritize the requirements.
    TECHNIQUES -  Backlog Management
                                 Business Cases
                                 Decision Analysis
                                 Risk Analysis and Management
                                 Workshops

4) ASSESS REQUIREMENT CHANGES - it generates the new and update or change requirements according to the scope.
    PURPOSE - it evaluates the implications of proposed changes to requirements and designs.
    TECHNIQUES - Backlog Management
                                 Business Cases
                                 Decision Analysis
                                 Risk Analysis and Management
                                 Workshops

5) APPROVE REQUIREMENT -  involved in the governance process to reach  the approval and agreement on requirement and design.
    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.
   TECHNIQUES - Acceptance and Evaluation Criteria
                               Decision Analysis
                               Item Tracking
                               Reviews
                               Workshops


Comments

  1. Kirandeep Kaur30 January 2020 at 17:56

    In Maintain requirement helps in maintaining the accuracy as well as reuse of requirements in the life cycle. So, it must remains valid overtime. To get more benefits of this, you should represents maintaining and reusing requirements consistently. Also, reviewed and approved these by using a standardized process for the maintenance. These requirements should be easily accessible and understandable. Business Analysts should also maintain the relationships between the requirements.

    ReplyDelete
  2. Kerone Barnett30 January 2020 at 19:29

    This week’s chapter focuses on Requirements Life Cycle Management. Having better understood the terminologies for this process, I decided to research how we can support the life cycle of a project using available technology.

    Using the right software or tools to support Life Cycle Management is prudent for Project Management. These tools help all stakeholders to track, test, and visualize the project from one phase to the next. According to www.thedigitalprojectmanager.com, “Requirements management tools are any tools that help you remove ambiguity—assumptions, wishful thinking, grey areas, interpretations—from a project’s requirements. As such, the end goal of requirements management (RM) is to operate with clear, realistic, and agreed-upon requirements.” These requirements software tools must serve as a reference point for documentation of the project’s requirements and implementation and serve as a guide for stakeholder expectations at the end of the project.

    There are several options for software support on the market. The deciding factor for any Project Manager will be what is required to support the project at hand. This decision will entail considerations such as how the tool facilitates communication and collaboration between stakeholders, how the tool integrates with existing working software, how the tool provides visual modelling for stakeholders (use of graphics, reports etc.) and ultimately how the tool supports tracing requirements and real time impact analyses to allow for relationships to be established, tests to be done and risks to be mitigated, where possible, throughout the project’s life cycle.

    ReplyDelete
  3. Sukhpreet Singh30 January 2020 at 21:06

    Requirement life cycle management refers to the process which begins with the representations of a business needs and it continues for finding them solutions. It proceeds further and ends when all the solutions and the requirements are met. The tasks which are involved in this cycle are: Trace requirements: - designed to check that all the tasks toward change are aligned
    Maintain requirements: -designed to record all the tasks and to check the accuracy of the cycle.
    Prioritize requirements: - designed to rank the needs and their solution to be put in action.
    Assess requirements change: - designed to analyze the results of the changes due to requirements. Approve requirements: -designed to get the approval of the requirements for the changes.

    ReplyDelete

Post a Comment

Popular posts from this blog

Chapter 7 – Business Requirements Gathering

Chapter 7 –  Understanding the Real Problem This chapter focuses on the Business Analyst “thinking above the line” and focusing on the true essence of the business. This requires reviewing the Brown Cow Model – that is looking at the area above the line – the “ What Now ”. This section examines the undiluted and core reason for the business’ existence. The next step would be to look at the future of the business, called the “Future What”. Examining these two areas helps the Business Analyst get to the heart of the business problem, rather than focus on possible solutions. With the right focus the Business Analyst is not distracted by what others may think the solution could be, but the BA delves and trawls through as much information as possible to accurately understand the business and how it functions, minus technology or automation. This determination to channel all efforts towards the core purpose of the business allows the BA to be more open to all possible solutions...
Read more

Chapter 3 - Business Requirements Gathering

Chapter 3 - Scoping the Business Problem This chapter focuses on Project Blastoff Deliverables such as Project Purpose, Scope of work, Stakeholders, Constraints, Names, Estimated Cost and Risks. The chapter refers to Scope, Stakeholders and Purpose as the Trinity confirming that these are core elements of any successful project blastoff. ·          For Project Scope, we must understand the extent of the work to be done and how this task (business improvement) will impact the current operational environment and its existing products and services. We must ensure that we accurately document the depth and breadth of the project. ·          For Project Purpose, we must accurately capture the quantifiable/ measurable business benefit to be gained from the completion of the project. ·          For Stakeholders, we must document all possible persons with a vest...
Read more

Chapter 4 - BUSINESS USE CASES

Business use cases  -Business events are useful to partition the work, but it is the work’s response to the  event that now captures the interest of the requirements analyst. For every business event, there is a preplanned response to it, known as a business use case (BUC). Rabbit Projects - it is important to have a rock-solid grasp of the business problem to be solved. Rabbits make use of business use cases to explore their problem domain before starting to formulate a solution. This approach does not add to the documentation load, and it lessens the time spent delivering inappropriate solutions. Horse Projects - Horse projects are more strategic than rabbits. they need more time to complete. There is also the possibility of using Business use case scenarios as the documentation to pass along to the developers. Elephant Projects - elephant projects have a large number of stakeholders, clear communication is both important and difficult. Business ...
Read more