Difference between revisions of "Proj-2013-2014-flying-3Dscan"
Jump to navigation
Jump to search
| Line 29: | Line 29: | ||
=Introduction= |
=Introduction= |
||
| + | ==...== |
||
| − | ==Purpose of the requirements document== |
||
| + | ==...== |
||
| − | ==Scope of the product== |
||
| − | ==Definitions, acronyms and abbreviations== |
||
| − | ==References== |
||
| − | ==Overview of the remainder of the document== |
||
= Team = |
= Team = |
||
*Tutors : Didier Donsez |
*Tutors : Didier Donsez |
||
*Members : GUO Kai , SUN Xuan , ZHANG Zhengmeng |
*Members : GUO Kai , SUN Xuan , ZHANG Zhengmeng |
||
=General description= |
=General description= |
||
| + | ==..== |
||
| − | ==Product perspective== |
||
| + | ==..== |
||
| − | ==Product functions== |
||
| − | ==User characteristics== |
||
| − | ==General constraints== |
||
| − | ==Assumptions and dependencies== |
||
=Specific requirements, covering functional, non-functional and interface requirements= |
=Specific requirements, covering functional, non-functional and interface requirements= |
||
* document external interfaces, |
* document external interfaces, |
||
| Line 49: | Line 43: | ||
* design constraints, |
* design constraints, |
||
* emergent system properties and quality characteristics. |
* emergent system properties and quality characteristics. |
||
| − | |||
==Requirement X.Y.Z (in Structured Natural Language)== |
==Requirement X.Y.Z (in Structured Natural Language)== |
||
'''Function''': |
'''Function''': |
||
Revision as of 13:49, 27 January 2014
The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.
Read first:
| Version | Date | Authors | Description | Validator | Validation Date | |
|---|---|---|---|---|---|---|
| 0.1.0 | TBC | TBC | TBC | TBC | TBC |
Introduction
...
...
Team
- Tutors : Didier Donsez
- Members : GUO Kai , SUN Xuan , ZHANG Zhengmeng
General description
..
..
Specific requirements, covering functional, non-functional and interface requirements
- document external interfaces,
- describe system functionality and performance
- specify logical database requirements,
- design constraints,
- emergent system properties and quality characteristics.
Requirement X.Y.Z (in Structured Natural Language)
Function:
Description:
Inputs:
Source:
Outputs:
Destination:
Action:
- Natural language sentences (with MUST, MAY, SHALL)
- Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
- Mathematical Notations
- Tabular notations for several (condition --> action) tuples
Non functional requirements:
Pre-condition:
Post-condition:
Side-effects: