Requirements Life Cycle Management

The Core Concept Model in Requirements Life Cycle
Management
• Trace Requirements: analyzes and maintains the relationships between requirements, designs, solution components, and other work products for impact analysis, coverage, and allocation.

Description:
Trace-ability is used to help ensure that the solution conforms to requirements and to assist in scope, change, risk, time, cost, and communication management. It is also used to detect missing functionality. For IBM traceability enables:
-Fast work
-discover gaps
-assessment of requirements
-the complexity of a change
     
Traceability process:-

Elements required for Traceability:-
-Inputs
-Elements
-Guidelines and tools
-Techniques
-Stakeholders
-Outputs

• Maintain Requirements: ensures that requirements and designs are
accurate and current throughout the life cycle and facilitates reuse where
appropriate. In order to maximize the benefits of maintaining and reusing requirements the requirements should be: consistently represented, approved for maintenance, easily accessible, understandable, standardized process.
IBM Storage maintenance services are:

• Direct access to our level 3 engineers.
• Technical support calls to CDS Operation
• Guaranteed spares for all IBM Storage system delivered to your data center in less than 2 hours
• Proactive monitoring and preventative maintenance to ensure arrays drives and auto-loaders continue to function optimally preventing downtime and data loss.

Few techniques for maintenance:-
-Business rules analysis
-Data flow diagrams
-Data modeling
-Document analysis
-Functional decomposition
-Process modeling
-User stories

• 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. The main purpose of IBM for Prioritizing requirements is to rank requirements in order of their importance. There are three elements for prioritizing:-

• Basis for prioritizing:-Typical factors that influence prioritization include- the advantages that accrues as a result of requirements, the consequences that result from not implementing a given requirement in order to meet the policies imposed on the organization, the cost effort, and resources needed to implement the requirement, Risk of being technically unfeasible, dependencies may also occur which means when one requirement is cannot be fulfilled unless the other requirement is fulfilled, requirements that must be implemented in order to meet regulatory or policy demands imposed on the organization, which may take precedence over other stakeholder interest.

• Challenges of prioritizing:- Prioritization is an assessment of relative value. Each stakeholder may value something different. When this occurs, there may be conflict among stakeholders. Stakeholders may also have difficulty characterizing any requirement as a lower priority, and this may impact the ability to make necessary trade-offs

• Continual prioritizing:- Priorities may shift as the context evolves and as more information becomes available. Initially, prioritization is done at a higher level of abstraction. As the requirements are further refined, prioritization is done at a more granular level and will incorporate additional bases for prioritization as they become appropriate.

• Assess Requirements Changes: evaluates new and changing stakeholder requirements to determine if they need to be acted on within the scope of a change. The purpose of Assess Requirements Changes is to evaluate the implications of proposed changes to requirements and designs.

Proposed Change: can be identified at any time and impact any aspect of business analysis work or deliverable completed to date. There are many triggers for a proposed change including business strategy changes, stakeholders, legal requirements, or regulatory changes.
Designs: may need to be assessed to identify the impact of a proposed modification.
Requirements: may need to be assessed to identify the impact of a proposed modification.

• Approve Requirements: works with stakeholders involved in the governance process to reach approval and agreement on requirements and designs.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.