SRS: System Requirement Specification:
It depicts entire system flow, how data is going to flow into the system and overall functionality of the system. SRS says brief about each module's functionality and doesn't include in-depth functionality of each page and module.
BRS: Business Requirement Specification:
This document is called as high level document includes all the requirement demanded by the client. Ideally, this document simply includes all the requirements should be part of proposed system.
FRS: Functional Requirement Specification:
FRS includes requirements, converted into functionality and says that how this requirement is going to work as a part of proposed system.
NOTE : FRS and BRS is little confusing : BRS includes list of requirements which are demanded by client and should be part of proposed system; whereas, FRS includes requirement converted into the way it is going to work as a part of proposed system.
It depicts entire system flow, how data is going to flow into the system and overall functionality of the system. SRS says brief about each module's functionality and doesn't include in-depth functionality of each page and module.
BRS: Business Requirement Specification:
This document is called as high level document includes all the requirement demanded by the client. Ideally, this document simply includes all the requirements should be part of proposed system.
FRS: Functional Requirement Specification:
FRS includes requirements, converted into functionality and says that how this requirement is going to work as a part of proposed system.
SRS
|
FRS
|
BRS
|
1. It means “Software Requirement
Specification” (SRS).
|
1. It means “Functional Requirement
Specification” (FRS).
|
1. It means “Business Requirement
Specification” (BRS).
|
2. It deals with resources provided by
Company.
|
2. It deals with requirements given by
client.
|
2. It deals with aspects of business
requirements.
|
3. It always includes Use cases to
describe the interaction of the system.
|
3. In this Use cases are not included.
|
3. In this Use cases are also not
included.
|
4. It is derived from BRS.
|
4.It is also derived by discussions.
|
4.It is derived from the client
requirement and discussions.
|
5. It is developed by System Analyst.
And it is also known as User Requirement Specifications.
|
5. It is always developed by
developers and engineers.
|
5. It is always developed by Business
Analyst.
|
6. In SRS, we describe all the
business functionalities of the application.
|
6. In FRS, we describe the particular
functionalities of every single page in detail from start to end.
|
6.In BRS, we defines what exactly
customer wants. This is the document which is followed by team from start to
end.
|
7. SRS tells means explains all the functional and non
functional requirements.
|
7. FRS tells means explains the sequence of operations to
be followed on every single process.
|
7. BRS tells means explains the story of whole
requirements.
|
8. SRS is a complete document which describes
the behavior of the system which would be developed.
|
8. FRS is a document, which describes
the Functional requirements i.e. all the functionalities of the system would
be easy and efficient for end user.
|
8. BRS is a simple document, which
describes the business requirements on a quite broad level.
|
NOTE : FRS and BRS is little confusing : BRS includes list of requirements which are demanded by client and should be part of proposed system; whereas, FRS includes requirement converted into the way it is going to work as a part of proposed system.
No comments:
Post a Comment