Question # 1:
What is SRS and BRS?
Answer:
SRS
SRS stands for “Software Requirement Specification”. It provides the
complete description of the intentional motive and environment for software
under development. The SRS completely describes what the software does
and how it is expected to perform its tasks. It describes the functional and
technical specification of the software, at a higher level by specifying the
functional and non-functional requirements of the software to be developed.
It is usually created by the System Architect who is a technical expert.
Although in smaller companies the Business Analyst (BA) will create SRS
as well while some companies do not create SRS altogether, because their
BRS is detailed enough to be used as SRS as well.
To build an SRS, following components must be satisfied:
➔ A purpose,
➔ An overall description, and
➔ Specific requirements.
Purpose of SRS:
An SRS is considered to be the basis of an organization’s entire project. It
presents the framework that will be followed by all the development teams.
It provides critical information to all the teams, including development,
operations, quality assurance (QA) and maintenance, ensuring the teams
are in agreement. It helps an enterprise confirm that the requirements are
fulfilled and helps business leaders make decisions about the lifecycle of
their product, such as when to retire a feature. Moreover, writing an SRS
can help developers reduce the time and effort necessary to meet their
goals as well as save money on the cost of development.
BRS
BRS stands for “Business Requirement Specifications”. It describes the
functional specifications of the software, at a very high level. It is a formal
document describing the requirement provided by the client, which could
What is SRS and BRS?
Answer:
SRS
SRS stands for “Software Requirement Specification”. It provides the
complete description of the intentional motive and environment for software
under development. The SRS completely describes what the software does
and how it is expected to perform its tasks. It describes the functional and
technical specification of the software, at a higher level by specifying the
functional and non-functional requirements of the software to be developed.
It is usually created by the System Architect who is a technical expert.
Although in smaller companies the Business Analyst (BA) will create SRS
as well while some companies do not create SRS altogether, because their
BRS is detailed enough to be used as SRS as well.
To build an SRS, following components must be satisfied:
➔ A purpose,
➔ An overall description, and
➔ Specific requirements.
Purpose of SRS:
An SRS is considered to be the basis of an organization’s entire project. It
presents the framework that will be followed by all the development teams.
It provides critical information to all the teams, including development,
operations, quality assurance (QA) and maintenance, ensuring the teams
are in agreement. It helps an enterprise confirm that the requirements are
fulfilled and helps business leaders make decisions about the lifecycle of
their product, such as when to retire a feature. Moreover, writing an SRS
can help developers reduce the time and effort necessary to meet their
goals as well as save money on the cost of development.
BRS
BRS stands for “Business Requirement Specifications”. It describes the
functional specifications of the software, at a very high level. It is a formal
document describing the requirement provided by the client, which could
