Proj-2013-2014-flying-3Dscan: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 79: | Line 79: | ||
=Product evolution= |
=Product evolution= |
||
=Progress= |
=Progress= |
||
==Week 0== |
==Week 0(Jan 13th - Jan 19th) == |
||
==Week 1== |
==Week 1(Jan 20th - Jan 26th) == |
||
==Week 2(Jan 27th - Feb 2nd) == |
|||
=Appendices= |
=Appendices= |
||
=Index= |
=Index= |
||
Revision as of 11:40, 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
General description
Product perspective
Product functions
User characteristics
General constraints
Assumptions and dependencies
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: