Scribd
Upload
95 views4 pages

Software Requirements Specification

This software requirements specification outlines a project with the goal of introducing and specifying requirements. It provides information on the project scope, functional and non-functional requirements, use case diagram, and usage scenarios in a table format with use case title, ID, and action descriptions. The document was submitted by a student and establishes the initial version and current date in the revision history.

Uploaded by

enigmazee
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
95 views4 pages

Software Requirements Specification

This software requirements specification outlines a project with the goal of introducing and specifying requirements. It provides information on the project scope, functional and non-functional requirements, use case diagram, and usage scenarios in a table format with use case title, ID, and action descriptions. The document was submitted by a student and establishes the initial version and current date in the revision history.

Uploaded by

enigmazee
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

<Give Here Your Own Project Title>

Software Requirements Specification

Version 1.0

Submitted By:
<Student ID> < Student Name>

Revision History
Date (dd/mm/yyyy)
Current date

Version
1.0

Description
Introduction of the project

Author
Write student(s) id

Table of Contents
1. Scope (of the project)

2. Functional Requirements Non Functional requirements

3. Use Case Diagram

4. Usage Scenarios

SRS Document

Scope of Project: <Write here in detail about the scope of your project>

Functional and non Functional Requirements: <Write here in detail about the functional and non-functional requirements of your system in separate headings>

Use Case Diagram(s): <Provide here the use case diagram of your system>

Usage Scenarios: <Provide here the usage scenarios of all use cases in table format explaining Use Case title, Use Case Id, actions description>

You might also like