Skip to content

SRS Template

Use this page to structure the formal Software Requirements Specification.

How to use this template

The SRS should read like a professional document. Students should keep numbered headings, clear formatting, page numbers and version details in the working document they produce from this template.

Cover Page

The cover page should include:

  • project name
  • student name
  • class
  • teacher
  • contact details if required
  • version number
  • date

Table of Contents

Insert an automatically generated table of contents after the cover page.

1. Purpose of This Document

Write a short paragraph that explains:

  • what this SRS is for
  • which problem, need or opportunity it addresses
  • that it will guide the design and later evaluation of the solution

2. Identified Problem, Need or Opportunity

Write a clear explanation of:

  • the current situation
  • the issue or opportunity that has been identified
  • why it matters
  • who is affected
  • why a software solution is being proposed

3. Users and Stakeholders

3.1 Primary user or client

  • role:
  • needs:
  • level of technical skill:

3.2 Secondary users

  • role:
  • needs:
  • level of technical skill:

3.3 Stakeholders

List anyone else with an interest in the solution.

-

4. Technical Environment

Describe the environment in which the software is expected to operate.

Category Details for this project
Hardware
Operating system
Network environment
Software dependencies
Data sources
Input devices
Output devices
Storage requirements

5. Functional Requirements

List what the solution must do.

ID Functional requirement Inputs required Processing or behaviour Output or result Evidence source
FR1
FR2
FR3
FR4

Add more rows as needed.

6. Non-Functional Requirements

List measurable quality requirements for the solution.

ID Category Requirement statement How it will be measured Evidence source
NFR1 Usability / Reliability / Portability / Robustness / Maintainability
NFR2
NFR3

Add more rows as needed.

7. Constraints

7.1 Economic constraints

Constraint Impact on the project
Budget
Time
Available resources

Address any legal requirements that apply, such as:

  • Copyright Act 1968
  • Privacy Act 1988
  • Privacy and Data Protection Act 2014
Legal issue How it affects this solution
Copyright / ownership of data
Privacy of user data
Permission to use data or media

7.3 Social constraints

Social constraint Impact on the project
User experience level
Accessibility expectations
Cultural or ethical considerations

7.4 Technical constraints

Technical constraint Impact on the project
Hardware limitations
Software dependencies
System integration
Performance requirements
Security requirements
Network limitations

8. Scope

8.1 In scope

List the features, functions and components that will be included.

-

8.2 Out of scope

List the features, functions and components that will not be included at this stage.

-

8.3 Scope statement

Write one short paragraph that summarises the boundaries of the project.

9. Analytical Tools

Insert the analytical tools that depict the existing process, system and user interactions investigated during analysis.

9.1 Use case diagram

Insert diagram and caption.

9.2 Context diagram

Insert diagram and caption.

9.3 Data flow diagram

Insert diagram and caption.

9.4 Notes on consistency

Briefly explain how the diagrams align with each other and with the collected evidence.

10. Design Implications

Summarise the key design implications that must carry into the design stage.

  • most important functional requirements:
  • most important non-functional requirements:
  • constraints that strongly shape the design:
  • features that are deliberately out of scope:

11. Appendices

List and attach the supporting evidence used to build the SRS.

  • Appendix A: interview evidence
  • Appendix B: survey or questionnaire evidence
  • Appendix C: observation evidence
  • Appendix D: report or secondary data evidence
  • Appendix E: any additional supporting material

Final Check Before Submission

  • [ ] Cover page included
  • [ ] Table of contents included
  • [ ] Numbered headings used
  • [ ] Page numbers added
  • [ ] Functional requirements are clear
  • [ ] Non-functional requirements are measurable
  • [ ] Constraints are realistic and specific
  • [ ] Scope includes both in-scope and out-of-scope items
  • [ ] Analytical tools are inserted
  • [ ] Appendices are attached
  • [ ] Formatting is consistent