Sie sind auf Seite 1von 2

PRACTICAL SRS DOCUMENT GENERATION

NO. 1 :
AIM: To generate SRS (Software Requirement Specification)
document for the project “ Course Scheduling System”

THEORY: In the context of computer-based systems (and software),


the term specification means different things to different
people. A specification can be a written document, a
graphical model, a formal mathematical model, a
collection of usage scenarios, a prototype, or any
combination of these.

Some suggest that a “standard template” [SOM97] should


be developed and used for a system specification, arguing
that this leads to requirements that are presented in a
consistent and therefore more understandable manner.
However, it is sometimes necessary to remain flexible
when a specification is to be developed. For large systems,
a written document, combining natural language
descriptions and graphical models may be the best
approach. However, usage scenarios may be all that are
required for smaller products or systems that reside within
well-understood technical environments.

The System Specification is the final work product


produced by the system and requirements engineer. It
serves as the foundation for hardware engineering,
software engineering, database engineering, and human
engineering. It describes the function and performance of
a computer-based system and the constraints that will
govern its development. The specification bounds each
allocated system element.
The System Specification also describes the information
(data and control) that is input to and output from the
system.

Characteristics of an SRS:

13
A good SRS is :

• Correct
• Complete
• Unambiguous
• Verifiable
• Consistent
• Ranked for importance and/or stability
• Modifiable
• Traceable

The general structure of SRS is :

1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
1.5 Overview
2. Overall Description
2.1 Product Perspective
2.2 Product Functions
2.3 User characteristics
2.4 General Constraints
2.5 Assumptions and Dependencies
3. Specific Requirements

CONCLUSION: We have generated an SRS document for the project “


Course Scheduling System ”

REFERENCES: 1. Software Engineering : By Pressman (5th Edition)

2. An integrated aproach to software engineering


Engineering : By Pankaj Jalote (3rd Edition)

14