Requirements Flow

Requirements Flow 

Requirements Flow:

 
Everyone is aware that the application is designed for end users based on the customer requirements.
But, only few people are aware that there are lot many faces that draw the customer requirements into different layers before converting / reflecting into an application.
Here is the explanation.

Just have a look at the diagram.
More information with regards to the Requirements Flow could be added to the table at the later editions.

Requirement:            

The basic customer needs are called as Requirements.

The set of all customer needs put together is called requirements document or marketing requirements document.

BRS (Business Requirement Specification):

At Business level, all the customer requirements are documented and approved by customer.

All these bossiness requirements should exactly map to end user real-time scenarios

FRS (Function Requirements Specification):

The BRS are segregated into different Functions / Modules and are described in more detailed and such that more detailed information is provided with respect all the functions / modules of the application.

And these documents are called FRS.

SRS (Software Requirement Specification):

In depth of the requirements, such as the detailed information like windows / dialog boxes information, field level information and Just as clear-cut document for coding and prototypes are called as SRS

SRS (System Requirement Specification):

The entire SRS (Software Requirement Specification) are merged together so as to make completeSystem approach is called System Requirement Specification.

Use Cases:  

Use Case is a document that describes the User actions versus System / Application responses

Posted in: Requirements Flow