We can breakdown a requirement into two principal types like Functional and Non-functional requirements.
For all the technology projects, functional and non-functional requirements must be segregated and separately analyzed.
To define the proper tool and an appropriate technique might be a daunting challenge. Whether you are doing a brand-new application or making change to an existing application. Considering the right technique for the functional process is an art by itself.
An overview of the widely-used business analysis techniques which are currently in the market −
|Processes||Techniques||Process Deliverables (Outcomes)|
|To Determine Functional and Non-Functional Requirements||● JAD Sessions● Scenarios and Use-cases● Organizational Modeling● Scope Modeling● Functional Decomposition● Interviews● Observation (Job Shadowing)● Focus Groups● Acceptance and Evaluation● Sequence Diagrams● User Stories● Brainstorming● Storyboarding● Prototyping● Structured Walk-through● Event Analysis● Business Rule analysis● Requirements Workshops● Risk Analysis● Root Cause Analysis||Business Requirements Documents −● Business and Functional Requirements● Non-Functional Requirements● Business Rules● Requirements Traceability MatrixCommon Template −● Business Requirements Document|
Although there are a variety of tools and procedures available to business analysts, it all depends upon the current practices of the organization and how they would like to use it.
For example, root-cause analysis is used when there is a requirement to go deeper into a certain important area or function.
However, business requirements document is the most popular and accepted way to put the requirements in documentation format.