Chapter 5: Requirements Life Cycle Management

-

Chapter 5: Requirements Life Cycle Management

11.     Lifecycle of Requirement:
The lifecycle of specifications requires a variety of steps and can sometimes be a complicated process. The essence of the cycle relies on the approach you choose for designing the applications, such as Agile, Waterfall, Incremental, etc. Every step will involve a lot of documentation and procedure of approval. It also manages the project documentation such as a project proposal, project management schedule, project scope and the business case.
Below is one of the common requirement lifecycle:


12.    The Requirements Life Cycle Management:
In this knowledge area, duties of a business analyst when joining in a project are clearly explained. Tasks that a business analyst must conduct including taking responsibility of managing and maintain requirements, planning data from the commencement to retirement.

The aim of life cycle management specifications is to ensure that standards and plans for enterprise, customers, and strategies are compatible with each other, and that they are enforced by the solution.
Beside primary tasks such as:
Ø  Finding an association between related specifications and designs
Ø  Evaluating improvements to specifications and structures for proposed modifications
Ø  Analyzing and reaching agreement on innovation
, business analyst also performs some supporting tasks:
Ø  Tracking requirements and proposals
Ø  Guiding of how requirements are about to be executed in concrete resolution
Making sure that business analyst figures are feasible for future application
The Requirements Life Cycle Management knowledge area involves these tasks:


13.     How requirements are traced?


In this phase, a business analyst needs the input information and necessary tools and guidelines so that the requirements and designs are traced properly which satisfy the demands. 

14.    How requirements are maintained?

At the previous phase, business analysts have had the traced requirements and designed, now to this phase they need to use Information Management Approach to maintain the requirements so that they remain accurate and updated after an approved changed. 

15.     How to prioritize requirements?

The purpose of prioritizing requirements is to rank requirements in the order of relative importance which is an important step to ensure the maximum value is achieved. After requirements and designs are maintained, business analyst will start prioritizing the requirements and designs by using various of guidelines and tools.

16.     How to assess requirements change?

When new needs or possible solution are recognized, business analyst needs to perform the assess requirements. After assessing requirements change, business analyst will have the output of requirements change assessment and designs change assessment.

17.    How requirements are approved?

At this last phase, the requirements and designs must gain the agreement and approval so that business analysis work are able to be advanced or/and solution construction to be progressed.


Posted by Kim Le

Comments

  1. Shaina LuthraJanuary 30, 2020 at 7:49 PM

    Prioritization means ranking requirements to determine their relative importance to stakeholders. In other words, priority refers to the relative value of a requirement, or to the sequence in which it will be implemented. Prioritization is an ongoing process because priorities may change as the context evolves or as more information becomes available. Prioritization is a critical exercise that seeks to ensure that maximum value is achieved.

    ReplyDelete
  2. Balpreet SinghJanuary 30, 2020 at 8:08 PM

    Requirement management is a continuous process throughout the project and it includes documenting,analyzing,prioritizing and get agreed on requirement.It also include communication with internal and external stakeholders.The main aim of requirement management is to satisfy the stakeholders means providing services to them as per their needs. Requirement management initiates from the critical analysis of organization objects and constraints and in further stages it includes the planning for requirements and also combining the requirement and to handle the change resistance.

    ReplyDelete
  3. Navdeep Kaur SranJanuary 30, 2020 at 10:36 PM

    The requirements life cycle management in business analysis involves all the steps which range from tracing the requirements to approving them. In TD bank the business analysts, firstly focus on discovering the wants of customers which means that what do they expect from bank. In the next step, the collected input (in first step) is maintained and the changes are also updated in this stage. After this, the requirements of customers are prioritized depending upon their importance. In the final stage, the selected requirements of customers are met by introducing new policies in the banking procedures.

    ReplyDelete

Post a Comment

Popular posts from this blog

Chapter 8: Starting the Solution

-
Chapter 8: Starting the Solution Question 1. What is a persona and when is it used? Answer: A persona is a virtual character that represents a large number of customers (or users) with similar characteristics or demographics. Personas are constructed from data collected through surveys of your target audience and so represent most of your eventual users. It is important that you construct your persona with enough characteristics for you and your team to feel that they understand it well enough to know what it wants.  Personas are used when you have a large number of in-house users, or a large number of customers who will be using the product. The business analysts and designers use a persona as their source of user specific requirements. Question 2. What do you mean by "Designing the User Experience" ? Answer: Designing the whole of the user experience is the best way to come up with a product that makes people want to buy it and/or use it. Experience de...
Read more

Chapter 7 Understanding the right Problem

-
Image
Chapter 7 Understanding the right Problem Question 1. What the brown cow model does? Answer The brown cow model is all about the number of ways (viewpoints) in which we can look at the work area, when we are investigating work area. In brown cow model there are four quadrants namely- How Now, What Now, Future what, How Future.   How Now is the place to start in most of the times and it shows the implementation of the work as it currently exists. Which includes physical artifacts, people that are used to do the work.   What Now shows the real business policy or the essence of the work. Future What shows the business as your owner want to have it in the future but still with technical neutrality that being used to implement that business. Future How shows the future business policy with the use of technology that being used to implement it. Question 2.   What are persons and how it is useful? Answer ...
Read more

CHAPTER 12: FIT CRITERIA AND RATIONALE

-
CHAPTER 12: FIT CRITERIA AND RATIONALE What are fit criteria and the rationale of a requirement? There are some differences between the fit criteria of functional and non-functional requirements. The fit criteria of functional requirements determine how business analysts will realize that the product has effectively accomplished that activity. For functional requirements, it is hardly possible to decide the scales of measurement: The action is either finished or not finished. Completion relies upon satisfying an authority that the product has correctly performed the action. The authority mentioned can be the source of the information or the nearby system that commenced the action. Business analysts can write functional requirements for various types of action. The fit criteria of non-functional requirements is a measure of those qualities such as usability, look and feel, performance, operational, and so on. In the first place, some of the nonfunctional requirements may appear ...
Read more