Projets-2016-2017-SmartSelfService/SRS - Revision history

Gilles.Bonhoure: /* 3.3 Requirement 1.2 | Admin's functions */

2017-02-06T10:20:10Z

3.3 Requirement 1.2 | Admin's functions

← Older revision		Revision as of 10:20, 6 February 2017
Line 192:		Line 192:

	'''Description''':		'''Description''':
			All the admin's functions

	'''Inputs''':		'''Inputs''': admin account

	'''Source''':		'''Source''': physical or applications

	'''Outputs''':		'''Outputs''': Edit the database, opens lockers...

	'''Destination''':		'''Destination''': physical or applications

	'''Action''':		'''Action''':
			* '''MUST''' create / update an account
	* Natural language sentences (with MUST, MAY, SHALL)
			* '''MAY''' delete an account
	* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
			* '''MUST''' control a locker
	* Mathematical Notations
			* '''MAY''' restrict an user
	* Tabular notations for several (condition --> action) tuples
			* '''MUST''' manage "points"

	'''Non functional requirements''':		'''Non functional requirements''':
Line 214:		Line 216:

	'''Side-effects''':		'''Side-effects''':
			* admin account overrides any action from an user
			* "restricted" user can still take-off it's own items

	==3.4 Requirement 2 \| Connected Lockers==		==3.4 Requirement 2 \| Connected Lockers==

Gilles.Bonhoure: /* 3.2 Requirement 1.1.2 | [User Extension] Owner's functions */

2017-02-06T10:10:10Z

3.2 Requirement 1.1.2 | [User Extension] Owner's functions

← Older revision		Revision as of 10:10, 6 February 2017
Line 163:		Line 163:

	'''Description''':		'''Description''':
			All the functions available for an owner

	'''Inputs''':		'''Inputs''':

	'''Source''':		'''Source''': physical or applications

	'''Outputs''':		'''Outputs''':

	'''Destination''':		'''Destination''': physical or applications

	'''Action''':		'''Action''':
			* '''MUST''' Drop-off an object
	* Natural language sentences (with MUST, MAY, SHALL)
			** '''MAY''' privatise it
	* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
			* '''MUST''' Take-off an own object
	* Mathematical Notations
			** '''MAY''' block an object since take-off
	* Tabular notations for several (condition --> action) tuples

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

	'''Pre-condition''':		'''Pre-condition''':
			* user is an owner

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

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


	==3.3 Requirement 1.2 \| Admin's functions==		==3.3 Requirement 1.2 \| Admin's functions==

Gilles.Bonhoure at 10:01, 6 February 2017

2017-02-06T10:01:23Z

@@ Line 125: / Line 125: @@
 * emergent system properties and quality characteristics.
-==3.1 Requirement 1 | Connected Lockers==
+==3.1 Requirement 1.1.1 | User's functions==
 '''Description''': Make the lockers communicate with the database
@@ Line 144: / Line 233: @@
 '''Non functional requirements''': The QRCode exists in the database and is not already used
-==3.2 Requirement 2 | Web-App : drop-off ==
+==3.5 Requirement 3 | Web-App : drop-off ==
 '''Description''': A way to drop-off an object in a locker
@@ Line 175: / Line 264: @@
 '''Side-effects''':
-==3.3 Requirement 3 | Web-app : Take-off ==
+==3.6 Requirement 4 | Web-app : Take-off ==
 '''Description''': A user must be able to take one of his object he left for someone to borrow
@@ Line 202: / Line 291: @@
 '''Post-condition''':
 * One locker is now empty
 '''Side-effects''':

Gilles.Bonhoure: /* 3.1 Requirement X.Y.Z (in Structured Natural Language) */

2017-02-06T09:57:46Z

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

← Older revision		Revision as of 09:57, 6 February 2017
Line 205:		Line 205:
	'''Side-effects''':		'''Side-effects''':

	==3.1 Requirement ~~X.Y.Z~~ ~~(in~~ ~~Structured Natural Language)~~==		==3.1 Requirement \| User's functions==
	'''Function''':		'''Function''':


	'''Description''':		'''Description''':
			All the users' functions

	'''Inputs''':		'''Inputs''': user actions

	'''Source''':		'''Source''': physical or application

	'''Outputs''':		'''Outputs''': ???

	'''Destination''':		'''Destination''': physical or application

	'''Action''':		'''Action''':
			* '''MUST''' create an account
	* Natural language sentences (with MUST, MAY, SHALL)
			* '''MAY''' delete his account
	* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
			* '''MUST''' consult available items
	* Mathematical Notations
			* '''SHOULD''' book an item
	* Tabular notations for several (condition --> action) tuples
			* '''MUST''' borrow an item
			* '''MUST''' bring back borrowed items

	'''Non functional requirements''':		'''Non functional requirements''':
			* User has an account or creates it

	'''Pre-condition''':		'''Pre-condition''':
			* Database structure is established

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

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


	==3.X Requirement X.Y.Z (in Structured Natural Language)==		==3.X Requirement X.Y.Z (in Structured Natural Language)==

Alicia.abonnenc: /* 3.3 Requirement 3 | Web-app : Take-off */

2017-02-05T19:58:33Z

3.3 Requirement 3 | Web-app : Take-off

