Government College University Faisalabad

BSCS FINAL PROJECT

<Phase>
<Project Title>
Project Advisor
<Advisor Name>
Presented !"
Group ID: xxxxxxx
St#dent Re$% St#dent Na&e
Department of Computer Science
Government College Uni versity
Faisal abad
Government College University Faisalabad
Software Requirements Specification
Version <Version #>
<Project Name>
Client: <Client Name>
Team <Team #>
Member Name Primary Responsibility
<Project Name>
Table of Contents
1. Introduction................................................................................................................................1
2. Overall Description.................................................................................................................... 2
3. Functional Requirements.......................................................................................................... 3
4. Nonfunctional Requirements.................................................................................................... 3
5. Other Requirements.................................................................................................................. 4
<Team #> SRS <Version #> Page iii
<Project Name>
Revision History
Name Date Reason For Changes Version
<Team #> SRS <Version #> Page iv
<Project Name>
1. Introduction
1.1 Product
<Provide a short description of the software being specified.>
1.2 Scope
< Describe the scope of the product that is covered by this SRS.>
1.3 Business Goals
<List all the business/corporate goals addressed by this software.>
1.4 Document Conventions
<Describe any standards or typographical conventions that were followed when writing this SRS,
such as fonts or highlighting that have special significance. or e!a"ple, state whether italici#ed
nouns represent e!ternal syste"s.>
1.5 References
<List all boo$s, conference papers, %ournal articles, websites, etc. used in preparing the content of
this SRS. Provide enough infor"ation so that the reader could access a copy of each reference,
including title, author, volu"e/edition nu"ber, page nu"ber&s', and publication year. (ention
co"plete )RLs for websites.>
<Team #> SRS <Version #> Page 1
<Project Name>
2. Overall Description
2.1 Product Features
<Su""ari#e the "a%or features the product contains or the significant functions that it perfor"s or
lets the user perfor". Details will be provided in Section *, so only a high level su""ary is needed
here. +rgani#e the functions to "a$e the" understandable to any reader of the SRS.>
2.2 User Classes and Characteristics
<,dentify the various user classes that you anticipate will use this product. )ser classes "ay be
differentiated based on fre-uency of use, subset of product functions used, technical e!pertise,
security or privilege levels, educational level, or e!perience. Describe the pertinent characteristics of
each user class. .ertain re-uire"ents "ay pertain only to certain user classes. Distinguish the
favored user classes fro" those who are less i"portant to satisfy.>
2.3 Operating Environment
<Describe the environ"ent in which the software will operate, including the hardware platfor",
operating syste" and versions, and any other software co"ponents or applications with which it
"ust peacefully coe!ist.>
2.4 Design and Implementation Constraints
<Describe any ite"s or issues that will li"it the options available to the developers. /hese "ight
include0 corporate or regulatory policies1 hardware li"itations &ti"ing re-uire"ents, "e"ory
re-uire"ents'1 interfaces to other applications1 specific technologies, tools, and databases to be
used1 parallel operations1 language re-uire"ents1 co""unications protocols1 security
considerations1 design conventions or progra""ing standards &for e!a"ple, if the custo"er2s
organi#ation will be responsible for "aintaining the delivered software'.>
2.5 Assumptions and Dependencies
<List any assu"ed factors &as opposed to $nown facts' that could affect the re-uire"ents stated in
the SRS. /hese could include third3party or co""ercial co"ponents that you plan to use, issues
around the develop"ent or operating environ"ent, or constraints. /he pro%ect could be affected if
these assu"ptions are incorrect, are not shared, or change. 4lso identify any dependencies the
pro%ect has on e!ternal factors, such as software co"ponents that you intend to reuse fro" another
pro%ect, unless they are already docu"ented elsewhere &for e!a"ple, in the vision and scope
docu"ent or the pro%ect plan'.>
<Team #> SRS <Version #> Page 2
<Project Name>
3. Functional Requirements
<4ll functional re-uire"ents are e!pressed as use3cases. ill out the following te"plate for each
use3case. Don2t really say 5)se3.ase 6.7 State the use3case na"e in %ust a few words e.g.
58ithdraw .ash fro" 4/(7. 4 use3case "ay have "ultiple alternate courses of action.>
3.1 Use-Case 1
Identifier UC-1
Purpose
Priority <Choose one from {High, Medium, Low}>
Pre-conditions

Post-
conditions

Typical Course of Action

S# Actor Action System Response
1
2
3

Alternate Course of Action

S# Actor Action System Response
1
2
3

