Requirements Specification - Revision history

Master: Added orderman interface link to requirements

2014-01-12T09:12:52Z

Added orderman interface link to requirements

Admin: specified login/logout and server startup

2013-11-07T16:57:30Z

specified login/logout and server startup

Admin: created page

2013-11-07T16:29:01Z

created page

Admin: moved Requirments Specification to Requirements Specification: spelling error

2013-11-07T16:27:27Z

moved Requirments Specification to Requirements Specification: spelling error

Admin: Created page with "= Requirements Specification ="

2013-11-07T14:09:45Z

Created page with "= Requirements Specification ="

New page

= Requirements Specification =

← Older revision		Revision as of 09:12, 12 January 2014
Line 27:		Line 27:
	== Server Startup ==		== Server Startup ==
	By launching FOS a login window must appear. The Boss must be able to access the administrative interface as well as the orderman itself. The server starts automatically in the background and manages the whole communication.		By launching FOS a login window must appear. The Boss must be able to access the administrative interface as well as the orderman itself. The server starts automatically in the background and manages the whole communication.
		+
		+	= Orderman Interface =
		+	Lookup the [[Orderman Interface]] documentation.

@@ Line 14: / Line 14: @@
 == Login ==
-Every waiter is identified by an user name and a password. As the waiter logs in, the application connects him to the server. If the login was successful the application shows all the tables assigned to the waiter allowing him to start his work.
+Every waiter must be identifiable. If the login was successful the application shows all the tables assigned to the waiter allowing him to start his work.
 == Orders ==
@@ Line 23: / Line 26: @@
 == Server Startup ==

← Older revision		Revision as of 16:29, 7 November 2013
Line 1:		Line 1:
−	= ~~Requirements Specification~~ =	+	= Communication =
		+	The Free Orderman System must provide and manage the communication between:
		+
		+	* smartphones
		+	* computers
		+	* printers
		+
		+	The communication must be save and fast enough to satisfy the work flow of a catering company.
		+
		+	= Waiters =
		+	The system must be able to manage various waiter accounts. Through these accounts they get access to the system (with their smartphone or via a terminal computer and so on). Every waiter can work on some tables – these tables are linked to the account of the waiter. It could be that the boss decides that 2 waiters can work on all tables. So it must be possible that at the same time two or more waiters work on the same table (i.e. get the orders together).
		+
		+	If the boss decides that waiter A can work on table 1, 3, 5 and waiter B can work on table 2, 4, 6, waiter A doesn't even see table 4 on his application. He sees only his 3 tables, and the same for waiter B.
		+
		+	== Login ==
		+	Every waiter is identified by an user name and a password. As the waiter logs in, the application connects him to the server. If the login was successful the application shows all the tables assigned to the waiter allowing him to start his work.
		+
		+	== Orders ==
		+	Every waiter can do an order for a table that is linked to his account. Two or more waiters can do orders at the same time.
		+
		+	= Boss =
		+	To do all the administrative work, the boss must be able to do this through a simple and easy to use interface, where he can manage the waiter accounts, the products, the tables and so on.
		+
		+	== Server Startup ==