Software Requirement Specifications

<Project Title>

Submitted by
<Student Name (Roll No)>

Submitted to
<Supervisor Name>

Department of Information Technology

Faculty of Computing
The Islamia University of Bahawalpur
 Meeting Details
Supervisor
Sr No Details Date
Signature
 Summary
Here the author will write summery of the document. They can provide a brief of the
background, their findings and requirements.
Table of Contents
1. Introduction.......................................................................................................................................4
1.1. Purpose.......................................................................................................................................4
1.2. Scope...........................................................................................................................................4
1.3. Product Perspective...................................................................................................................4
1.4. User Characteristics..................................................................................................................4
1.5. Similar apps and systems/Literature Review...........................................................................4
1.6. Proposed Technologies...............................................................................................................4
2. Requirements.....................................................................................................................................5
2.1. Function Requirements.............................................................................................................5
2.1.1. Sign Up...............................................................................................................................5
2.2. Non-Functional Requirements..................................................................................................5
3. Use Cases and Flow of Processes......................................................................................................6
3.1. Use Case 1...................................................................................................................................7
4. References..........................................................................................................................................8
1. Introduction
If project is developing for a specific organization (e.g. Hospital Management System for XYZ
Hospital) then provide a detail introduction of organization for example services provided by
organization, number of employees, number of annual customers served. Authors should also
provide information about the specific module which is going to be develop. This information
will be provided under the start of Introduction without heading.

1.1. Purpose
Clearly define the goals and objectives of Project

1.2. Scope
Authors must define the boundaries of project and define the item that may be develop and also
mentioned that which items will not develop.

1.3. Product Perspective

Define that how your developed module will be fit in the system

1.4. User Characteristics

Users such as admins, data entry operators, customers or other human roles that interact with
system.

1.5. Similar apps and systems/Literature Review

In this section you can provide the other apps system and already work done. You can put the
details of similar apps, their features and short comings

1.6. Proposed Technologies

Author will provide the list of technologies which be use to develop this system for example if it
is a web-based system then web associated technologies can be mention (React, Django, MySQL
etc.)
2. Requirements
Authors have to provide a brief of functions of the project. For example, if a Hospital
Management System is going to develop and Patient and Doctor module is going to implement
then patient admission, appointment system and billing can be described here. Authors will write
these items in the form of paragraph without providing some title.

2.1. Function Requirements

Authors will provide definite number of functional requirements in standard format. These
requirements directly in the with functions which are already provided. The requirement format
as following.
2.1.1. Sign Up
 Name: FR001
 Purpose: Sign up process is required for a user to become the member of system.
 User(s): Admin, Data Entry Operator, Doctor
 Input:
o Name: Actual name of user according to ID card.
o Password: Must be 8 characters long and must include number
o Address: Actual residence address which is accessible by post and other staff.
o Phone: Working phone number. Must be on WhatsApp
o Display Picture: Latest face picture
o Approval from Super User: Superuser will be verify the information and
approved the status of user a member of system.
 Output: User will be the member of system and able to login
Other requirements will be provided in similar way.

2.2. Non-Functional Requirements

Describe non-function requirements here. Normally, non-functional requirements are considering
as general obligations but sometimes these requirements are also should be discuss in details
3. Use Cases and Flow of Processes
Use cases are the formal representation of process flow defined by functional requirements.
Authors should provide a flow of events in this. There should be system level use case which is
directly influenced to project functions with their user(s) (called actor(s)) which are described in
requirements chapters

Figure 1: System Level Use Case Diagram

3.1. Use Case 1
ID UC001
Name Sign Up
Description This use case describes the process flow of Sing Up
Requirement(s) FR001
Actor(s) Admin, Data Entry, Operator
Precondition Actors must not be member of Hospital
Postcondition Actors will view the message for approval from admin
Basic Flow Basic Flow
1. Actor enter credentials
2. System validates the inputs
2.1. Following fields are required
2.1.1. Name
2.1.2. Email
2.1.3. Password
2.1.4. Address
2.1.5. Phone
2.2. Check the proper inputs for following
2.2.1. Email
2.2.2. Password must be 8 character including number
2.2.3. Phone Number on 11 digits
2.3. On successful validation the system will create new user
Alternative Flow
1. Admin Sign In
2. Create a new User by entering data
Exceptions
1. Invalid Inputs
2. System unable to response
Diagrams
Author should provide the Activity diagram of each Use case. If required then sequency
diagrams also add to this section.
4. References
Author should provide references in IEEE format