SRS Document Sample

Software Requirements
Specification
for
<Online Grievance Redressal

System>
Version 1.0 approved
Prepared by
<Divya.S>
<Jane Varamani Sulekha.V>
<Rathna @ Krithika.R>
< Thiagarajar College of Engineering - Department of Computer
Applications >
<22/09/2014>
Table of Contents .............................................................................................................................

1. Introduction ..............................................................................................................................1
1.1
1.2
Purpose.1
References....................................................................................................................................... 1
2. Overall Description ..................................................................................................................1

2.1
2.2
2.3
2.4
User Classes and Characteristics .................................................................................................... 3

Operating Environment .................................................................................................................. 1
Design and Implementation Constraints ......................................................................................... 2
Assumptions and Dependencies ..................................................................................................... 2
3. External Interface Requirements...2

4. System Use Cases .....................................................................................................................3
4.1 Use case name and identifier .......................................................................................................... 4
4.2 Public lodges grievances (U2) ........................................................................................................... 4
4.3 Staff solves the grievances (U3) ...................................................................................................... 5
4.4 Admin Forward the grievances (U4..7
4.5Higher Officials taking action against unsolved grievances (U5)..8
5. Other Nonfunctional Requirements .......................................................................................9

5.1
5.2
5.3
5.4
Performance Requirements ............................................................................................................. 9

Safety Requirements ....................................................................................................................... 9
Security Requirements .................................................................................................................... 9
Software Quality Attributes ............................................................................................................ 9
6. Other Requirements ..............................................................................................................10

7. System Requirements Chart .................................................................................................10
Appendix A: Analysis Models .....................................................................................................11
Software Requirements Specification for Online Grievance Redressal System
Page 1
1. Introduction
1.1 Purpose
The purpose of an Online Grievance Redressal System is to provide a platform for citizens to lodge
their complaints related to various services they receive from the government. It bridges the
communication gap between the government and the citizens, and provides citizens a platform
through which they can get their grievances addressed in a timely and transparent manner.
1.2 References
Software Engineering, Sixth Edition, Roger S. Pressman.
PHP: The Complete Reference, Steven-Holzne
2. Overall Description
2.1 User Classes and Characteristics
There are four basic users PUBLIC, ADMIN, OFFICERS, and HIGHER OFFICIALS.
Public can submit their grievance to a particular department, and get a track id.
Grievance will be forwarded to concern department.
Once the complaint is rectified, the department officer updates the grievance status. It will be
notified to the public.
Public can view grievance status (open, closed, pending).
If particular department officer does not solve the grievance, it will escalate to higher official.
Higher official can view all reports.
Admin can add department, view all the reports
2.2 Operating Environment

Client on Internet
Web Browser, Operating System (any)
Client on Intranet
Page 2
Web Server
Operating System (any)
Data Base Server
Oracle, Operating System (any)
Development End
PHP, HTML, XML, Oracle, OS (Windows)
Hardware Interface
Recommended Requirements:
Client Side
Browser: Chrome, Firefox
Processor: All Intel or AMD - 1 GHZ
RAM: 256 MB
Disk Space: 200MB
Server Side
RAM: 2GB
Disk Space: 3GB
Communication interface
Client (customer) on Internet will be using HTTP/HTTPS protocol.
Client (system user) on Internet will be using HTTP/HTTPS protocol.
2.3 Design and Implementation Constraints

GUI is only in English.
Only Registered people can use this system
2.4 Assumptions and Dependencies

Network and server problems- These problems may reduce the function of the product.
Communication When a user does not know the language to communicate(i.e. English)
Negligence When any user character(actors) do not care about the grievances the system
may fail.
3. External Interface Requirements

SKIP ALL OF SECTION 3 for the SRS Well do this as part of the GUI Prototype
4. System Use Cases
2.1. Software Interface

Client on Internet
Client on Intranet
Web Server
Operating System (any)
Data Base Server
Oracle, Operating System (any)
Development End
PHP, HTML, XML, Oracle, OS (Windows)
2.2. Hardware Interface

Recommended Requirements:
Client Side
Browser: Chrome, Firefox
RAM: 256 MB
Disk Space: 200MB
Server Side
Page 3
Page 4
4.1 Use case name and identifier

1.
2.
3.
4.
5.
6.
U1
Objective Establish the relationship between user classes and process.
Priority High
Source Public(Eg: Selvaraj, an accountant at EB department,Madurai)
Actors - PUBLIC, ADMIN, OFFICERS, and HIGHER OFFICIALS.
Flow of Events
6.1. Basic Flow
6.1.1 Public registers details.
6.1.2 Public login to the system.
6.1.3 Public lodges the complaint.
6.1.4 Staff login to the system
6.1.5 Staff solves the complaint.
6.1.6 Staff updates the status.
6.2. Alternative Flow(s) At step 6.1.3 if the public does not choose the right department
an error message is displayed.
6.3. Exception Flow(s) When the complaint is not registered properly by the public the
whole process will be blocked.
7. Includes U1,U4
8. Preconditions Public must be registered before they lodge their complaints.
9. Post conditions A Track-id will be received by the public.
10. Notes/Issues - None
4.2 Public lodges grievances (U2)

U2
Objective The public lodges their grievances.
Priority High
Source Nagarevathi(Software tester,Google)
Actors Public, grievance system
Flow of Events
6.1. Basic Flow
6.1.1. Public login
6.1.2. Public registering complaint
6.2. Alternative Flow 1 At step 6.1.1 if the user does not login the system cant be used.
6.3. Exception Flow 1
When the public details are incorrect to login error will be shown.
7. Includes
Exception occurs
8. Preconditions User is logged in
9. Post conditions Grievances are registered
10. Notes/Issues None
1.
2.
3.
4.
5.
6.
Page 5
4.3 Staff solves the grievances (U3)

11. U3
12. Objective The staff takes action against the grievances.
13. Priority High
14. Source Chief engineer, Water Department.
15. Actors Staff, grievance system
16. Flow of Events
16.1. Basic Flow
16.1.1.
Staff login
16.1.2.
Staff solves the complaint
16.2. Alternative Flow 1 At step 17.1.1 if the staff does not login the grievance cant be
solved.
16.3. Exception Flow 1 When the staff details are incorrect to login error will be shown.
17. Includes
Exception occurs
18. Preconditions Staff is logged in
19. Post conditions Grievances are solved

20. Notes/Issues None
Page 6
4.4 Admin Forward the grievances (U4)
Page 7
4.5 Higher Officials taking action against unsolved grievances (U5)
Page 8
Page 9
5. Other Nonfunctional Requirements

5.1 Performance Requirements
Performance is measured in terms of the output provided by the application. Requirement specification plays
an important part in the analysis of a system. Only when the requirement specifications are properly given, it
is possible to design a system, which will fit into required environment. It rests largely in the part of the users
of the existing system to give the requirement specifications because they are the people who finally use the
system. This is because the requirements have to be known during the initial stages so that the system can be
designed according to those requirements. It is very difficult to change the system once it has been designed
and on the other hand designing a system, which does not cater to the requirements of the user, is of no use.
The requirement specification for any system can be broadly stated as given below:
The system should be able to interface with the existing system
The system should be accurate
The system should be better than the existing system
The existing system is completely dependent on the user to perform all the duties.
5.2
Safety Requirements
This describes the safety-related H/W and high level S/W architecture. It decomposes the design of the safety
functions and specifies the associated safety integrity functions such as self-tests and safety support functions such as
operating and communication systems and justifies the partitioning.
5.3 Security Requirements

All the details in this system must be secured. It must be confidential.
5.4 Software Quality Attributes

adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability,
reusability, robustness, testability, and usability.
Page 10
6. Other Requirements
1.Online Surveys.
2.Facility to upload photos of the complaint. for eg, garbage problem.
3.Help pages in the form of forums and FAQs.
4.Assigning performance ratings to different sections of municipal administration as per direct feedback received from users.
7. System Requirements Chart

ID
U1
Priority
High
Type
F
U2
High
Source
Public,
staff,admin,higher
official
Public
U3
High
Staff
U4
Medium
Admin
U5
Medium
Higher official
Description
All the activities of
the system
Registers the
grievances
Takes action against
the grievances
Forward the
grievances to Staff
Check for unsolved
grievances by staff
Appendix A: Analysis Models
Page 11

SRS Document Sample

Uploaded by

Copyright:

Available Formats

SRS Document Sample

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SRS Document Sample

Uploaded by

Copyright:

Available Formats

Software Requirements

<Online Grievance Redressal

Table of Contents .............................................................................................................................

2. Overall Description ..................................................................................................................1

User Classes and Characteristics .................................................................................................... 3

3. External Interface Requirements...2

5. Other Nonfunctional Requirements .......................................................................................9

Performance Requirements ............................................................................................................. 9

6. Other Requirements ..............................................................................................................10

Software Requirements Specification for Online Grievance Redressal System

2.2 Operating Environment

Software Requirements Specification for Online Grievance Redressal System

2.3 Design and Implementation Constraints

2.4 Assumptions and Dependencies

3. External Interface Requirements

Software Requirements Specification for Online Grievance Redressal System

4. System Use Cases

2.1. Software Interface

2.2. Hardware Interface

Software Requirements Specification for Online Grievance Redressal System

4.1 Use case name and identifier

4.2 Public lodges grievances (U2)

Software Requirements Specification for Online Grievance Redressal System

4.3 Staff solves the grievances (U3)

Software Requirements Specification for Online Grievance Redressal System

19. Post conditions Grievances are solved

Software Requirements Specification for Online Grievance Redressal System

4.4 Admin Forward the grievances (U4)

Software Requirements Specification for Online Grievance Redressal System

4.5 Higher Officials taking action against unsolved grievances (U5)

Software Requirements Specification for Online Grievance Redressal System

5. Other Nonfunctional Requirements

The system should be able to interface with the existing system

The system should be accurate

The system should be better than the existing system

5.3 Security Requirements

5.4 Software Quality Attributes

Software Requirements Specification for Online Grievance Redressal System

2.Facility to upload photos of the complaint. for eg, garbage problem.

3.Help pages in the form of forums and FAQs.

7. System Requirements Chart

Software Requirements Specification for Online Grievance Redressal System

Appendix A: Analysis Models

You might also like