Difference between revisions of "RICM4 2017 2018 - IGreenHouse / SRS"
Jump to navigation
Jump to search
| Line 32: | Line 32: | ||
==2.3 User characteristics== |
==2.3 User characteristics== |
||
==2.4 General constraints== |
==2.4 General constraints== |
||
| + | |||
| + | CHARO |
||
| + | |||
==2.5 Assumptions and dependencies== |
==2.5 Assumptions and dependencies== |
||
=3.Specific requirements, covering functional, non-functional and interface requirements= |
=3.Specific requirements, covering functional, non-functional and interface requirements= |
||
Revision as of 11:54, 5 February 2018
| Version | Date | Authors | Description | Validator | Validation Date | |
|---|---|---|---|---|---|---|
| 0.1.0 | 05/02/2018 | SURIER GAROFALO Aurélien, FERREIRA Joffrey, OZENDA Thomas | TBC | TBC | TBC |
1. Introduction
1.1 Purpose of the requirements document
1.2 Scope of the product
1.3 Definitions, acronyms and abbreviations
1.4 References
1.5 Overview of the remainder of the document
2. General description
2.1 Product perspective
2.2 Product functions
2.3 User characteristics
2.4 General constraints
CHARO
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: