Chat with us, powered by LiveChat SRS - STUDENT SOLUTION USA

Software Requirements Specification

for

Version 1.0 approved

Prepared by

Table of Contents

iiTable of Contents

Revision History
ii

1.
Introduction
1

1.1
Purpose
1
1.2
Document Conventions
1
1.3
Intended Audience and Reading Suggestions
1
1.4
Product Scope
1
1.5
References
1

2.
Overall Description
2

2.1
Product Perspective
2
2.2
Product Functions
2
2.3
User Classes and Characteristics
2
2.4
Operating Environment
2
2.5
Design and Implementation Constraints
2
2.6
User Documentation
2
2.7
Assumptions and Dependencies
3

3.
External Interface Requirements
3

3.1
User Interfaces
3
3.2
Hardware Interfaces
3
3.3
Software Interfaces
3
3.4
Communications Interfaces
3

4.
System Features
4

4.1
System Feature 1
4
4.2
System Feature 2 (and so on)
4

5.
Other Nonfunctional Requirements
4

5.1
Performance Requirements
4
5.2
Safety Requirements
5
5.3
Security Requirements
5
5.4
Software Quality Attributes
5
5.5
Business Rules
5

6.
Other Requirements
5

Appendix A: Glossary
5

Appendix B: Analysis Models
5

Appendix C: To Be Determined List
6

Revision History

Name

Date

Reason For Changes

Version

1. Introduction

1.1 Purpose

1.2 Document Conventions

1.3 Intended Audience and Reading Suggestions

1.4 Product Scope

1.5 References

2. Overall Description

2.1 Product Perspective

2.2 Product Functions

2.3 User Classes and Characteristics

2.4 Operating Environment

2.5 Design and Implementation Constraints

2.6 User Documentation

2.7 Assumptions and Dependencies

3. External Interface Requirements

3.1 User Interfaces

3.2 Hardware Interfaces

3.3 Software Interfaces

3.4 Communications Interfaces

4. System Features

4.1 System Feature 1

4.1.1
Description and Priority

4.1.2
Stimulus/Response Sequences

4.1.3
Functional Requirements

REQ-1:

REQ-2:

4.2 System Feature 2 (and so on)

5. Other Nonfunctional Requirements

5.1 Performance Requirements

5.2 Safety Requirements

5.3 Security Requirements

5.4 Software Quality Attributes

5.5 Business Rules

6. Other Requirements

Appendix A: Glossary

Appendix B: Analysis Models

Appendix C: To Be Determined List

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.

Instructions

Purpose

The purpose of this assignment is for you to prepare an SRS (Software Requirements Specification) for the Case Study.

Directions

1. Use the attached SRS template to create a preliminary draft of a Software Requirements Specification for the Case Study proposed in your Week 2 Case Study.
2. Name your SRS like SRSDraftLastnameFirstname
3. Complete the Title Page, Sections 1, 2, 3, and 4. Do not change the formatting of the SRS template but rather just add your content and remove the instructions in the angle brackets <> after you have completed the section.
4. For the Appendix B Analysis Models you will choose whether you want to use the Structured Analysis and Design Technique or the Object oriented Analysis and Design Technique.
4.1 If you choose to use the Structured Analysis and Design Technique, you will develop a Level 0 Context DFD (Data Flow Diagram) and a Level 1 DFD for your Case Study. See the Contents for information on how to create these models.
4.2 If you choose to use the Object oriented Analysis and Design Technique, you will develop a Use Case Diagram and Detailed Description for the Use Cases for your Case Study. See the Contents for information on how to create these models.
5. For an example SRS see the Cafeteria Ordering System SRS.

SRS Specification

Use this template for your SRS: srs_template-ieee.doc.
Your submission will be graded using the following grading Rubric.

Program and Course Objectives

CO4: Describe Object Oriented Analysis and Design technique and the UML models

CO8: Apply the principles of systems analysis and design in the development of information systems

SLO (Program Objectives): Apply industry driven techniques for designing, developing, deploying, and securing enterprise applications on the desktop and on the Web.

SLO (Program Objectives): Demonstrate use of analytical, logical, and critical thinking to design, develop, and deploy effective Information Technology solutions.

Assessment Rubric

Exemplary 

Accomplished 

Developing 

Beginning 

Points Available

Comments

 

1. Title, Sections 1-4 of the SRS template are completed and provide meaningful technical specifications for your chosen system.

(50)
Student effectivelycompleted the assignment.

(40)
Student partiallycompleted the assignment.

(30)
The student provided limited and meaninglesssubstance completing the assignment.

(0)
Student failed to complete the assignment.

50

 

 

2. For Appendix B: SA Level 0 DFD or for OO Use Case Diagram are included and correctly model your system. 

(20)
Student effectivelycompleted the assignment.

(15)
Student partiallycompleted the assignment.

(10)
The student provided limited and meaninglesssubstance completing the assignment.

(0)
Student failed to complete the assignment.

20

 

 

3. For Appendix B:  Level 1 DFD or for OO Detailed use case descriptions are included and correctly model your system.

(20)
Student effectivelycompleted the assignment.

(15)
Student partiallycompleted the assignment.

(10)
The student provided limited and meaninglesssubstance completing the assignment.

(0)
Student failed to complete the assignment.

20

 

 

4.  Writing Format

Write the paper in APA format. Grammatical, spelling or punctuation—the writing is grammatically correct, clear and concise.  The response is well formulated and easy to read and understand.  Correct terminology was used when needed. See references below:

What is Plagiarism and How to Avoid It:  
http://www.youtube.com/watch?v=eIsLV9zOOe0

Writing Help: http://apus.libguides.com/c.php?g=241212&p=1603794

Purdue Online Writing Lab: https://owl.english.purdue.edu/owl/resource/560/01/

APA and MLA Citation Game Home Page: http://depts.washington.edu/trio/quest/citation/apa_mla_citation_game/

 

(10)
Student effectivelywrote the paper using provided format.

(8)
Student partiallywrote the paper using provided format.

(5)
Student wrote the paper with limited and meaninglessuse of provided format

(0)
Student failed to use provided format.

10

 

 

Total

100

 

 

Attachments

ENTD311_srs_template-ieee.doc

(57 KB)

error: Content is protected !!