Software Requirements

Specification and Design

for

<Project Name>

Version <X.X>

Prepared by

<name> <student #> Section #

<name> <student #> Section #
<name> <student #> Section #
<name> <student #> Section #
<name> <student #> Section #
<name> <student #> Section #
<name> <student #> Section #

Instructor: <place your instructor’s name here>

Course: <place your course name here>

Date: <place the date of submission here>

Table of Contents
Software Requirements Specification and design for <Project> Page ii

1 INTRODUCTION................................................................................................................................................1

1.1 PRODUCT SCOPE........................................................................................................................................1

1.2 DEFINITIONS, ACRONYMS AND ABBREVIATIONS...................................................................................1
2 STAKEHOLDERS & OPERATING ENVIRONMENT.................................................................................1
2.1 END USERS AND CHARACTERISTICS.................................................................................................... 1
2.2 SYSTEM STAKEHOLDERS..................................................................................................................... 1
2.3 OPERATING ENVIRONMENT.................................................................................................................. 2
3 SPECIFIC REQUIREMENTS...........................................................................................................................2
3.1 FUNCTIONAL REQUIREMENTS............................................................................................................... 2
3.2 USE CASE DIAGRAM............................................................................................................................ 2
4 NON-FUNCTIONAL REQUIREMENTS.........................................................................................................2
4.1 SOFTWARE QUALITY ATTRIBUTES........................................................................................................ 2
5 OTHER REQUIREMENTS...............................................................................................................................3

6 REQUIREMENTS ANALYSIS.........................................................................................................................3
6.1 SEQUENCE DIAGRAM............................................................................................................................. 3
7 SOFTWARE ARCHITECTURE.......................................................................................................................3

8 DATA DESIGN...................................................................................................................................................3
8.1 PROGRAM STRUCTURE (CLASS DIAGRAM).............................................................................................. 3
8.2 <OBJECT CLASS NAME IF ANY> OR A DESCRIPTION FOR CLASS 1............................................................3
8.3 <OBJECT CLASS NAME IF ANY> OR A DESCRIPTION FOR CLASS 2............................................................4
9 GRAPHICAL USER INTERFACE DESIGN..................................................................................................4

10 References and acknowledgment....................................................................................................................4

Software Requirements Specification for <Project> Page 1

1 Introduction
<TO DO: Please provide a brief introduction to your project and a brief overview of what the
reader will find in this document.
Identify the product and the purpose of this document. This should including relevant benefits,
objectives, and goals.
>

1.1 Product Scope

<Provide a short description of the software being specified and its purpose; describe the scope
of the product that is covered by this SRS, particularly if this SRS describes only part of the
system or a single subsystem.
TO DO: 1-2 paragraphs describing the scope of the product. Make sure to describe how it is
associated with other product or subsystems.>

1.2 Definitions, Acronyms and Abbreviations

<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations.
TO DO: Please provide a list of all abbreviations and acronyms used in this document sorted in
alphabetical order.>

2 STAKEHOLDERS & OPERATING ENVIRONMENT

2.1 End Users and Characteristics

<Identify the various users that you anticipate will use this product. Users may be differentiated
based on frequency of use, subset of product functions used, technical expertise, security or
privilege levels, educational level, or experience.
TO DO:
1. Describe the characteristics of each user. Certain requirements may affect (relate) only to
certain users.
2. Distinguish the most important users for this product from those who are less important to
satisfy.>

2.2 System Stakeholders

You should build a list of your system stakeholders. You should define the role of each
stakeholder in the big system.
Software Requirements Specification for <Project> Page 2

2.3 Operating Environment

<Describe the environment in which the software will operate, including the hardware platform,
operating system and versions, and any other software components or applications with which it
must peacefully coexist.
TO DO: in at least one paragraph, describe the environment your system will have to operate in.
Make sure to include the minimum platform requirements for your system. >

3 Specific Requirements

3.1 Functional Requirements

<Functional requirements capture the intended behavior of the system. This behavior may be
expressed as services, tasks or functions the system is required to perform. (System
Requirements)
TO DO: Break the functional requirements to several functional areas and divide this section into
subsections accordingly. Provide a detailed list of all product operations related to these
functional areas.

3.2 Use Case Diagram

<A use case defines a goal-oriented set of interactions between actors and the system under
consideration.
TO DO: Provide a use case diagram which will encapsulate the entire system and all possible
actors. Do not include detailed use case descriptions, but make sure to include a short
description of what every use-case is, who are the actors in your diagram>

4 Non-functional Requirements

4.1 Software Quality Attributes

<Specify any quality characteristics for the product that will be important to either the customers
or the developers. Some to consider are: performance, safety, security, adaptability, availability,
correctness, flexibility, interoperability, maintainability, portability, reliability, reusability,
robustness, testability, and usability. >
 Software Requirements Specification for <Project> Page 3

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.>

6 Requirements Analysis

6.1 Sequence diagram

Choose two main usecases and draw a sequence diagram for each of them

drawings of the Sequence diagram are presented here

7 Software architecture
where you identify the overall structure of the system, the principal components (sometimes
called sub-systems or modules), their relationships and how they are distributed. In this part,
make sure to include a simple diagram that shows the major components of the overall system,
subsystem interconnections.

8 Data design

8.1 Program Structure (class diagram)

A drawing of the class diagram is presented here

8.2 <object class name if any> or a Description for Class 1

A detailed description of each class contained within the architecture is presented. You
should list both the state and the behavior of each object class. You should explain each
attribute and each method. Section 3.1 should be repeated for each object class.
 Software Requirements Specification for <Project> Page 4
8.2.1 <object-name, if any> or Object Class 1: The State

A detail description for all attributes and/or member fields.

8.2.2 <object-name, if any> or Object Class 1: The Behaviour:

A detailed description for each method within the object class.

8.3 <object class name if any> or a Description for Class 2

Repeat the same as for class 1

8.3.1 The State

8.3.2 The Behaviour

.
.
.

9 Graphical User Interface Design

<Describe the logical characteristics of each interface between the software product and the
users. This should include sample screen images, any GUI standards.
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(Graphical User Interface
screenshots).>

You should describe each interface briefly.

10References and acknowledgment

<List any other documents or Web addresses to which this document refers. These may include
user interface style guides, contracts, standards, system requirements specifications, use case
documents, or a vision and scope document.>