Professional Documents
Culture Documents
Specification
for
<Project>
Version <X.X>
Prepared by
<student #>
<student #>
<student #>
<student #>
<student #>
Instructor:
Course:
Lab Section:
Teaching Assistant:
Date:
<e-mail>
<e-mail>
<e-mail>
<e-mail>
<e-mail>
Contents
REVISIONS................................................................................................................................................................III
SoftwareRequirementsSpecificationfor<Project>
1
INTRODUCTION................................................................................................................................................1
1.1
1.2
1.3
1.4
1.5
1.6
PRODUCT PERSPECTIVE...................................................................................................................... 3
PRODUCT FUNCTIONALITY................................................................................................................... 3
USERS AND CHARACTERISTICS............................................................................................................ 3
OPERATING ENVIRONMENT.................................................................................................................. 3
DESIGN AND IMPLEMENTATION CONSTRAINTS......................................................................................4
USER DOCUMENTATION....................................................................................................................... 4
ASSUMPTIONS AND DEPENDENCIES..................................................................................................... 4
SPECIFIC REQUIREMENTS...........................................................................................................................5
3.1
3.2
3.3
DOCUMENT PURPOSE.................................................................................................................................1
PRODUCT SCOPE................................................................................................................................ 1
INTENDED AUDIENCE AND DOCUMENT OVERVIEW ...............................................................................1
DEFINITIONS, ACRONYMS AND ABBREVIATIONS....................................................................................1
DOCUMENT CONVENTIONS.................................................................................................................. 1
REFERENCES AND ACKNOWLEDGMENTS.............................................................................................. 2
OVERALL DESCRIPTION...............................................................................................................................3
2.1
2.2
2.3
2.4
2.5
2.6
2.7
Pageii
PERFORMANCE REQUIREMENTS.......................................................................................................... 7
SAFETY AND SECURITY REQUIREMENTS.............................................................................................. 7
SOFTWARE QUALITY ATTRIBUTES....................................................................................................... 7
OTHER REQUIREMENTS...............................................................................................................................8
Revisions
Version
Primary Author(s)
Description of Version
Draft Type
and
Number
Full Name
Date Completed
00/00/00
SoftwareRequirementsSpecificationfor<Project>
Pageiii
<In this template you will find text bounded by the <> symbols. This text appears in italics and
is intended to guide you through the template and provide explanations regarding the different
sections in this document. There are two types of comments in this document. These
comments that are in black are intended specifically for that course. These comments that are
in blue are more general and apply to any SRS. Please, make sure to delete all of the
comments before submitting the document.
The explanations provided below, do not cover all of the material, but merely, the general
nature of the information you would usually find in SRS documents. It is based on the IEEE
requirements and was adapted specifically for the needs of Software Engineering 3K04/3M04
courses. Most of the sections in this template are required sections, i.e. you must include them
in your version of the document. Failure to do so will result in marks deductions. Optional
sections will be explicitly marked as optional.
SoftwareRequirementsSpecificationfor<Project>
Page1
1 Introduction
<TO DO: Please provide a brief introduction to your project and a brief overview of what the
reader will find in this section.>
SoftwareRequirementsSpecificationfor<Project>
Page2
SoftwareRequirementsSpecificationfor<Project>
Page3
2 Overall Description
2.1 Product Perspective
<Describe the context and origin of the product being specified in this SRS. For example, state
whether this product is a follow-on member of a product family, a replacement for certain existing
systems, or a new, self-contained product. If the SRS defines a component of a larger system,
relate the requirements of the larger system to the functionality of this software and identify
interfaces between the two. In this part, make sure to include a simple diagram that shows the
major components of the overall system, subsystem interconnections, and external interface . In
this section it is crucial that you will be creative and provide as much information as possible.
TO DO: Provide at least one paragraph describing product perspective. Provide a general
diagram that will illustrate how your product interacts with the environment and in what context it
is being used.>
SoftwareRequirementsSpecificationfor<Project>
Page4
SoftwareRequirementsSpecificationfor<Project>
Page5
3 Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
<Describe the logical characteristics of each interface between the software product and the
users. This may include sample screen images, any GUI standards or product family style guides
that are to be followed, screen layout constraints, standard buttons and functions (e.g., Cancel)
that will appear on every screen, error message display standards, and so on. Define the
software components for which a user interface is needed.
TO DO: The least you can do for this section is to describe in words the different User Interfaces
and the different screens that will be available to the user. Those who will be able to provide
optional Graphical User Interface screenshots, will be rewarded by extra marks.>
SoftwareRequirementsSpecificationfor<Project>
Page6
specify the exact encryption standards, but rather, specify the fact that the data will be encrypted
and name what standards you consider using. >
SoftwareRequirementsSpecificationfor<Project>
Page7
SoftwareRequirementsSpecificationfor<Project>
Page8
5 Other Requirements
<This section is Optional. Define any other requirements not covered elsewhere in the SRS. This
might include database requirements, internationalization requirements, legal requirements, reuse
objectives for the project, and so on. Add any new sections that are pertinent to the project.>
SoftwareRequirementsSpecificationfor<Project>
Page9
SoftwareRequirementsSpecificationfor<Project>
Page10