Proj-2016-2017-ColisMatter/SRS - Revision history

Hugo.Amodru-Favin: /* 2.3 User characteristics */

2017-02-06T14:51:22Z

2.3 User characteristics

← Older revision		Revision as of 14:51, 6 February 2017
Line 66:		Line 66:
	==2.3 User characteristics==		==2.3 User characteristics==
	Our product is designed to be used by companies to localize all their products in transit. Among each companies, different users appears :		Our product is designed to be used by companies to localize all their products in transit. Among each companies, different users appears :
	* ''Factory'' user : He creates new packages. Thus, he only ~~use~~ the first app.		* ''Factory'' user : He creates new packages. Thus, he only uses the first app.
	* ''Transit'' user : He scans packages during the transit		* ''Transit'' user : He scans packages during the transit
	* ''Arrival'' user : He is the last one to scan the package and can then modify its characteristics in the database after checking the validity of the package. If imperfect, he can manage to search for missing package, or identify where a wrong article should be.		* ''Arrival'' user : He is the last one to scan the package and can then modify its characteristics in the database after checking the validity of the package. If imperfect, he can manage to search for missing package, or identify where a wrong article should be.

Hugo.Amodru-Favin: /* 2.3 User characteristics */

2017-02-06T14:51:03Z

2.3 User characteristics

← Older revision		Revision as of 14:51, 6 February 2017
Line 65:		Line 65:

	==2.3 User characteristics==		==2.3 User characteristics==
			Our product is designed to be used by companies to localize all their products in transit. Among each companies, different users appears :
			* ''Factory'' user : He creates new packages. Thus, he only use the first app.
			* ''Transit'' user : He scans packages during the transit
			* ''Arrival'' user : He is the last one to scan the package and can then modify its characteristics in the database after checking the validity of the package. If imperfect, he can manage to search for missing package, or identify where a wrong article should be.

	==2.4 General constraints==		==2.4 General constraints==
	==2.5 Assumptions and dependencies==		==2.5 Assumptions and dependencies==

Hugo.Amodru-Favin: /* 2.2 Product functions */

2017-02-06T14:39:22Z

2.2 Product functions

@@ Line 51: / Line 51: @@
 ==2.1   Product perspective==
 ==2.2   Product functions==
 ==2.3   User characteristics==
 ==2.4   General constraints==

Hugo.Amodru-Favin: /* 1.3 Definitions, acronyms and abbreviations */

2017-02-06T14:03:57Z

1.3 Definitions, acronyms and abbreviations

← Older revision		Revision as of 14:03, 6 February 2017
Line 43:		Line 43:

	==1.3 Definitions, acronyms and abbreviations==		==1.3 Definitions, acronyms and abbreviations==
			* '''Package''' : In this project, we consider a package as a sum of different RFID tags. The presence of every RFID tag defines the package. In a stable state, the package contains the same tags since its creation.
			* '''Reader''' : RFID Reader, the Nordic ID Stix.

	==1.4 References==		==1.4 References==
	==1.5 Overview of the remainder of the document==		==1.5 Overview of the remainder of the document==

Hugo.Amodru-Favin: /* 1.2 Scope of the product */

2017-02-06T13:58:14Z

1.2 Scope of the product

← Older revision		Revision as of 13:58, 6 February 2017
Line 36:		Line 36:

	==1.2 Scope of the product==		==1.2 Scope of the product==
			By using open sources demo apps, the purpose of the project is to develops android applications to enable professionals to scan their products and follow them during their transit.

			Two applications will be developed :
			* The first one will allow the user to scan his package and register it in the database before its transit.
			* The second one will be used during the transit by an user who will scan the package and make it match or no the database.

	==1.3 Definitions, acronyms and abbreviations==		==1.3 Definitions, acronyms and abbreviations==
	==1.4 References==		==1.4 References==

Hugo.Amodru-Favin: /* 3.2 Requirement 2 : Application 2: Following Packages */

2017-02-06T13:22:25Z

3.2 Requirement 2 : Application 2: Following Packages

