FOS Wiki - User contributions [en]

Milestones v0.2

2014-04-26T09:15:39Z

Admin:

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

= DataManagement on Server =
Through an user-interface on the server it's possible to modify, insert, delete the basic data sets: location, table, category and products. All these changes will be real-time reported to the connected clients, and the preparation (the signals) for this intention will be already implemented in this version.

Protocol Design

2014-03-02T10:38:06Z

Admin: Introduced the basic concepts of the protocol

= Basics =
The hole communication is based on a TCP/IP connection.
The server and the client communicate to each other through UTF-8 encoded messages.

== Message ==
A message is a json encoded object. Each message has a common "type" property, which determines it's type.
The message ends with the determination of the json object: <code>}</code>.

= Session =
To start a session the client must send a valid username and password encapsulated in the json object "Login".

[[File:protocol-login-logout.png]]

= Dynamic Data (Server ⇒ Client) =

The protocol design is ''not'' based on a request-response concept. It's based on a concept similar to the model-view concept. The idea behind is: On login the client receives the current data: all locations, all tables, all orders, all products, ... . On each change of the data on server-side, the client gets an ''update''. The goal is to have a valid (up-to-date) data pool all the time on every client.

To achieve this, it's necessary to have id-value based data structures - to be able to identify a data set in an update.

Protocol Design

2014-02-06T13:27:19Z

Admin: added dynamic data section...

Protocol Design

2014-02-06T13:04:07Z

Admin: /* Login - Logout */

Protocol Design

2014-02-06T12:59:53Z

Admin: /* Message */

Protocol Design

2014-02-06T12:56:34Z

Admin: Started clean protocol specification

Use Cases v0.2

2014-01-13T18:45:25Z

Admin:

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

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

Use Cases v0.2

2014-01-13T18:44:24Z

Admin:

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

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

Use Cases v0.3

2014-01-13T11:59:03Z

Admin: Created page with "= 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..."

= 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-13T11:58:47Z

Admin: Moving it to v0.3

Use Cases v0.2

2014-01-13T11:57:24Z

Admin: Added locations

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

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

Asynchronous Client Handling

2014-01-07T13:50:33Z

Admin:

Client Handling has to be asynchronous, because each client must be able to communicate to the others without blocking the system.
= Threads =
The first intention is to make one thread for each client. This has several advantages:
* they can easily communicate to each other using QT's powerful singnals- and slots mechanism
* no problems to maintain a list of all client(-threads)

Milestones v0.1

2014-01-06T15:00:32Z

Admin: Removed DB Access, moving it to the next version

= 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:
* [[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.

JSON Objects Handling

2014-01-06T14:52:45Z

Admin: Created page with "Handling the json objects is necessary on both sides - the client and the server side. Since both sides are written in C++, we can put together some functions to convert the s..."

Handling the json objects is necessary on both sides - the client and the server side.
Since both sides are written in C++, we can put together some functions to convert the strings to defined types.

Basically we need to functions:

*toJson(Object)
*parseJson(String)

Since parseJson() must return different types it suites to use QVariant.

Asynchronous Client Handling

2013-12-14T15:13:22Z

Admin: Created page with "Client Handling has to be asynchronous, because each client must be able to communicate to the others without blocking the system. = Threads = The first intention is to make o..."

Client Handling has to be asynchronous, because each client must be able to communicate to the others without blocking the system.
= Threads =
The first intention is to make one thread for each client. This has several advantages:
* they can easily communicate to each other
* no problems to maintain a list of all client(-threads)
* using QT's powerful singnals- and slots mechanism

Administrative User Interface

2013-12-14T15:06:48Z

Admin: explained the administrative user interface

The administrative user interface contains simply a button to start and stop the server with a text browser underneath to show status information.

Protocol Design

2013-11-26T14:25:09Z

Admin: explained the type property

= Protocol =
The communication is based on JSON objects. As first property every object has a "type" string, which determines the structure of the json object.

= Login - Logout =
[[File:protocol-login-logout.png]]

FOS

2013-11-20T19:51:29Z

Admin: added link to protocol design

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

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

Protocol Design

2013-11-20T19:50:11Z

Admin: Started Page

= Protocol =
The communication is based on JSON objects.

= Login - Logout =
[[File:protocol-login-logout.png]]

File:Protocol-login-logout.png

2013-11-20T19:41:32Z

Admin: Activity diagramm for the login - logout procedure

Activity diagramm for the login - logout procedure

FOS

2013-11-15T16:25:40Z

Admin: Enabled the main page on mobile devices

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

=== 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-11-14T09:55:29Z

Admin: moved versions to the top

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

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

Milestones v0.1

2013-11-11T15:22:34Z

Admin: Added Project Startup (the first milestone) and the codenames

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

Milestones v0.1

2013-11-08T07:57:34Z

Admin: /* Login / Logout */

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

= Login / Logout =
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]].

