Organising Requirements

#businessanalysis Once you have prioritised Requirements the Business Analyst will need to organise them. The output of this work will be a set of views of the Requirements. These views will be used to both enable work going forward as well as help communicate the requirements to the IIBA Stakeholders.

The two key objectives when organising requirements are;

Understand which models are appropriate for the business domains and solution scope.
Identify model interrelationships and dependencies. Requirements alone are not complex; it is the relationships and interdependencies among requirements that adds the element of complexity. Therefore, the organised requirements must also clearly depict the inherent relationships between requirements. ^[A Guide to the Business Analysis Body of Knowledge® (BABOK ( PDFDrive ).pdf]

1. Ensure you have the required Inputs

each project (or business analysis domain) will have specific information and documentation a Business Analyst needs to effectively Prioritise the Requirements. To effectively organise Requirements you will need to understand the Inputs for organising requirements

Organisational process assets
Requirements
Solution scope

Understand the key concepts and process

To deliver key documentation consistently and at a high level. Following the bellow guidelines you will be able to ensure effective delivery.

Follow to guidelines or documentation set out be the organisation. If none exsist you will have to go through a decision process to decide on Techniques used to organise requirements.
KISS! Use simple and most importantly consistent definitions of Requirements. Try to always use language which is common in the organisation.
Keep consistent documentation of dependencies and interrelationships. Map and model as much as possible. This will help you when you need to justify your decisions to IIBA Stakeholders.
If you do use models keep them consistent to avoid any underlying issues in model transfer.

The Business Analyst will also need to

Levels of abstraction
Model Selection
- user classes profiles or roles
- concepts and relationships
- Events
- Processes
- Reles

4. Acknowledge the techniques you’ll need to Organise requirements

There are many techniques used by business analysts. By having a broad understanding of the tasks and skills a Business Analyst needs you will better be able to achieve your goals.

Specific to prioritisation you will need to understand the Techniques used to organise requirements. These break down into;

Business Rules Analysis
Data flow diagrams
data modeling
functional decomposition
organisation modeling
process modeling

5. Understand the IIBA Stakeholders you may have to deal with

Domain SME
Implementation SME
End User
Sponsor

5. Deliver Outputs