Format of SRS &SDD
(Prepared by using ISO 9001 quality standard manual)
< Project name >
Software Requirements and Design
Specification
Version X.0
<date>
1. Introduction
1.1
Methodology
Mention the title of methodology. This may be any process model. For example: Unified Rational
Process. Also describe briefly about the model (Maximum 10 lines) with diagram and justification for
choosing the model with respect to your application interms of few bullet points.
1.2
Purpose
In this section, mention all functional and non functional requirements.
I have discussed in the class about functional and non functional requirements. Pls refer your class note.
1.3
Document Convention
It tells about the formatting conventions, styles and size of main headings, sub headings and rest of the
document
1.4
Intended Audience and Reading suggestion
1.5
Scope
---------------------Rajkumar S AP(Sr)----------------------
Detailed features such as different actors and their roles
1.6
Definitions, Acronyms and abbreviations
Example:
UML
Unified Modeling Language. is a standard language for writing software blueprints. The
UML may be used to visualize, specify, construct and document
XML
Extensible Markup Language. is a text based format that let developers describe, deliver and
exchange structured data between a range of applications to client for display and manipulation.
< Project name >
Software Requirements and Design
Specification
1.7
Version X.0
<date>
References
1. Roger S.Pressman, Software Engineering - A Practitioners Approach, McGrawHill
International Edition, 5th edition, 2001.
2. http:\\www.example.com\example.html
3. L. C. Parra, Reconstruction of cone-beam projections from Compton scattered data,
IEEE Trans. Nucl. Sci., vol. 47, no. 4, pp. 15431550,Aug. 2010.
1.8
Overview
---------------------Rajkumar S AP(Sr)----------------------
Drawbacks in existing and overcome by proposal
2. The Overall description
2.1
Product Perspective
Brief about different modules of your project-For example: Login module---2 lines about the purpose of
the module
2.2
Product features
This division is same as that of 1.5. Detailed features such as different actors and their roles
2.3
User classes and characteristics
For example: The primary user will be the students and faculty of educational institutions; other user
may include the non-teaching staffs. The administrator will be the librarian who will be responsible for
the customers profile database
2.4
Operating Environment
Example:
Hardware
: Intel core i3, 2.3 GHz, 2 GB RAM, 500 GB HDD, 1.44 MB FDD
Software
: C++, Microsoft Access 2011 or later ---------------------Rajkumar S AP(Sr)----------------------
Front end
: C++
Back end
: Microsoft Access 2011 or later
Operating System : Windows 7.0 or later
< Project name >
Software Requirements and Design
Specification
2.5
Version X.0
<date>
Design and Implementation constraints
Example:
The computer with C++ installed can only run the project.
The administrator should have prior knowledge of handling the database.
The database should be highly secured and only the administrator can access the database.
2.6
User documentation
This division deals with the user manual
2.7
Assumptions and dependencies
For ex:
---------------------Rajkumar S AP(Sr)----------------------
This software is platform independent.
It will run only on specified hardware and software configuration such as Intel I3 with 2
GB RAM or higher and OS Windows 7 or later version and Turbo C++ compiler.
The members should have the basic knowledge in computers.
3. External Interface requirements
3.1 Hardware Interfaces
Example :
Client Side
Internet Explorer
6
Processor
RAM
Disk Space
All Intel or AMD - 1
GHZ
256 MB
100 MB
5.0 Megapixel Camera
Web cam software
Server Side
Processor
RAD
DB2 - 9.5
All Intel or AMD - 2
GHZ
RAM
Disk Space
2 GB
3.5 GB
500 MB
512 MB
(Excluding Data
Size)
< Project name >
Software Requirements and Design
Specification
Version X.0
<date>
3.2 Software Interfaces
Front end: Web Browser, Operating System (any)
Server-end: Web Server(WASCE),Operating System (any)
Development-end:RAD (J2EE, Java, Java Bean, Servlets, HTML, XML, AJAX), Operating System
(any)
Back-end:DB2
---------------------Rajkumar S AP(Sr)----------------------
3.3 User Interfaces
This section is focused about graphical interface module.
3.4 Communication Interfaces
This section deals with the protocols involved.
3.5 Constraints
It is related to interface and normal constraints
4. Analysis models
(In this section, place all the modeling diagrams so far we discussed in the class)
4.1 Use case Diagram
4.2 Class Diagram
4.3 Sequence diagram
---------------------Rajkumar S AP(Sr)----------------------
4.4 Collaboration diagram
4.5 Statechart diagram
4.6 Activity diagram
4.7 Component Diagram
4.8 Deployment Diagram
Version X.0
< Project name >
Software Requirements Specification
<date>
5. System features
5.1
Functional Requirements
5.2
Non Functional Requirements
5.2.1 Reliability
5.2.2 Availability
5.2.3 Security
5.2.4 Maintainability
5.2.5 Portability
6. Document Approval
7. Supporting Information
7.1
Appendix-A
7.2
Appendix-B
---------------------Rajkumar S AP(Sr)----------------------
