Difference between revisions of "SRS-Template"
Jump to navigation
Jump to search
m |
|||
Line 31: | Line 31: | ||
=1. Introduction= |
=1. Introduction= |
||
==1.1 Purpose of the requirements document== |
==1.1 Purpose of the requirements document== |
||
+ | |||
− | L'objectif de ce document est de présenter une description détaillée de la plateforme COOPCYCLE de livraison utilisable par les |
||
− | coopératives de livreurs à vélo. Il expliquera l'objectif et les caractéristiques du logiciel, le |
||
− | les interfaces du logiciel, ce que le logiciel fera et les contraintes sous lesquelles |
||
− | il doit fonctionner. Ce document est destiné aux utilisateurs du logiciel et aussi |
||
− | des développeurs potentiels. |
||
==1.2 Scope of the product== |
==1.2 Scope of the product== |
||
+ | |||
− | cOOPCYCLE un logiciel de mise en relation entre clients, commerçants (restaurateurs, |
||
− | artisans ...) et livreurs à vélo. Sur smartphone ou via votre navigateur pour poste de travail vous |
||
− | pouvez passer commande et vous faire livrer. |
||
==1.3 Definitions, acronyms and abbreviations== |
==1.3 Definitions, acronyms and abbreviations== |
Revision as of 19:18, 10 February 2020
The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.
Read first:
- http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
- http://en.wikipedia.org/wiki/Software_requirements_specification
- IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998
Version | Date | Authors | Description | Validator | Validation Date | |
---|---|---|---|---|---|---|
0.1.0 | TBC | TBC | 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
Site web Coopcycle https://coopcycle.org/fr/
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
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: