ECOM RICM5 Groupe2 2017 SRS

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

=1.  Introduction=

1.1 Purpose of the requirements document
......

1.2 Scope of the product
......

1.3 Definitions, acronyms and abbreviations
......

1.4 References
Docker installation : ....

1.5 Overview of the remainder of the document
=2.  General description=

2.1 Product perspective
....

2.2 Product functions
The website should make possible to :
 * View restaurants
 * Filter the results
 * Choose one of them and see its menus
 * Choose date and number of meals
 * Reserved and payed
 * Send confirmation by email to the user

2.3 User characteristics
Users of the website will be :
 * People from 15 years old to 99 years old who want to reserve a seat
 * Chef of a restaurant in order to check his restaurant and the competition

2.4 General constraints
Design a website that is :
 * easy to adapt to new restaurants
 * easy to use by anyone (novice as expert)
 * responsive

2.5 Assumptions and dependencies
.....

=3.Specific requirements, covering functional, non-functional and interface requirements= ......

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:

=4. Product evolution=

=5. Appendices=

=6. Index=