Srs - Template - Uidb
Srs - Template - Uidb
SoftwareRequirementsSpecificationTemplate
Vishal Kumar
<ProjectName>
Revision History
Date
<date>
Description
<Version 1>
SoftwareRequirementsSpecification
Author
Vishal
Comments
<First Revision>
Pageii
<ProjectName>
Table of Contents
REVISION HISTORY.................................................................................................................II
1. INTRODUCTION.....................................................................................................................1
1.1 PURPOSE.................................................................................................................................1
1.2 SCOPE.......................................................................................................................................
.......................................................................................................................................................
1.5 OVERVIEW..............................................................................................................................1
2. GENERAL DESCRIPTION.....................................................................................................2
2.1 PRODUCT PERSPECTIVE..........................................................................................................2
2.2 PRODUCT FUNCTIONS.............................................................................................................2
2.3 USER CHARACTERISTICS........................................................................................................2
2.4 GENERAL CONSTRAINTS........................................................................................................2
2.5 ASSUMPTIONS AND DEPENDENCIES.......................................................................................2
3. SPECIFIC REQUIREMENTS.................................................................................................2
3.1 EXTERNAL INTERFACE REQUIREMENTS.................................................................................3
3.1.1 User Interfaces...............................................................................................................3
3.1.2 Hardware Interfaces.......................................................................................................3
3.1.3 Software Interfaces.........................................................................................................3
3.1.4 Communications Interfaces............................................................................................3
3.2 FUNCTIONAL REQUIREMENTS................................................................................................3
3.2.1 <Functional Requirement or Feature #1>.....................................................................3
3.2.2 <Functional Requirement or Feature #2>.....................................................................3
3.3 USE CASES.............................................................................................................................3
3.3.1 Use Case #1....................................................................................................................3
3.3.2 Use Case #2....................................................................................................................3
3.4 CLASSES / OBJECTS................................................................................................................3
3.4.1 <Class / Object #1>.......................................................................................................3
3.4.2 <Class / Object #2>.......................................................................................................3
3.5 NON-FUNCTIONAL REQUIREMENTS.......................................................................................4
3.5.1 Performance...................................................................................................................4
3.5.2 Reliability.......................................................................................................................4
3.5.3 Availability......................................................................................................................4
3.5.4 Security...........................................................................................................................4
3.5.5 Maintainability...............................................................................................................4
3.5.6 Portability.......................................................................................................................4
3.6 INVERSE REQUIREMENTS.......................................................................................................4
3.7 DESIGN CONSTRAINTS...........................................................................................................4
3.8 LOGICAL DATABASE REQUIREMENTS.....................................................................................4
3.9 OTHER REQUIREMENTS..........................................................................................................4
4. ANALYSIS MODELS...............................................................................................................4
4.1 SEQUENCE DIAGRAMS............................................................................................................5
SoftwareRequirementsSpecification
Pageiii
<ProjectName>
4.3 DATA FLOW DIAGRAMS (DFD)..............................................................................................5
4.2 STATE-TRANSITION DIAGRAMS (STD)...................................................................................5
5. CHANGE MANAGEMENT PROCESS.................................................................................5
A. APPENDICES...........................................................................................................................5
A.1 APPENDIX 1...........................................................................................................................5
A.2 APPENDIX 2...........................................................................................................................5
SoftwareRequirementsSpecification
Pageiv
<ProjectName>
1. Introduction
This SRS describes the software functional and nonfunctional requirements of the University
Database Information System. Unless otherwise noted, all requirements specified here is high
priority.
1.1 Purpose
This SRS describes the software functional and nonfunctional requirements for release 1.0 of the
University Database Information System. This document is intended to be used by the members
of the project team that will implement and verify the correct functioning of the system. Unless
otherwise noted, all requirements specified here are high priority and committed for release 1.0
1.2 Scope
The University Database Information System will permit Process Impact employees to support
querying the academic details of each student by inputting his registration number. A detailed
project description is available in the University Database Information System Document [1].
The section in that document titled Scope of Initial and Subsequent Releases lists the features
that are scheduled for full or partial implementation in this release.
1.3 Overview
This subsection should:
(1) Describe what the rest of the SRS contains
(2) Explain how the SRS is organized.
2. General Description
2.1 Product Perspective
TheUniversityDatabaseSystemisanewsystemthatreplacesthecurrentmanualprocessof
Inventorymanagementandqueryingtheacademicdetailsaboutthestudentenrolled.
ThecontextdiagraminFigure1illustratestheexternalentitiesandsysteminterfacesforversion
1.0..Thesystemisexpectedtoevolveoverseveralreleases,ultimatelyconnectingtothe
Internetandenablingstudentstoregisterfornewcoursesontheinternetportal.
2.2 User Characteristics
Student,university details
Department
Secretary
Student information,
SoftwareRequirementsSpecification
UniversityInformationDatabase
Dept.Inventorysystem
Cashbookaccount
Researchtrackingsystem
Grantsystem
Studentdetails
Page1
<ProjectName>
Accounts,expenditure, research
information
(a) context level diagram of University information database system
DesignandImplementationConstraints
CO-1:
CO-2:
The system shall use a SQL Database to correctly store student and Department
details.
All Code written should conform to Java coding rules.
Page2
<ProjectName>
3.2.2.3Outputs:PrepareInventory
3.2.3R3:CheckUndergoingResearch
3.2.3.1Inputs:DepartmentName
3.2.1.2Processing:OngoingProjectDetails.
3.2.1.3Outputs:ListofResearchAreasandProfworkingontheresearch.
SoftwareRequirementsSpecification
Page3
<ProjectName>
Example Appendices could include (initial) conceptual documents for the software project,
marketing materials, minutes of meetings with the customer(s), etc.
A.1 Appendix 1
A.2 Appendix 2
SoftwareRequirementsSpecification
Page4