Skip to content

mikeebid/TeaRoom-Ing.Software-Systems-Unibo

Repository files navigation

Final Project - Software Systems Engineering M

Read the documentation for more information: installation, git structure

Introduction

The manager of a tearoom intends to regulate the access to the service by means of a ddr robot (waiter).

The tearoom is a rectangular room that includes:

  • an entrancedoor to enter in the room and an exitdoor to exit form it;
  • a number N (N=2) of teatable;
  • a serviceare including a servicedesk at which works a barman;
  • a hall equipped with a presencedetector, i.e. a device (e.g. a sonar) that can detect the presence of a person (or some other entity) in it.

The waiter can freely move along the borders of the tearoom, since there are no obstacles there.

Requirements

The waiter should perform the following tasks:

  • accept the request of a client to enter in the tearoom if there is at least one teatable in the state tableclean, i.e. the table is free and has been properly cleaned;
  • inform the client about the maximum waiting time if there is no tableclean;
  • reach the entrance door and convoy the accepted client to the selected teatable;
  • take the order of the client and transmit it (using a wifi-device) to the barman;
  • serve the client when the barman says that the requested drink is ready;
  • collect the payment from the client when he/she has finished to consume or when the maxstaytime is expired;
  • convoy the client to the exitdoor;
  • clean the tea-table just freed by the client;
  • rest at my home when there is nothing to do.

Since the room could contain N clients at the time, the waiter should reduce as much as possible the waiting time of the requests coming from each client.

Optional: one client in the hall

The waiter must open the exitdoor only when the hall is free, i.e. it must not open that door if the hall is already engaged by a client waiting to enter at the entrancedoor.

Non functional requirements

  • The ideal work team is composed of 3 persons. Teams of 1 or 2 persons (NOT 4 or more) are also allowed.
  • The team must present a workplan as the result of the requirement/problem analysis, including some significant TestPlan.
  • The team must present the sequence of SPRINT performed, with appropriate motivations.
  • The team must present (in synthetic, schematic way) the specific activity of each team-component.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published