Requirement Analysis

Requirement Analysis
Before getting in to the topic we need to know a few things about this requirement analysis.
What is requirement..?
What is analysis..?
Need to identify the stake holders..?
How to identify the requirements of the stake holder..?

 Basically the requirement is nothing but the need of an organization, where is can be carried out with a group of stake holders.
 After getting the requirements we need to analyze all the gathered information in a drill-down process.
 There will be a group of stakeholders from a respective company or organization, where we can get the exact requirements from a desired people only.
 We can gather the requirements from the stake holder through some elicitation technique,or some brain storming or through 5-why techniques.

What is requirement analysis..?
Gathering the requirements from the client and making drill down on each and every requirements in order to meet the organization expectation or stake holder expectation.
Requirement analysis is nothing but business requirements.
We will understand more about each of the above elements by elaborating them.
Understanding the requirements:-
Once after gathering all the requirements from the client side, they might not be understood properly and there is a possibility to missing some scenarios or information. so in order to gather all the missing information we will go for further meetings or through some elicitation techniques.
The requirements are further can be divided in to
 Functional
 Non functional
 Performance requirements
 Design requirements

Functional requirements:-
 This define what the system will “do”, that mean the behavior of the system will be know.
 Functional requirements are the key element for an project. With the help of this only we can know the connectivity of an database.
Example :-out put of the product or an software.
Non functional requirements:-
This define how the system will “be”, this requirements specify the quality and attribute of the system.
Example: – usability.
Performance requirements:-
Performance mean nothing but speed, that mean getting an out put with no more time taking.
Example:- Say that currently the customer is holding for each transaction at least 1 min,this is can be resolved by the performance issues and now the client need to complete the hole transaction in 30 sec.
Design requirements:-
 These are more for technical solutions where it’s initially defined how the system shall be designed and built.
 Need to design as per the user or stake holder requirements.
Modeling the requirement:-
 Modeling the requirements is not a small task where in this part Project manager will also see how to handle to model the requirements.
 Modeling the requirement is not simply matching the gathered information and getting delivery to the development team. This may consist of business, technical, testing, and go-live of an project.
Use case:-
 This scenario-based technique lets you talk about the whole system. In a step by step process as a user.
 It helps you understand how the system or service would work.
 This is a very good technique for gathering the functional requirements,but you may need “n” number of use cases.
Building the prototype:-
 Creating mock-up screen’s for client in order to understand the given requirements.
 It will give an idea for the users and how it will be looking like.

There are many techniques to gather all of the requirements.
Validate requirements:-
 Requirement validation consists of the process of making sure that the requirements to achieve the business need.
 If we have done validate requirements in a correct manner then the client can understood well about his business is and can predict to which level he/she can take to(it”s nothing but gap analysis from the client side).
Manage requirements:-
Managing requirements is the process of documenting, tracking, collaborating, communicating the solution requirements.