← Older revision		Revision as of 19:58, 5 February 2017
Line 182:		Line 182:
	* The ID of the object (or the corresponding locker)		* The ID of the object (or the corresponding locker)
	* The ID of the user		* The ID of the user
	* [~~Optionnal~~] the desired pick-up date		* [Optional] the desired pick-up date
	'''Source''': The user		'''Source''': The user

Alicia.abonnenc: /* 3.3 Requirement 3 | Web-app : Take-off */

2017-02-05T19:58:04Z

3.3 Requirement 3 | Web-app : Take-off

← Older revision		Revision as of 19:58, 5 February 2017
Line 182:		Line 182:
	* The ID of the object (or the corresponding locker)		* The ID of the object (or the corresponding locker)
	* The ID of the user		* The ID of the user
			* [Optionnal] the desired pick-up date

	'''Source''': The user		'''Source''': The user

Line 190:		Line 190:

	'''Action''':		'''Action''':
			Please see the [[Projets-2016-2017-SmartSelfService/UML#Picking_up_an_object_you_blocked_before\| corresponding UML]]
	* 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''':

Alicia.abonnenc: /* 3.3 Requirement 3 | Web-app : Take-off */

2017-02-05T19:55:45Z

3.3 Requirement 3 | Web-app : Take-off

← Older revision		Revision as of 19:55, 5 February 2017
Line 177:		Line 177:
	==3.3 Requirement 3 \| Web-app : Take-off ==		==3.3 Requirement 3 \| Web-app : Take-off ==

			'''Description''': A user must be able to take one of his object he left for someone to borrow
	'''Description''':

	'''Inputs''':		'''Inputs''':
			* The ID of the object (or the corresponding locker)
			* The ID of the user

	'''Source''':		'''Source''': The user

	'''Outputs''':		'''Outputs''': Unlocking a locker and upadting the database.

	'''Destination''':		'''Destination''': The database

	'''Action''':		'''Action''':
Line 193:		Line 195:
	* Tabular notations for several (condition --> action) tuples		* Tabular notations for several (condition --> action) tuples

	'''Non functional requirements''':		'''Non functional requirements''':
			* Security : A user must have access to his objects and his objects only.
			* If a user wants to pick up an object, is someone borrowed it he must return it <== based on trust for the delays.

	'''Pre-condition''':		'''Pre-condition''':
			* The object is in on locker and not borrowed at the moment
			* The given Id for the object or locker corresponds to an object belonging to the user connected.

	'''Post-condition''':		'''Post-condition''':
			* One locker is now empty

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

Alicia.abonnenc: /* 3.2 Requirement 2 | Web-App : drop-off */

2017-02-05T19:50:37Z

3.2 Requirement 2 | Web-App : drop-off

← Older revision		Revision as of 19:50, 5 February 2017
Line 154:		Line 154:
	* [Optional] : authorized user or group of users		* [Optional] : authorized user or group of users

	'''Source''': ~~???~~		'''Source''': Database and user

	'''Outputs''':		'''Outputs''':
Line 171:		Line 171:
	* User has an account and is logged		* User has an account and is logged

			'''Post-condition''': The locker is marked as filled in the database and the informations related to the object are known
	'''Post-condition''':

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

Alicia.abonnenc: /* 1.3 Definitions, acronyms and abbreviations */

2017-02-05T19:36:29Z

1.3 Definitions, acronyms and abbreviations

← Older revision		Revision as of 19:36, 5 February 2017
Line 62:		Line 62:

	==1.3 Definitions, acronyms and abbreviations==		==1.3 Definitions, acronyms and abbreviations==
			* QRcode : Quick Response Code, is a grid containing black and white squares which can be interpreted to extract data (here a request) when seen through a camera.

	==1.4 References==		==1.4 References==

Alicia.abonnenc: /* 4. Product evolution */

2017-02-05T19:32:41Z

4. Product evolution

← Older revision		Revision as of 19:32, 5 February 2017
Line 255:		Line 255:

	=4. Product evolution=		=4. Product evolution=
			This app and system could evolve depending on hardware evolution, customer evolution or added features.
	This app can be deployed to several spots if connected lockers are built.
⚫	It could also be used as a platform of exchange rather than just lending, or even used to sell objects if money is added into the system.

			=== New system for the lockers ===
⚫	~~Another~~ possibility would be to deploy it into stores or a postoffice where the ~~onnected~~ lockers will eb used so that people can come pick up their mail and packages even when the office is closed.
			The lockers we got from previous years projects are connected through Wi-Fi, this can be a security flaw.
			Therefore, the product could evolve if instead of using a wireless network those lockers were to be connected using cables and other system. It would mean : changing the ahrware but also changing the app and code because it will be built on APIs different fromt he one this project uses.

			=== New lockers with the same system ===
			At the moment, we plan on managing only one set of locker, but if lockers were to be placed in different places, the app will have to have a feature allowing administrators to registers new lockers.

			=== Deployment for a company ===
		⚫	A possibility would be to deploy it into stores or a postoffice where the connected lockers will be used so that people can come pick up their mail and packages even when the office is closed.

			=== Exchanging and/or selling items ===
		⚫	This system could also be used as a platform of exchange rather than just lending, or even used to sell objects if money is added into the system. In order to do that new features will have to be implemented and a system of money or value in points corresponding to items will have to be created.

	=5. Appendices=		=5. Appendices=