About The Project: Difference between revisions

From Ameise-en
Jump to navigationJump to search
No edit summary
No edit summary
 
(40 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Image:AmeiseWall.gif|right|310px|thumbnail|Ameise Wall - Project overview]]
[[Image:AmeiseWall_en.png|right|310px|thumbnail|Ameise Wall - Project Overview]]
The '''AMEISE-System''' provides students of informatics,business informatics and economics as well as subject-related university or college-studies, the ability to collect project-managment experience on a '''simulator'''. Critical situations can be defined and trained with AMEISE without getting a real project in danger.  
The '''AMEISE-System''' provides students of informatics, business informatics and economics as well as subject-related university or college-studies, the ability to collect project management experience on a '''simulator'''. Critical situations can be defined and trained with AMEISE without getting a real project in danger.  


Future project-leaders can execute projects in a few hours that would normally take several months. They also get confronted with typical problems of projects and should solve them.  
Future project-leaders can execute projects in a few hours that would normally take several months. They also get confronted with typical problems of projects and should solve them.  


Currently the AMEISE system offers three different '''models''': a ''Beginner-Model'' (Mini model, with less requirements), a ''Standard model'' (with a particular focus on quality assurance), and a ''Maintenance-model'' (which is based on the activities after delivery the product).
Currently the AMEISE system offers three different '''models''': a ''Beginner-Model'' (Mini model, with less requirements), a ''Standard model'' (with a particular focus on quality assurance), and a ''Maintenance-model'' (which is based on the activities after delivering the product).
AMEISE is more than a simulator. The instructor can activate many different components for example '''the advisor''' or '''evaluation components'''. A special feature is the ability to simulate at certain points reset ('''rollback'''). Thereby different variants can be tested by the project leader(for example change developers or using a different strategy) and then the results can be compared.
AMEISE is more than a simulator. The instructor can activate many different components, for example '''the advisor''' or '''evaluation components'''. A special feature is the ability to reset the simulation run at a certain point in time('''rollback'''). Thereby different variants can be tested by the project leader (for example change developers or using a different strategy) and then the results can be compared.  


