Requirements Analysis: Organize Requirements

A good requirements structure targets consistency, repeat ability and high levels of quality.

Inputs :

• Organizational Process Assets
• Stated Requirements
• Solution Scope

Tasks:

• Defining the level of abstraction or detail for your requirements
• Selecting appropriate modelling techniques
• User classes, profiles or roles
• Concepts and their relationships- Data modelling
• Events- Scope models, process models, state models and use cases
• Process- Use cases, organizational models, state diagrams
• Rules

Techniques:

• Business Rules Analysis
• Organizational Modelling
• State Diagrams
• Data Flow Diagrams
• Data Modelling
• Process Modelling
• Use Cases
• Functional Decomposition
• Scope modelling

Knowledge areas using the o/p (Requirements structure):

Prepare requirements package -- Req management and communication

Specify and model reqs-Req analysis

Other stakeholders:

• Domain SME
• Implementation SME
• Sponsor
• End user

Requirements Analysis -Prioritizing requirements

More about requirements analysis here http://vishiwrld.blogspot.in/2016/01/requirements-analysis-overview.html

The first task in requirements analysis is prioritizing the requirements.
Your requirements management plan should have already decided the basis on which the requirements will be prioritized.

Inputs to prioritize requirements:

• Business Case - Requirements should align with goals , objectives and success measures that are defined in project's business case.  --- Enterprise Analysis
• Business need-  If business case is not available then business need serves the purpose.--- Enterprise Analysis
• Requirements- 
• Stated , unconfirmed requirements , Confirmed requirements --- ( Post Elicitation)
• Allocated (Post Allocate Requirements) in Solution assessment and Validation
• Analyzed (Post Specify and Model Requirements), Prioritized (Post Prioritize requirements) , Validated (Post Validate Requirements), Verified (Post Verified Requirements)  from ---Requirements Analysis
• Approved Requirements (Manage Solution Scope and requirements), Communicated requirements (Communicate Requirements) , Maintained and reusable (Maintain requirements for reuse), traced requirements (manage requirements for traceability) from ---Requirements management and communication
• Requirements Management Plan   Plan Requirements management process BAPM
• Stakeholder list , roles and responsibilities  Conduct stakeholder analysis BAPM

Techniques:

• Decision analysis
• Risk Analysis
• MoSCoW Analysis
• Timeboxing/Budgeting Methodologies- All In, All out, Selective
• Voting

O/p(Prioritized Requirements)  used by:

• Assess proposed solution
• Allocate requirements
• Validate Solution
• Requirements Management and Communication Knowledge area

Tasks to consider:

• Basis on which the requirements are prioritized
• Considering challenges when felicitating prioritization

Requirements prioritization criteria:

Prioritization Criteria	Requirements are implemented first that
Business Value	Provide the most business Value
Business or Technical risk	Pose the highest risk for project success
Implementation difficulty	Easiest
Likelihood of success	Quick yields
Regulatory or policy compliance	addresses the issue
Relationship to other reqs	Support other high business reqs
Stakeholder agreement	Receive aagreement from many
Urgency	Most urgent

Other stakeholders:

• Domain SME
• Implementation SME
• Sponsor

Requirements Analysis-Overview

Requirements analysis takes your elicited requirements and gives them a proper shape.
The output of  requirements analysis are:

• Assumptions and constraints
• Requirements structure
• Prioritized stakeholder requirements
• Verified stakeholder requirements
• Validate stakeholder requirements

Techniques to specify and model requirements are:

• Acceptance and evaluation criteria definition
• Business Rules analysis
• Data Dictionary and Glossary
• Data flow diagrams
• Data modelling  -  http://www.agiledata.org/essays/dataModeling101.html
• Functional Decomposition
• Interface Analysis
• Metrics and key performance indicators
• Non functional requirements analysis
• Organizational Modelling
• Process Modelling
• Prototyping
• Scenarios and Usecases
• Sequence diagrams
• User stories

Task List:

• Prioritizing Requirements
• Organizing requirements
• Specifying and modelling requirements
• Defining assumptions and constraints
• Verifying requirements
• Validating requirements

We shall go through each of the items in the task list in separate posts.