ECOM RICM5 Groupe2 2017 SRS
<<<< Retour The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.
| Version | Date | Authors | Description | Validator | Validation Date | |
|---|---|---|---|---|---|---|
| 0.2.0 | 16/12/2017 | E.Allard L.Cochinho A.Delise L.Guerry L.Rocher | TBC | TBC | TBC |
1. Introduction
1.1 Purpose of the requirements document
A software requirements specification (SRS) is a description of a software system to be developed. It lays out functional and non-functional requirements, and may include a set of use cases that describe user interactions that the software must provide.
1.2 Scope of the product
The scope of our product is to provide a responsive website which is able to present restaurants to the user.
Users of the application will be able to choose the type of filters they want to applied for their research.
They can also see the different menus of one restaurant and will be able to book one of them for 1 ou many persons.
1.3 Definitions, acronyms and abbreviations
E-commerce : electronic commerce is a transaction of buying or selling online.
Users : People who interact with the application.
Docker (software) : Docker is an open-source project that automates the deployment of applications inside software containers.
1.4 References
Docker installation : [1]
1.5 Overview of the remainder of the document
2. General description
2.1 Product perspective
The aim of the project is to provide a e-commerce website able to show restaurants to the user and let him choose a restaurant to book.
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
- Book 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
We assume that restaurant will put their informations to the website.
3.Specific requirements, covering functional, non-functional and interface requirements
- server to deploy the website
- specify logical database requirements,
- design constraints : Human machine interactions, graphic rules to follow
- list of restaurant, with detailled menus and prices
4. Product evolution
Later the website as to be able to be modified by the restaurant chiefs (for the informations about their restaurant). Indeed all restaurant officer as to be able to manage their tables and reservations.