← Older revision		Revision as of 13:22, 6 February 2017
Line 76:		Line 76:
	'''Post-condition''':		'''Post-condition''':

	==3.2 Requirement 2 : Application 2: Following Packages==		==3.2 Requirement 2 : Application 2 : Following Packages==
	'''Function''': Scanning packages to update their localisation and identify issues (articles missing, wrong articles)		'''Function''': Scanning packages to update their localisation and identify issues (articles missing, wrong articles)

Hugo.Amodru-Favin: /* 3.Specific requirements, covering functional, non-functional and interface requirements */

2017-02-06T13:22:12Z

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

← Older revision		Revision as of 13:22, 6 February 2017
Line 73:		Line 73:

	'''Pre-condition''': Database operational		'''Pre-condition''': Database operational

			'''Post-condition''':

			==3.2 Requirement 2 : Application 2: Following Packages==
			'''Function''': Scanning packages to update their localisation and identify issues (articles missing, wrong articles)

			'''Description''': Build a top level layer and application on the NurApi

			'''Inputs''': Communication with a RFID sensor to scan packages

			'''Source''': NurApi

			'''Outputs''': Database Updated

			'''Destination''': User or another Application

			'''Action''':
			* ''MUST'' : Communicate with RFid Sensor through the NurApi in order to register the package into the database.
			* ''MUST'' : Let users sign in to scan new packages
			* ''MUST'' : Inform the user about his scan

			'''Non functional requirements''':

			'''Pre-condition''': Package already registered in the database

	'''Post-condition''':		'''Post-condition''':

Hugo.Amodru-Favin: /* 3.1 Requirement 1 : Application 1 : RFID Reader */

2017-02-06T12:31:27Z

3.1 Requirement 1 : Application 1 : RFID Reader

← Older revision		Revision as of 12:31, 6 February 2017
Line 67:		Line 67:
	'''Action''':		'''Action''':
	* ''MUST'' : Communicate with RFid Sensor through the NurApi in order to register the package into the database.		* ''MUST'' : Communicate with RFid Sensor through the NurApi in order to register the package into the database.
			* ''MUST'' : Let users sign in to register new packages
			* ''SHOULD'' : Allow users to have access to the database

	'''Non functional requirements''':		'''Non functional requirements''':

Hugo.Amodru-Favin: /* 3.1 Requirement 1 : Application 1 : RFID Reader */

2017-02-06T12:26:00Z

3.1 Requirement 1 : Application 1 : RFID Reader

← Older revision		Revision as of 12:26, 6 February 2017
Line 73:		Line 73:

	'''Post-condition''':		'''Post-condition''':

	'''Side-effects''':

	'''Side-effects''':

	=4. Product evolution=		=4. Product evolution=

Hugo.Amodru-Favin: /* 3.1 Requirement X.Y.Z (in Structured Natural Language) */

2017-02-06T12:25:45Z

3.1 Requirement X.Y.Z (in Structured Natural Language)

← Older revision		Revision as of 12:25, 6 February 2017
Line 52:		Line 52:
	* emergent system properties and quality characteristics.		* emergent system properties and quality characteristics.

	==3.1 Requirement ~~X.Y.Z~~ ~~(in~~ ~~Structured~~ ~~Natural~~ ~~Language)~~==		==3.1 Requirement 1 : Application 1 : RFID Reader==
	'''Function''':		'''Function''': RFID Sensor communication

	'''Description''':		'''Description''': Build a top level layer and application on the NurApi

	'''Inputs''':		'''Inputs''': Communication with a RFID sensor

	'''Source''':		'''Source''': NurApi

	'''Outputs''':		'''Outputs''': RFID Tag

	'''Destination''':		'''Destination''': User or another Application

	'''Action''':		'''Action''':
			* ''MUST'' : Communicate with RFid Sensor through the NurApi in order to register the package into the database.
	* 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''':		'''Non functional requirements''':

	'''Pre-condition''':		'''Pre-condition''': Database operational

	'''Post-condition''':		'''Post-condition''':

			'''Side-effects''':

	'''Side-effects''':		'''Side-effects''':