CS 3802 - Introduction to Software Engineering
Software Requirements Specification
- Project Deliverable #3
Fall Semester 1999
DUE: 28 October 1999
TURN-IN:
2 copies of your document should be turned in. One copy will be graded
and the other will be given to your design team.
GOAL:
The purpose of this assignment is to prepare
a Software Requirements Specification. The document should present the
requirements and a system model for the educational game you are developing.
DESCRIPTION:
Write a Software Requirements Specification
including the following information:
-
Introduction
-
Project Overview/ Problem Statement
-
Document Overview
-
System Model
-
Choose a model that is most appropriate for the educational game you are
developing; your most likely options are Data Flow Diagrams, an Object
Model, or State Machine diagrams. (Be sure that the model you choose
is consistent with the analysis method you have chosen)
-
Provide a clean, electronic drawing of your model
-
Include explanatory text as needed
-
Functional Requirements
-
Be sure to state your requirements clearly.
-
Include a numbering scheme that will allow traceability.
-
You may provide a brief design rationale for
any requirement which you feel requires explanation for how and/or why
the requirement was derived.
-
Non-functional Requirements
-
Be sure to state your requirements clearly.
-
Include a numbering scheme that will allow traceability.
-
You may provide a brief design rationale for
any requirement which you feel requires explanation for how and/or why
the requirement was derived.
-
Also, remember to include system, performance,
and usability requirements in this section.
-
Validation Criteria
-
Requirements Validation: How do you know that
you have the right requirements? What steps did you take to make sure that
you had enough information? What steps did you take to make sure that you
had correct information?
-
Testing Plan Overview: How will you make sure
that your system is developed according to the requirements stated? How
will you make sure that your requirements are validated and verified throughout
the development process? You do not need to go into specific testing
plan strategies (i.e. white box, black box, etc.).
-
Appendix
-
Methodology Analysis: What analysis methodology
did you chose and why?
-
Elicitation Techniques: What elicitation techniques
did you use? What information were you seeking from each technique? Also,
include in this section any sample surveys, interview questions, etc. that
you used.
-
Sources & Bibliography
GRADING
CRITERIA
Back
to Project Information Page | Back to CS 3802
Home Page