DD1363, Mjukvarukonstruktion

Aktuell kursomgång: period 2-4 07/08

Kursledare: Rand Waltzman
Datorpostadress(er): rand@nada.kth.se

 

Requirements Document (RD)

The requirements document must have the following sections:

 

  1. Preface
    1. Define expected readership of the document.
    2. Describe version history.

                                                               i.      Rational for the creation of each new version.

                                                             ii.      A summary of the changes made in each version.

  1. Introduction
    1. Describe the need for the system.
    2. Briefly describe its functions and how it will work with other systems.
    3. Describe how the system fits in with the business or strategic objectives of the commisioning organization.
  2. Glossary
    1. Define the technical terms used in the document.
    2. Do not make assumptions about the experience or expertise of the reader.
  3. User requirements definition
    1. Describe the services provided for the user, i.e., the functional requirements.
    2. Describe the non-functional requirements.
    3. Descriptions may use NL, diagrams, or other notations understandable by the customer. 
    4. Behavioral descriptions must be specified using use cases.
    5. Specify any product or process standards that must be followed.
  4. System architecture
    1. Present a high level overview of the anticipated system architecture.
    2. Show the distribution of functions across system modules.
    3. Highlight architectural components that are reused.
  5. System requirements specification
    1. Describe the functional and non-functional requirements in more detail than the User Requirements Definition section.
    2. Behavioral descriptions must be specified with use cases.
    3. Show the trace back to the user requirements from each of the system requirements.
    4. Add any additional necessary details to the non-functional requirements

                                                               i.      E.g., interfaces to other systems might be defined.

  1. System evolution
    1. Describe the fundamental assumptions on which the system is based.
    2. Specify anticipated changes due to

                                                               i.      Hardware evolution

                                                             ii.      Changing user needs

                                                            iii.      Etc.

  1. Appendices
    1. Provide detailed, specific information which is related to the application which is being developed.
    2. Examples

                                                               i.      Hardware descriptions

                                                             ii.      Minimal and optimal configurations for the system.

                                                            iii.      Data base descriptions

                                                           iv.      Logical organization of the data

                                                             v.      Relationships between the data

  1. Index
    1. Several indexes may be included

                                                               i.      Normal alphabetic index

                                                             ii.      Index of diagrams

                                                            iii.      Index of functions

                                                           iv.      Etc.

 

 

 

^Upp till Nadas kurser.

Sidansvarig: <rand@nada.kth.se>
Tekniskt stöd: <webmaster@nada.kth.se>