RICM4 2017 2018 - UltraTeamMV/ SRS - Revision history

Enzo.Molion at 14:47, 11 February 2018

2018-02-11T14:47:22Z

← Older revision		Revision as of 14:47, 11 February 2018
Line 46:		Line 46:
	*GPS = '''G'''lobal '''P'''ositioning '''S'''ystem		*GPS = '''G'''lobal '''P'''ositioning '''S'''ystem
	==1.4 References==		==1.4 References==
	*The main page of the project: [~~[Proj-2013-2014-StartAIR-2]~~]		*The main page of the project [http://air.imag.fr/index.php/UltraTeam]

	==1.5 Overview of the remainder of the document==		==1.5 Overview of the remainder of the document==

Enzo.Molion: /* 3.Specific requirements, covering functional, non-functional and interface requirements */

2018-02-08T07:38:52Z

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

← Older revision		Revision as of 07:38, 8 February 2018
Line 74:		Line 74:
	=3.Specific requirements, covering functional, non-functional and interface requirements=		=3.Specific requirements, covering functional, non-functional and interface requirements=

	This section will describe two types of requirements :		'''This section will describe two types of requirements : '''
	* User requirements		* User requirements
	Statements in natural language plus diagrams of the services the system provides and its operational constraints. Written for customers.		Statements in natural language plus diagrams of the services the system provides and its operational constraints. Written for customers.
Line 80:		Line 80:
	* System requirements		* System requirements
	A structured document setting out detailed descriptions of the system’s functions, services and operational constraints. Defines what should be implemented so may be part of a contract between client and contractor.		A structured document setting out detailed descriptions of the system’s functions, services and operational constraints. Defines what should be implemented so may be part of a contract between client and contractor.

			'''Those requirement will be classified in 3 categories :'''
			* Functional requirements
			Statements of services the system should provide, how the system should react to particular inputs and how the system should behave in particular situations. It may also state what the system should not do.

			* Non-functional requirements
			Constraints on the services or functions offered by the system such as timing constraints, constraints on the development process, standards, etc.

			* Domain requirements
			Constraints on the system from the domain of operation.

Enzo.Molion: /* 3.Specific requirements, covering functional, non-functional and interface requirements */

2018-02-08T07:24:48Z

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

@@ Line 73: / Line 73: @@
 =3.Specific requirements, covering functional, non-functional and interface requirements=
 * document external interfaces,
 * describe system functionality and performance

Enzo.Molion: /* 3.0 Template : Requirement X.Y.Z */

2018-02-05T11:56:20Z

3.0 Template : Requirement X.Y.Z

← Older revision		Revision as of 11:56, 5 February 2018
Line 79:		Line 79:
	* emergent system properties and quality characteristics.		* emergent system properties and quality characteristics.

	==3.1 Requirement X.Y.Z (in Structured Natural Language)==		==3.0 Template : Requirement X.Y.Z (in Structured Natural Language)==
	'''Function''':		'''Function''':

Leo.Valette at 11:48, 5 February 2018

2018-02-05T11:48:57Z

← Older revision		Revision as of 11:48, 5 February 2018
Line 40:		Line 40:

	==1.3 Definitions, acronyms and abbreviations==		==1.3 Definitions, acronyms and abbreviations==
	*LoRa = ~~Long~~ ~~Range~~ : Low powered radio based communication technology		*LoRa = '''L'''ong '''R'''ange : Low powered radio based communication technology
	*LoRaWAN = ~~Long~~ ~~Range~~ ~~Wide~~ ~~Area~~ ~~Networks~~ : LoRa overlayer to ease (& securise) LoRa communication implementation		*LoRaWAN = '''L'''ong '''R'''ange '''W'''ide '''A'''rea '''N'''etworks : LoRa overlayer to ease (& securise) LoRa communication implementation
			*LPWAN = '''L'''ow '''P'''owered '''W'''ide '''A'''rea '''N'''etworks
	*LPWAN = Low Powered Wide Area Networks
			*BLE = '''B'''luetooth '''L'''ow '''E'''nergy
	*BLE = Bluetooth Low Energy
			*GPS = '''G'''lobal '''P'''ositioning '''S'''ystem
	*GPS = Global Positioning System
	==1.4 References==		==1.4 References==
	*The main page of the project: [[Proj-2013-2014-StartAIR-2]]		*The main page of the project: [[Proj-2013-2014-StartAIR-2]]

Leo.Valette at 11:46, 5 February 2018

2018-02-05T11:46:48Z

← Older revision		Revision as of 11:46, 5 February 2018
Line 40:		Line 40:

	==1.3 Definitions, acronyms and abbreviations==		==1.3 Definitions, acronyms and abbreviations==
	LoRa = Long Range : Low powered radio based communication technology		*LoRa = Long Range : Low powered radio based communication technology
	LoRaWAN = Long Range Wide Area Networks : LoRa overlayer to ease (& securise) LoRa communication implementation		*LoRaWAN = Long Range Wide Area Networks : LoRa overlayer to ease (& securise) LoRa communication implementation
	LPWAN = Low Powered Wide Area Networks		*LPWAN = Low Powered Wide Area Networks
	BLE = Bluetooth Low Energy		*BLE = Bluetooth Low Energy
	GPS = Global Positioning System		*GPS = Global Positioning System
	==1.4 References==		==1.4 References==
	*The main page of the project: [[Proj-2013-2014-StartAIR-2]]		*The main page of the project: [[Proj-2013-2014-StartAIR-2]]

Leo.Valette at 11:46, 5 February 2018

2018-02-05T11:46:11Z

← Older revision		Revision as of 11:46, 5 February 2018
Line 40:		Line 40:

	==1.3 Definitions, acronyms and abbreviations==		==1.3 Definitions, acronyms and abbreviations==
	LoRa = Long Range : communication technology ~~(“”””upgraded””””” bluetooth)~~		LoRa = Long Range : Low powered radio based communication technology
	LoRaWAN = Long Range Wide Area Networks : LoRa overlayer to ease (& securise) LoRa communication implementation		LoRaWAN = Long Range Wide Area Networks : LoRa overlayer to ease (& securise) LoRa communication implementation
	LPWAN = Low Powered Wide Area Networks		LPWAN = Low Powered Wide Area Networks

Leo.Valette at 11:39, 5 February 2018

2018-02-05T11:39:18Z

@@ Line 35: / Line 35: @@
 ==1.2   Scope of the product==
 ==1.3   Definitions, acronyms and abbreviations==
 ==1.4   References==
 *The main page of the project: [[Proj-2013-2014-StartAIR-2]]
@@ Line 43: / Line 52: @@
 =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,

Leo.Valette: 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..."

2018-02-05T09:28:41Z

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
| TBC
| TBC
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==
This Software Requirements Specification (SRS) identifies the requirements for project StartAir Safe.
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.

==1.2 Scope of the product==
==1.3 Definitions, acronyms and abbreviations==
==1.4 References==
*The main page of the project: [[Proj-2013-2014-StartAIR-2]]

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

=6. Index=