Difference between revisions of "Proj-2013-2014-flying-3Dscan"
Jump to navigation
Jump to search
| Line 28: | Line 28: | ||
| − | = |
+ | = Introduction= |
| − | == |
+ | == Purpose of the requirements document== |
| − | == |
+ | == Scope of the product== |
| − | == |
+ | == Definitions, acronyms and abbreviations== |
| − | == |
+ | == References== |
| − | == |
+ | == Overview of the remainder of the document== |
| + | = Team = |
||
| + | *Tutors : Olivier Richard |
||
| + | *Members : [[User:Kai GUO|GUO Kai]] , [[User:Xuan SUN|SUN Xuan]], [[User:Zhengmeng ZHANG|ZHANG Zhengmeng]] |
||
=2. General description= |
=2. General description= |
||
==2.1 Product perspective== |
==2.1 Product perspective== |
||
Revision as of 13:31, 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
Purpose of the requirements document
Scope of the product
Definitions, acronyms and abbreviations
References
Overview of the remainder of the document
Team
- Tutors : Olivier Richard
- Members : GUO Kai , SUN Xuan, ZHANG Zhengmeng
2. General description
2.1 Product perspective
2.2 Product functions
2.3 User characteristics
2.4 General constraints
2.5 Assumptions and dependencies
3.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.
3.1 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: