Requirement Analysis is a sequential process in which we try to unfold the deep secrets. As a Business Analyst, your analytical skill is going to be your goodwill. Ideally a BA has to perform the requirement analysis, however the other team members can also support and contribute.

Before we start requirement analysis we must have the requirements handy either as BRD or any other template.

The sequence that I follow –

1. Functional Architecture Design
2. Integration Requirements
3. Functional Requirements
4. User Requirements
5. Report / Statement Requirements
6. Nonfunctional Requirements

Sometimes functional requirements are analyzed before integration requirements. Both ways are fine as long as we can keep a balance between the 6 areas of requirement analysis.

I will post seperate post on each areas.

The deliverables of Requirements Analysis is Functional Specification Document (FSD) or Functional Requirement Document (FRD). In addition we also produce –

• Use Case,
• Data Dictionary,
• Data Mapping,
• Activity Diagram,
• Sequence Diagram,
• Class Diagram etc.

We will later learn about Unified Modeling Language (UML) to understand more about the diagrams.

I will also suggest to go through http://mybatrainer.com/what-is-functional-knowledge-for-a-business-analyst/