Download C# application development SRS template and more Study Guides, Projects, Research Applied Computing in PDF only on Docsity!
Software Requirements
Specification
for
Version <X.X>
Prepared by
Group Name: < place your group name here >
<student #> <e-mail>
<student #> <e-mail>
<student #> <e-mail>
<student #> <e-mail>
<student #> <e-mail>
Instructor: < place your instructor’s name here>
Course:
Date:
Software Requirements Specification for Page ii Contents CONTENTS.................................................................................................................................................................II REVISIONS.................................................................................................................................................................II 1 INTRODUCTION (P1)....................................................................................................................................... 1 1.1 DOCUMENT PURPOSE................................................................................................................................. 1 1.2 PRODUCT SCOPE................................................................................................................................ 1 1.3 INTENDED AUDIENCE AND DOCUMENT OVERVIEW............................................................................... 1 1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS................................................................................... 1 1.5 REFERENCES AND ACKNOWLEDGMENTS.............................................................................................. 1 2 OVERALL DESCRIPTION (P1)...................................................................................................................... 2 2.1 PRODUCT OVERVIEW........................................................................................................................... 2 2.2 PRODUCT FUNCTIONALITY................................................................................................................... 2 3 SPECIFIC REQUIREMENTS (P1 & M1)....................................................................................................... 2 3.1 FUNCTIONAL REQUIREMENTS (P1)...................................................................................................... 2 3.2 USE CASE MODEL (P1)....................................................................................................................... 3 3.3 WIREFLOW (P1).................................................................................................................................... 3 4 TECHNICAL DESIGN (M1).............................................................................................................................. 5 4.1 ENTITY RELATIONSHIP DIAGRAM (ERD)............................................................................................... 5 4.2 CLASS DIAGRAM.................................................................................................................................. 5 4.3 ACTIVITY DIAGRAM............................................................................................................................. 5 4.4 GANTT CHART...................................................................................................................................... 5 5 RISK ASSESSMENT (P2)................................................................................................................................ 5 5.1 Risk Assessment.......................................................................................................................................... 5 Revisions Version Primary Author(s) Description of Version Date Completed Draft Type and Number Full Name Information about the revision. This table does not need to be filled in whenever a document is touched, only when the version is being upgraded.
2 Overall Description (P1)
2.1 Product Overview
<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. This is not a formal diagram, but rather something that is used to illustrate the
product at a high level.>
2.2 Product Functionality
<Summarize the major functions the product must perform or must let the user perform. Details
will be provided in Section 3, so only a high level summary is needed here. These can be at the
level given in the project description.>
TO DO:
1. Provide a bulleted list of all the major functions of the system
3 Specific Requirements (P1 & M1)
3.1 Functional Requirements (P1)
< 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.
ID AS A < TYPE OF USER
I WANT TO < PERFORM SOME TASK > SO THAT I CAN < ACHIEVE SOME GOAL > 1 Project Manager View a status report from each team member Ensure the project stays on track. 2 Employee Be reminded of upcoming deadlines Complete my tasks on time. 3 Director See the big picture view of department work Stay in the loop.
3.2 Use Case Model (P1)
TO DO: Provide a use case diagram that will encapsulate the entire system and all actors.
3.3 Wireflow (P1)
<Describe the logical characteristics of each interface between the software product and the
users. For your project, you only need to be concerned with the main thermostat (not the mobile
app) and can use the graphic from the project description as the basis for your user interface..
TO DO: Provide the graphic for the thermostat user interface and provide a basic description as to
how users will interact (e.g. tough screen, menus, etc.).>
4 Technical Design (M1)
4.1 Entity Relationship Diagram (ERD)
4.2 Class Diagram
4.3 Activity Diagram
4.4 Gantt Chart
5 Risk Assessment (P2)
5.1 Risk Assessment
Identify and list Hazards List Current Risk Controls Risk Rating List Additional Controls (if any - where current controls are not adequately managing the level of ris k ) 1 2 3