FOS

2013-11-07T18:51:58Z

Admin: /* Development */

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

*[[Requirements Specification]]
*[[Database Design]]

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

Milestones v0.1

2013-11-07T18:50:33Z

Admin: Initial definition of the two milestones for v0.1

Use Cases v0.1

2013-11-07T17:24:48Z

Admin: created page

= Launch Server =
Everyone can start the server by launching FOS. At this point the computer (server) must be connected to the wireless router which provides the communication. This router must be configured to port forward the FOS server port specified in the settings.
= Login =
The user gets a login name and a password which he enters in the login form and gets access to the system.
To test this use case some test users are created manually on the database.
= Logout =
The user can logout from the system by clicking on a simple button.

FOS

2013-11-07T17:17:00Z

Admin: database design added

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

[[Requirements Specification]]
[[Database Design]]

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

Requirements Specification

2013-11-07T16:57:30Z

Admin: specified login/logout and server startup

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

FOS

2013-11-07T16:30:44Z

Admin: added v0.1

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

[[Requirements Specification]]

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

Requirements Specification

2013-11-07T16:29:01Z

Admin: created page

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

Requirements Specification

2013-11-07T16:27:27Z

Admin: moved Requirments Specification to Requirements Specification: spelling error

= Requirements Specification =

FOS

2013-11-07T16:26:38Z

Admin:

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

[[Requirements Specification]]

FOS

2013-11-07T16:17:37Z

Admin: roadmap deleted

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

Requirements Specification

2013-11-07T14:09:45Z

Admin: Created page with "= Requirements Specification ="

= Requirements Specification =

FOS

2013-11-07T14:03:04Z

Admin: /* Roadmap */

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

= Roadmap =
[[Image:Roadmap.png]]

FOS

2013-11-06T17:23:55Z

Admin:

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

= Roadmap =
[[Image:]]

FOS

2013-11-06T17:09:50Z

Admin:

<center>Free Orderman System</center>

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

= Roadmap =
[[Image:]]

MediaWiki:Mainpage

2013-11-06T11:04:56Z

Admin: Die Seite wurde neu angelegt: „FOS“

FOS

2013-11-06T10:53:52Z

Admin: Der Seiteninhalt wurde durch einen anderen Text ersetzt: „Introduction to FOS“

Introduction to FOS

FOS

2013-11-06T10:51:55Z

Admin: hat „Hauptseite“ nach „FOS“ verschoben: Moving the main page to "FOS" to give there an introduction to the project

'''MediaWiki wurde erfolgreich installiert.'''

Hilfe zur Benutzung und Konfiguration der Wiki-Software findest du im [http://meta.wikimedia.org/wiki/Help:Contents Benutzerhandbuch].

== Starthilfen ==

* [http://www.mediawiki.org/wiki/Manual:Configuration_settings Liste der Konfigurationsvariablen]
* [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki-FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce Mailingliste neuer MediaWiki-Versionen]