Transform your project description and requirements into a professionally structured Software Requirements Specification document with clearly defined functional and non-functional requirements.
Like this prompt? Use it in Team-GPT for free now →
🗒️
You are tasked with creating a comprehensive Software Requirements Specification (SRS) document based on the provided project description and requirements. Follow these instructions carefully to produce a well-structured and detailed SRS.
First, you will be given a project description:
<project_description>
{{PROJECT_DESCRIPTION}}
</project_description>
Then, you will be provided with a list of requirements:
<requirements>
{{REQUIREMENTS}}
</requirements>
Guidelines for writing the SRS:
1. Use clear, concise, and unambiguous language.
2. Be specific and avoid vague terms.
3. Use "shall" for mandatory requirements and "should" for recommended ones.
4. Number each requirement uniquely for easy reference.
5. Ensure consistency throughout the document.
6. Avoid technical jargon unless necessary, and explain any used.
Structure your SRS document as follows:
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
1.5 Overview
2. Overall Description
2.1 Product Perspective
2.2 Product Functions
2.3 User Classes and Characteristics
2.4 Operating Environment
2.5 Design and Implementation Constraints
2.6 User Documentation
2.7 Assumptions and Dependencies
3. Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
3.1.2 Hardware Interfaces
3.1.3 Software Interfaces
3.1.4 Communications Interfaces
3.2 Functional Requirements
3.3 Non-Functional Requirements
3.3.1 Performance Requirements
3.3.2 Safety Requirements
3.3.3 Security Requirements
3.3.4 Software Quality Attributes
3.4 Other Requirements
4. Appendices (if necessary)
For each section:
1. Introduction: Provide an overview of the project, its purpose, and scope based on the project description.
2. Overall Description: Describe the product context, main functions, user classes, and any constraints or assumptions.
3. Specific Requirements: Detail all functional and non-functional requirements, ensuring each one is clear, testable, and traceable.
4. Appendices: Include any supplementary information, diagrams, or tables that support the main document.
Before finalizing your SRS:
1. Review the document for consistency, completeness, and clarity.
2. Ensure all requirements from the provided list are addressed.
3. Check that each requirement is uniquely numbered and traceable.
4. Verify that the language used is precise and unambiguous.
Present your final SRS document within <srs> tags. Use appropriate subsection tags (e.g., <introduction>, <overall_description>, <specific_requirements>) to structure your document.
Remember to think carefully about how to organize and present the information in a clear, logical manner that will be easily understood by both technical and non-technical stakeholders.