You are on page 1of 2

Software Requirement Specification

For

<Topic Name>

Submitted by:
Name:
Registration Number:
Section:
Roll number:
1. Introduction
2. Requirement analysis
a) Functional requirements (Minimum 10)
For each functional requirement, mention Input, Process, and Output.
For example:
FR1: Login
Input: Credentials (Username and password)
Process: Verify and validate username based on proper password from the database.
Output: Allow to view ticket reservation.
b) Non-functional requirements (Minimum 5)
c) Constraints (Minimum 3)
3. Data flow diagram
DFD: Context diagram (L0), L1-DFD
4. UML diagrams
Usecase diagram
5. Testcase
A format will be shared later.

Note:
1. All the above four points are compulsory for the assignment to include.
2. Assignment will be handwritten, and then take the picture of the pages, merge
them as pdf and then upload. The handwritten assignments need to be shown at
the time of viva.
3. Diagrams must also have some explanation to write and label the diagram properly.
For example.

Figure-1: Context diagram for Tic Tac Toe game

Explanation: The above diagram or Figure-1 shows a game software playing tic tac toe game. The
software is usable by the players or users. The user gives some input move and the game eventually
completes with some result.

For any query, feel free to contact me at lpulive or at 38-207.

You might also like