ECOM RICM5 Groupe2 2017 SRS - Revision history

Louis.Cochinho at 14:34, 16 December 2017

2017-12-16T14:34:41Z

← Older revision		Revision as of 14:34, 16 December 2017
Line 1:		Line 1:
	[[ECOM RICM5 Groupe2 2017\|<<<< Retour]]		[[ECOM RICM5 Groupe2 2017\|<<<< Retour]]

	The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.		The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.

Louis.Cochinho at 14:34, 16 December 2017

2017-12-16T14:34:35Z

← Older revision		Revision as of 14:34, 16 December 2017
Line 1:		Line 1:
			[[ECOM RICM5 Groupe2 2017\|<<<< Retour]]
	The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.		The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.

Louis.Cochinho at 14:33, 16 December 2017

2017-12-16T14:33:55Z

← Older revision		Revision as of 14:33, 16 December 2017
Line 14:		Line 14:
	\|-		\|-
	!scope="row" \|		!scope="row" \|
	\| 0.1.0
	\| 12/12/2017
	\| E.Allard L.Cochinho A.Delise L.Guerry L.Rocher
	\| TBC
	\| TBC
	\| TBC

	\| 0.2.0		\| 0.2.0
	\| 16/12/2017		\| 16/12/2017

Louis.Cochinho at 14:33, 16 December 2017

2017-12-16T14:33:35Z

← Older revision		Revision as of 14:33, 16 December 2017
Line 21:		Line 21:
	\| TBC		\| TBC

	!scope="row" \|
	\| 0.2.0		\| 0.2.0
	\| 16/12/2017		\| 16/12/2017

Louis.Cochinho at 14:32, 16 December 2017

2017-12-16T14:32:51Z

@@ Line 1: / Line 1: @@
 The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.
  {|class="wikitable alternance"
@@ Line 21: / Line 16: @@
  | 0.1.0
  | 12/12/2017
  | E.Allard L.Cochinho A.Delise L.Guerry L.Rocher
  | TBC
@@ Line 31: / Line 34: @@
 =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 : [https://www.docker.com/]
 ==1.5   Overview of the remainder of the document==
@@ Line 50: / Line 62: @@
 ==2.1   Product perspective==
 ==2.2   Product functions==
@@ Line 58: / Line 70: @@
 *Choose one of them and see its menus
 *Choose date and number of meals
-*Reserved and payed
+*Book and payed
 *Send confirmation by email to the user
@@ Line 73: / Line 85: @@
 ==2.5   Assumptions and dependencies==
 =3.Specific requirements, covering functional, non-functional and interface requirements=
 =5. Appendices=

Louis.Cochinho: /* 5. Appendices */

2017-12-12T07:37:20Z

5. Appendices

← Older revision		Revision as of 07:37, 12 December 2017
Line 108:		Line 108:

	=5. Appendices=		=5. Appendices=
	[[Projets-2016-2017-Plateform_Analyse_Données_IOT/UML\| '''UML diagrams''']]

	=6. Index=		=6. Index=

Louis.Cochinho: Created page with "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-an..."

2017-12-12T07:35:58Z

Created page with "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-an..."

New page

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
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| 12/12/2017
| E.Allard L.Cochinho A.Delise L.Guerry L.Rocher
| 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==

Docker installation : [https://www.docker.com/]
....

==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=
[[Projets-2016-2017-Plateform_Analyse_Données_IOT/UML| '''UML diagrams''']]

=6. Index=