SRS - Site d'annonces: Difference between revisions
Jump to navigation
Jump to search
Regis.Ramel (talk | contribs) No edit summary |
Regis.Ramel (talk | contribs) |
||
| Line 10: | Line 10: | ||
=1. Introduction= |
=1. Introduction= |
||
== 1.1 Objectif du projet == |
|||
==1.1 Purpose of the requirements document== |
|||
Le but du projet est de réaliser un site d'annonce inspiré d'eBay, le bon coin, etc. |
|||
This Software Requirements Specification (SRS) identifies the requirements for project ECOM 2016. |
|||
Le site permet aux particuliers de déposer des annonces, et de chercher un article parmi les annonces déposées. |
|||
In case of a open source project, we must present the requirement to others potential contributors. This document is a guideline about the functionalities offered and the problems that the system solves. |
|||
Le site n'affiche aucun prix, il se charge simplement de mettre le propriétaire et les acheteurs potentiels en relation pour procéder à la transaction. |
|||
==1.2 Scope of the product== |
==1.2 Scope of the product== |
||
Revision as of 15:43, 4 October 2016
Voici la fiche SRS du projet ECOM 2016-2017 Site d'annonces.
Équipe :
- NOUGUIER Thibaut (Chef de projet)
- RAMEL Régis (Scrum Master)
- HATTINGUAIS Julian
- NIOGRET Edwin
1. Introduction
1.1 Objectif du projet
Le but du projet est de réaliser un site d'annonce inspiré d'eBay, le bon coin, etc. Le site permet aux particuliers de déposer des annonces, et de chercher un article parmi les annonces déposées. Le site n'affiche aucun prix, il se charge simplement de mettre le propriétaire et les acheteurs potentiels en relation pour procéder à la transaction.
1.2 Scope of the product
1.3 Definitions, acronyms and abbreviations
1.4 References
- The main page of the project: Proj-2016-2017-ECOM-5
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:
4. Product evolution
5. Appendices
5.1. SRS structure
The document is based on template of the Software Requirements Specification (SRS) inspired of the IEEE/ANSI 830-1998 Standard.
References:
- 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