FOS Wiki - User contributions [en]

Use Cases v0.2

2014-03-06T13:55:18Z

Master: added use case Make Orders

= Location and Tables Visualization =
The user will be able to visualize the locations with their related tables and all orders of every table.

Make Orders

The user will be able to create a new Order by choosing one or multiple products. To test this process the database will contain some standard categories. Every category will contain some standard products. For example

Pizza: Margherita, Marinara, Bufala...
Pasta: Carbonara, Bolognese...
Vines: Morellino, Pinot Nero, Chardonnay...
Caffe: Espresso, Macchiato, Cappucino...
...

= Manage User Accounts =
An administrator must be able to manage the user accounts on the server. Therefor it must be possible to do a login on the server user interface.

= Manage Locations and Tables =
An administrator must be able to manage all the tables and different locations through a simple UI on the server.

FOS

2014-03-06T13:54:52Z

Master:

<div id="mf-home">
= Introduction =
The Free Orderman System (FOS) wants to be a free solution for ordering management in bars, pubs, restaurants, clubs and so on. As an open source project it will be a fast, secure and simple software accessible to everyone.

== The FOS Development Team ==
Team members:
*Alex Mazzon (18)
*Florian Mahlknecht (18)
See the team in [https://launchpad.net/~fosdevelopers Launchpad].

== The Idea ==

«''The idea to create a free order-man system was born in Innsbruck when I worked as waiter in an Italian restaurant last summer. There I discovered that a order-man system costs a big amount of money. I never thought about it but as I realized the real cost I had an idea: Why not use smartphones as “ordermans” and connect them to a common PC?. I presented my idea to my classmate Florian and we decided to realize the project together.''» Alex

== Motivation ==
Basically we need three things to create a really cheap order-man system:

* a smartphone
* a computer
* and a printer

Actually these three things are already available in nearly every bar or restaurant. From a small village pub to the most hidden refuge up in the mountains.

Just one thing is missing: the software.

= Development =

== Version 0.1 ==
*[[Use Cases v0.1]]
**Launch Server
**Login
**Logout
*[[Milestones v0.1]]
**Project Startup
**Server Startup
**Login / Logout

== Version 0.2 ==

*[[Use Cases v0.2]]
*[[Milestones v0.2]]

== Documentation ==

Global documents for the documentation of FOS:
*[[Requirements Specification]]
*[[Database Design]]
*[[Protocol Design]]
*[[Orderman Interface]]

=== How to write the FOS documentation ===
When we begin to develop a new version of FOS the first thing to do is to plan and schedule the whole work. This means:
* Add all the new requirements to the [[Requirements Specification]]. If the requirement for the new version is already described in this document this requirement will be updated.
* Make sure that the database provides all data that the new version of FOS needs
* Create and describe the use cases
* Create and describe the milestones with their related blueprints

=== Glossary ===
All specific words and abbreviations used in the FOS documentation are explained here:
* '''FOS''':
FOS is the abbreviation for ''Free Orderman System''
* '''orderman''':
Whenever the words ''orderman'', ''orderman interface'' or ''orderman application'' are used in the FOS documentation the interface which allows the waiter to order is meant.

</div>

Orderman Interface

2014-03-06T13:29:42Z

Master: /* Menus */

= Login =
When the waiter starts the orderman a login window will appear. This window consists of two text fields: one for the username and another for the password. A simple button will allow to login and if the login was successful the waiter will see his tables and can start to work.

= Logout =
A simple button will provide the logout.

= Orderman =
The Orderman interface shows the tables of the restaurant, bar or whatever. A table is visualized through a simple rectangle with the table number on it. When an order has already been done on a table this table will have a different color of the tables where no order has been made.
By clicking on a table the ''Order'' interface will be shown.

It is important that no other stuff is placed on this interface, because the waiter must have a good overview of the tables. No other wearing stuff will be shown on the orderman.

= Menus =
When the user presses and holds on a table a bottom menu must appear where it will be possible (in a further moment) to split a table or move the orders from one table to another.

By clicking on the table number of the table view a menu will be shown, witch contains the total price of the table and the options ''pay, pay separately'' and others.

= Order =
On this interface the waiter can look up the orders that already have been made on the chosen table. In addition he can make new orders.

The screen is divided in two parts. The top half of the screen will show all orders that have been made. The other half will be used to make a new order. When the waiter clicks on a table he will see all categories and by clicking on one of them all products in this category will be visualized. By clicking on a product this product will be added to the product list of the order. By clicking on ''ok'' the order will be sent with all his products. After the new order has been sent to the FOS server the ''orderman interface'' with all the tables will be shown again.

= Settings =
The user can set:
* the FOS server ip
* ...

Orderman Interface

2014-03-06T13:28:51Z

Master: Added the Menu Interface documentation

= Login =
When the waiter starts the orderman a login window will appear. This window consists of two text fields: one for the username and another for the password. A simple button will allow to login and if the login was successful the waiter will see his tables and can start to work.

= Logout =
A simple button will provide the logout.

= Orderman =
The Orderman interface shows the tables of the restaurant, bar or whatever. A table is visualized through a simple rectangle with the table number on it. When an order has already been done on a table this table will have a different color of the tables where no order has been made.
By clicking on a table the ''Order'' interface will be shown.

It is important that no other stuff is placed on this interface, because the waiter must have a good overview of the tables. No other wearing stuff will be shown on the orderman.

= Menus =
When the user presses and holds on a table a bottom menu must appear where it will be possible (in a further moment) to split a table or move the orders from one table to another.
By clicking on the table number of the table view a menu will be shown, witch contains the total price of the table and the options ''pay, pay separately'' and others.

= Order =
On this interface the waiter can look up the orders that already have been made on the chosen table. In addition he can make new orders.

The screen is divided in two parts. The top half of the screen will show all orders that have been made. The other half will be used to make a new order. When the waiter clicks on a table he will see all categories and by clicking on one of them all products in this category will be visualized. By clicking on a product this product will be added to the product list of the order. By clicking on ''ok'' the order will be sent with all his products. After the new order has been sent to the FOS server the ''orderman interface'' with all the tables will be shown again.

= Settings =
The user can set:
* the FOS server ip
* ...

Use Cases v0.2

2014-03-06T13:27:31Z

Master:

= Location and Tables Visualization =
The user will be able to visualize the locations with their related tables and all orders of every table.

= Manage User Accounts =
An administrator must be able to manage the user accounts on the server. Therefor it must be possible to do a login on the server user interface.

= Manage Locations and Tables =
An administrator must be able to manage all the tables and different locations through a simple UI on the server.

Milestones v0.2

2014-03-06T13:22:00Z

Master: created the milestones visualize tables and visualize orders

= Visualize Tables =
After a successful login the user will see an overview of all tables or - if there is more than one location and the user can work on these tables - an overview of the locations. To test this use case there will be some test tables in the database. For example ''table 1'', ''table 2'' and ''table 3'' in 'location 1'.

= Visualize Orders =
The user will be able to visualize all products (and their quantity) that has already been ordered.

Use Cases v0.2

2014-03-06T13:21:16Z

Master: merged the visualized use cases

= Visualization =
The user will be able to visualize the locations with their related tables and all orders of every table.

= Manage User Accounts =
An administrator must be able to manage the user accounts on the server. Therefor it must be possible to do a login on the server user interface.

= Manage Locations and Tables =
An administrator must be able to manage all the tables and different locations through a simple UI on the server.

Milestones v0.2

2014-01-14T11:11:43Z

Master: created page...

= Visualize Tables =
TODO
= Visualize Orders =
TODO

FOS

2014-01-14T11:08:28Z

Master: added v0.3

<div id="mf-home">
= Introduction =
The Free Orderman System (FOS) wants to be a free solution for ordering management in bars, pubs, restaurants, clubs and so on. As an open source project it will be a fast, secure and simple software accessible to everyone.

== The FOS Development Team ==
Team members:
*Alex Mazzon (18)
*Florian Mahlknecht (18)
See the team in [https://launchpad.net/~fosdevelopers Launchpad].

== The Idea ==

«''The idea to create a free order-man system was born in Innsbruck when I worked as waiter in an Italian restaurant last summer. There I discovered that a order-man system costs a big amount of money. I never thought about it but as I realized the real cost I had an idea: Why not use smartphones as “ordermans” and connect them to a common PC?. I presented my idea to my classmate Florian and we decided to realize the project together.''» Alex

== Motivation ==
Basically we need three things to create a really cheap order-man system:

* a smartphone
* a computer
* and a printer

Actually these three things are already available in nearly every bar or restaurant. From a small village pub to the most hidden refuge up in the mountains.

Just one thing is missing: the software.

= Development =

== Version 0.1 ==
*[[Use Cases v0.1]]
**Launch Server
**Login
**Logout
*[[Milestones v0.1]]
**Project Startup
**Server Startup
**Login / Logout

== Version 0.2 ==

*[[Use Cases v0.2]]
*[[Milestones v0.2]]

== Version 0.3 ==

*[[Use Cases v0.3]]
*[[Milestones v0.3]]

== Documentation ==

Global documents for the documentation of FOS:
*[[Requirements Specification]]
*[[Database Design]]
*[[Protocol Design]]
*[[Orderman Interface]]

=== How to write the FOS documentation ===
When we begin to develop a new version of FOS the first thing to do is to plan and schedule the whole work. This means:
* Add all the new requirements to the [[Requirements Specification]]. If the requirement for the new version is already described in this document this requirement will be updated.
* Make sure that the database provides all data that the new version of FOS needs
* Create and describe the use cases
* Create and describe the milestones with their related blueprints

=== Glossary ===
All specific words and abbreviations used in the FOS documentation are explained here:
* '''FOS''':
FOS is the abbreviation for ''Free Orderman System''
* '''orderman''':
Whenever the words ''orderman'', ''orderman interface'' or ''orderman application'' are used in the FOS documentation the interface which allows the waiter to order is meant.

</div>

Use Cases v0.2

2014-01-12T12:32:04Z

Master:

= Visualize Tables =
After a successful login the user will see an overview of all tables. To test this use case there will be some test tables in the database. For example ''table 1'', ''table 2'' and ''table 3''.

= Visualize Orders =
The user will be able to visualize all products (and their quantity) that has already been ordered.

= Make Orders =
The user will be able to create a new ''Order'' by choosing one or multiple products. To test this process the database will contain some ''standard categories''. Every ''category'' will contain some ''standard products''. For example

*Pizza: Margherita, Marinara, Bufala...
*Pasta: Carbonara, Bolognese...
*Vines: Morellino, Pinot Nero, Chardonnay...
*Caffe: Espresso, Macchiato, Cappucino...
*...

Use Cases v0.2

2014-01-12T12:30:11Z

Master:

= Visualize Tables =
After a successful login the user will see an overview of all tables. To test this use case there will be some test tables in the database. For example ''table 1'', ''table 2'' and ''table 3''.

= Visualize Orders =
The user will be able to visualize all products (and their quantity) that has already been ordered.

= Make Orders =
The user will be able to create a new Order by choosing one or multiple products. To test this process the database will contain some ''standard categories''. Every ''category'' will contain some ''standard products''. For example

*Pizza: Margherita, Marinara, Bufala...
*Pasta: Carbonara, Bolognese...
*Vines: Morellino, Pinot Nero, Chardonnay...
*Caffe: Espresso, Macchiato, Cappucino...
*...

Use Cases v0.2

2014-01-12T12:29:01Z

Master: /* Visualize Tables */

= Visualize Tables =
After a successful login the user will see an overview of all tables. To test this use case there will be some test tables in the database. For example ''table 1'', ''table 2'' and ''table 3''.

= Make Orders =
The user will be able to create a new Order by choosing one or multiple products. To test this process the database will contain some ''standard categories''. Every ''category'' will contain some ''standard products''. For example

*Pizza: Margherita, Marinara, Bufala...
*Pasta: Carbonara, Bolognese...
*Vines: Morellino, Pinot Nero, Chardonnay...
*Caffe: Espresso, Macchiato, Cappucino...
*...

= Visualize Orders =
The user will be able to visualize all products (and their quantity) that has already been ordered.

Use Cases v0.2

2014-01-12T12:24:29Z

Master: added visualize tables

= Visualize Tables =
After a successful login the user will see an overview of all tables. By clicking on a table the user will be able to make new orders and visualize the orders that have already been made.

= Make Orders =
The user will be able to create a new Order by choosing one or multiple products. To test this process the database will contain some ''standard categories''. Every ''category'' will contain some ''standard products''. For example

*Pizza: Margherita, Marinara, Bufala...
*Pasta: Carbonara, Bolognese...
*Vines: Morellino, Pinot Nero, Chardonnay...
*Caffe: Espresso, Macchiato, Cappucino...
*...

= Visualize Orders =
The user will be able to visualize all products (and their quantity) that has already been ordered.

Use Cases v0.2

2014-01-12T12:21:12Z

Master: /* Viualize Orders */

= Make Orders =
The user will be able to create a new Order by choosing one or multiple products. To test this process the database will contain some ''standard categories''. Every ''category'' will contain some ''standard products''. For example

*Pizza: Margherita, Marinara, Bufala...
*Pasta: Carbonara, Bolognese...
*Vines: Morellino, Pinot Nero, Chardonnay...
*Caffe: Espresso, Macchiato, Cappucino...
*...

= Visualize Orders =
The user will be able to visualize all products (and their quantity) that has already been ordered.

Use Cases v0.2

2014-01-12T12:20:59Z

Master: created page and added Make Orders and Visualize Orders

= Make Orders =
The user will be able to create a new Order by choosing one or multiple products. To test this process the database will contain some ''standard categories''. Every ''category'' will contain some ''standard products''. For example

*Pizza: Margherita, Marinara, Bufala...
*Pasta: Carbonara, Bolognese...
*Vines: Morellino, Pinot Nero, Chardonnay...
*Caffe: Espresso, Macchiato, Cappucino...
*...

= Viualize Orders =
The user will be able to visualize all products (and their quantity) that has already been ordered.

Orderman Interface

2014-01-12T11:49:29Z

Master: corrected some mistakes...

= Login =
When the waiter starts the orderman a login window will appear. This window consists of two text fields: one for the username and another for the password. A simple button will allow to login and if the login was successful the waiter will see his tables and can start to work.
= Logout =
A simple button will provide the logout.
= Orderman =
The Orderman interface shows the tables of the restaurant, bar or whatever. A table is visualized through a simple rectangle with the table number on it. When an order has already been done on a table this table will have a different color of the tables where no order has been made.
By clicking on a table the ''Order'' interface will be shown.

It is important that no other stuff is placed on this interface, because the waiter must have a good overview of the tables. No other wearing stuff will be shown on the orderman.
= Order =
On this interface the waiter can look up the orders that already have been made on the chosen table. In addition he can make new orders.

The screen is divided in two parts. The top half of the screen will show all orders that have been made. The other half will be used to make a new order. When the waiter clicks on a table he will see all categories and by clicking on one of them all products in this category will be visualized. By clicking on a product this product will be added to the product list of the order. By clicking on ''ok'' the order will be sent with all his products. After the new order has been sent to the FOS server the ''orderman interface'' with all the tables will be shown again.

= Settings =
The user can set:
* the FOS server ip
* ...

Requirements Specification

2014-01-12T09:12:52Z

Master: Added orderman interface link to requirements

= 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 must be identifiable. If the login was successful the application shows all the tables assigned to the waiter allowing him to start his work.

== Logout ==
On logout the waiter must recieve his payoff whitch shows all cash receipts since the last login.

== 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 ==
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.

Orderman Interface

2014-01-10T17:39:52Z

Master: added the interfaces Orderman and Order

= Login =
When the waiter starts the orderman a login window will appear. This window consists of two text fields: one for the username and another for the password. A simple button will allow to login and if the login was successful the waiter will see his tables and can start to work.
= Logout =
A simple button will provide the logout.
= Orderman =
The Orderman interface shows the tables of the restaurant, bar or whatever. A table is visualized through a simple rectangle with the table number on it. When an order has already been done on a table this table will have a different color of the tables where no order has been made.
By clicking on a table the ''Order'' interface will be shown.

It is important that no other stuff is placed on this interface, because the waiter must have a good overview of the tables. No other wearing stuff will be shown on the orderman.
= Order =
On this interface the waiter can look up the orders that already have been made on the chosen table. In addition he can make new orders.

The screen is divided in two parts. The top half of the screen will show all orders that have been made. The other half of the screen will be used to make a new order. When the waiter clicks on a table he will see all categories and by clicking on one of them all products in this category will be shown. By clicking on a product this product will be added to the product list of a this order. By clicking on ''ok'' the order will be sent with all the products added to this new order of the table. After the new order has been sent the orderman interface with all the tables will be shown again.
= Settings =
The user can set:
* the FOS server ip
* ...

FOS

2014-01-10T17:22:17Z

Master: /* Version 0.2 */

FOS

2014-01-10T17:22:03Z

Master: added v0.2

<div id="mf-home">
= Introduction =
The Free Orderman System (FOS) wants to be a free solution for ordering management in bars, pubs, restaurants, clubs and so on. As an open source project it will be a fast, secure and simple software accessible to everyone.

== The FOS Development Team ==
Team members:
*Alex Mazzon (18)
*Florian Mahlknecht (18)
See the team in [https://launchpad.net/~fosdevelopers Launchpad].

== The Idea ==

«''The idea to create a free order-man system was born in Innsbruck when I worked as waiter in an Italian restaurant last summer. There I discovered that a order-man system costs a big amount of money. I never thought about it but as I realized the real cost I had an idea: Why not use smartphones as “ordermans” and connect them to a common PC?. I presented my idea to my classmate Florian and we decided to realize the project together.''» Alex

== Motivation ==
Basically we need three things to create a really cheap order-man system:

* a smartphone
* a computer
* and a printer

Actually these three things are already available in nearly every bar or restaurant. From a small village pub to the most hidden refuge up in the mountains.

Just one thing is missing: the software.

= Development =

== Version 0.1 ==
*[[Use Cases v0.1]]
**Launch Server
**Login
**Logout
*[[Milestones v0.1]]
**Project Startup
**Server Startup
**Login / Logout

== Version 0.2 ==

*[[Use Cases v0.1]]
*[[Milestones v0.1]]

== Documentation ==

Global documents for the documentation of FOS:
*[[Requirements Specification]]
*[[Database Design]]
*[[Protocol Design]]
*[[Orderman Interface]]

=== How to write the FOS documentation ===
When we begin to develop a new version of FOS the first thing to do is to plan and schedule the whole work. This means:
* Add all the new requirements to the [[Requirements Specification]]. If the requirement for the new version is already described in this document this requirement will be updated.
* Make sure that the database provides all data that the new version of FOS needs
* Create and describe the use cases
* Create and describe the milestones with their related blueprints

=== Glossary ===
All specific words and abbreviations used in the FOS documentation are explained here:
* '''FOS''':
FOS is the abbreviation for ''Free Orderman System''
* '''orderman''':
Whenever the words ''orderman'', ''orderman interface'' or ''orderman application'' are used in the FOS documentation the interface which allows the waiter to order is meant.

</div>

Orderman Interface

2014-01-10T17:21:01Z

Master:

Orderman Interface

2014-01-10T17:19:39Z

Master: added screenshots

File:SC20140110-181151.png

2014-01-10T17:19:17Z

Master:

File:SC20140110-181141.png

2014-01-10T17:14:51Z

Master:

Server Access

2014-01-10T17:10:09Z

Master: /* The Socket */

= The Socket =
==Modify the Project File==
The first thing to do is add ''networking'' to the project file, so that Qt knows that we wanna work with the network model. Also ''xml'' and ''svg'' will be add so that we can use svg images on the phone.

==The Client==

The orderman socket uses the class [http://qt-project.org/doc/qt-5.1/qtnetwork/qtcpsocket.html QTcpSocket] to communicate with the FOS server. If the communication fails the user will be asked to set the right FOS server ip. This ip is static and has to be set only once in the settings. The application settings and an explanation how to set the correct port will be shown. The user will also be advertised to turn on wifi and connect to the same router as the FOS server.

The socket will be closed when the waiter logs out.

= Android Permissions =
The order man application must have the appropriate permissions that allow the connection to the server. An important permission to do that is the [http://developer.android.com/reference/android/Manifest.permission.html#INTERNET INTERNET] permission, which allows applications to open network sockets.

Server Access

2013-12-18T18:15:41Z

Master: deleted nearly whole documentation, todo...

Server Access

2013-12-17T16:08:07Z

Master: error in title...

= The Socket =
==Modify the Project File==
The first thing to do is add ''networking'' to the project file, so that Qt knows that we wanna work with the network model.

==The Client==

The orderman socket uses the class [http://qt-project.org/doc/qt-5.1/qtnetwork/qtcpsocket.html QTcpSocket] to communicate with the FOS server. The function ''connect()'' connects the application socket to the FOS server on login. If the communication fails the user will be asked to set the right port. The application settings and an explanation how to set the correct port will be shown. The user will also be advertised to turn on wifi.

When the waiter starts the orderman the application has to find out the ip adress and the port which allows the communication with the server. The port is set in the application settings and must correspond to the FOS server port specified in the server settings. The class [http://qt-project.org/doc/qt-5.1/qtnetwork/qnetworkconfigurationmanager.html#details QNetworkConfiguration] provides access to the network configurations known to the system and allows to find out the router port with the function [http://qt-project.org/doc/qt-5.1/qtnetwork/qnetworkconfigurationmanager.html#allConfigurations allConfigurations]().

The function ''send()'' sends the JSON objects to the server. When the signal ''readyRead()'' is emitted by the server it means that the server sent back a JSON object.

The socket will be closed when the waiter logs out.

= Android Permissions =
The order man application must have the appropriate permissions that allow the connection to the server. An important permission to do that is the [http://developer.android.com/reference/android/Manifest.permission.html#INTERNET INTERNET] permission, which allows applications to open network sockets.

FOS

2013-12-17T16:05:17Z

Master: listed the team members..

<div id="mf-home">
= Introduction =
The Free Orderman System (FOS) wants to be a free solution for ordering management in bars, pubs, restaurants, clubs and so on. As an open source project it will be a fast, secure and simple software accessible to everyone.

== The FOS Development Team ==
Team members:
*Alex Mazzon (18)
*Florian Mahlknecht (18)
See the team in [https://launchpad.net/~fosdevelopers Launchpad].

== The Idea ==

«''The idea to create a free order-man system was born in Innsbruck when I worked as waiter in an Italian restaurant last summer. There I discovered that a order-man system costs a big amount of money. I never thought about it but as I realized the real cost I had an idea: Why not use smartphones as “ordermans” and connect them to a common PC?. I presented my idea to my classmate Florian and we decided to realize the project together.''» Alex

== Motivation ==
Basically we need three things to create a really cheap order-man system:

* a smartphone
* a computer
* and a printer

Actually these three things are already available in nearly every bar or restaurant. From a small village pub to the most hidden refuge up in the mountains.

Just one thing is missing: the software.

= Development =

== Version 0.1 ==
*[[Use Cases v0.1]]
**Launch Server
**Login
**Logout
*[[Milestones v0.1]]
**Project Startup
**Server Startup
**Login / Logout

== Documentation ==

Global documents for the documentation of FOS:
*[[Requirements Specification]]
*[[Database Design]]
*[[Protocol Design]]
*[[Orderman Interface]]

=== How to write the FOS documentation ===
When we begin to develop a new version of FOS the first thing to do is to plan and schedule the whole work. This means:
* Add all the new requirements to the [[Requirements Specification]]. If the requirement for the new version is already described in this document this requirement will be updated.
* Make sure that the database provides all data that the new version of FOS needs
* Create and describe the use cases
* Create and describe the milestones with their related blueprints

=== Glossary ===
All specific words and abbreviations used in the FOS documentation are explained here:
* '''FOS''':
FOS is the abbreviation for ''Free Orderman System''
* '''orderman''':
Whenever the words ''orderman'', ''orderman interface'' or ''orderman application'' are used in the FOS documentation the interface which allows the waiter to order is meant.

</div>

FOS

2013-12-16T18:48:51Z

Master: added blueprint list to the milestones and the use case list

<div id="mf-home">
= Introduction =
The Free Orderman System (FOS) wants to be a free solution for ordering management in bars, pubs, restaurants, clubs and so on. As an open source project it will be a fast, secure and simple software accessible to everyone.

== The FOS Development Team ==
The team consists of Alex Mazzon (18) and Florian Mahlknecht (18). See the team in [https://launchpad.net/~fosdevelopers Launchpad].

== The Idea ==

«''The idea to create a free order-man system was born in Innsbruck when I worked as waiter in an Italian restaurant last summer. There I discovered that a order-man system costs a big amount of money. I never thought about it but as I realized the real cost I had an idea: Why not use smartphones as “ordermans” and connect them to a common PC?. I presented my idea to my classmate Florian and we decided to realize the project together.''» Alex

== Motivation ==
Basically we need three things to create a really cheap order-man system:

* a smartphone
* a computer
* and a printer

Actually these three things are already available in nearly every bar or restaurant. From a small village pub to the most hidden refuge up in the mountains.

Just one thing is missing: the software.

= Development =

== Version 0.1 ==
*[[Use Cases v0.1]]
**Launch Server
**Login
**Logout
*[[Milestones v0.1]]
**Project Startup
**Server Startup
**Login / Logout

== Documentation ==

Global documents for the documentation of FOS:
*[[Requirements Specification]]
*[[Database Design]]
*[[Protocol Design]]
*[[Orderman Interface]]

=== How to write the FOS documentation ===
When we begin to develop a new version of FOS the first thing to do is to plan and schedule the whole work. This means:
* Add all the new requirements to the [[Requirements Specification]]. If the requirement for the new version is already described in this document this requirement will be updated.
* Make sure that the database provides all data that the new version of FOS needs
* Create and describe the use cases
* Create and describe the milestones with their related blueprints

=== Glossary ===
All specific words and abbreviations used in the FOS documentation are explained here:
* '''FOS''':
FOS is the abbreviation for ''Free Orderman System''
* '''orderman''':
Whenever the words ''orderman'', ''orderman interface'' or ''orderman application'' are used in the FOS documentation the interface which allows the waiter to order is meant.

</div>

FOS

2013-12-16T18:44:42Z

Master: added Orderman Interface as global document

<div id="mf-home">
= Introduction =
The Free Orderman System (FOS) wants to be a free solution for ordering management in bars, pubs, restaurants, clubs and so on. As an open source project it will be a fast, secure and simple software accessible to everyone.

== The FOS Development Team ==
The team consists of Alex Mazzon (18) and Florian Mahlknecht (18). See the team in [https://launchpad.net/~fosdevelopers Launchpad].

== The Idea ==

«''The idea to create a free order-man system was born in Innsbruck when I worked as waiter in an Italian restaurant last summer. There I discovered that a order-man system costs a big amount of money. I never thought about it but as I realized the real cost I had an idea: Why not use smartphones as “ordermans” and connect them to a common PC?. I presented my idea to my classmate Florian and we decided to realize the project together.''» Alex

== Motivation ==
Basically we need three things to create a really cheap order-man system:

* a smartphone
* a computer
* and a printer

Actually these three things are already available in nearly every bar or restaurant. From a small village pub to the most hidden refuge up in the mountains.

Just one thing is missing: the software.

= Development =

== Version 0.1 ==
*[[Use Cases v0.1]]
*[[Milestones v0.1]]

== Documentation ==

Global documents for the documentation of FOS:
*[[Requirements Specification]]
*[[Database Design]]
*[[Protocol Design]]
*[[Orderman Interface]]

=== How to write the FOS documentation ===
When we begin to develop a new version of FOS the first thing to do is to plan and schedule the whole work. This means:
* Add all the new requirements to the [[Requirements Specification]]. If the requirement for the new version is already described in this document this requirement will be updated.
* Make sure that the database provides all data that the new version of FOS needs
* Create and describe the use cases
* Create and describe the milestones with their related blueprints

=== Glossary ===
All specific words and abbreviations used in the FOS documentation are explained here:
* '''FOS''':
FOS is the abbreviation for ''Free Orderman System''
* '''orderman''':
Whenever the words ''orderman'', ''orderman interface'' or ''orderman application'' are used in the FOS documentation the interface which allows the waiter to order is meant.

</div>

Server Access

2013-12-06T21:35:07Z

Master: some updates...

= The Socket =
==Modify the project file==
The first thing to do is add ''networking'' to the project file, so that Qt knows that we wanna work with the network model.
==The Client==

The orderman socket uses the class [http://qt-project.org/doc/qt-5.1/qtnetwork/qtcpsocket.html QTcpSocket] to communicate with the FOS server. The function ''connect()'' connects the application socket to the FOS server on login. If the communication fails the user will be asked to set the right port. The application settings and an explanation how to set the correct port will be shown. The user will also be advertised to turn on wifi.

When the waiter starts the orderman the application has to find out the ip adress and the port which allows the communication with the server. The port is set in the application settings and must correspond to the FOS server port specified in the server settings. The class [http://qt-project.org/doc/qt-5.1/qtnetwork/qnetworkconfigurationmanager.html#details QNetworkConfiguration] provides access to the network configurations known to the system and allows to find out the router port with the function [http://qt-project.org/doc/qt-5.1/qtnetwork/qnetworkconfigurationmanager.html#allConfigurations allConfigurations]().

The function ''send()'' sends the JSON objects to the server. When the signal ''readyRead()'' is emitted by the server it means that the server sent back a JSON object.

The socket will be closed when the waiter logs out.

= Android Permissions =
The order man application must have the appropriate permissions that allow the connection to the server. An important permission to do that is the [http://developer.android.com/reference/android/Manifest.permission.html#INTERNET INTERNET] permission, which allows applications to open network sockets.

Server Access

2013-12-06T20:56:33Z

Master: /* The class FOSClient */

= The Socket =
==Modify the project file==
The first thing to do is add ''networking'' to the project file, so that Qt knows that we wanna work with the network model.
==The Client==

The orderman socket implements a [http://qt-project.org/doc/qt-5.1/qtnetwork/qtcpsocket.html QTcpSocket]. The function ''Connect'' connects the application socket to the FOS server. If the communication fails the user will be asked to set the right port. The application settings and an explanation how to set the correct port will be shown. The user will also be advertised to turn on wifi.

When the waiter starts the orderman the application has to find out the ip adress and the port which allows the communication with the server. The port is set in the application settings and must correspond to the FOS server port specified in the server settings. The class [http://qt-project.org/doc/qt-5.1/qtnetwork/qnetworkconfigurationmanager.html#details QNetworkConfiguration] provides access to the network configurations known to the system and allows to find out the router port with the function [http://qt-project.org/doc/qt-5.1/qtnetwork/qnetworkconfigurationmanager.html#allConfigurations allConfigurations]().

The function ''Send'' sends the JSON objects to the server and the function ''Receive'' waits for the answer.

The socket will be closed when the waiter logs out.

= Android Permissions =
The order man application must have the appropriate permissions that allow the connection to the server. An important permission to do that is the [http://developer.android.com/reference/android/Manifest.permission.html#INTERNET INTERNET] permission, which allows applications to open network sockets.

Server Access

2013-12-05T06:07:11Z

Master: added some titles for more overview

= The Socket =
==Modify the project file==
The first thing to do is add ''networking'' to the project file, so that Qt knows that we wanna work with the network model.
==The class FOSClient==
When the waiter starts the orderman the application has to find out the ip adress and the port which allows the communication with the server. The port is set in the application settings and must correspond to the FOS server port specified in the server settings. The class [http://qt-project.org/doc/qt-5.1/qtnetwork/qnetworkconfigurationmanager.html#details QNetworkConfiguration] provides access to the network configurations known to the system and allows to find out the router port with the function [http://qt-project.org/doc/qt-5.1/qtnetwork/qnetworkconfigurationmanager.html#allConfigurations allConfigurations]().

The orderman socket implements a [http://qt-project.org/doc/qt-5.1/qtnetwork/qtcpsocket.html QTcpSocket]. The function ''Connect'' connects the application socket to the FOS server. If the communication fails the user will be asked to set the right port. The application settings and an explanation how to set the correct port will be shown. The user will also be advertised to turn on wifi.

The function ''Send'' sends the JSON objects to the server and the function ''Receive'' waits for the answer.

The socket will be closed when the waiter logs out.

= Android Permissions =
The order man application must have the appropriate permissions that allow the connection to the server. An important permission to do that is the [http://developer.android.com/reference/android/Manifest.permission.html#INTERNET INTERNET] permission, which allows applications to open network sockets.

Server Access

2013-11-26T14:53:56Z

Master: turn on wifi!

= The Socket =
The first thing to do is add ''networking'' to the project file, so that Qt knows that we wanna work with the network model.

When the waiter starts the orderman the application has to find out the ip adress and the port which allows the communication with the server. The port is set in the application settings and must correspond to the FOS server port specified in the server settings. The class [http://qt-project.org/doc/qt-5.1/qtnetwork/qnetworkconfigurationmanager.html#details QNetworkConfiguration] provides access to the network configurations known to the system and allows to find out the router port with the function [http://qt-project.org/doc/qt-5.1/qtnetwork/qnetworkconfigurationmanager.html#allConfigurations allConfigurations]().

The orderman socket implements a [http://qt-project.org/doc/qt-5.1/qtnetwork/qtcpsocket.html QTcpSocket]. The function ''Connect'' connects the application socket to the FOS server. If the communication fails the user will be asked to set the right port. The application settings and an explanation how to set the correct port will be shown. The user will also be advertised to turn on wifi.

The function ''Send'' sends the JSON objects to the server and the function ''Receive'' waits for the answer.

The socket will be closed when the waiter logs out.

= Android Permissions =
The order man application must have the appropriate permissions that allow the connection to the server. An important permission to do that is the [http://developer.android.com/reference/android/Manifest.permission.html#INTERNET INTERNET] permission, which allows applications to open network sockets.

Server Access

2013-11-26T14:31:43Z

Master: added how to find out the router port

= The Socket =
The first thing to do is add ''networking'' to the project file, so that Qt knows that we wanna work with the network model.

When the waiter starts the orderman the application has to find out the ip adress and the port which allows the communication with the server. The port is set in the application settings and must correspond to the FOS server port specified in the server settings. The class [http://qt-project.org/doc/qt-5.1/qtnetwork/qnetworkconfigurationmanager.html#details QNetworkConfiguration] provides access to the network configurations known to the system and allows to find out the router port with the function [http://qt-project.org/doc/qt-5.1/qtnetwork/qnetworkconfigurationmanager.html#allConfigurations allConfigurations]().

The orderman socket implements a [http://qt-project.org/doc/qt-5.1/qtnetwork/qtcpsocket.html QTcpSocket]. The function ''Connect'' connects the application socket to the FOS server. If the communication fails the user will be asked to set the right port. The application settings and an explanation how to set the correct port will be shown.

The function ''Send'' sends the JSON objects to the server and the function ''Receive'' waits for the answer.

The socket will be closed when the waiter logs out.

= Android Permissions =
The order man application must have the appropriate permissions that allow the connection to the server. An important permission to do that is the [http://developer.android.com/reference/android/Manifest.permission.html#INTERNET INTERNET] permission, which allows applications to open network sockets.

Server Access

2013-11-21T09:19:59Z

Master: Added description fir ip adress, not finished ye! see todo

= The Socket =
The first thing to do is add ''networking'' to the project file, so that Qt knows that we wanna work with the network model.

When the waiter starts the orderman the application has to find out the ip adress and the port which allows the communication with the server. The port is set in the application settings and must correspond to the FOS server port specified in the server settings. The ip adress of the router TODO

The orderman socket implements a [http://qt-project.org/doc/qt-5.1/qtnetwork/qtcpsocket.html QTcpSocket]. The function ''Connect'' connects the application socket to the FOS server. If the communication fails the user will be asked to set the right port. The application settings and an explanation how to set the correct port will be shown.

The function ''Send'' sends the JSON objects to the server and the function ''Receive'' waits for the answer.

The socket will be closed when the waiter logs out.

= Android Permissions =
The order man application must have the appropriate permissions that allow the connection to the server. An important permission to do that is the [http://developer.android.com/reference/android/Manifest.permission.html#INTERNET INTERNET] permission, which allows applications to open network sockets.

Server Access

2013-11-20T20:29:37Z

Master: added some decription

= The Socket =
The first thing to do is add ''networking'' to the project file, so that Qt knows that we wanna work with the network model.

When the waiter starts the orderman the application has to find out which port allows the communication with the server. This port is set in the application settings and must correspond to the FOS server port specified in the server settings.

The orderman socket implements a [http://qt-project.org/doc/qt-5.1/qtnetwork/qtcpsocket.html QTcpSocket]. The function ''Connect'' connects the application socket to the FOS server. If the communication fails the user will be asked to set the right port. The application settings and an explanation how to set the correct port will be shown.

The function ''Send'' sends the JSON objects to the server and the function ''Receive'' waits for the answer.

The socket will be closed when the waiter logs out.

= Android Permissions =
The order man application must have the appropriate permissions that allow the connection to the server. An important permission to do that is the [http://developer.android.com/reference/android/Manifest.permission.html#INTERNET INTERNET] permission, which allows applications to open network sockets.

Orderman Interface

2013-11-20T19:35:04Z

Master: /* Logout */

Orderman Interface

2013-11-20T19:33:28Z

Master: created page: login/logout

FOS

2013-11-14T09:12:01Z

Master: /* The Idea */

= Introduction =
The Free Orderman System (FOS) wants to be a free solution for ordering management in bars, pubs, restaurants, clubs and so on. As an open source project it will be a fast, secure and simple software accessible to everyone.

== The FOS Development Team ==
The team consists of Alex Mazzon (18) and Florian Mahlknecht (18). See the team in [https://launchpad.net/~fosdevelopers Launchpad].

== The Idea ==

«''The idea to create a free order-man system was born in Innsbruck when I worked as waiter in an Italian restaurant last summer. There I discovered that a order-man system costs a big amount of money. I never thought about it but as I realized the real cost I had an idea: Why not use smartphones as “ordermans” and connect them to a common PC?. I presented my idea to my classmate Florian and we decided to realize the project together.''» Alex

== Motivation ==
Basically we need three things to create a really cheap order-man system:

* a smartphone
* a computer
* and a printer

Actually these three things are already available in nearly every bar or restaurant. From a small village pub to the most hidden refuge up in the mountains.

Just one thing is missing: the software.

= Development =

== Documentation ==

Global documents for the documentation of FOS:
*[[Requirements Specification]]
*[[Database Design]]

=== How to write the FOS documentation ===
When we begin to develop a new version of FOS the first thing to do is to plan and schedule the whole work. This means:
* Add all the new requirements to the [[Requirements Specification]]. If the requirement for the new version is already described in this document this requirement will be updated.
* Make sure that the database provides all data that the new version of FOS needs
* Create and describe the use cases
* Create and describe the milestones with their related blueprints

=== Glossary ===
All specific words and abbreviations used in the FOS documentation are explained here:
* '''FOS''':
FOS is the abbreviation for ''Free Orderman System''
* '''orderman''':
Whenever the words ''orderman'', ''orderman interface'' or ''orderman application'' are used in the FOS documentation the interface which allows the waiter to order is meant.

== Version 0.1 ==
*[[Use Cases v0.1]]
*[[Milestones v0.1]]

Database Design

2013-11-13T21:22:44Z

Master: created page and added the db design image

[[File:Db-design.jpg]]

File:Db-design.jpg

2013-11-13T21:20:43Z

Master: The FOS database design

The FOS database design

FOS

2013-11-13T21:14:58Z

Master: /* The FOS Development Team */

= Introduction =
The Free Orderman System (FOS) wants to be a free solution for ordering management in bars, pubs, restaurants, clubs and so on. As an open source project it will be a fast, secure and simple software accessible to everyone.

== The FOS Development Team ==
The team consists of Alex Mazzon (18) and Florian Mahlknecht (18). See the team in [https://launchpad.net/~fosdevelopers Launchpad].

== The Idea ==

«''The idea to create a free order-man system was born in Innsbruck when I worked as waiter in an Italian restaurant last summer. There I discovered that a order-man system costs a big amount of money. I never thought about it but as I realized the real cost I had an idea: Why not use smartphones as “ordermans” and connect them to a common PC?''. I presented my idea to my classmate Florian and we decided to realize the project together.» Alex

== Motivation ==
Basically we need three things to create a really cheap order-man system:

* a smartphone
* a computer
* and a printer

Actually these three things are already available in nearly every bar or restaurant. From a small village pub to the most hidden refuge up in the mountains.

Just one thing is missing: the software.

= Development =

== Documentation ==

Global documents for the documentation of FOS:
*[[Requirements Specification]]
*[[Database Design]]

=== How to write the FOS documentation ===
When we begin to develop a new version of FOS the first thing to do is to plan and schedule the whole work. This means:
* Add all the new requirements to the [[Requirements Specification]]. If the requirement for the new version is already described in this document this requirement will be updated.
* Make sure that the database provides all data that the new version of FOS needs
* Create and describe the use cases
* Create and describe the milestones with their related blueprints

=== Glossary ===
All specific words and abbreviations used in the FOS documentation are explained here:
* '''FOS''':
FOS is the abbreviation for ''Free Orderman System''
* '''orderman''':
Whenever the words ''orderman'', ''orderman interface'' or ''orderman application'' are used in the FOS documentation the interface which allows the waiter to order is meant.

== Version 0.1 ==
*[[Use Cases v0.1]]
*[[Milestones v0.1]]

FOS

2013-11-13T21:11:24Z

Master: /* How to write the FOS documentation */

= Introduction =
The Free Orderman System (FOS) wants to be a free solution for ordering management in bars, pubs, restaurants, clubs and so on. As an open source project it will be a fast, secure and simple software accessible to everyone.

== The FOS Development Team ==
The team consists of Alex Mazzon (18) and Florian Mahlknecht (18).

== The Idea ==

«''The idea to create a free order-man system was born in Innsbruck when I worked as waiter in an Italian restaurant last summer. There I discovered that a order-man system costs a big amount of money. I never thought about it but as I realized the real cost I had an idea: Why not use smartphones as “ordermans” and connect them to a common PC?''. I presented my idea to my classmate Florian and we decided to realize the project together.» Alex

== Motivation ==
Basically we need three things to create a really cheap order-man system:

* a smartphone
* a computer
* and a printer

Actually these three things are already available in nearly every bar or restaurant. From a small village pub to the most hidden refuge up in the mountains.

Just one thing is missing: the software.

= Development =

== Documentation ==

Global documents for the documentation of FOS:
*[[Requirements Specification]]
*[[Database Design]]

=== How to write the FOS documentation ===
When we begin to develop a new version of FOS the first thing to do is to plan and schedule the whole work. This means:
* Add all the new requirements to the [[Requirements Specification]]. If the requirement for the new version is already described in this document this requirement will be updated.
* Make sure that the database provides all data that the new version of FOS needs
* Create and describe the use cases
* Create and describe the milestones with their related blueprints

=== Glossary ===
All specific words and abbreviations used in the FOS documentation are explained here:
* '''FOS''':
FOS is the abbreviation for ''Free Orderman System''
* '''orderman''':
Whenever the words ''orderman'', ''orderman interface'' or ''orderman application'' are used in the FOS documentation the interface which allows the waiter to order is meant.

== Version 0.1 ==
*[[Use Cases v0.1]]
*[[Milestones v0.1]]

FOS

2013-11-13T21:10:39Z

Master: /* How to write the FOS documentation */

= Introduction =
The Free Orderman System (FOS) wants to be a free solution for ordering management in bars, pubs, restaurants, clubs and so on. As an open source project it will be a fast, secure and simple software accessible to everyone.

== The FOS Development Team ==
The team consists of Alex Mazzon (18) and Florian Mahlknecht (18).

== The Idea ==

«''The idea to create a free order-man system was born in Innsbruck when I worked as waiter in an Italian restaurant last summer. There I discovered that a order-man system costs a big amount of money. I never thought about it but as I realized the real cost I had an idea: Why not use smartphones as “ordermans” and connect them to a common PC?''. I presented my idea to my classmate Florian and we decided to realize the project together.» Alex

== Motivation ==
Basically we need three things to create a really cheap order-man system:

* a smartphone
* a computer
* and a printer

Actually these three things are already available in nearly every bar or restaurant. From a small village pub to the most hidden refuge up in the mountains.

Just one thing is missing: the software.

= Development =

== Documentation ==

Global documents for the documentation of FOS:
*[[Requirements Specification]]
*[[Database Design]]

=== How to write the FOS documentation ===
When we begin to develop a new version of FOS the first thing to do is to plan and schedule the whole work. This means:
* Add all the new requirements to the [[Requirements Specification]]. If the requirement for the new version is already described in this document this requirement will be updated.
* Make sure that the database provides all data that the new version of FOS needs
* Create the use cases
* Create the milestones and the related blueprints

=== Glossary ===
All specific words and abbreviations used in the FOS documentation are explained here:
* '''FOS''':
FOS is the abbreviation for ''Free Orderman System''
* '''orderman''':
Whenever the words ''orderman'', ''orderman interface'' or ''orderman application'' are used in the FOS documentation the interface which allows the waiter to order is meant.

== Version 0.1 ==
*[[Use Cases v0.1]]
*[[Milestones v0.1]]

FOS

2013-11-13T19:01:46Z

Master: /* The Idea */

= Introduction =
The Free Orderman System (FOS) wants to be a free solution for ordering management in bars, pubs, restaurants, clubs and so on. As an open source project it will be a fast, secure and simple software accessible to everyone.

== The FOS Development Team ==
The team consists of Alex Mazzon (18) and Florian Mahlknecht (18).

== The Idea ==

«''The idea to create a free order-man system was born in Innsbruck when I worked as waiter in an Italian restaurant last summer. There I discovered that a order-man system costs a big amount of money. I never thought about it but as I realized the real cost I had an idea: Why not use smartphones as “ordermans” and connect them to a common PC?''. I presented my idea to my classmate Florian and we decided to realize the project together.» Alex

== Motivation ==
Basically we need three things to create a really cheap order-man system:

* a smartphone
* a computer
* and a printer

Actually these three things are already available in nearly every bar or restaurant. From a small village pub to the most hidden refuge up in the mountains.

Just one thing is missing: the software.

= Development =

== Documentation ==

Global documents for the documentation of FOS:
*[[Requirements Specification]]
*[[Database Design]]

=== How to write the FOS documentation ===
When we begin to develop a new version of FOS the first thing to do is to plan and schedule the whole work. This means:
* Add all the new requirements to the [[Requirements Specification]]. If the requirement for the new version is already described in this document this requirement will be updated.
* Make sure that the database provides all data that the new version of FOS will use
* Create the use cases
* Create the milestones and the related blueprints

=== Glossary ===
All specific words and abbreviations used in the FOS documentation are explained here:
* '''FOS''':
FOS is the abbreviation for ''Free Orderman System''
* '''orderman''':
Whenever the words ''orderman'', ''orderman interface'' or ''orderman application'' are used in the FOS documentation the interface which allows the waiter to order is meant.

== Version 0.1 ==
*[[Use Cases v0.1]]
*[[Milestones v0.1]]

FOS

2013-11-13T19:00:06Z

Master: /* The Idea */

= Introduction =
The Free Orderman System (FOS) wants to be a free solution for ordering management in bars, pubs, restaurants, clubs and so on. As an open source project it will be a fast, secure and simple software accessible to everyone.

== The FOS Development Team ==
The team consists of Alex Mazzon (18) and Florian Mahlknecht (18).

== The Idea ==
Alex:

«''The idea to create a free order-man system was born in Innsbruck when I worked as waiter in an Italian restaurant last summer. There I discovered that a order-man system costs a big amount of money. I never thought about it but as I realized the real cost I had an idea: Why not use smartphones as “ordermans” and connect them to a common PC?''. I presented my idea to my classmate Florian and we decided to realize the project together.»

== Motivation ==
Basically we need three things to create a really cheap order-man system:

* a smartphone
* a computer
* and a printer

Actually these three things are already available in nearly every bar or restaurant. From a small village pub to the most hidden refuge up in the mountains.

Just one thing is missing: the software.

= Development =

== Documentation ==

Global documents for the documentation of FOS:
*[[Requirements Specification]]
*[[Database Design]]

=== How to write the FOS documentation ===
When we begin to develop a new version of FOS the first thing to do is to plan and schedule the whole work. This means:
* Add all the new requirements to the [[Requirements Specification]]. If the requirement for the new version is already described in this document this requirement will be updated.
* Make sure that the database provides all data that the new version of FOS will use
* Create the use cases
* Create the milestones and the related blueprints

=== Glossary ===
All specific words and abbreviations used in the FOS documentation are explained here:
* '''FOS''':
FOS is the abbreviation for ''Free Orderman System''
* '''orderman''':
Whenever the words ''orderman'', ''orderman interface'' or ''orderman application'' are used in the FOS documentation the interface which allows the waiter to order is meant.

== Version 0.1 ==
*[[Use Cases v0.1]]
*[[Milestones v0.1]]

FOS

2013-11-13T18:59:32Z

Master: /* The Idea */

= Introduction =
The Free Orderman System (FOS) wants to be a free solution for ordering management in bars, pubs, restaurants, clubs and so on. As an open source project it will be a fast, secure and simple software accessible to everyone.

== The FOS Development Team ==
The team consists of Alex Mazzon (18) and Florian Mahlknecht (18).

== The Idea ==
Alex:

«''The idea to create a free order-man system was born in Innsbruck when I worked as waiter in an Italian restaurant last summer. There I discovered that a order-man system costs a big amount of money. I never thought about it but as I realized the real cost I had an idea: Why not use smartphones as “ordermans” and connect them to a common PC?''»

I presented my idea to my classmate Florian and we decided to realize the project together.

== Motivation ==
Basically we need three things to create a really cheap order-man system:

* a smartphone
* a computer
* and a printer

Actually these three things are already available in nearly every bar or restaurant. From a small village pub to the most hidden refuge up in the mountains.

Just one thing is missing: the software.

= Development =

== Documentation ==

Global documents for the documentation of FOS:
*[[Requirements Specification]]
*[[Database Design]]

=== How to write the FOS documentation ===
When we begin to develop a new version of FOS the first thing to do is to plan and schedule the whole work. This means:
* Add all the new requirements to the [[Requirements Specification]]. If the requirement for the new version is already described in this document this requirement will be updated.
* Make sure that the database provides all data that the new version of FOS will use
* Create the use cases
* Create the milestones and the related blueprints

=== Glossary ===
All specific words and abbreviations used in the FOS documentation are explained here:
* '''FOS''':
FOS is the abbreviation for ''Free Orderman System''
* '''orderman''':
Whenever the words ''orderman'', ''orderman interface'' or ''orderman application'' are used in the FOS documentation the interface which allows the waiter to order is meant.

== Version 0.1 ==
*[[Use Cases v0.1]]
*[[Milestones v0.1]]

FOS

2013-11-13T18:56:06Z

Master:

= Introduction =
The Free Orderman System (FOS) wants to be a free solution for ordering management in bars, pubs, restaurants, clubs and so on. As an open source project it will be a fast, secure and simple software accessible to everyone.

== The FOS Development Team ==
The team consists of Alex Mazzon (18) and Florian Mahlknecht (18).

== The Idea ==
Alex: ''The idea to create a free order-man system was born in Innsbruck when I worked as waiter in an Italian restaurant last summer. There I discovered that a order-man system costs a big amount of money. I never thought about it but as I realized the real cost I had an idea: Why not use smartphones as “ordermans” and connect them to a common PC?''

I presented my idea to my classmate Florian and we decided to realize the project together.

== Motivation ==
Basically we need three things to create a really cheap order-man system:

* a smartphone
* a computer
* and a printer

Actually these three things are already available in nearly every bar or restaurant. From a small village pub to the most hidden refuge up in the mountains.

Just one thing is missing: the software.

= Development =

== Documentation ==

Global documents for the documentation of FOS:
*[[Requirements Specification]]
*[[Database Design]]

=== How to write the FOS documentation ===
When we begin to develop a new version of FOS the first thing to do is to plan and schedule the whole work. This means:
* Add all the new requirements to the [[Requirements Specification]]. If the requirement for the new version is already described in this document this requirement will be updated.
* Make sure that the database provides all data that the new version of FOS will use
* Create the use cases
* Create the milestones and the related blueprints

=== Glossary ===
All specific words and abbreviations used in the FOS documentation are explained here:
* '''FOS''':
FOS is the abbreviation for ''Free Orderman System''
* '''orderman''':
Whenever the words ''orderman'', ''orderman interface'' or ''orderman application'' are used in the FOS documentation the interface which allows the waiter to order is meant.

== Version 0.1 ==
*[[Use Cases v0.1]]
*[[Milestones v0.1]]

FOS

2013-11-13T18:55:34Z

Master: Added FOS Development Team, Glossary and How to write the FOS documentation

= Introduction =
The Free Orderman System (FOS) wants to be a free solution for ordering management in bars, pubs, restaurants, clubs and so on. As an open source project it will be a fast, secure and simple software accessible to everyone.

== The FOS Development Team ==
The team consists of Alex Mazzon (18) and Florian Mahlknecht (18).

== The Idea ==
Alex: The idea to create a free order-man system was born in Innsbruck when I worked as waiter in an Italian restaurant last summer. There I discovered that a order-man system costs a big amount of money. I never thought about it but as I realized the real cost I had an idea: Why not use smartphones as “ordermans” and connect them to a common PC?

I presented my idea to my classmate Florian and we decided to realize the project together.

== Motivation ==
Basically we need three things to create a really cheap order-man system:

* a smartphone
* a computer
* and a printer

Actually these three things are already available in nearly every bar or restaurant. From a small village pub to the most hidden refuge up in the mountains.

Just one thing is missing: the software.

= Development =

== Documentation ==

Global documents for the documentation of FOS:
*[[Requirements Specification]]
*[[Database Design]]

=== How to write the FOS documentation ===
When we begin to develop a new version of FOS the first thing to do is to plan and schedule the whole work. This means:
* Add all the new requirements to the [[Requirements Specification]]. If the requirement for the new version is already described in this document this requirement will be updated.
* Make sure that the database provides all data that the new version of FOS will use
* Create the use cases
* Create the milestones and the related blueprints

=== Glossary ===
All specific words and abbreviations used in the FOS documentation are explained here:
* '''FOS''':
FOS is the abbreviation for ''Free Orderman System''
* '''orderman''':
Whenever the words ''orderman'', ''orderman interface'' or ''orderman application'' are used in the FOS documentation the interface which allows the waiter to order is meant.

== Version 0.1 ==
*[[Use Cases v0.1]]
*[[Milestones v0.1]]

Milestones v0.1

2013-11-13T17:49:09Z

Master: added name

= Project Startup (britney) =
This milestone includes the initial work that has to be done to be able to split the work:
* [[Database Design]]
* [[Protocol Design]]

= Server Startup (melissa) =
To perform the connection- and data management, the server has to arrange the following things:
* [[Database Access]]
* [[Asynchronous Client Handling]]
* [[Administrative User Interface]]

= Login / Logout (sarah) =
To be able to log in on the client application, the connection to the server must be established ([[Server Access]]).
In order to get a successful response, the server has to [[JSON Objects Handling|handle the JSON Objects]].
The [[Orderman Interface]] must provide the login and logout functionality.