Table 1: UC-1
3.2 Use-Case 2 (and so on)
4. Nonfunctional Requirements
4.1 Performance Requirements
<,f there are perfor"ance re-uire"ents for the product under various circu"stances, state the"
here and e!plain their rationale, to help the developers understand the intent and "a$e suitable
design choices. Specify the ti"ing relationships for real ti"e syste"s. (a$e such re-uire"ents as
<Team #> SRS <Version #> Page 3
<Project Name>
specific as possible. 9ou "ay need to state perfor"ance re-uire"ents for individual functional
re-uire"ents or features.>
4.2 Safety Requirements
<Specify those re-uire"ents that are concerned with possible loss, da"age, or har" that could
result fro" the use of the product. Define any safeguards or actions that "ust be ta$en, as well as
actions that "ust be prevented. Refer to any e!ternal policies or regulations that state safety issues
that affect the product2s design or use. Define any safety certifications that "ust be satisfied.>
4.3 Security Requirements
<Specify any re-uire"ents regarding security or privacy issues surrounding use of the product or
protection of the data used or created by the product. Define any user identity authentication
re-uire"ents. Refer to any e!ternal policies or regulations containing security issues that affect the
product. Define any security or privacy certifications that "ust be satisfied.>
4.4 Software Quality Attributes
<Specify any additional -uality characteristics for the product that will be i"portant to either the
custo"ers or the developers. So"e to consider are0 adaptability, availability, correctness, fle!ibility,
interoperability, "aintainability, portability, reliability, reusability, robustness, testability, and usability.
8rite these to be specific, -uantitative, and verifiable when possible. 4t the least, clarify the relative
preferences for various attributes, such as ease of use over ease of learning.>
5. Other Requirements
<Define any other re-uire"ents not covered elsewhere in the SRS. /hese "ight include database
re-uire"ents, e!ternal &hardware, software, or co""unication' interface re-uire"ents,
internationali#ation re-uire"ents, legal re-uire"ents, and reuse ob%ectives for the pro%ect.>
<Team #> SRS <Version #> Page 4
<Project Name>
Appendix A: Glossary
<Define all the ter"s necessary to properly interpret the SRS, including acrony"s and
abbreviations. 9ou "ay wish to build a separate glossary that spans "ultiple pro%ects or the entire
organi#ation, and %ust include ter"s specific to a single pro%ect in each SRS.>
<Team #> SRS <Version #> Page 5
<Project Name>
Appendix B: Analysis Models
<,nclude the following analysis "odels0 use3case diagra", entity3relationship diagra", class
diagra", se-uence diagra".>
<Team #> SRS <Version #> Page 6
<Project Name>
Appendix C: Design Models
< ,nclude the following design "odel0 co"ponent diagra", deploy"ent diagra".>
<Team #> SRS <Version #> Page 7
<Project Name>
Appendix D: Screenshots
< ,nclude all screenshots of your software application2s graphical user interface.>
<Team #> SRS <Version #> Page 8
<Project Name>
Appendix E: Test Cases
< ill out the following te"plate for each test case.>
Identifier TC-1
Priority <Choose one from {High, Medium, Low}>
Related
requirementss!
<Include use-cse iden!ifier"s# for func!ionl
re$uiremen!"s# nd %&% sec!ion'su(-sec!ion
num(er"s# for o!her re$uiremen!"s#)>
S"ort description

Pre-conditions!

Input data

#etailed steps

$%pected results!

Post-conditions!

Table 2: TC-1
<Team #> SRS <Version #> Page 9
<Project Name>
Appendix F: IV & V Report
(Independent verification & validation)
I& ' & Resource
*me %ign!ure
S# #efect #escription (ri)in Sta)e Status
*i% Time
+ours ,inutes
1
+
,

Table : !ist o" non-tri#ial $e"ects

<Team #> SRS <Version #> Page 10
<Project Name>
CLASSIFICATION OF SRS
SRS VER. 1
(After 03 Weeks) Submission Date: 22-4-2014.
1. Introduction................................................................................................................................1
2. Overall Description.................................................................................................................... 2
3. Functional Requirements.......................................................................................................... 3
4. Nonfunctional Requirements.................................................................................................... 3
5. Other Requirements.................................................................................................................. 4
<Team #> SRS <Version #> Page 11
<Project Name>
SRS VER. 2
Submission Date: 03-06-2014.
1. Introduction................................................................................................................................1
2. Overall Description.................................................................................................................... 2
3. Functional Requirements.......................................................................................................... 3
4. Nonfunctional Requirements.................................................................................................... 3
5. Other Requirements.................................................................................................................. 4
'Core (eat#res i&)le&ented*
<Team #> SRS <Version #> Page 12
<Project Name>
Final Documentation
Submission Date: 01-7-2014.
1. Introduction................................................................................................................................1
2. Overall Description.................................................................................................................... 2
3. Functional Requirements.......................................................................................................... 3
4. Nonfunctional Requirements.................................................................................................... 3
5. Other Requirements.................................................................................................................. 4
(Complete Documentation with final working product)
<Team #> SRS <Version #> Page 13