Software Requirement Specification
|Xxxxx xxxxxx||Business Analyst||[email protected]|
|Yyyyy yyyyy||Project Manager||[email protected]|
|Name/Author||Date||Reason For changes||Version|
Under the subsections of this section, an overview of the SRS is provided which can be deemed as an executive summery.
Under this subsection the following aspect of SRS developed are mentioned in a brief manner.
- The overall purpose of document.
- The reason of its creation
- Identity of the stakeholders for whom it is addressed.
Under this subsection, the following aspects of the overall software to be developed are mentioned in a briefs manner
- Main Functions
- What it will do?
- What it will not do?
- How it will be used?
1.3. Assumption and Dependencies.
Under this subsection, the factors influencing the requirements under the SRS are explained.
- List of Factors
- A brief description of each factor
Under this subsection, the structure of SRS document is described with reference to
- The topic covered.
2. General Description
Under the subsections of this section, the general factors which affect the proposed software to be developed, and its requirements are mentioned.
2.1. Product Perspective
Under this subsection, nature of the software product to be developed is mentioned.
- Nature of product
- Functions(If a component or subsystem)
- Identified Interconnection(if a component or subsystem)
- Block diagram of product and its relationship with the external and internal environment.
2.2. Product Functions
Under this subsection, function of the software product are described in terms of
- List of function performed.
- Summary description of each function
- An explanatory block diagrams of the function with their interrelationship.
2.3. User characteristics
Under this subsection, the characteristics of the user of product which affects requirements are mentioned in terms of
- Classes of users.
- Characteristic of each user class in terms of experience and technical expertise.
2.4. General Constraints
Under this subsection, the various constraints which influences the design and development of the proposed software product are mentioned i.e,
- Regulatory Policies
- Hardware Limitation
- Interface to other application
- Safety and security consideration.
3. Specific Requirements
Under the subsection of this section, the details of the requirements are elaborated to facilitate the developer to create the software design documents before commencing the coding activity. Attention is focused on following in this context
- Individual requirements are defined keeping in mind quality characteristics.
- Source of each requirement is defined and referenced properly.
- All requirements are organized in a structured and logical manner.
3.1. Functional requirement
Under this subsection, all functional requirements which need to be implemented in relation to the product are specified.
Under this, the rationale and intent of including the functional requirement is clarified.
Under this input values which will be accepted by the product as input in context of the functional requirement are elaborated in terms of the source, valid range, timings, Operator requirements, and special interfaces required.
Under this the operations which will be performed by the product to transform the input in context of the functional requirement are elaborated in terms of the validity checks, response to abnormal conditions and type of processing required.
Under this the output which will be generated by the product after processing the input, in context of the functional requirement are elaborated in terms of the destination, valid range, timing, handling of illegal values, error messages and special interface required.
3.2.External Interface requirements
Under this subsection, all the interfaces to the external entities which need to be implemented by designer specified in relation to the software product as under.
3.2.1. User Interface
Under this the characteristic of the interface for the human interaction with the software product are specified in terms of screen format, layout, menus, relative timing for input and outputs, programmable function keys, a list do’s and don’ts on how the system will appear to the user.
3.2.2. Hardware Interface
Under this, the logical characteristics of the interface between the software product and various hardware components are specified in terms of which device will supported, how they will be supported, block diagrams depicting the relationship between the hardware components and the software functions.
3.2.3. Software Interface
Under this, the logical characteristics of the interface between the software product and various other eternally required software products are specified in terms of the technical name, version number, manner of communication in terms of message content and format.
3.2.4. Communication Interface
Under this, the various interfaces between the software product and various communication and network protocols are specified in terms of local network protocol.
3.3. Performance Requirement
Under this subsection, the details of the performance related requirement placed on the software product or the human interaction with the software product.
- Static numerical requirements such as number of terminals, simultaneous users, files and records, size of tables and files.
- Dynamic numerical requirements such as number of transactional task and amount of data to be processed within the time limits under normal and peak workload conditions.
3.4. Design Constraints
Under this subsection, the details of requirement placed on the software product as constraints which need to be taken in the account.
3.4.1. Standard compliance
Under this, the requirement related to existing standard and regulations which need to be compiled with the software product such as report formats, data naming convention etc..
3.4.2. Hardware Limitation
Under this, the requirement related to various hardware constraints and operating environment which need to compiled with by the software product are specified.
3.5. Quality Characteristic
Under this subsection, quality requirement places on the software product as constraint.Relevent quality characteristic are selected from generic one such as correctness, efficiency, flexibility, security, maintainability, portability, reliability and usability.
3.6. Other Requirements
Under this the specific requirements of any database which need to be developed as a part of the software product are specified such as
- Type of information to be used
- Frequency of use
- Accessing capabilities
- Data elements and file description
- Relationship between data elements, records and files.
3.6.2. Site Adaption Requirement
Under this the specific requirements related to any specific installation site environment which need to be supported by the software product are specified such as
- Data or installation sequence specific to any site, mission or operational modes e.g safety mode.
- Any customized software product features modification required for a specific site.
4. Supporting Information
Under the subsection of this section, all supporting information is included to ensure the completeness of the SRS such as
4.1. Definition, acronyms and abbreviation
Under this subsection, the meaning and definition of all keywords and short form used in the SRS document are given to facilitate proper interpretation with reference to appendix or other documents.
Under this subsection, the list of documents reference in the SRS along with the title, reference id, date, author, document resources and web resources are given including the traceability table.
Find Below link to download SRS template.