Give me the example of SRS and FRS

Q

Give me the example of SRS and FRS

✍: ashish kumar

A

SRS :- Software Requirement Specification
BRS :- Basic Requirement Specification
FRS :- Functional requirment specification


FRS mainly says the particular functionality. FRS mainly used for change request, enchancements, additional functionalites.

BRD contain Basic requirement and validatiob that Client wants
BRD is a high level documention (means tables) and SRS/FRS is Low level documention (use case diagrams).

SRS contain all information of BRD and make any changes and released to developers for more information

SRS.... A Software Requirements Specification (SRS) is a complete description of the behavior of the system to be developed. It includes a set of use cases that describe all the interactions the users will have with the software. Use cases are also known as functional requirements. In addition to use cases, the SRS also contains nonfunctional (or supplementary) requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints).




To begin with, we should understand the difference between the two document types. Software Requirements Specification describes the system's functional as well as non-functional requirements (e.g. performance requirements, security requirements, availability requirements etc.). On the other hand Functional Requirements Specification (FS) deals with the functional requirements only.

In a particular project, the following four possibilities exist.
1) Both SRS and FS are available
In this case, you should find out which document is the latest one. As mentioned above, you may understand the non-functional requirements from the SRS and in case the FS is the latest document, the functional requirements from there. Be warned that sometimes even non-functional requirements are documented in the FS. The structure of the available SRS and FS should be able to guide you in your study.

2) Only SRS is available
There is no confusion in this case. You may understand all the software requirements from this document.

3) Only FS is available
You may understand the functional requirements from this document. However, you should find out about the non-functional requirements from the business analyst/ project manager/ customer support etc.

4) None of these documents is available
This can happen when the project has been running for a long time. Either the SRS or FS documents will not be available or they will be quite out-of-date and therefore, unusable.


In such a case, you should find out the availability of any other documents/ material e.g. high-level business requirements, existing help files/ user manuals, existing test cases, user stories, customer issues and resolutions etc. In addition, it becomes important to discuss the requirements with various project roles that may be present e.g. system analyst, business analyst, product management, development, support etc. so that you may get your queries resolved. If you notice any discrepancies, you should point it out to the concerned roles and note their resolution.

On top of SRS/ FS, the Test Engineer should refer Change Requests (mainly enhancements/ modifications to the software) and the resolution of customer issues. By following the above guidelines, the Test Engineer can understand the requirements and subsequently perform testing. Note: It will be useful to find out about the project stakeholders and project roles before attempting to understand the requirements. This is important because, depending on project characteristics, some project organizations are unusual. Your manager and team members should be able to help you with this.

2009-03-17, 15411👍, 0💬