Started in 2001 as part of a nml project from bm:bwk,AMEISE is used on several universities and colleges in austria,germany and the magreb region.The heart of the AMEISE-system is ([http://www.iste.uni-stuttgart.de/se/research/sesam SESAM])which was developed at the university of stuttgart(Prof. Jochen Ludewig)and related [http://www.iste.uni-stuttgart.de/se/research/sesam/models/index.html Quality assurance models] (also referred as QA-models).  
Started in 2001 as part of a nml project from bm:bwk / Austria, AMEISE is and has been used at several Universities and Colleges in Austria, Germany and the Maghreb region. The heart of the AMEISE-system is ([http://www.iste.uni-stuttgart.de/se/research/sesam SESAM]) which was developed at the University of Stuttgart (Prof. Jochen Ludewig) and its related
[http://www.iste.uni-stuttgart.de/se/research/sesam/models/index.html Quality Assurance Models] (also referred to as QA-models).  


== Components of the project==
== Components of the Project==


AMEISE is a Client-Server System, which can be executed locally on a computer or distributed in intranet or internet. The system is designed so that even unstable compounds have no effect on the simulation.As a trainee you can use the AMEISE client to manage a virtual project what means to distribute tasks,to have an overview about the project and of course to deliver your product at the end of the simulation run.  
AMEISE is a Client-Server System which can be executed locally on a computer or distributed in intranet or internet. The system is designed so that even unstable environments have no effect on the simulation runs. As a trainee you can use the AMEISE client to manage a virtual project which means to delegate tasks, do project control and, of course, to deliver a product of acceptable quality at the end of the simulation run.


=== Client ===
=== Client ===
[[Image:AfterLogin.gif|right|thumbnail|SimulationPlus- Interface for users]]
[[Image:Client_nach_dem_Anmelden_en.png|right|thumbnail|SimulationPlus- User Interface]]


The AMEISE client provides a graphical interface for trainees and designed as a java-application it runs virtually on every platform. Comment inputs and feedbacks are usually text-based, but to make the inputs more comfortable there is also a mouse-based version available:
The AMEISE client provides a graphical interface for trainees and is implemented as a Java-application that runs virtually on every platform. Comment inputs and feedbacks are usually text-based, but to make the inputs more comfortable there is a mouse-based version available:


* '''SimulationPlus'''. Nach erfolgreicher Authentifizierung erhält man ein Fenster das im oberen Teil die Rückmeldungen des Simulators enthält und im unteren Teil die zur Verfügung stehenden Kommandos beinhaltet. Es können Befehle abegesetzt und die Reaktionen beobachtet werden. Weiters ist man in der Lage die Simulationszeit tageweise weiterzuschalten.
* '''SimulationPlus'''. After a successful authentication, a window appears which contains the feedback from the simulator in the upper part and the available commands in the lower part. There, commands can be entered (and combined), and responses from the simulation environment can be followed. One is also able to advance the simulation time per day.  


Als Projektleiter kann man nun aus der Menge an Kommandos wählen um Mitarbeiter zu führen und/oder den Status zu erfragen.  
Project managers can choose between the different available commands to manage the tasks of the developers or to get informed about the project status. Literally, there are now restrictions to the order the command are used and managers can choose among them freely. However, that means that managers (as in real life) can start reasonable as well as unreasonable activities at any time – yielding situations which have positive or negative effects on the project run.  
Dabei ist die Wahl der Kommandos zu jeder Zeit wirklich beliebig und frei wählbar. D.h. als Benutzer kann man so vernünftige
 
oder auch unvernünftige Aktivitäten veranlassen - man hat wie in der Realität freie Wahl, muss aber auch damit rechnen,
The AMEISE Client provides an interface for the simulator but also many supervisory components supporting the learning process during and after the simulation run. They can be activated or deactivated by the instructor.  
dass Handlungen auf den Projektfortschritt positive wie auch negative Effekte haben können.  
Der AMEISE Client bietet jedoch nicht nur eine Schnittstelle für den Simulator. Zahlreiche, vom Lehrveranstaltungsleiter
aktivier und deaktivierbare Hilfsmittel unterstützen den Lernprozess während oder im Anschluss an die Simulation.


* Erklärungskomponente - '''Ratgeber'''. Diese Komponente imitiert eine/n "erfahrene/n" Mitarbeiter/in, zu dem/der Sie als Projektleiter gehen können, und in Bezug auf Ihren Projektstatus um Rat fragen können. Diese/r Mitarbeiter/in sieht sich Ihre bisherige Leistung an und gibt seine/ihre Meinung in Bezug auf Projektphasen und (mittlerweise entstandene) Produkte ab. Standardmässig ist diese Komponente während einer Simulation aktiviert.
* Explanation component - '''Advisor'''. This component imitates an “experienced employee in the next office” whom you can ask questions about your project.  
This “experienced employee” looks at your performance and gives you feedback to single project phases and the product. This component is deactivated during a simulation run by default.  


[[Image:EK02.gif|right|thumbnail|Erklärungskomponenten- Auswertung]]
[[Image:EK02_en.png|right|thumbnail|Explanation Component - feedback]]
    
    
* Erklärungskomponente - '''Evaluation'''. Diese Komponente analysiert ihren Projektstatus im Detail und generiert Diagramme und Tabellen um Ihnen einen genauen Überblick über Ihren Projektverlauf zu liefern. So erfahren Sie hier Konkretes zu Ihrer Performanz, den Mitarbeitereinsatz und der Qualität aller Zwischen und Endprodukte. Üblicherweise wird diese Komponente erst nach Abschluss eines Projektes aktiviert und ermöglicht so die Eigenanalyse der Simulation oder die Analyse durch den Lehrveranstaltungsleiter.
* Explanation component - '''Evaluation'''. This component analyzes your current project status and generates diagrams and tables to give you an overview about your project. You can get information about your performance, the employees used and the quality of your interim - and final products. Usually, this component is deactivated during a simulation run, and activated quite after the end of your project, allowing for an immediate self-assessment.  


* '''Friendly Peer'''. Diese Komponente imitiert ebenso eine/n "erfahrene/n" Mitarbeiter/in, ist jedoch als eigenständiger Prozess umgesetzt. Als Beobachter steht Ihnen der Friendly Peer während der Simulation zur Seite und gibt, wenn kritische oder problembehaftete Entscheidungen gefällt wurden, von sich aus Ihnen Ratschläge. Die Komponente ist standardmäßig deaktiviert und kann vom Simulationsleiter aktiviert werden.
* '''Friendly Peer'''. This component imitates an “experienced employee sitting in your office”. You can use the friendly-peer as an observer during the simulation run. The friendly-peer gives you advices in tricky situations and warns you when steering the project into the wrong direction. The component is disabled by default and has to be enabled by the instructor.  


Um den Überblick zu bewahren gibt es neben der SimulationPlus Komponente noch weitere Sichten auf den Projektverlauf.
The SimulationPlus component can be combined with the following interfaces to get an even better sight onto your project.  


* '''AmeiseWall'''. Für einen besseren zeitlichen Überblick kann man mittels dieser Komponente die gesetzten Aktivitäten in Form einer ''Perspective Wall'' betrachten. Nach Mitarbeiter geordnet erscheinen Aktivitäten als kleine Grafiken.  
* '''AmeiseWall'''. For a better overview of your project you can use this component to see the set activities in form of a Perspective Wall. The activities appear as small icons ordered by employees over time.  


* '''TreeView'''. Die AMEISE ermöglicht nicht nur die einmalige Simulation eines Modells. Es entstehen somit verschiedene Pfade die ein Projekt nehmen kann. Die TreeView Komponente stellt den Simulationsverlauf grafisch in Form eines Baumes dar.
* '''TreeView'''. AMEISE allows for undoing commands (please note, for didactical reasons it is strongly recommended not to use this feature in the first runs). Therefore different paths in a project are possible. The TreeView component represents these paths in the form of a tree.
 
* '''PhaseView'''. In contrast to the TreeView component (which represents each simulation step), the PhaseView component offers a phase-oriented perspective. Bars represent commenced and completed phases of the project.  


* '''PhaseView'''. Im Gegensatz zum TreeView, welcher jeden Simulationsschritt darstellt, bietet der PhaseView eine phasenorientierte (vorgehensmodellabhängige) Sichtweise an. Balken repräsentieren begonnene und abgeschlossene Phasen im Projekt.


=== Server ===
=== Server ===


Kern der AMEISE ist der AMEISE Server, eine Java Applikation mit dazugehöriger SQL-Datenbank. Der Server besteht im Grunde neben der Datenbank aus zwei unterschiedlichen Anwendungen, dem Simulationskern und einem Lastverteilungsmanager.
The core of AMEISE is the AMEISE server, a Java application with an SQL database in the background. Apart from the database, the server consists of two different applications: the simulation core (Wrapper) and the load balancing manager (LBMMgr).  


* '''AmeiseWrapper'''. Diese Komponente beinhaltet den Simulationskern. Der aus Stuttgart stammende Simulationskern ist ein Einbenutzersystem. Im Wrapper wird dieser in eine Java Applikation eingebettet und mehrbenutzerfähig gemacht. Auch werden hier Daten in die Datenbank geschrieben. Je nach Auslastung kann die AMEISE mehrere Wrapper parallel betreiben und somit gleichzeitig abgesetzte Clientanfragen schneller bearbeiten.  
* '''AMEISE Wrapper'''. This component represents the simulation engine written in ADA95. The simulation engine is a single-user system. So, the AMEISE Wrapper embeds the simulation engine in a Java application and makes it multi-user capable. It also collects simulation data and writes it into the database. Depending on the workload, AMEISE can make use of several wrappers in parallel.  


* '''LBMMgr''' (Load Balancing Manager). Eigentlich ein Lastverteilungsmanager, der dafür sorgt, dass jeder AMEISE Client einen freien und besonders schnellen Simulationskern zur Verfügung hat. Der LBMMgr ist ausserdem die Schnittstelle nach aussen und erledigt die von den Erklärungskomponenten benötigten Datenbankabfragen.
* '''LBMMgr''' (Load Balancing Manager). Actually, as several Wrapper machines might be available, a load distribution manager ensures that every AMEISE-client has access to the least occupied simulation engine. Behind a firewall, the LBMMgr is also the interface to the outside and acts as a proxy for requests.  


=== Modelle ===
=== Models ===


Kern der AMEISE (wie auch von SESAM) sind die zur Verfügung stehenden Simulationsmodelle und deren dazugehörigen Erklärungstexte. Die in AMEISE eingesetzten Modelle basieren weitestgehend auf dem in Stuttgart entworfenen Qualitätssicherungsmodell. Das zugrunde liegende Vorgehensmodell ist
The didactical core of AMEISE (as well as of SESAM) is the collection of simulation models and its explanatory texts. Models of AMEISE are largely based on the quality assurance model which was designed by our partners at the University of Stuttgart. The underlying model is a waterfall-like model focusing on quality and quality assurance measures. The rules behind the model are based on a wide range of empirically validated data.  
ein lineares und legt Wert auf den Punkt Qualität und qualitätssichernde Maßnahmen. Die dem Modell zugrunde liegenden Regeln basieren auf einer breiten Datenbasis, sind empirisch gehaltvoll und mehrfach validiert.
   
   
* '''Qualitätssicherungsmodell'''
* ''' Quality assurance model '''


  * Minimodell.  
  * Mini model.  
  Dieses Modell dient dem Kennenlernen des Simulators und dem User Interface.  
    This model is used to get acquainted with the simulator and the user interface.
  Ziel ist es über eine in der Komplexität stark reduzierte Aufgabenstellung
    The management objectives are reduced to a project with almost now
  (Projekt mit nur 3000 LOC, 3 fix eingestellte Mitarbeiter, ausreichend Zeit
    complexity(project with only 3000 LOC, 3 fixed employees, sufficient time and budget)
  und Budget) Eigenschaften der Simulationsumgebung kennenzulernen. Das Modell
    so that user can focus on learning how to interact with the simulation environment.  
  wurde an der Universität Klagenfurt definiert.
    The model was defined at the University of Klagenfurt.


  * Standardmodell.
  * Standard model.
  Dieses Modell entspricht dem in Stuttgart definierten Qualitätssicherungsmodell QS200.  
    This model corresponds to the basic Quality Assurance Model of Stuttgart(called QA200).
  Die Aufgabe ist es hier innerhalb von 9 Monaten und 225.000 EUR Budget ein
    The project head has to manage a project within 9 months and 225,000 EUR of budget. The project size is
  200 [[http://en.wikipedia.org/wiki/Function_point Adjusted Function Point]] Projekt durchzuführen.  
    about 200 [[http://en.wikipedia.org/wiki/Function_point Adjusted Function Point]] .  


* '''Weiterführende Modelle'''
* '''Further models '''


  * Wartungsmodell.
  * Maintenance model.
  Dieses an der Universität Linz geschaffene Modell schließt an das Standardmodell an,  
    This model, created at the University of Linz, is related to the standard QA200 model,  
  der Fokus liegt jedoch auf den NACH einem Projekt durchzuführenden Wartungsphasen.  
    but the focus is on maintenance activities.  
  In unregelmäßigen Abständen kommt es zu Wartungsaufgaben (korrektiv und präventiv),  
    At irregular intervals maintenance tasks (corrective and preventive) are triggered,
  die vom Projektleiter zu managen sind.
    and have to be managed by the project manager.
   
   
== Die Geschichte ==
== The History ==


Die Idee zur AMEISE entstand im Rahmen einer nml-Projektausschreibung (Neue Medien in der Lehre des
The basics of AMEISE were developed during an nml (New Media in the Teaching) project of bm:bmwk, Austria in 2001 and go back to a conference presentation of SESAM by Prof. Jochen Ludewig (from the University of Stuttgart). The objective of the AMEISE project was to extend SESAM in such a way that it could be used with larger groups, meaning that an automated analysis of the results got inherently necessary. Started at the University of Klagenfurt (Prof. Mittermeir, Dr. Bollin), soon the Carinthia University of Applied Sciences (Prof. Hochmüller), the University of Linz (Prof. Chroust) and the University of Stuttgart (Prof. Ludewig) joined the AMEISE team.  
bm:bmwk, Österreich) im Jahr 2001 und bei einer Präsentation von SESAM der Universität Stuttgart (Prof. Jochen Ludewig). Ziel war es, SESAM insofern zu erweitern, sodass der Einsatz in großen Gruppen,
auch unbetreut und nicht begleitet, zu ermöglichen und die Auswertung der Ergebnisse zu automatisieren.
Rund um die Alpen-Adria Universität Klagenfurt (Prof. Mittermeir, Dr. Bollin) kamen das Technikum Fachhochschule Kärnten (Prof. Hochmüller), die Universität Linz (Prof. Croust) und die Universität Stuttgart (Prof. Ludewig) mit ins Team.  


Von 2001 bis 2003 gab es die Entwicklungsphase, in der eine Client-Server Architektur aufgebaut wurde.
The development phase, where a client / server architecture was built, lasted from 2001 to 2003. The use of free software (GPL based) and Java enabled broadest possible platform independence, but also led to many technical problems (going back to a lack in documentation of the free software) during the maintenance phase. It took us 3 years (from 2003 to 2006) to overcome all the problems and to stabilize the system. Despite the projects’ official end in 2006, AMEISE is being further developed and is the basis for several ongoing projects and dissertations.  
Der Einsatz von freier Software (GPL basierend) und Java ermöglichte eine weitestgehende Plattform-
Unabhängigkeit, führte aber auch zu vielen technischen Problemen, die im Rahmen der Wartungsphase
von 2003 bis 2006 gelöst werden konnten. Trotz Projektende im Jahr 2006 wird die AMEISE weiterentwickelt
und ist Basis mehrerer Projekt- bzw. Diplomarbeiten.  


Seit 2002 ist die AMEISE an den Projektstandorten in Lehrveranstaltungen im Einsatz und teilweise
Since 2002, the AMEISE is in use at the project sites and partially embedded in the respective curricula. Since 2004, AMEISE is and has been used at partner Universities in Germany and Slovakia. In 2004, AMEISE was also part of an EU-MEDIDA project and was used in the Maghreb region.  
bereits auch im jeweiligen Curriculum verankert. Seit 2004 wird die AMEISE an Partneruniversitäten
in Deutschland verwendet. Seit 2004 ist AMEISE auch Teil eines EU-MEDIDA Projektes und wird im
maghrebinischen Raum eingesetzt.  


== Technical Requirements ==


== Technische Voraussetzungen ==
[[Image:AmeiseSystem.gif|right| Example Architecture - AMEISE Architecture]]


[[Image:AmeiseSystem.gif|right|100px|thumbnail|Beispielarchitektur - AMEISE Architektur]]
AMEISE can be used in two different ways. Either one uses the AMEISE server of the University of Klagenfurt (to be agreed upon) and only installs the AMEISE client locally, or one installs the whole system (server and client) locally. AMEISE can now also be installed on a single computer (including laptops) for demonstration purposes, but in a course a distributed system is recommended.  
Die AMEISE kann auf zwei Arten verwendet werden. Entweder man nutzt den AMEISE Server der
Alpen-Adria Universität Klagenfurt und greift nur per Client auf den Server zu, oder man installiert
den Server vor Ort. Die AMEISE kann zu Demozwecken auf einem einzigen Rechner (auch Laptop) installiert
werden, für den Einsatz in einer Lehrveranstaltung empfiehlt sich aber ein verteiltes System.
Für eine Internet/Intranet Verbindung ist demnach zu sorgen. Je nach Einsatz sind die technischen Anforderungen unterschiedlich, wobei folgende Daumenregeln gegeben werden können:


* '''Client'''. Der Client ist als Windows Executable oder als Java Applikation (für Linux, MaxOS, Solaris und Windows) erhältlich. Die einzige Voraussetzung ist eines der obigen Betriebsysteme, ein Internetzugang (zumindest zum AMEISE Server), und Java JDK 5.
Depending on the situation on site, the technical requirements are different. The following rules of thumb can be given:


* '''Server'''. Der Server besteht aus 3 Teilkomponenten: der Datenbank, einem Lastverteilungsmanager und einem oder mehreren Simulationskernen:
* '''Client'''.  
The client is available as a Windows executable or as a Java application (for Linux, MacOS, Solaris and Windows). The sole requirements are the mentioned operating systems, network access (at least to the AMEISE Server) and Java JDK 5.


   * Datenbank. Benötigt wird die freie SQL Datenbank mysql in der Version 4.1 (innodb-Type um
* '''Server'''.
     transaktionssicher zu sein). Als Daumenregel gilt: je Simulation (Benutzer) werden 60MB
The server consists of three sub-components: the database, the load balancing manager (LBMMgr) and one or more simulation cores (Wrapper):
    an Festplattenplatz benötigt.
 
   * Database.  
    You need a free SQL database mysql in version 5.1 (innodb-Type to be transaction-safe).
     Rule of thumb: every simulation run (Client user) requires 60MB of disk space.
 


   * Lastverteilungsmanager (auch als LBMMgr bezeichnet). Dieser ist ebenso für Linux, Solaris
   * Load balancing manager (LBMMgr).  
    und Windows als Java Applikation verfügbar. Benötigt wird Java JDK 1.4, etwa 50MB an
    It is available for Linux, Solaris and Windows as a Java application.  
    Hauptspeicher und 10MB an Festplattenplatz.  
    At least Java JDK 1.4, 50MB of RAM and approximately 10MB of hard disk space(for logs) are required.


   * Simulationskern (auch als Wrapper bezeichnet). Dieser ist für Linux, Solaris
   * Simulation core (Wrapper).  
     und Windows als Java Applikation verfügbar. Benötigt wird Java JDK 1.4 (Achtung, JDK 5
    The Wrapper is available for Linux, Solaris and Windows as a Java application. For Linux and Solaris, you need
    darf nicht verwendet werde!). Um die Performanz zu erhöhen sollten mehrere Wrapper
     the gnat95 libraries installed on the system.  
     laufen, als Daumenregel gilt: je 5 Clients sollte ein Wrapper installiert werden.  
    Java JDK 1.54 or above is required (please note, JDK 7 is possible but reported to be instable sometimes!).  
     Je Wrapper werden 500MB an RAM benötigt und 10MB an Festplattenplatz benötigt.
     In order to increase the simulation performance during a course, several Wrappers should be installed in parallel.
    The rule of thumb:  
    For every 5 clients used in the course, one wrapper should be installed.
     For every Wrapper, 500MB RAM and 10 MB of disk space are required.
    
    
== Mehrere Fragen? ==
== Further questions? ==


'''Ich möchte mehr über das Projekt wissen'''
'''I want to know more about the project'''
* siehe [[Tutorial]], [[Indexseite mit Unterlagen]], [[Interessentenseite]]
* see [[Tutorial]], [[Table of Contents]]




'''Ich möchte am Projekt mitarbeiten'''
'''I want to work on the project'''
* siehe [[Kontakt]], [[Interessentenseite]]
* see [[Contacts]]




'''Ich möchte die AMEISE herunterladen'''
'''I want to download AMEISE'''
* siehe [[Download]]
* see [[Download]]




'''Was gibt es Neues im AMEISE Projekt?'''
'''What’s new in the AMEISE-project?'''
* siehe [[Neuigkeiten]]
* see [[News]]
<!-- [[en:About The Project]] -->
[[de:Über das Projekt]]
[[en:About The Project]]
<!--
[[sk:Hlavná stránka]]
[[fr:Accueil]]
-->


__NOEDITSECTION__
__NOEDITSECTION__

Latest revision as of 12:04, 24 August 2013

Ameise Wall - Project Overview

The AMEISE-System provides students of informatics, business informatics and economics as well as subject-related university or college-studies, the ability to collect project management experience on a simulator. Critical situations can be defined and trained with AMEISE without getting a real project in danger.

Future project-leaders can execute projects in a few hours that would normally take several months. They also get confronted with typical problems of projects and should solve them.

Currently the AMEISE system offers three different models: a Beginner-Model (Mini model, with less requirements), a Standard model (with a particular focus on quality assurance), and a Maintenance-model (which is based on the activities after delivering the product). AMEISE is more than a simulator. The instructor can activate many different components, for example the advisor or evaluation components. A special feature is the ability to reset the simulation run at a certain point in time(rollback). Thereby different variants can be tested by the project leader (for example change developers or using a different strategy) and then the results can be compared.

Started in 2001 as part of a nml project from bm:bwk / Austria, AMEISE is and has been used at several Universities and Colleges in Austria, Germany and the Maghreb region. The heart of the AMEISE-system is (SESAM) which was developed at the University of Stuttgart (Prof. Jochen Ludewig) and its related Quality Assurance Models (also referred to as QA-models).

Components of the Project

AMEISE is a Client-Server System which can be executed locally on a computer or distributed in intranet or internet. The system is designed so that even unstable environments have no effect on the simulation runs. As a trainee you can use the AMEISE client to manage a virtual project which means to delegate tasks, do project control and, of course, to deliver a product of acceptable quality at the end of the simulation run.

Client

SimulationPlus- User Interface

The AMEISE client provides a graphical interface for trainees and is implemented as a Java-application that runs virtually on every platform. Comment inputs and feedbacks are usually text-based, but to make the inputs more comfortable there is a mouse-based version available:

  • SimulationPlus. After a successful authentication, a window appears which contains the feedback from the simulator in the upper part and the available commands in the lower part. There, commands can be entered (and combined), and responses from the simulation environment can be followed. One is also able to advance the simulation time per day.

Project managers can choose between the different available commands to manage the tasks of the developers or to get informed about the project status. Literally, there are now restrictions to the order the command are used and managers can choose among them freely. However, that means that managers (as in real life) can start reasonable as well as unreasonable activities at any time – yielding situations which have positive or negative effects on the project run.

The AMEISE Client provides an interface for the simulator but also many supervisory components supporting the learning process during and after the simulation run. They can be activated or deactivated by the instructor.

  • Explanation component - Advisor. This component imitates an “experienced employee in the next office” whom you can ask questions about your project.

This “experienced employee” looks at your performance and gives you feedback to single project phases and the product. This component is deactivated during a simulation run by default.

Explanation Component - feedback
  • Explanation component - Evaluation. This component analyzes your current project status and generates diagrams and tables to give you an overview about your project. You can get information about your performance, the employees used and the quality of your interim - and final products. Usually, this component is deactivated during a simulation run, and activated quite after the end of your project, allowing for an immediate self-assessment.
  • Friendly Peer. This component imitates an “experienced employee sitting in your office”. You can use the friendly-peer as an observer during the simulation run. The friendly-peer gives you advices in tricky situations and warns you when steering the project into the wrong direction. The component is disabled by default and has to be enabled by the instructor.

The SimulationPlus component can be combined with the following interfaces to get an even better sight onto your project.

  • AmeiseWall. For a better overview of your project you can use this component to see the set activities in form of a Perspective Wall. The activities appear as small icons ordered by employees over time.
  • TreeView. AMEISE allows for undoing commands (please note, for didactical reasons it is strongly recommended not to use this feature in the first runs). Therefore different paths in a project are possible. The TreeView component represents these paths in the form of a tree.
  • PhaseView. In contrast to the TreeView component (which represents each simulation step), the PhaseView component offers a phase-oriented perspective. Bars represent commenced and completed phases of the project.


Server

The core of AMEISE is the AMEISE server, a Java application with an SQL database in the background. Apart from the database, the server consists of two different applications: the simulation core (Wrapper) and the load balancing manager (LBMMgr).

  • AMEISE Wrapper. This component represents the simulation engine written in ADA95. The simulation engine is a single-user system. So, the AMEISE Wrapper embeds the simulation engine in a Java application and makes it multi-user capable. It also collects simulation data and writes it into the database. Depending on the workload, AMEISE can make use of several wrappers in parallel.
  • LBMMgr (Load Balancing Manager). Actually, as several Wrapper machines might be available, a load distribution manager ensures that every AMEISE-client has access to the least occupied simulation engine. Behind a firewall, the LBMMgr is also the interface to the outside and acts as a proxy for requests.

Models

The didactical core of AMEISE (as well as of SESAM) is the collection of simulation models and its explanatory texts. Models of AMEISE are largely based on the quality assurance model which was designed by our partners at the University of Stuttgart. The underlying model is a waterfall-like model focusing on quality and quality assurance measures. The rules behind the model are based on a wide range of empirically validated data.

  • Quality assurance model
* Mini model. 
   This model is used to get acquainted with the simulator and the user interface.  
   The management objectives are reduced to a project with almost now 
   complexity(project with only 3000 LOC, 3 fixed employees, sufficient time and budget)
   so that user can focus on learning how to interact with the simulation environment. 
   The model was defined at the University of Klagenfurt.
* Standard model.
   This model corresponds to the basic Quality Assurance Model of Stuttgart(called QA200).
   The project head has to manage a project within 9 months and 225,000 EUR of budget. The project size is
   about 200 [Adjusted Function Point] . 
  • Further models
* Maintenance model.
   This model, created at the University of Linz, is related to the standard QA200 model, 
   but the focus is on maintenance activities. 
   At irregular intervals maintenance tasks (corrective and preventive) are triggered,
   and have to be managed by the project manager.

The History

The basics of AMEISE were developed during an nml (New Media in the Teaching) project of bm:bmwk, Austria in 2001 and go back to a conference presentation of SESAM by Prof. Jochen Ludewig (from the University of Stuttgart). The objective of the AMEISE project was to extend SESAM in such a way that it could be used with larger groups, meaning that an automated analysis of the results got inherently necessary. Started at the University of Klagenfurt (Prof. Mittermeir, Dr. Bollin), soon the Carinthia University of Applied Sciences (Prof. Hochmüller), the University of Linz (Prof. Chroust) and the University of Stuttgart (Prof. Ludewig) joined the AMEISE team.

The development phase, where a client / server architecture was built, lasted from 2001 to 2003. The use of free software (GPL based) and Java enabled broadest possible platform independence, but also led to many technical problems (going back to a lack in documentation of the free software) during the maintenance phase. It took us 3 years (from 2003 to 2006) to overcome all the problems and to stabilize the system. Despite the projects’ official end in 2006, AMEISE is being further developed and is the basis for several ongoing projects and dissertations.

Since 2002, the AMEISE is in use at the project sites and partially embedded in the respective curricula. Since 2004, AMEISE is and has been used at partner Universities in Germany and Slovakia. In 2004, AMEISE was also part of an EU-MEDIDA project and was used in the Maghreb region.

Technical Requirements

Example Architecture - AMEISE Architecture

AMEISE can be used in two different ways. Either one uses the AMEISE server of the University of Klagenfurt (to be agreed upon) and only installs the AMEISE client locally, or one installs the whole system (server and client) locally. AMEISE can now also be installed on a single computer (including laptops) for demonstration purposes, but in a course a distributed system is recommended.

Depending on the situation on site, the technical requirements are different. The following rules of thumb can be given:

  • Client.

The client is available as a Windows executable or as a Java application (for Linux, MacOS, Solaris and Windows). The sole requirements are the mentioned operating systems, network access (at least to the AMEISE Server) and Java JDK 5.

  • Server.

The server consists of three sub-components: the database, the load balancing manager (LBMMgr) and one or more simulation cores (Wrapper):

 * Database. 
   You need a free SQL database mysql in version 5.1 (innodb-Type to be transaction-safe). 
   Rule of thumb: every simulation run (Client user) requires 60MB of disk space.
 
 * Load balancing manager (LBMMgr). 
   It is available for Linux, Solaris and Windows as a Java application. 
   At least Java JDK 1.4, 50MB of RAM and approximately 10MB of hard disk space(for logs) are required.
 * Simulation core (Wrapper). 
   The Wrapper is available for Linux, Solaris and Windows as a Java application. For Linux and Solaris, you need
   the gnat95 libraries installed on the system. 
   Java JDK 1.54 or above is required (please note, JDK 7 is possible but reported to be instable sometimes!). 
   In order to increase the simulation performance during a course, several Wrappers should be installed in parallel.
   The rule of thumb: 
   For every 5 clients used in the course, one wrapper should be installed.
   For every Wrapper, 500MB RAM and 10 MB of disk space are required.
 

Further questions?

I want to know more about the project


I want to work on the project


I want to download AMEISE


What’s new in the AMEISE-project?