https://ameise.aau.at/ameise/en/api.php?action=feedcontributions&user=Toffler&feedformat=atomAmeise-en - User contributions [en]2024-03-29T09:18:58ZUser contributionsMediaWiki 1.39.6https://ameise.aau.at/ameise/en/index.php?title=Using_the_Advisor&diff=2055Using the Advisor2013-08-11T13:22:23Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|The Simulation with the “SimulationPlus” component|Features of the QA Model / Part 1}}<br />
<br />
<br />
The following image shows the user interface of the advisor component. You can find an animation explaining how to use the advisor component at our [[Special:ViewletDemos|Demos page]].<br />
<br />
[[Image:Ratgeber_en.png|500px|thumb|center|The User Interface of the Advisor Component]]<br />
<br />
<br />
<br />
== Description==<br />
<br />
'''1. Starting the Advisor Component'''<br />
<br />
{| style="width:100%;padding-left:1em" |<br />
|- <br />
|To start the advisor component, first click on the tab '''«EC-Unit»'''.<br />
<br />
[[Image:Ratg1_en.png|500px|thumb|center]]<br />
<br />
<br />
Then activate the tab '''«Explanation»''' to open the advisor component.<br />
<br />
[[Image:Ratg2_en.png|500px|thumb|center]] <br />
|}<br />
<br />
<br />
<br />
'''2. The Advisor Component'''<br />
<br />
{| style="width:100%;padding-left:1em" |<br />
|- <br />
|The advisor component is vertically divided into two parts. The left part contains the questionnaire, the right part shows the advice, which trainees will get from the system.<br />
<br />
[[Image:Ratg3_en.png|500px|thumb|center|]]<br />
<br />
<br />
If you start the advisor for the first time, the questionnaire is always empty. Click on the button '''«get Candidates»''' to load the questions. Now, the options are listed.<br />
<br />
[[Image:Ratg4_en.png|500px|thumb|center|]]<br />
|}<br />
<br />
<br />
<br />
'''3. Selecting an Advice'''<br />
<br />
{| style="width:100%;padding-left:1em" |<br />
|- <br />
|Now you have the opportunity to select one of the advice options, and after clicking the '''«show candidates»''' button, you will get the related advice.<br />
<br />
[[Image:Ratg5_en.png|500px|thumb|center]]<br />
<br />
<br />
The next image shows some appropriate advice examples:<br />
<br />
[[Image:Ratg6_en.png|500px|thumb|center]]<br />
|}<br />
<br />
<br />
<br />
'''4. Deselection'''<br />
<br />
{| style="width:100%;padding-left:1em" |<br />
|- <br />
|Before you can select a new question from the questionnaire, you have to cancel the previous selected question. Therefore click on the button '''«Turn back»'''. <br />
|}<br />
<br />
<br />
[[de:Die Benutzung des Ratgebers]]<br />
[[en:Main Using the Advisor]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--><br />
<br />
<br />
{{NavigatorBar|The Simulation with the “SimulationPlus” component|Features of the QA Model / Part 1}}<br />
<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=The_Advisor&diff=2047The Advisor2013-08-11T13:13:13Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Project Support in AMEISE|The Friendly Peer}}<br />
<br />
<br />
<br />
====Advisor====<br />
<br />
The advisor can be asked by the trainee if he/she is in trouble. <br />
<br />
<br />
====Purpose of the Advisor====<br />
<br />
The task of the advisor is to provide the trainee with a couple of questions from a predefined catalog. When the trainee chooses one of these questions, the advisor will answer it. <br />
The advisor has an own interface in the simulation environment. The advice possibilities are snap - shots, they only refer to the actual state of the simulation run. Hence, the advisor is not able to judge on aspects which would need long-term observations of a simulation run.<br />
<br />
<br />
====Questions====<br />
<br />
The following list includes advices, which can be delivered by the advisor on demand:<br />
# '''Predecessor phases should not be forgotten.'''<br/>Phases always need a previous document as a basis. If this document is missing the phase is doomed to failure.<br />
# '''The predecessor phase should be finished before starting a new phase.'''<br/>It is important for subsequent phases, that the predecessor phase and the emerged previous document have been finished by more than 50% to enable an overlapping of these phases. If this is not the case, the initiated phase fails. The limit of 50% depends on the model. (QA Model).<br />
# ''' The predecessor phase should be reviewed before starting a new phase.'''<br/>To build on results of phases, it is important to review these phases. After the review, trainees know that the result of this phase still contains errors. These errors need to be corrected, in order to not adopt them into the follow-up phase. <br />
# '''The predecessor phase should be corrected based on the review before starting a new phase.'''<br/>After the review, it is important to correct the remaining errors to avoid error propagation in following phases.<br />
# '''Testing activities should be followed by corrective activities.'''<br/>A part from a review, trainees also can carry out tests to find errors in documents. These errors also have to be corrected in order to obtain a correct document. <br/><br />
# '''Incomplete documents should be subjected to a further review.'''<br/> During a simulation run, it may happen that single phases don’t meet enough requirements or exhibit too many errors. If the advisor recognizes a situation like this, he can react and give advice to improve the phase.<br />
<br />
<br />
<br />
==== Please note that ====<br />
{{Box1|The '''Feedback''' of the Advisor can be positive or negative!}}<br />
<br />
The feedback of the advisor depends on the '''current state''' of the phase or an activity. The answer to e.g. the question whether the specification has to be revised depends on the completeness of the specification document. If the specification already satisfies the requirements, this will be communicated to the trainee. If not, the trainee will get the advice to revise the document. <br />
The advisor '''can not''' judge on phases, which have not yet been started! In this case, the trainee gets a message, stating that there is not enough data available for assessment. <br />
<br />
<br />
[[de:Der Ratgeber]]<br />
[[en:The Advisor]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--><br />
<br />
{{NavigatorBar|Project Support in AMEISE|The Friendly Peer}}<br />
<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=About_The_Project&diff=2006About The Project2013-05-16T14:09:04Z<p>Toffler: </p>
<hr />
<div>[[Image:AmeiseWall_en.png|right|310px|thumbnail|Ameise Wall - Project Overview]]<br />
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. <br />
<br />
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. <br />
<br />
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).<br />
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. <br />
<br />
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<br />
[http://www.iste.uni-stuttgart.de/se/research/sesam/models/index.html Quality Assurance Models] (also referred to as QA-models). <br />
<br />
== Components of the Project==<br />
<br />
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. <br />
<br />
=== Client ===<br />
[[Image:Client_nach_dem_Anmelden_en.png|right|thumbnail|SimulationPlus- User Interface]]<br />
<br />
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:<br />
<br />
* '''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. <br />
<br />
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. <br />
<br />
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. <br />
<br />
* Explanation component - '''Advisor'''. This component imitates an “experienced employee in the next office” whom you can ask questions about your project. <br />
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. <br />
<br />
[[Image:EK02_en.png|right|thumbnail|Explanation Component - feedback]]<br />
<br />
* 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. <br />
<br />
* '''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. <br />
<br />
The SimulationPlus component can be combined with the following interfaces to get an even better sight onto your project. <br />
<br />
* '''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. <br />
<br />
* '''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. <br />
<br />
* '''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. <br />
<br />
<br />
=== Server ===<br />
<br />
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). <br />
<br />
* '''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. <br />
<br />
* '''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. <br />
<br />
=== Models ===<br />
<br />
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. <br />
<br />
* ''' Quality assurance model '''<br />
<br />
* Mini model. <br />
This model is used to get acquainted with the simulator and the user interface. <br />
The management objectives are reduced to a project with almost now <br />
complexity(project with only 3000 LOC, 3 fixed employees, sufficient time and budget)<br />
so that user can focus on learning how to interact with the simulation environment. <br />
The model was defined at the University of Klagenfurt.<br />
<br />
* Standard model.<br />
This model corresponds to the basic Quality Assurance Model of Stuttgart(called QA200).<br />
The project head has to manage a project within 9 months and 225,000 EUR of budget. The project size is<br />
about 200 [[http://en.wikipedia.org/wiki/Function_point Adjusted Function Point]] . <br />
<br />
* '''Further models '''<br />
<br />
* Maintenance model.<br />
This model, created at the University of Linz, is related to the standard QA200 model, <br />
but the focus is on maintenance activities. <br />
At irregular intervals maintenance tasks (corrective and preventive)are triggered,<br />
and have to be managed by the project manager.<br />
<br />
== The History ==<br />
<br />
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. <br />
<br />
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. <br />
<br />
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. <br />
<br />
== Technical Requirements ==<br />
<br />
[[Image:AmeiseSystem.gif|right|100px|thumbnail| Example Architecture - AMEISE Architecture]]<br />
<br />
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. <br />
<br />
Depending on the situation on site, the technical requirements are different. The following rules of thumb can be given:<br />
<br />
* '''Client'''. <br />
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. <br />
<br />
* '''Server'''. <br />
The server consists of three sub-components: the database, the load balancing manager (LBMMgr) and one or more simulation cores (Wrapper): <br />
<br />
* Database. <br />
You need a free SQL database mysql in version 5.1 (innodb-Type to be transaction-safe). <br />
Rule of thumb: every simulation run (Client user) requires 60MB of disk space.<br />
<br />
<br />
* Load balancing manager (LBMMgr). <br />
It is available for Linux, Solaris and Windows as a Java application. <br />
At least Java JDK 1.4, 50MB of RAM and approximately 10MB of hard disk space(for logs) are required.<br />
<br />
* Simulation core (Wrapper). <br />
The Wrapper is available for Linux, Solaris and Windows as a Java application. For Linux and Solaris, you need<br />
the gnat95 libraries installed on the system. <br />
Java JDK 1.54 or above is required (please note, JDK 7 is possible but reported to be instable sometimes!). <br />
In order to increase the simulation performance during a course, several Wrappers should be installed in parallel.<br />
The rule of thumb: <br />
For every 5 clients used in the course, one wrapper should be installed.<br />
For every Wrapper, 500MB RAM and 10 MB of disk space are required.<br />
<br />
== Further questions? ==<br />
<br />
'''I want to know more about the project'''<br />
* see [[Tutorial]], [[Table of Contents]]<br />
<br />
<br />
'''I want to work on the project'''<br />
* see [[Contacts]]<br />
<br />
<br />
'''I want to download AMEISE'''<br />
* see [[Download]]<br />
<br />
<br />
'''What’s new in the AMEISE-project?'''<br />
* see [[News]]<br />
[[de:Über das Projekt]]<br />
[[en:About the project]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--><br />
<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=About_The_Project&diff=1997About The Project2013-05-16T13:49:23Z<p>Toffler: </p>
<hr />
<div>[[Image:AmeiseWall_en.png|right|310px|thumbnail|Ameise Wall - Project Overview]]<br />
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. <br />
<br />
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. <br />
<br />
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).<br />
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.<br />
<br />
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 <br />
[http://www.iste.uni-stuttgart.de/se/research/sesam/models/index.html Quality Assurance Models] (also referred to as QA-models). <br />
<br />
== Components of the Project==<br />
<br />
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. <br />
<br />
=== Client ===<br />
[[Image:Client_nach_dem_Anmelden_en.png|right|thumbnail|SimulationPlus- User Interface]]<br />
<br />
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 also a mouse-based version available:<br />
<br />
* '''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.<br />
<br />
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 which have positive or negative effects on the project run. <br />
<br />
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.<br />
<br />
* Explanation component - '''Advisor'''. This component imitates an "experienced employee in the next office", whom you can ask questions about your project.<br />
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.<br />
<br />
[[Image:EK02_en.png|right|thumbnail|Explanation Component - feedback]]<br />
<br />
* 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.<br />
<br />
* '''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.<br />
<br />
The SimulationPlus can be combined with the following interfaces to get an even better sigth onto your project.<br />
<br />
* '''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. <br />
<br />
* '''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.<br />
<br />
* '''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.<br />
<br />
<br />
=== Server ===<br />
<br />
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).<br />
<br />
* '''AMEISE Wrapper'''. This component represents the simulation engine written in ADA95. The simulation engine is a single - user system. So, the AMEISE wrapper, embed 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 us of several wrappers in parallel.<br />
<br />
* '''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.<br />
<br />
=== Models ===<br />
<br />
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. <br />
<br />
* ''' Quality assurance model '''<br />
<br />
* Mini model. <br />
This model is used to get acquainted with the simulator and the user interface. <br />
The management objectives are reduced to a project with almost now <br />
complexity(project with only 3000 LOC, 3 fixed employees, sufficient time and budget)<br />
so that user can focus on learning how to interact with the simulation environment. <br />
The model was defined at the University of Klagenfurt.<br />
<br />
* Standard model.<br />
This model corresponds to the basic Quality Assurance Model of Stuttgart(called QA200).<br />
The project head has to manage a project within 9 months and 225,000 EUR of budget. The project size is<br />
about 200 [[http://en.wikipedia.org/wiki/Function_point Adjusted Function Point]] . <br />
<br />
* '''Further models '''<br />
<br />
* Maintenance model.<br />
This model, created at the University of Linz, is related to the standard QA200 model, <br />
but the focus is on maintenance activities. <br />
At irregular intervals maintenance tasks (corrective and preventive)are triggered,<br />
and have to be managed by the project manager.<br />
<br />
== The History ==<br />
<br />
The basics of AMEISE were developed during a 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.<br />
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.<br />
<br />
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 project´s official end in 2006, AMEISE is being further developed and is the basis for several ongoing projects and dissertations.<br />
<br />
Since 2002, the AMEISE is in use at the project sites and partially<br />
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.<br />
<br />
<br />
== Technical Requirements ==<br />
<br />
[[Image:AmeiseSystem.gif|right|100px|thumbnail| Example Architecture - AMEISE Architecture]]<br />
<br />
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.<br />
<br />
Depending on the situation on the site, the technical requirements are different. The following rules of thumb can be given:<br />
<br />
* '''Client'''. <br />
The client is available as a Windows executable or as a Java application (for Linux, MacOS, Solaris and Windows). <br />
The sole requirements are the mentioned operating systems, network access (at least to the AMEISE Server) and Java JDK 5.<br />
<br />
* '''Server'''. <br />
The server consists of three sub-components: the database, the load balancing manager(LBMMgr) and one or more simulation cores(Wrapper): <br />
<br />
* Database. <br />
You need a free SQL database mysql in version 5.1 (innodb-Type to be transaction-safe). <br />
Rule of thumb: every simulation run (Client user) requires 60MB of disk space.<br />
<br />
<br />
* Load balancing manager (LBMMgr). <br />
It is available for Linux, Solaris and Windows as a Java application. <br />
At least Java JDK 1.4, 50MB of RAM and approximately 10MB of hard disk space(for logs) are required.<br />
<br />
* Simulation core (Wrapper). <br />
The Wrapper is available for Linux, Solaris and Windows as a Java application. For Linux and Solaris, you need<br />
the gnat95 libraries installed on the system. <br />
Java JDK 1.54 or above is required (please note, JDK 7 is possible but reported to be instable sometimes!). <br />
In order to increase the simulation performance during a course, several Wrappers should be installed in parallel.<br />
The rule of thumb: <br />
For every 5 clients used in the course, one wrapper should be installed.<br />
For every Wrapper, 500MB RAM and 10 MB of disk space are required.<br />
<br />
== Further questions? ==<br />
<br />
'''I want to know more about the project'''<br />
* see [[Tutorial]], [[Table of Contents]]<br />
<br />
<br />
'''I want to work on the project'''<br />
* see [[Contacts]]<br />
<br />
<br />
'''I want to download AMEISE'''<br />
* see [[Download]]<br />
<br />
<br />
'''What’s new in the AMEISE-project?'''<br />
* see [[News]]<br />
[[de:Über das Projekt]]<br />
[[en:About the project]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--><br />
<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=The_SESAM_-_System&diff=1996The SESAM - System2013-05-16T13:40:37Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|The QA - Model|AMEISE}}<br />
<br />
<br />
<br />
===The Structure of the SESAM - System===<br />
<br />
The main objective when using SESAM is to provide an almost realistic simulation environment of software projects for training purposes. On the basis of a simulation run, trainees should be able to apply their acquired knowledge in a game-like environment and strengthen their management skills. <br />
<br />
<br />
Another objective is to make assumptions about effects of project decisions and study the consequences by replaying them in the simulation environment. The SESAM - System consists of various ''' Components ''' which are used by different roles:<br />
<br />
<br />
* '''Modeler''':<br />
** He or she creates the empirical models that are simulated by the simulation engine. The modeler determines which objects and relationships of a software project are mapped to the system and what effects may occur. He or she defines the world in which the trainee is able to move. <br />
<br />
<br />
* '''Trainee''':<br />
** The trainee takes the role of a project manager. By issuing commands he intervenes in the course of a simulation run and receives messages about the current state from the system. <br />
<br />
* '''Instructor''':<br />
** The instructor (or tutor) conducts training courses where trainees are able to participate. He or she guides trainees and he has the possibility to analyze simulation runs by several evaluation tools. Finally, he or she also discusses the achieved results together with the trainees. <br />
<br />
<br />
The following figure shows the '''Roles ''' and their '''Interaction ''' with the components of the system.<br />
<br />
[[Image:Komponenten_en.gif|center|frame|Components and Roles of the SESAM - System]]<br />
<br />
<br />
<br />
<br />
{{NavigatorBar|The QA - Model|AMEISE}}<br />
[[Category:Tutorial]]<br />
__NOEDITSECTION__<br />
[[de:Das SESAM-System]]<br />
[[en:The SESAM - System]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--></div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=The_QA_-_Model&diff=1994The QA - Model2013-05-16T13:36:22Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|SESAM - The Heart of AMEISE|The SESAM - System}}<br />
<br />
<br />
<br />
The '''QA - Model''' is the first and fully developed model that is used for SESAM simulation runs. The model focuses on the development of software in small to medium sized projects. To be precise, it is primary focused on quality assurance measurements and therefore the model is called Quality Assurance - Model (QA - Model). <br />
<br />
From trainees, the QA - Model requires proper staffing as well as the monitoring progress and quality control. Thereby, analysis, the specification, the system and module design, code, and the manual as well as the integration and delivery of the system have to be performed. In addition, all documents have to be reviewed and corrected. Also, module, integration, system and acceptance tests have to be performed. Trainees are also responsible for hiring employees, assigning tasks to them, and releasing them back into the pool of developers. <br />
<br />
<br />
<br />
{| style="width:100%;background:#FFFFCA;padding:0.5em" |<br />
|- <br />
| All of this has to be done on time and within the budget! <br />
|}<br />
<br />
<br />
===Waterfall Model===<br />
The [[Waterfall Model]] was chosen and has been extended by additional structural and analytical measures. The model leaves it up to the trainees to decide in which '''order''' they perform the various activities. Possible phases in the QA - Model are shown in the following figure:<br />
<br />
<br />
[[Image:Wasserfall_en.gif|800px|thumb|center|Possible Procedures in the QA - Model]]<br />
<br />
<br />
The dashed arrows between the activities indicate that trainees do not have to act according to the waterfall model. While there is a predefined sequence between the phases, the trainees are not forced to follow them at all. <br />
<br />
<br />
===Code-and-Fix Approach===<br />
A code-and-fix approach is possible; however, the trainees are at least forced to create an '''Analyzing Document ''' and to do the '''Implementation '''. All other phases (between analysis and implementation) can be skipped. Thus, trainees are not retained from trying out the Code-and-Fix approach.<br />
<br />
Furthermore '''Rollbacks''' to previous phases are possible, as long as the document created in that phase, still contains some errors which are not corrected. <br />
<br />
<br />
{| style="width:100%;background:#FFFFCA;padding:0.5em" |<br />
|- <br />
| Documents can be checked and corrected as often as necessary! <br />
|}<br />
<br />
<br />
It is important to note that the correction after a review has to be successfully completed before starting a new review. After correcting the document, all other activities can be executed in the usual manner. <br />
<br />
<br />
<br />
<br />
{{NavigatorBar|SESAM - The Heart of AMEISE|The SESAM - System}}<br />
__NOEDITSECTION__<br />
[[Category:Tutorial]]<br />
<br />
[[de:Das QS-Modell]]<br />
[[en:The QA - Model]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--></div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=SESAM_-_The_Heart_of_AMEISE&diff=1993SESAM - The Heart of AMEISE2013-05-16T13:31:55Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Motivation|The QA - Model}}<br />
<br />
===Project Overview and Motivation ===<br />
<br />
Good project management is one of the key factors for the successful implementation of a (software) project. Often, in the field of project management, the training of project managers is strongly neglected, and the education of a project manager is only based on theoretical knowledge. <br />
<br />
<br />
===The Simulation of Projects===<br />
<br />
To improve the training, the SESAM-Project ('''S'''oftware-'''E'''ngineering-'''S'''imulation through '''A'''nimated '''M'''odels) has been developed at the department of Software Engineering at the Universität of Stuttgart. Besides a theoretical foundation, the education of students should be improved by some realistic components. It is not possible that every student leads a real project during a bachelor degree course, and so SESAM offers the great opportunity to train project management by simulation. The approach is also interesting for the training of future project managers in industry, as it can be accomplished quickly and cheaply. <br />
<br />
<br />
[[Image:Grundidee_en.gif|center]]<br />
<br />
<br />
{| style="background:#FFFFCA;padding:0.5em" |<br />
|- <br />
| In the context of training, trainees simulate projects on a simulator, where he or she is in the position of a project manager and interacts with a customer, developers and several types of documents and software code. The simulation time is divided into time sections, and the project is controlled by different commands. <br />
|}<br />
<br />
<br />
The '''Training Environment''' offers trainees the following effects:<br />
<br />
* During a simulation run one learns how to use resources.<br />
* A change of resources or the development process has important consequences. <br />
* Trainees are getting confronted with situations which arise normally on real projects <br />
<br />
===Models===<br />
The simulation is based on models that include all relevant aspects of a project. The model which is loaded in the simulator decides which project is taken. In addition to the '''QA - Model''' simulation runs are possible with other models. <br />
<br />
__NOEDITSECTION__<br />
{{NavigatorBar|Motivation|The QA - Model}}<br />
[[de:SESAM - Der Kern von AMEISE]]<br />
[[en:SESAM - The Heart of AMEISE]]<br />
[[Category:Help]]</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Motivation&diff=1992Motivation2013-05-16T13:25:26Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Tutorial Document|SESAM - The Heart of AMEISE}}<br />
<br />
<br />
The successful implementation of a software projects is a difficult task. Both, technical and organizational, problems must be solved, and less experience in project management usually yields to failed projects. Therefore, it is useful to provide trainees the opportunity to take the role of a project manager during their education. By simulations, the anxiety about project failure and the worry about the associated consequences should be taken from students. <br />
<br />
==Purpose of the Project==<br />
<br />
<br />
In general, students of economics and informatics learn project management in theoretical lessons. Universities and Colleges claim to train students for project management, but in classical lectures this cannot or only under specific circumstances be achieved. <br />
<br />
The AMEISE project, as part of the "New Media in teaching on Universities and Colleges" initiative of the bm:bwk/Austria, addresses this issue. AMEISE is an acronym for "'''A''' '''M'''edia - '''E'''ducation '''I'''nitiative for '''S'''oftware '''E'''ngineering".<br />
<br />
==AMEISE==<br />
<br />
<br />
The AMEISE system provides students of computer science and business economics (as well as other subject-related university or college studies), the ability to collect project management experience on a simulator. Comparable to the training of pilots in a flight simulator, critical situations can be defined and trained, without bringing real project in danger. Whereas a real-life project would take several months, AMEISE allows for managing projects by trainees in a few hours. They are nevertheless faced with the typical problems in software projects and these situations needs to be solved during the simulation run. The heart of the AMEISE system was developed at the Universität Stuttgart, and it is called “SESAM simulator”. <br />
<br />
==SESAM==<br />
<br />
<br />
In order to simulate a project, a model must be loaded in the simulator first. The model defines the project. Thus, by assuming appropriate models available, any type of project could be simulated by SESAM. <br />
<br />
==Objectives==<br />
<br />
<br />
In addition to theoretical knowledge, especially practical skills should be learned by using the simulator. Therefore, students are put into the role of a project manager (as they would in a real project), allowing for practicing planning skills and acquiring important project management skills. <br />
<br />
<br />
{{NavigatorBar|Tutorial Document|SESAM - The Heart of AMEISE}}<br />
__NOEDITSECTION__<br />
[[de:Motivation]]<br />
[[en:Motivation]]<br />
[[Category:Tutorial]]<br />
__NOTOC__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Viewlet_Demos&diff=1990Viewlet Demos2013-05-16T13:17:55Z<p>Toffler: </p>
<hr />
<div>The AMEISE - System consists of several components. The AMEISE client offers a lot of features, and there is also a tool for creating assessment-reports (AORTA). The following short viewlets demonstrate the most important navigation abilities and supporting components (from a didactic point of view) during and after a simulation run. If you don’t know AMEISE, please start with the general introduction of the AMEISE client. <br />
<br />
== AMEISE Client ==<br />
[[Image:Film.jpg|right|140px|]]<br />
<div style='padding-left:1.5em'><br />
=== General Introduction ===<br />
<br />
<div style='padding-left:1.5em'><br />
[[media:Ameise_Demo.flv|AMEISE-Client (Duration ~ 5 min)]]<br />
* Presents a short simulation run. <br />
* No prior knowledge is required. <br />
</div><br />
<br />
=== Navigation Options ===<br />
<div style='padding-left:1.5em'><br />
<b>Ameise Wall (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE Client.<br />
* Visualizes the steps of a simulation run on a "Perspective Wall".<br />
<br />
<b>TreeView (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE Client.<br />
* Visualizes the steps of a simulation run in a tree-like structure.<br />
</div><br />
<br />
=== Supervising Components ===<br />
<div style='padding-left:1.5em'><br />
<b>Advisor (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE Client (optional).<br />
* The advisor provides feedback about the current simulation run and gives advice on how to improve the simulation results. <br />
<br />
<b>PhaseView (Duration ~ 30 sec)</b><br />
* Part of the AMEISE Client.<br />
* This component visualizes the phases of a simulation run in a bar chart.<br />
<br />
<b>Friendly Peer (Duration ~ 30 sec)</b><br />
* Part of the AMEISE Client (optional).<br />
* An agent, running in the background, and observing the simulation run. When activates, it provides information about possible problems on the fly.<br />
<br />
<b>Rollback (Duration ~ 45 sec)</b><br />
* Part of the AMEISE Client (optional).<br />
* Both, the tree view and the phase view component, provide a feature to move back to an earlier point of time during a simulation run. With it one can try out different simulation strategies. <br />
</div><br />
<br />
<br />
== Tools ==<br />
<div style='padding-left:1.5em'><br />
<b>AORTA (Duration ~ 1 min.)</b><br />
* Java-based tool for creating an assessment report and exporting it to a PDF file. <br />
* No prior knowledge is required. <br />
</div><br />
<br />
<br />
<br />
<!-- __NOTOC__ --><br />
__NOEDITSECTION__<br />
[[de:DemosTest]]<br />
[[en:DemosTest]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--></div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Viewlet_Demos&diff=1989Viewlet Demos2013-05-16T13:17:31Z<p>Toffler: </p>
<hr />
<div>The AMEISE - System consists of several components. The AMEISE client offers a lot of features, and there is also a tool for creating assessment-reports (AORTA). The following short viewlets demonstrate the most important navigation abilities and supporting components (from a didactic point of view) during and after a simulation run. If you don’t know AMEISE, please start with the general introduction of the AMEISE client. <br />
<br />
== AMEISE Client ==<br />
[[Image:Film.jpg|right|140px|]]<br />
<div style='padding-left:1.5em'><br />
=== General Introduction ===<br />
<br />
<div style='padding-left:1.5em'><br />
[[Ameise_Demo.flv|AMEISE-Client (Duration ~ 5 min)]]<br />
* Presents a short simulation run. <br />
* No prior knowledge is required. <br />
</div><br />
<br />
=== Navigation Options ===<br />
<div style='padding-left:1.5em'><br />
<b>Ameise Wall (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE Client.<br />
* Visualizes the steps of a simulation run on a "Perspective Wall".<br />
<br />
<b>TreeView (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE Client.<br />
* Visualizes the steps of a simulation run in a tree-like structure.<br />
</div><br />
<br />
=== Supervising Components ===<br />
<div style='padding-left:1.5em'><br />
<b>Advisor (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE Client (optional).<br />
* The advisor provides feedback about the current simulation run and gives advice on how to improve the simulation results. <br />
<br />
<b>PhaseView (Duration ~ 30 sec)</b><br />
* Part of the AMEISE Client.<br />
* This component visualizes the phases of a simulation run in a bar chart.<br />
<br />
<b>Friendly Peer (Duration ~ 30 sec)</b><br />
* Part of the AMEISE Client (optional).<br />
* An agent, running in the background, and observing the simulation run. When activates, it provides information about possible problems on the fly.<br />
<br />
<b>Rollback (Duration ~ 45 sec)</b><br />
* Part of the AMEISE Client (optional).<br />
* Both, the tree view and the phase view component, provide a feature to move back to an earlier point of time during a simulation run. With it one can try out different simulation strategies. <br />
</div><br />
<br />
<br />
== Tools ==<br />
<div style='padding-left:1.5em'><br />
<b>AORTA (Duration ~ 1 min.)</b><br />
* Java-based tool for creating an assessment report and exporting it to a PDF file. <br />
* No prior knowledge is required. <br />
</div><br />
<br />
<br />
<br />
<!-- __NOTOC__ --><br />
__NOEDITSECTION__<br />
[[de:DemosTest]]<br />
[[en:DemosTest]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--></div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Viewlet_Demos&diff=1988Viewlet Demos2013-05-16T13:16:07Z<p>Toffler: </p>
<hr />
<div>The AMEISE - System consists of several components. The AMEISE client offers a lot of features, and there is also a tool for creating assessment-reports (AORTA). The following short viewlets demonstrate the most important navigation abilities and supporting components (from a didactic point of view) during and after a simulation run. If you don’t know AMEISE, please start with the general introduction of the AMEISE client. <br />
<br />
== AMEISE Client ==<br />
[[Image:Film.jpg|right|140px|]]<br />
<div style='padding-left:1.5em'><br />
=== General Introduction ===<br />
<br />
<div style='padding-left:1.5em'><br />
[http://www.youtube.com/watch?v=Vp4Svi1z71Q|AMEISE-Client (Duration ~ 5 min)]<br />
* Presents a short simulation run. <br />
* No prior knowledge is required. <br />
</div><br />
<br />
=== Navigation Options ===<br />
<div style='padding-left:1.5em'><br />
<b>Ameise Wall (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE Client.<br />
* Visualizes the steps of a simulation run on a "Perspective Wall".<br />
<br />
<b>TreeView (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE Client.<br />
* Visualizes the steps of a simulation run in a tree-like structure.<br />
</div><br />
<br />
=== Supervising Components ===<br />
<div style='padding-left:1.5em'><br />
<b>Advisor (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE Client (optional).<br />
* The advisor provides feedback about the current simulation run and gives advice on how to improve the simulation results. <br />
<br />
<b>PhaseView (Duration ~ 30 sec)</b><br />
* Part of the AMEISE Client.<br />
* This component visualizes the phases of a simulation run in a bar chart.<br />
<br />
<b>Friendly Peer (Duration ~ 30 sec)</b><br />
* Part of the AMEISE Client (optional).<br />
* An agent, running in the background, and observing the simulation run. When activates, it provides information about possible problems on the fly.<br />
<br />
<b>Rollback (Duration ~ 45 sec)</b><br />
* Part of the AMEISE Client (optional).<br />
* Both, the tree view and the phase view component, provide a feature to move back to an earlier point of time during a simulation run. With it one can try out different simulation strategies. <br />
</div><br />
<br />
<br />
== Tools ==<br />
<div style='padding-left:1.5em'><br />
<b>AORTA (Duration ~ 1 min.)</b><br />
* Java-based tool for creating an assessment report and exporting it to a PDF file. <br />
* No prior knowledge is required. <br />
</div><br />
<br />
<br />
<br />
<!-- __NOTOC__ --><br />
__NOEDITSECTION__<br />
[[de:DemosTest]]<br />
[[en:DemosTest]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--></div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Viewlet_Demos&diff=1987Viewlet Demos2013-05-16T13:15:20Z<p>Toffler: </p>
<hr />
<div>The AMEISE - System consists of several components. The AMEISE client offers a lot of features, and there is also a tool for creating assessment-reports (AORTA). The following short viewlets demonstrate the most important navigation abilities and supporting components (from a didactic point of view) during and after a simulation run. If you don’t know AMEISE, please start with the general introduction of the AMEISE client. <br />
<br />
== AMEISE Client ==<br />
[[Image:Film.jpg|right|140px|]]<br />
<div style='padding-left:1.5em'><br />
=== General Introduction ===<br />
<br />
<div style='padding-left:1.5em'><br />
[[http://www.youtube.com/watch?v=Vp4Svi1z71Q|AMEISE-Client (Duration ~ 5 min)]]<br />
* Presents a short simulation run. <br />
* No prior knowledge is required. <br />
</div><br />
<br />
=== Navigation Options ===<br />
<div style='padding-left:1.5em'><br />
<b>Ameise Wall (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE Client.<br />
* Visualizes the steps of a simulation run on a "Perspective Wall".<br />
<br />
<b>TreeView (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE Client.<br />
* Visualizes the steps of a simulation run in a tree-like structure.<br />
</div><br />
<br />
=== Supervising Components ===<br />
<div style='padding-left:1.5em'><br />
<b>Advisor (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE Client (optional).<br />
* The advisor provides feedback about the current simulation run and gives advice on how to improve the simulation results. <br />
<br />
<b>PhaseView (Duration ~ 30 sec)</b><br />
* Part of the AMEISE Client.<br />
* This component visualizes the phases of a simulation run in a bar chart.<br />
<br />
<b>Friendly Peer (Duration ~ 30 sec)</b><br />
* Part of the AMEISE Client (optional).<br />
* An agent, running in the background, and observing the simulation run. When activates, it provides information about possible problems on the fly.<br />
<br />
<b>Rollback (Duration ~ 45 sec)</b><br />
* Part of the AMEISE Client (optional).<br />
* Both, the tree view and the phase view component, provide a feature to move back to an earlier point of time during a simulation run. With it one can try out different simulation strategies. <br />
</div><br />
<br />
<br />
== Tools ==<br />
<div style='padding-left:1.5em'><br />
<b>AORTA (Duration ~ 1 min.)</b><br />
* Java-based tool for creating an assessment report and exporting it to a PDF file. <br />
* No prior knowledge is required. <br />
</div><br />
<br />
<br />
<br />
<!-- __NOTOC__ --><br />
__NOEDITSECTION__<br />
[[de:DemosTest]]<br />
[[en:DemosTest]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--></div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Viewlet_Demos&diff=1982Viewlet Demos2013-05-16T12:59:08Z<p>Toffler: </p>
<hr />
<div>The AMEISE - System consists of several components. The AMEISE client offers a lot of features, and there is also a tool for creating assessment-reports (AORTA). The following short viewlets demonstrate the most important navigation abilities and supporting components (from a didactic point of view) during and after a simulation run. If you don’t know AMEISE, please start with the general introduction of the AMEISE client. <br />
<br />
== AMEISE Client ==<br />
[[Image:Film.jpg|right|140px|]]<br />
<div style='padding-left:1.5em'><br />
=== General Introduction ===<br />
<br />
<div style='padding-left:1.5em'><br />
[[Media:AMEISE_Demo.flv|AMEISE-Client (Duration ~ 5 min)]]<br />
* Presents a short simulation run. <br />
* No prior knowledge is required. <br />
</div><br />
<br />
=== Navigation Options ===<br />
<div style='padding-left:1.5em'><br />
<b>Ameise Wall (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE Client.<br />
* Visualizes the steps of a simulation run on a "Perspective Wall".<br />
<br />
<b>TreeView (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE Client.<br />
* Visualizes the steps of a simulation run in a tree-like structure.<br />
</div><br />
<br />
=== Supervising Components ===<br />
<div style='padding-left:1.5em'><br />
<b>Advisor (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE Client (optional).<br />
* The advisor provides feedback about the current simulation run and gives advice on how to improve the simulation results. <br />
<br />
<b>PhaseView (Duration ~ 30 sec)</b><br />
* Part of the AMEISE Client.<br />
* This component visualizes the phases of a simulation run in a bar chart.<br />
<br />
<b>Friendly Peer (Duration ~ 30 sec)</b><br />
* Part of the AMEISE Client (optional).<br />
* An agent, running in the background, and observing the simulation run. When activates, it provides information about possible problems on the fly.<br />
<br />
<b>Rollback (Duration ~ 45 sec)</b><br />
* Part of the AMEISE Client (optional).<br />
* Both, the tree view and the phase view component, provide a feature to move back to an earlier point of time during a simulation run. With it one can try out different simulation strategies. <br />
</div><br />
<br />
<br />
== Tools ==<br />
<div style='padding-left:1.5em'><br />
<b>AORTA (Duration ~ 1 min.)</b><br />
* Java-based tool for creating an assessment report and exporting it to a PDF file. <br />
* No prior knowledge is required. <br />
</div><br />
<br />
<br />
<br />
<!-- __NOTOC__ --><br />
__NOEDITSECTION__<br />
[[de:DemosTest]]<br />
[[en:DemosTest]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--></div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Viewlet_Demos&diff=1980Viewlet Demos2013-05-16T12:49:49Z<p>Toffler: </p>
<hr />
<div>The AMEISE - System consists of several components. The AMEISE client offers a lot of features, and there is also a tool for creating assessment-reports (AORTA). The following short viewlets demonstrate the most important navigation abilities and supporting components (from a didactic point of view) during and after a simulation run. If you don’t know AMEISE, please start with the general introduction of the AMEISE client. <br />
<br />
== AMEISE Client ==<br />
[[Image:Film.jpg|right|140px|]]<br />
<div style='padding-left:1.5em'><br />
=== General Introduction ===<br />
<br />
<div style='padding-left:1.5em'><br />
[[Media:MovieClient.jpg|AMEISE-Client (Duration ~ 5 min)]]<br />
* Presents a short simulation run. <br />
* No prior knowledge is required. <br />
</div><br />
<br />
=== Navigation Options ===<br />
<div style='padding-left:1.5em'><br />
<b>Ameise Wall (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE Client.<br />
* Visualizes the steps of a simulation run on a "Perspective Wall".<br />
<br />
<b>TreeView (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE Client.<br />
* Visualizes the steps of a simulation run in a tree-like structure.<br />
</div><br />
<br />
=== Supervising Components ===<br />
<div style='padding-left:1.5em'><br />
<b>Advisor (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE Client (optional).<br />
* The advisor provides feedback about the current simulation run and gives advice on how to improve the simulation results. <br />
<br />
<b>PhaseView (Duration ~ 30 sec)</b><br />
* Part of the AMEISE Client.<br />
* This component visualizes the phases of a simulation run in a bar chart.<br />
<br />
<b>Friendly Peer (Duration ~ 30 sec)</b><br />
* Part of the AMEISE Client (optional).<br />
* An agent, running in the background, and observing the simulation run. When activates, it provides information about possible problems on the fly.<br />
<br />
<b>Rollback (Duration ~ 45 sec)</b><br />
* Part of the AMEISE Client (optional).<br />
* Both, the tree view and the phase view component, provide a feature to move back to an earlier point of time during a simulation run. With it one can try out different simulation strategies. <br />
</div><br />
<br />
<br />
== Tools ==<br />
<div style='padding-left:1.5em'><br />
<b>AORTA (Duration ~ 1 min.)</b><br />
* Java-based tool for creating an assessment report and exporting it to a PDF file. <br />
* No prior knowledge is required. <br />
</div><br />
<br />
<br />
<br />
<!-- __NOTOC__ --><br />
__NOEDITSECTION__<br />
[[de:DemosTest]]<br />
[[en:DemosTest]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--></div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Motivation&diff=1832Motivation2013-05-11T11:33:23Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Tutorial Document|SESAM - The Heart of AMEISE}}<br />
<br />
<br />
The successful implementation of software projects is a difficult task. Both technical and also organizational problems must be solved. Less experience of young project managers leads to an unsolved first project in most cases. Therefore, it is useful to give trainees the opportunity to take the role of a project manager during their education. This opportunity should take the fear of failure and the worry about the associated consequences from students.<br />
<br />
==Purpose of the Project==<br />
<br />
<br />
Students of economics and informatics learn project management in general as a theoretical guide for practice. Universities and Colleges claim to train students for project management, but this could be achieved only very limited and selective in context of a lecture.<br />
<br />
AMEISE applies an innovative project "New Media in teaching on Universities and Colleges" in this context. AMEISE stands for "'''A''' '''M'''edia - '''E'''ducation '''I'''nitiative for '''S'''oftware '''E'''ngineering".<br />
<br />
==AMEISE==<br />
<br />
<br />
The AMEISE system provides students of computer science and business operations as well as subject-related university or college studies, the ability to collect project management experience on a simulator. Comparable to the training of pilots on a flight simulator, critical situations can be defined and trained with AMEISE perfectly without compromising equal to a real project is in danger.<br />
Thus, future projects can be performed by the project manager in a few hours that would normally take several months. They will be faced with the typical problems in projects and these situations should be solved by them. The heart of the AMEISE system is developed at the Universität Stuttgart, and it is called SESAM simulator.<br />
<br />
==SESAM==<br />
<br />
<br />
A model must be loaded in the simulator in order to simulate a project. The model decides,which project should be taken. Thus any type of project can be simulated (assuming appropriate models).<br />
<br />
==Objectives==<br />
<br />
<br />
In addition to the theoretical knowledge also the practical skills should be learned by using the simulator. Therefore, students assume the role of a project manager as they would do in a real project. This allows students to practice the independent planning and execution of projects and acquire important project management skills.<br />
<br />
<br />
{{NavigatorBar|Tutorial Document|SESAM - The Heart of AMEISE}}<br />
__NOEDITSECTION__<br />
[[de:Motivation]]<br />
[[en:Motivation]]<br />
[[Category:Tutorial]]<br />
__NOTOC__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Viewlet_Demos&diff=1829Viewlet Demos2013-05-11T11:28:14Z<p>Toffler: </p>
<hr />
<div>The AMEISE - System consists of several components. The AMEISE-client offers a lot of features and besides a tool called (AORTA), which creates assessment-reports. The following short viewlets demonstrate the most important navigation abilities and the most important supporting components (from a didactic point of view) during a simulation run. If you don’t know AMEISE, please start with the general introduction of the AMEISE-Client. <br />
<br />
== The AMEISE-Client ==<br />
[[Image:Film.jpg|right|140px]]<br />
=== General Introduction ===<br />
<div style='padding-left:1.5em'><br />
<b>AMEISE-Client (Duration ~ 5 min)</b><br />
* Shows you a short simulation run.<br />
* No previous experience necessary.<br />
</div><br />
<br />
=== Navigation Options ===<br />
<div style='padding-left:1.5em'><br />
<b>Ameise Wall (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE-Client.<br />
* Shows you the simulation run on a \"Perspective Wall\".<br />
<br />
<b>TreeView (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE-Client.<br />
* Shows you the simulation run as a Tree - Structure.<br />
</div><br />
<br />
=== Supervising Components ===<br />
<div style='padding-left:1.5em'><br />
<b>Advisor (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE-Client (optional).<br />
* The advisor provides information on the current simulation run and gives advice to improve the results.<br />
<br />
<b>PhaseView (Duration ~ 30 sec)</b><br />
* Part of the AMEISE-Client.<br />
* Shows the phases of the simulation run as a bar graph.<br />
<br />
<b>Friendly Peer (Duration ~ 30 sec)</b><br />
* Part of the AMEISE-Client (optional).<br />
* A little agent, who is watching the simulation from the background and gives information about possible problems on his own.<br />
<br />
<b>Rollback (Duration ~ 45 sec)</b><br />
* Part of the AMEISE-Client (optional).<br />
* Both, the tree view and the phase view have the opportunity to move back to an earlier point during a simulation run, so you can try different simulation ways.<br />
</div><br />
<br />
<br />
== Tools ==<br />
<div style='padding-left:1.5em'><br />
<b>AORTA (Duration ~ 1 min.)</b><br />
* Java-based tool to create an assessment report as a PDF - Document<br />
* No previous experience necessary.<br />
</div><br />
<br />
<br />
<br />
<!-- __NOTOC__ --><br />
__NOEDITSECTION__<br />
[[de:DemosTest]]<br />
[[en:DemosTest]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--></div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Project_Support_in_AMEISE&diff=1827Project Support in AMEISE2013-05-11T11:27:45Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Learning Objectives|The Advisor}}<br />
<br />
<br />
The analysis of the previous simulation runs shows, that trainees who have not performed project planning achieved worse results than trainees who planned the project before a simulation run.<br />
<br />
<br />
<br />
====Project Planning====<br />
{{Box1|Therefore the project should be planned before executing a simulation run. The project design is intended to include the sequence of actions to be undertaken in the project and include an appropriate workforce planning.}}<br />
<br />
However, a careful planning of the project is only possible after starting a simulation run, because from this point on trainees get relevant information (costs, employee skills) about the simulation run. The AMEISE - System provides also support information, that is available to trainees only after activities, which means that the student has to finish the work before getting a feedback from the support tools.<br />
<br />
Thereby, errors cannot be avoided, but trainees are alerted to mistakes and can learn from it. The support to the trainees is not to guide a perfect practice, but to give clues, which lead to an improvement of the current situation.<br />
<br />
<br />
<br />
====Common Mistakes====<br />
The analysis of SESAM/AMEISE - simulation runs has shown that the following mistakes were committed frequently:<br />
<br />
* '''Objectives are not fulfilled'''<br />
** The students have a big problem to fulfill all objectives of a simulation run.<br />
<br />
* '''Employee Utilization'''<br />
** Occupying their employees constantly, is a great problem for most students. Therefore, employees are often without an activity over a long period of time, but still earning money.<br />
<br />
* '''Checking - and corrective actions are missing or only partially carried out'''<br />
** Trainees forget about the necessary checking- and corrective actions of individual phases during the simulation run. This leads to bad results.<br />
<br />
<br />
<br />
====Support Tools====<br />
<br />
New components were integrated in the AMEISE environment to reduce those errors and support the trainees. Two options of '''Support Tools''' are available:<br />
<br />
* Advisor<br />
* Friendly Peer<br />
<br />
The instructor decides, if those support tools are available during a simulation run.<br />
<br />
<br />
<br />
====Overview====<br />
The advisor is a '''passive''' support tool and has to be questioned by the trainee. Therefore, the advisor assumes the role of the instructor and answers relevant questions during a simulation run. The friendly - peer is an '''active''' support tool and indicates the trainee if a difficult situation appears. The friendly - peer assumes the role of an experienced colleague who gives advice to trainees.<br />
<br />
<br />
{{NavigatorBar|Learning Objectives|The Advisor}}<br />
[[de:Projektunterstützung in AMEISE]]<br />
[[en:Project Support in AMEISE]]<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=The_Advisor&diff=1826The Advisor2013-05-11T11:27:18Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Project Support in AMEISE|The Friendly Peer}}<br />
<br />
<br />
<br />
====Advisor====<br />
<br />
The advisor can be asked by the trainee if he/she is in trouble. <br />
<br />
<br />
====Purpose of the Advisor====<br />
<br />
The task of the advisor is giving the trainee a couple of questions from a predefined catalog. If the trainee chooses one of these questions, the advisor will answer it. The advisor has an own interface in the simulation environment. Advice from the advisor is just snap - shot advice. That means he does not have the possibility to give statements about long time aspects of simulation runs.<br />
<br />
<br />
====Questions====<br />
<br />
The following list includes advice, which are delivered by the advisor:<br />
# '''Previous phases should not be forgotten.'''<br/>Phases always need a previous document as a basis. If this document is missing the phase is doomed to failure.<br />
# '''The previous phase should be finished before starting a new phase.'''<br/>It is important for following phases, that the previous phase and the emerged previous document has been finished by more than 50% to enable an overlapping of the phases. If this is not the case, the initiated phase fails. The limit of 50% depends on the model. (QA - Model).<br />
# ''' The previous phase should be reviewed before starting a new phase.'''<br/>To build on results of phases, it is important to review these phases. After the review, trainees know that the result of this phase still contains errors. These errors need to be corrected, in order to not adopt them into the next phase. <br />
# '''The previous phase should be corrected based on the review, before starting a new phase.'''<br/>After the review, it is important to correct the remaining errors to avoid their adoption in following phases.<br />
# '''After testing a correction should be performed'''<br/>Beside the review, trainees also can make a test to find errors in documents. Those errors also have to be corrected in order to obtain a correct document. <br/><br />
# '''Incomplete documents should be subjected to a further revision.'''<br/> During a simulation run it happens that single phases satisfy to less requirements or include too much errors. If the advisor recognizes a situation like this, he can react and deliver trainees an advice to improve the phase.<br />
<br />
<br />
<br />
==== Please note that ====<br />
{{Box1|The '''Feedback''' of the Advisor can be positive or negative!}}<br />
<br />
The feedback of the advisor depends on the '''current state''' of the phase. If asked that specifications have to revised, it depends on the completeness of the specification - document which feedback trainees get from the advisor. If the specifications are already satisfying, it is communicated to the trainees. If not, trainees get the advice to revise the document. <br />
The advisor '''can not''' give statements to phases, which have not been started! In this case, the trainee gets a message, which refers that there are not enough data available to evaluate. <br />
<br />
<br />
[[de:Der Ratgeber]]<br />
[[en:The Advisor]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--><br />
<br />
{{NavigatorBar|Project Support in AMEISE|The Friendly Peer}}<br />
<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Advices_of_the_Support_Tools&diff=1825Advices of the Support Tools2013-05-11T11:26:08Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|The Friendly Peer|Starting the Simulator}}<br />
<br />
<br />
<br />
The following list includes various advice for the relevant QA - Model which is associated to the support tools. Trainees get these advice directly from the advisor or the friendly - peer, to indicate and avoid difficult situations.<br />
<br />
====Allocation of the identifying Advice on the Support Tools====<br />
<br />
{|<br />
|-<br />
| style="text-align:center;background:#FFFFCA" | '''Advice''' <br />
| style="text-align:center;background:#FFFFCA" colspan="2" | '''Tool(s)'''<br />
|-<br />
| style="width:60%;text-align:center;background:#FFFFCA" | <br />
| style="width:20%;text-align:center;background:#FFFFCA" | '''Friendly - Peer'''<br />
| style="width:20%;text-align:center;background:#FFFFCA" | '''Advisor'''<br />
|-<br />
| style="text-align:left;background:#DDE9FF" | The author should not be used as a consultant.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" |The author should perform the correction of documents by himself.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | Previous phases should not be forgotten.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#FFFFCA" | The previous phase should be finished, before starting the next phase.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#DDE9FF" | The previous phase should be checked, before starting the next phase.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#FFFFCA" | The previous phase should be corrected in reference to the review, before starting the next phase.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#DDE9FF" | A new review can only be proceeded after a successful correction of a proceeded review. <br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | A correction should be made after performing a test.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#DDE9FF" | The customer should participate in specification- and manual reviews.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | The manual should be written in an early phase of the project.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | Do not change employees frequently.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | The activity and utilization of your developers should be observed.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | The employment of staff should be observed in each single phase.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | Employees should not be removed prematurely from a phase.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | Removing employees should be considered accurate.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | Employees should get activities which they are qualified for.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | Incomplete documents should be subjected to a further review.<br />
| style="text-align:center;background:#DDE9FF" | <br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
|}<br />
<br />
<br />
{{NavigatorBar|The Friendly Peer|Starting the Simulator}}<br />
<br />
[[de:Hinweise zu den Unterstützungswerkzeugen]]<br />
[[en:Advices of the Support Tools]]<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Motivation&diff=1822Motivation2013-05-11T11:18:34Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Tutorial Document|SESAM - The Heart of AMEISE}}<br />
<br />
<br />
The successful implementation of software projects is a difficult task. Both technical and also organizational problems must be solved. Less experience of young project managers leads to an unsolved first project in most cases. Therefore, it is useful to give trainees the opportunity to take the role of a project manager during their education. This opportunity should take the fear of failure and the worry about the associated consequences from students.<br />
<br />
==Purpose of the Project==<br />
<br />
<br />
Students of economics and informatics learn project management in general as a theoretical guide for practice. Universities and Colleges claim to train students for project management, but this could be achieved only very limited and selective in context of a lecture.<br />
<br />
AMEISE applies an innovative project "New Media in teaching on Universities and Colleges" in this context. AMEISE stands for "'''A''' '''M'''edia - '''E'''ducation '''I'''nitiative for '''S'''oftware '''E'''ngineering".<br />
<br />
==AMEISE==<br />
<br />
<br />
The AMEISE system provides students of computer science and business operations as well as subject-related university or college studies, the ability to collect project management experience on a simulator. Comparable to the training of pilots on a flight simulator, critical situations can be defined and trained with AMEISE perfectly without compromising equal to a real project is in danger.<br />
Thus, future projects can be performed by the project manager in a few hours that would normally take several months. They will be faced with the typical problems in projects and these situations should be solved by them. The heart of the AMEISE system is developed at the University of Stuttgart, and it is called SESAM simulator.<br />
<br />
==SESAM==<br />
<br />
<br />
A model must be loaded in the simulator in order to simulate a project. The model decides,which project should be taken. Thus any type of project can be simulated (assuming appropriate models).<br />
<br />
==Objectives==<br />
<br />
<br />
In addition to the theoretical knowledge also the practical skills should be learned by using the simulator. Therefore, students assume the role of a project manager as they would do in a real project. This allows students to practice the independent planning and execution of projects and acquire important project management skills.<br />
<br />
<br />
{{NavigatorBar|Tutorial Document|SESAM - The Heart of AMEISE}}<br />
__NOEDITSECTION__<br />
[[de:Motivation]]<br />
[[en:Motivation]]<br />
[[Category:Tutorial]]<br />
__NOTOC__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Motivation&diff=1821Motivation2013-05-11T11:15:19Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Tutorial Document|SESAM - The Heart of AMEISE}}<br />
<br />
<br />
The successful implementation of software projects is a difficult task. Both technical and also organizational problems must be solved. Less experience of young project managers leads to an unsolved first project in most cases. Therefore, it is useful to give trainees the opportunity to take the role of a project manager during their education. This opportunity should take the fear of failure from students, and they do not have to worry about the associated consequences.<br />
<br />
==Purpose of the Project==<br />
<br />
<br />
Students of economics and informatics learn project management in general as a theoretical guide for practice. Universities and Colleges claim to train students for project management, but this could be achieved only very limited and selective in context of a lecture.<br />
<br />
AMEISE applies an innovative project "New Media in teaching on Universities and Colleges" in this context. AMEISE stands for "'''A''' '''M'''edia - '''E'''ducation '''I'''nitiative for '''S'''oftware '''E'''ngineering".<br />
<br />
==AMEISE==<br />
<br />
<br />
The AMEISE system provides students of computer science and business operations as well as subject-related university or college studies, the ability to collect project management experience on a simulator. Comparable to the training of pilots on a flight simulator, critical situations can be defined and trained with AMEISE perfectly without compromising equal to a real project is in danger.<br />
Thus, future projects can be performed by the project manager in a few hours that would normally take several months. They will be faced with the typical problems in projects and these situations should be solved by them. The heart of the AMEISE system is developed at the University of Stuttgart, and it is called SESAM simulator.<br />
<br />
==SESAM==<br />
<br />
<br />
A model must be loaded in the simulator in order to simulate a project. The model decides,which project should be taken. Thus any type of project can be simulated (assuming appropriate models).<br />
<br />
==Objectives==<br />
<br />
<br />
In addition to the theoretical knowledge also the practical skills should be learned by using the simulator. Therefore, students assume the role of a project manager as they would do in a real project. This allows students to practice the independent planning and execution of projects and acquire important project management skills.<br />
<br />
<br />
{{NavigatorBar|Tutorial Document|SESAM - The Heart of AMEISE}}<br />
__NOEDITSECTION__<br />
[[de:Motivation]]<br />
[[en:Motivation]]<br />
[[Category:Tutorial]]<br />
__NOTOC__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=SESAM_-_The_Heart_of_AMEISE&diff=1820SESAM - The Heart of AMEISE2013-05-11T11:12:05Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Motivation|The QA - Model}}<br />
<br />
===Project Overview and Motivation ===<br />
<br />
Good project management is one of the key factors for the successful implementation of a (software) project. Often the training of project managers in the field of project management is strongly neglected. Usually, the education of a project manager is only theoretical.<br />
<br />
<br />
===The Simulation of Projects===<br />
To improve the training, the SESAM-Project ('''S'''oftware-'''E'''ngineering-'''S'''imulation through '''A'''nimated '''M'''odels)has been developed in the department of Software Engineering at the Universität of Stuttgart. Beside the theoretical component, a realistic component should complete the education of students. SESAM offers the opportunity for students to simulate different projects because it is not possible to allow every student to lead a real project during their bachelor degree course. This approach is also very interesting for the training of future project managers in the industry, because it can be accomplished quickly and cheaply.<br />
<br />
<br />
[[Image:Grundidee_en.gif|center]]<br />
<br />
<br />
{| style="background:#FFFFCA;padding:0.5em" |<br />
|- <br />
| In the context of training, trainees simulate projects on a simulator, where he is in the position of a project manager and interacts with customers, developers and documents. The simulation is divided into closed time sections, and the project is controlled by different commands.<br />
|}<br />
<br />
<br />
The '''Training Environment''' offers trainees the following options:<br />
<br />
* Simulation runs show how resources should be used.<br />
* If a trainee changes resources or the development process, simulation runs show them the consequences of their actions<br />
* Trainees are getting confronted with situations, which arise normally on real projects<br />
<br />
===Models===<br />
The simulation is based on models that include all relevant aspects of a project. The model which is loaded in the simulator decides which project is taken. In addition to the '''QA - Model''' it is also possible to execute the simulation with other models.<br />
<br />
__NOEDITSECTION__<br />
{{NavigatorBar|Motivation|The QA - Model}}<br />
[[de:SESAM - Der Kern von AMEISE]]<br />
[[en:SESAM - The Heart of AMEISE]]<br />
[[Category:Help]]</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=SESAM_-_The_Heart_of_AMEISE&diff=1819SESAM - The Heart of AMEISE2013-05-11T09:17:40Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Motivation|The QA - Model}}<br />
<br />
===Project Overview and Motivation ===<br />
<br />
Good project management is one of the key factors for the successful implementation of a (software) project. Often the training of project managers in the field of project management is strongly neglected. Usually, the education of a project manager is only theoretical.<br />
<br />
<br />
===The Simulation of Projects===<br />
To improve the training, the SESAM-Project ('''S'''oftware-'''E'''ngineering-'''S'''imulation through '''A'''nimated '''M'''odels)has been developed in the department of Software Engineering at the Universität of Stuttgart. Beside the theoretical component, a realistic component should complete the education of students. SESAM offers the opportunity for students to simulate different projects because it is not possible to allow every student to lead a real project during their bachelor degree course. This approach is also very interesting for the training of future project managers in the industry, because it can be accomplished quickly and cheaply.<br />
<br />
<br />
[[Image:Grundidee_en.gif|center]]<br />
<br />
<br />
{| style="background:#FFFFCA;padding:0.5em" |<br />
|- <br />
| In the context of training, trainees simulate projects on a simulator, where he is in the position of a project manager and interacts with customers, developers and documents. The simulation is divided into closed time sections, and the project is controlled by different commands.<br />
|}<br />
<br />
<br />
The '''Training Environment''' offers trainees the following options:<br />
<br />
* Simulation runs show how ressources should be used.<br />
* If a trainee changes ressources or the development process, simulation runs show them the consequences of their actions<br />
* Trainees are getting confronted with situations, which arise normally on real projects<br />
<br />
===Models===<br />
The simulation is based on models that include all relevant aspects of a project. The model which must be loaded in the simulator decides which project is taken. In addition to the '''QA - Model''' it is also possible to execute the simulation with other models.<br />
<br />
__NOEDITSECTION__<br />
{{NavigatorBar|Motivation|The QA - Model}}<br />
[[de:SESAM - Der Kern von AMEISE]]<br />
[[en:SESAM - The Heart of AMEISE]]<br />
[[Category:Help]]</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=SESAM_-_The_Heart_of_AMEISE&diff=1818SESAM - The Heart of AMEISE2013-05-11T09:14:57Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Motivation|The QA - Model}}<br />
<br />
===Project Overview and Motivation ===<br />
<br />
Good project management is one of the key factors for the successful implementation of a (software) project. Often the training of project managers in the field of project management is strongly neglected. The education of a project manager is usually only theoretical.<br />
<br />
<br />
===The Simulation of Projects===<br />
To improve the training, the SESAM-Project ('''S'''oftware-'''E'''ngineering-'''S'''imulation through '''A'''nimated '''M'''odels)has been developed in the department of Software Engineering at the Universität of Stuttgart. Beside the theoretical component, a realistic component should complete the education of students. SESAM offers the opportunity for students to simulate different projects because it is not possible to allow every student to lead a real project during their bachelor degree course. This approach is also very interesting for the training of future project managers in the industry, because it can be accomplished quickly and cheaply.<br />
<br />
<br />
[[Image:Grundidee_en.gif|center]]<br />
<br />
<br />
{| style="background:#FFFFCA;padding:0.5em" |<br />
|- <br />
| In the context of training, trainees simulate projects on a simulator, where he is in the position of a project manager and interacts with customers, developers and documents. The simulation is divided into closed time sections, and the project is controlled by different commands.<br />
|}<br />
<br />
<br />
The '''Training Environment''' offers trainees the following options:<br />
<br />
* Simulation runs show how ressources should be used.<br />
* If a trainee changes ressources or the development process, simulation runs show them the consequences of their actions<br />
* Trainees are getting confronted with situations, which arise normally on real projects<br />
<br />
===Models===<br />
The simulation is based on models that include all relevant aspects of a project. The model which must be loaded in the simulator decides which project is taken. In addition to the '''QA - Model''' it is also possible to execute the simulation with other models.<br />
<br />
__NOEDITSECTION__<br />
{{NavigatorBar|Motivation|The QA - Model}}<br />
[[de:SESAM - Der Kern von AMEISE]]<br />
[[en:SESAM - The Heart of AMEISE]]<br />
[[Category:Help]]</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Viewlet_Demos&diff=1817Viewlet Demos2013-05-11T09:11:47Z<p>Toffler: </p>
<hr />
<div>The AMEISE - System consists of several components. The AMEISE-client offers a lot of features and besides a tool called (AORTA), which creates assessment-reports. The following short viewlets demonstrate the most important navigation abilities and the most important supporting components (from a didactic point of view) during a simulation run. If you don’t know AMEISE, please start with the general introduction of the AMEISE-Client. <br />
<br />
== The AMEISE-Client ==<br />
[[Image:Film.jpg|right|140px]]<br />
=== General Introduction ===<br />
<div style='padding-left:1.5em'><br />
<b>AMEISE-Client (Duration ~ 5 min)</b><br />
* Shows you a short simulation run.<br />
* No previous experience necessary.<br />
</div><br />
<br />
=== Navigation Options ===<br />
<div style='padding-left:1.5em'><br />
<b>Ameise Wall (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE-Client.<br />
* Shows you the simulation run on a \"Perspective Wall\".<br />
<br />
<b>TreeView (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE-Client.<br />
* Shows you the simulation run as a Tree - Structure.<br />
</div><br />
<br />
=== Supervising Components ===<br />
<div style='padding-left:1.5em'><br />
<b>Advisor (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE-Client (optional).<br />
* The advisor provides information on the current simulation run and gives advises to improve the results.<br />
<br />
<b>PhaseView (Duration ~ 30 sec)</b><br />
* Part of the AMEISE-Client.<br />
* Shows the phases of the simulation run as a bar graph.<br />
<br />
<b>Friendly Peer (Duration ~ 30 sec)</b><br />
* Part of the AMEISE-Client (optional).<br />
* A little agent, who is watching the simulation from the background and gives information about possible problems on his own.<br />
<br />
<b>Rollback (Duration ~ 45 sec)</b><br />
* Part of the AMEISE-Client (optional).<br />
* Both, the tree view and the phase view have the opportunity to move back to an earlier point during a simulation run, so you can try different simulation ways.<br />
</div><br />
<br />
<br />
== Tools ==<br />
<div style='padding-left:1.5em'><br />
<b>AORTA (Duration ~ 1 min.)</b><br />
* Java-based tool to create an assessment report as a PDF - Document<br />
* No previous experience necessary.<br />
</div><br />
<br />
<br />
<br />
<!-- __NOTOC__ --><br />
__NOEDITSECTION__<br />
[[de:DemosTest]]<br />
[[en:DemosTest]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--></div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Viewlet_Demos&diff=1816Viewlet Demos2013-05-11T09:08:28Z<p>Toffler: </p>
<hr />
<div>The AMEISE - System consists of several components. The AMEISE-client offers a lot of features and besides a tool called (AORTA), which creates assessment-reports. The following short viewlets demonstrate the most important navigation abilities and the most important supporting components (from a didactic point of view) during a simulation run. If you don’t know AMEISE, please start with the general introduction of the AMEISE-client. <br />
<br />
== The AMEISE-client ==<br />
[[Image:Film.jpg|right|140px]]<br />
=== General Introduction ===<br />
<div style='padding-left:1.5em'><br />
<b>AMEISE - Client (Duration ~ 5 min)</b><br />
* Shows you a short simulation run.<br />
* No previous experience necessary.<br />
</div><br />
<br />
=== Navigation Options ===<br />
<div style='padding-left:1.5em'><br />
<b>Ameise Wall (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE-client.<br />
* Shows you the simulation run on a \"Perspective Wall\".<br />
<br />
<b>TreeView (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE-client.<br />
* Shows you the simulation run as a Tree - Structure.<br />
</div><br />
<br />
=== Supervising Components ===<br />
<div style='padding-left:1.5em'><br />
<b>Advisor (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE - Client (optional).<br />
* The advisor provides information on the current simulation run and gives advises to improve the results.<br />
<br />
<b>PhaseView (Duration ~ 30 sec)</b><br />
* Part of the AMEISE-client.<br />
* Shows the phases of the simulation run as a bar graph.<br />
<br />
<b>Friendly Peer (Duration ~ 30 sec)</b><br />
* Part of the AMEISE-client (optional).<br />
* A little agent, who is watching the simulation from the background and gives information about possible problems on his own.<br />
<br />
<b>Rollback (Duration ~ 45 sec)</b><br />
* Part of the AMEISE-client (optional).<br />
* Both, the tree view and the phase view have the opportunity to move back to an earlier point during a simulation run, so you can try different simulation ways.<br />
</div><br />
<br />
<br />
== Tools ==<br />
<div style='padding-left:1.5em'><br />
<b>AORTA (Duration ~ 1 min.)</b><br />
* Java-based tool to create an assessment report as a PDF - Document<br />
* No previous experience necessary.<br />
</div><br />
<br />
<br />
<br />
<!-- __NOTOC__ --><br />
__NOEDITSECTION__<br />
[[de:DemosTest]]<br />
[[en:DemosTest]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--></div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Viewlet_Demos&diff=1815Viewlet Demos2013-05-11T09:06:04Z<p>Toffler: </p>
<hr />
<div>The AMEISE - System consists of several components. The AMEISE-client offers a lot of features and besides a tool called (AORTA), which creates assessment-reports. The following short viewlets demonstrate the most important navigation abilities and the most important supporting components (from a didactic point of view) during a simulation run. If you don’t know AMEISE, please start with the general introduction of the AMEISE - Client. <br />
<br />
== The AMEISE - Client ==<br />
[[Image:Film.jpg|right|140px]]<br />
=== General Introduction ===<br />
<div style='padding-left:1.5em'><br />
<b>AMEISE - Client (Duration ~ 5 min)</b><br />
* Shows you a short simulation run.<br />
* No previous experience necessary.<br />
</div><br />
<br />
=== Navigation Options ===<br />
<div style='padding-left:1.5em'><br />
<b>Ameise Wall (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE - Client.<br />
* Shows you the simulation run on a \"Perspective Wall\".<br />
<br />
<b>TreeView (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE - Client.<br />
* Shows you the simulation run as a Tree - Structure.<br />
</div><br />
<br />
=== Supervising Components ===<br />
<div style='padding-left:1.5em'><br />
<b>Advisor (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE - Client (optional).<br />
* The advisor provides information on the current simulation run and gives advises to improve the results.<br />
<br />
<b>PhaseView (Duration ~ 30 sec)</b><br />
* Part of the AMEISE - Client.<br />
* Shows the phases of the simulation run as a bar graph.<br />
<br />
<b>Friendly Peer (Duration ~ 30 sec)</b><br />
* Part of the AMEISE - Client (optional).<br />
* A little agent, who is watching the simulation from the background and gives information about possible problems on his own.<br />
<br />
<b>Rollback (Duration ~ 45 sec)</b><br />
* Part of the AMEISE - Client (optional).<br />
* Both, the treeview and the phaseview have the opportunity to move back to an earlier point during a simulation run, so you can try different simulation ways.<br />
</div><br />
<br />
<br />
== Tools ==<br />
<div style='padding-left:1.5em'><br />
<b>AORTA (Duration ~ 1 min.)</b><br />
* Java-based tool to create an assessment report as a PDF - Document<br />
* No previous experience necessary.<br />
</div><br />
<br />
<br />
<br />
<!-- __NOTOC__ --><br />
__NOEDITSECTION__<br />
[[de:DemosTest]]<br />
[[en:DemosTest]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--></div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Viewlet_Demos&diff=1814Viewlet Demos2013-05-11T09:02:17Z<p>Toffler: </p>
<hr />
<div>The AMEISE - System consists of several components. The AMEISE - Client offers a lot of features and besides a tool(AORTA) creates Assessment - Reports. The following short viewlets demonstrate the most important navigation abilities and the most important supporting components during a simulation run. If you don’t know AMEISE, please start with the general introduction of the AMEISE - Client. <br />
<br />
== The AMEISE - Client ==<br />
[[Image:Film.jpg|right|140px]]<br />
=== General Introduction ===<br />
<div style='padding-left:1.5em'><br />
<b>AMEISE - Client (Duration ~ 5 min)</b><br />
* Shows you a short simulation run.<br />
* No previous experience necessary.<br />
</div><br />
<br />
=== Navigation Options ===<br />
<div style='padding-left:1.5em'><br />
<b>Ameise Wall (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE - Client.<br />
* Shows you the simulation run on a \"Perspective Wall\".<br />
<br />
<b>TreeView (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE - Client.<br />
* Shows you the simulation run as a Tree - Structure.<br />
</div><br />
<br />
=== Supervising Components ===<br />
<div style='padding-left:1.5em'><br />
<b>Advisor (Duration ~ 30 sec.)</b><br />
* Part of the AMEISE - Client (optional).<br />
* The advisor provides information on the current simulation run and gives advises to improve the results.<br />
<br />
<b>PhaseView (Duration ~ 30 sec)</b><br />
* Part of the AMEISE - Client.<br />
* Shows the phases of the simulation run as a bar graph.<br />
<br />
<b>Friendly Peer (Duration ~ 30 sec)</b><br />
* Part of the AMEISE - Client (optional).<br />
* A little agent, who is watching the simulation from the background and gives information about possible problems on his own.<br />
<br />
<b>Rollback (Duration ~ 45 sec)</b><br />
* Part of the AMEISE - Client (optional).<br />
* Both, the treeview and the phaseview have the opportunity to move back to an earlier point during a simulation run, so you can try different simulation ways.<br />
</div><br />
<br />
<br />
== Tools ==<br />
<div style='padding-left:1.5em'><br />
<b>AORTA (Duration ~ 1 min.)</b><br />
* Java-based tool to create an assessment report as a PDF - Document<br />
* No previous experience necessary.<br />
</div><br />
<br />
<br />
<br />
<!-- __NOTOC__ --><br />
__NOEDITSECTION__<br />
[[de:DemosTest]]<br />
[[en:DemosTest]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--></div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Project_Support_in_AMEISE&diff=1813Project Support in AMEISE2013-05-11T08:50:47Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Learning Objectives|The Advisor}}<br />
<br />
<br />
The analysis of the previous simulation runs shows, that trainees who have not performed project planning achieved worse results than trainees who planned the project before a simulation run.<br />
<br />
<br />
<br />
====Project Planning====<br />
{{Box1|Therefore the project should be planned before executing a simulation run. The project design is intended to include the sequence of actions to be undertaken in the project and include an appropriate workforce planning.}}<br />
<br />
However, a careful planning of the project is only possible after starting a simulation run, because from this point on trainees get relevant information (costs, employee skills) about the simulation run. The AMEISE - System provides also support information, that is available to trainees only after activities, which means that the student has to finish the work before getting a feedback from the support tools.<br />
<br />
Thereby, errors cannot be avoided, but trainees are alerted to mistakes and can learn from it. The support to the trainees is not to guide a perfect practice, but to give clues, which lead to an improvement of the current situation.<br />
<br />
<br />
<br />
====Common Mistakes====<br />
The analysis of SESAM/AMEISE - simulation runs has shown that the following mistakes were committed frequently:<br />
<br />
* '''Objectives are not fulfilled'''<br />
** The students have a big problem to fulfill all objectives of a simulation run.<br />
<br />
* '''Employee Utilization'''<br />
** Occupying their employees constantly, is a great problem for most students. Therefore, employees are often without an activity over a long period of time, but still earning money.<br />
<br />
* '''Checking - and corrective actions are missing or only partially carried out'''<br />
** Trainees forget about the necessary checking- and corrective actions of individual phases during the simulation run. This leads to bad results.<br />
<br />
<br />
<br />
====Support Tools====<br />
<br />
New components were integrated in the AMEISE environment to reduce those errors and support the trainees. Two options of '''Support Tools''' are available:<br />
<br />
* Advisor<br />
* Friendly Peer<br />
<br />
The instructor decides, if those support tools are available during a simulation run.<br />
<br />
<br />
<br />
====Overview====<br />
The advisor is a '''passive''' support tool and has to be questioned by the trainee. Therefore, the advisor assumes the role of the instructor and answers relevant questions during a simulation run. The friendly - peer is an '''active''' support tool and indicates the trainee if a difficult situation appears. The friendly - peer assumes the role of an experienced colleague who gives advises to trainees.<br />
<br />
<br />
{{NavigatorBar|Learning Objectives|The Advisor}}<br />
[[de:Projektunterstützung in AMEISE]]<br />
[[en:Project Support in AMEISE]]<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Project_Support_in_AMEISE&diff=1812Project Support in AMEISE2013-05-11T08:50:01Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Learning Objectives|The Advisor}}<br />
<br />
<br />
The analysis of the previous simulation runs shows, that trainees who have not performed project planning achieved worse results than trainees who planned the project before a simulation run.<br />
<br />
<br />
<br />
====Project Planning====<br />
{{Box1|Therefore the project should be planned before executing a simulation run. The project design is intended to include the sequence of actions to be undertaken in the project and include an appropriate workforce planning.}}<br />
<br />
However, a careful planning of the project is only possible after starting a simulation run, because from this point on trainees get relevant information (costs, employee skills) about the simulation run. The AMEISE - System provides also support information, that is available to trainees only after activities, which means that the student has to finish the work before getting a feedback from the support tools.<br />
<br />
Thereby, errors cannot be avoided, but trainees are alerted to mistakes and can learn from it. The support to the trainees is not to guide a perfect practice, but to give clues, which lead to an improvement of the current situation.<br />
<br />
<br />
<br />
====Common Mistakes====<br />
The analysis of SESAM/AMEISE - simulation runs has shown that the following mistakes were committed frequently:<br />
<br />
* '''Objectives are not fulfilled'''<br />
** The students have a big problem to fulfill all objectives of a simulation run.<br />
<br />
* '''Employee Utilization'''<br />
** Occupying their employees constantly, is a great problem for most students. Therefore, employees are often without an activity over a long period of time, but still earning money.<br />
<br />
* '''Checking - and corrective actions are missing or only partially carried out'''<br />
<br />
** Trainees forget about the necessary checking- and corrective actions of individual phases during the simulation run. This leads to bad results.<br />
<br />
<br />
<br />
====Support Tools====<br />
<br />
New components were integrated in the AMEISE environment to reduce those errors and support the trainees. Two options of '''Support Tools''' are available:<br />
<br />
* Advisor<br />
* Friendly Peer<br />
<br />
The instructor decides, if those support tools are available during a simulation run.<br />
<br />
<br />
<br />
====Overview====<br />
The advisor is a '''passive''' support tool and has to be questioned by the trainee. Therefore, the advisor assumes the role of the instructor and answers relevant questions during a simulation run. The friendly - peer is an '''active''' support tool and indicates the trainee if a difficult situation appears. The friendly - peer assumes the role of an experienced colleague who gives advises to trainees.<br />
<br />
<br />
{{NavigatorBar|Learning Objectives|The Advisor}}<br />
[[de:Projektunterstützung in AMEISE]]<br />
[[en:Project Support in AMEISE]]<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Project_Support_in_AMEISE&diff=1811Project Support in AMEISE2013-05-11T08:49:39Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Learning Objectives|The Advisor}}<br />
<br />
<br />
The analysis of the previous simulation runs shows, that trainees who have not performed project planning achieved worse results than trainees who planned the project before a simulation run.<br />
<br />
<br />
<br />
====Project Planning====<br />
{{Box1|Therefore the project should be planned before executing a simulation run. The project design is intended to include the sequence of actions to be undertaken in the project and include an appropriate workforce planning.}}<br />
<br />
However, a careful planning of the project is only possible after starting a simulation run, because from this point on trainees get relevant information (costs, employee skills) about the simulation run. The AMEISE - System provides also support information, that is available to trainees only after activities, which means that the student has to finish the work before getting a feedback from the support tools.<br />
<br />
Thereby, errors cannot be avoided, but trainees are alerted to mistakes and can learn from it. The support to the trainees is not to guide a perfect practice, but to give clues, which lead to an improvement of the current situation.<br />
<br />
<br />
<br />
====Common Mistakes====<br />
The analysis of SESAM/AMEISE - simulation runs has shown that the following mistakes were committed frequently:<br />
<br />
* '''Objectives are not fulfilled'''<br />
** The students have a big problem to fulfill all objectives of a simulation run.<br />
<br />
* '''Employee Utilization'''<br />
** Occupying their employees constantly, is a great problem for most students. Therefore, employees are often without an activity over a long period of time, but still earning money.<br />
<br />
* '''Checking - and corrective actions are missing or only partially carried out'''<br />
<br />
** Trainees forget about the necessary checking- and corrective actions of individual phases during the simulation run. This leads to bad results.<br />
<br />
<br />
<br />
====Support Tools====<br />
<br />
New components were integrated in the AMEISE environment to reduce those errors and support the trainees. Two options of '''Support Tools''' are available:<br />
<br />
* Advisor<br />
* Friendly Peer<br />
<br />
The instructor decides, if these support tools are available during a simulation run.<br />
<br />
<br />
<br />
====Overview====<br />
The advisor is a '''passive''' support tool and has to be questioned by the trainee. Therefore, the advisor assumes the role of the instructor and answers relevant questions during a simulation run. The friendly - peer is an '''active''' support tool and indicates the trainee if a difficult situation appears. The friendly - peer assumes the role of an experienced colleague who gives advises to trainees.<br />
<br />
<br />
{{NavigatorBar|Learning Objectives|The Advisor}}<br />
[[de:Projektunterstützung in AMEISE]]<br />
[[en:Project Support in AMEISE]]<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Project_Support_in_AMEISE&diff=1810Project Support in AMEISE2013-05-11T08:49:13Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Learning Objectives|The Advisor}}<br />
<br />
<br />
The analysis of the previous simulation runs shows, that trainees who have not performed project planning achieved worse results than trainees who planned the project before a simulation run.<br />
<br />
<br />
<br />
====Project Planning====<br />
{{Box1|Therefore the project should be planned before executing a simulation run. The project design is intended to include the sequence of actions to be undertaken in the project and include an appropriate workforce planning.}}<br />
<br />
However, a careful planning of the project is only possible after starting a simulation run, because from this point on trainees get relevant information (costs, employee skills) about the simulation run. The AMEISE - System provides also support information, that is available to trainees only after activities, which means that the student has to finish the work before getting a feedback from the support tools.<br />
<br />
Thereby, errors cannot be avoided, but trainees are alerted to mistakes and can learn from it. The support to the trainees is not to guide a perfect practice, but to give clues, which lead to an improvement of the current situation.<br />
<br />
<br />
<br />
====Common Mistakes====<br />
The analysis of SESAM/AMEISE - simulation runs has shown that the following mistakes were committed frequently:<br />
<br />
* '''Objectives are not fulfilled'''<br />
** The students have a big problem to fulfill all objectives of a simulation run.<br />
<br />
* '''Employee Utilization'''<br />
** Occupying their employees constantly, is a great problem for most students. Therefore, employees are often without an activity over a long period of time, but still earning money.<br />
<br />
* '''Checking - and corrective actions are missing or only partially carried out'''<br />
<br />
** Trainees forget about the necessary checking- and corrective actions of individual phases during the simulation run. This leads to bad results.<br />
<br />
<br />
<br />
====Support Tools====<br />
<br />
New components were integrated in the AMEISE environment to reduce those errors and support the trainees. Two options of '''Support Tools''' are available:<br />
<br />
* Advisor<br />
* Friendly Peer<br />
<br />
The instructor decides, if these support tools are available during a simulation run.<br />
<br />
<br />
<br />
====Overview====<br />
The advisor is a '''passive''' support tool and has to be questioned by the trainee. Therefore, the advisor assumes the role of the instructor and answers relevant questions during a simulation run. The friendly - peer is an '''active''' support tool and indicates the trainee if a difficult situation appears. The friendly - peer assumes the role of an experienced colleague who gives advises to trainees.<br />
<br />
<br />
{{NavigatorBar|Learning Objectives|The Advisor}}<br />
[[de:Projektunterstützung in AMEISE]]<br />
[[en:Project Support in AMEISE]]<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Project_Support_in_AMEISE&diff=1809Project Support in AMEISE2013-05-11T08:47:02Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Learning Objectives|The Advisor}}<br />
<br />
<br />
The analysis of the previous simulation runs shows, that trainees who have not performed project planning achieved worse results than trainees who planned the project before a simulation run.<br />
<br />
<br />
<br />
====Project Planning====<br />
{{Box1|Therefore the project should be planned before executing a simulation run. The project design is intended to include the sequence of actions to be undertaken in the project and include an appropriate workforce planning.}}<br />
<br />
However, a careful planning of the project is only possible after starting a simulation run, because from this point on trainees get relevant information (costs, employee skills) about the simulation run. The AMEISE - System provides also support information, that is available to trainees only after activities, which means that the student has to finish the work before getting a feedback from the support tools.<br />
<br />
Thereby, errors cannot be avoided, but trainees are alerted to mistakes and can learn from it. The support to the trainees is not to guide a perfect practice, but to give clues, which lead to an improvement of the current situation.<br />
<br />
<br />
<br />
====Common Mistakes====<br />
The analysis of SESAM/AMEISE - simulation runs has shown that the following mistakes were committed frequently:<br />
<br />
* '''Objectives are not fulfilled'''<br />
** The students have a big problem to fulfill all objectives of a simulation run.<br />
<br />
* '''Employee Utilization'''<br />
** Occupying their employees constantly, is a great problem for most students. Therefore, employees are often without an activity over a long period of time, but still earning money.<br />
<br />
* '''Checking - and corrective actions are missing or only partially carried out'''<br />
<br />
** Trainees forget about the necessary checking- and corrective actions of individual phases during the simulation run. This leads to bad results.<br />
<br />
<br />
<br />
====Support Tools====<br />
<br />
New components were integrated in the AMEISE environment, to reduce this errors and support the trainees. Two options of '''Support Tools''' are available:<br />
<br />
*Advisor<br />
*Friendly Peer<br />
<br />
The instructor decides, if these support tools are available during a simulation run.<br />
<br />
<br />
<br />
====Overview====<br />
The advisor is a '''passive''' support tool and has to be questioned by the trainee. Therefore the advisor assumes the role of the instructor and answers relevant questions during a simulation run. The friendly - peer is an '''active''' support tool and indicates the trainee if a difficult situation appears. The friendly - peer assumes the role of an experienced colleague who gives advises to trainees.<br />
<br />
<br />
{{NavigatorBar|Learning Objectives|The Advisor}}<br />
[[de:Projektunterstützung in AMEISE]]<br />
[[en:Project Support in AMEISE]]<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Project_Support_in_AMEISE&diff=1808Project Support in AMEISE2013-05-11T08:45:52Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Learning Objectives|The Advisor}}<br />
<br />
<br />
The analysis of the previous simulation runs shows, that trainees who have not performed project planning achieved worse results than trainees who planned the project before a simulation run.<br />
<br />
<br />
<br />
====Project Planning====<br />
{{Box1|Therefore the project should be planned before executing a simulation run. The project design is intended to include the sequence of actions to be undertaken in the project and include an appropriate workforce planning.}}<br />
<br />
However, a careful planning of the project is only possible after starting a simulation run, because from this point on trainees get relevant information (costs, employee skills) about the simulation run. The AMEISE - System provides also support information, that is available to trainees only after activities, which means that the student has to finish the work before getting a feedback from the support tools.<br />
<br />
Thereby, errors cannot be avoided, but trainees are alerted to mistakes and can learn from it. The support to the trainees is not to guide a perfect practice, but to give clues, which lead to an improvement of the current situation.<br />
<br />
<br />
<br />
====Common Mistakes====<br />
The analysis of SESAM/AMEISE - simulation runs has shown that the following mistakes were committed frequently:<br />
<br />
* '''Objectives are not fulfilled'''<br />
** The students have a big problem to fulfill all objectives of a simulation run.<br />
<br />
* '''Employee Utilization'''<br />
** Occupying their employees constantly, is a great problem for most students. Therefore, employees are often without an activity over a long period of time, but still earning money.<br />
<br />
* '''Checking - and corrective actions are missing or only partially carried out'''<br />
<br />
** Trainees forget about the necessary checking- and corrective actions of individual phases during the simulation run. This leads to bad results.<br />
<br />
<br />
<br />
====Support Tools====<br />
<br />
New components were integrated in the AMEISE environment, to reduce this errors and support the trainees. Two options of '''Support Tools''' are available:<br />
<br />
Advisor<br />
Friendly Peer<br />
<br />
The instructor decides, if these support tools are available during a simulation run.<br />
<br />
<br />
<br />
====Overview====<br />
The advisor is a '''passive''' support tool and has to be questioned by the trainee. Therefore the advisor assumes the role of the instructor and answers relevant questions during a simulation run. The friendly - peer is an '''active''' support tool and indicates the trainee if a difficult situation appears. The friendly - peer assumes the role of an experienced colleague who gives advises to trainees.<br />
<br />
<br />
{{NavigatorBar|Learning Objectives|The Advisor}}<br />
[[de:Projektunterstützung in AMEISE]]<br />
[[en:Project Support in AMEISE]]<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Project_Support_in_AMEISE&diff=1807Project Support in AMEISE2013-05-11T08:42:31Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Learning Objectives|The Advisor}}<br />
<br />
<br />
The analysis of the previous simulation runs shows, that trainees who have not performed project planning achieved worse results than trainees who planned the project before a simulation run.<br />
<br />
<br />
<br />
====Project Planning====<br />
{{Box1|Therefore the project should be planned before executing a simulation run. The project design is intended to include the sequence of actions to be undertaken in the project and include an appropriate workforce planning.}}<br />
<br />
However, a careful planning of the project is only possible after starting a simulation run, because from this point on trainees get relevant information (costs, employee skills) about the simulation run. The AMEISE - System provides also support information, that is available to trainees only after activities, which means that the student has to finish the work before getting a feedback from the support tools.<br />
<br />
Thereby, errors cannot be avoided, but trainees are alerted to mistakes and can learn from it. The support to the trainees is not to guide a perfect practice, but to give clues, which lead to an improvement of the current situation.<br />
<br />
<br />
<br />
====Common Mistakes====<br />
The analysis of SESAM/AMEISE - simulation runs has shown that the following mistakes were committed frequently:<br />
<br />
* '''Objectives are not fulfilled'''<br />
** The students have a big problem to fulfill all objectives of a simulation run.<br />
<br />
* '''Employee Utilization'''<br />
** Occupying their employees constantly, is a great problem for most students. Therefore, employees are often without an activity over a long period of time, but continue to earn money.<br />
<br />
* '''Checking - and corrective actions are missing or only partially carried out'''<br />
<br />
** Trainees forget about the necessary checking- and corrective actions of individual phases during the simulation run. This leads to bad results.<br />
<br />
<br />
<br />
====Support Tools====<br />
<br />
New components were integrated in the AMEISE environment, to reduce this errors and support the trainees. Two options of '''Support Tools''' are available:<br />
<br />
Advisor<br />
Friendly Peer<br />
<br />
The instructor decides, if these support tools are available during a simulation run.<br />
<br />
<br />
<br />
====Overview====<br />
The advisor is a '''passive''' support tool and has to be questioned by the trainee. Therefore the advisor assumes the role of the instructor and answers relevant questions during a simulation run. The friendly - peer is an '''active''' support tool and indicates the trainee if a difficult situation appears. The friendly - peer assumes the role of an experienced colleague who gives advises to trainees.<br />
<br />
<br />
{{NavigatorBar|Learning Objectives|The Advisor}}<br />
[[de:Projektunterstützung in AMEISE]]<br />
[[en:Project Support in AMEISE]]<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Project_Support_in_AMEISE&diff=1806Project Support in AMEISE2013-05-11T08:40:29Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Learning Objectives|The Advisor}}<br />
<br />
<br />
The analysis of the previous simulation runs shows, that trainees who have not performed project planning achieved worse results than trainees who planned the project before a simulation run.<br />
<br />
<br />
<br />
====Project Planning====<br />
{{Box1|Therefore the project should be planned before executing a simulation run. The project design is intended to include the sequence of actions to be undertaken in the project and include an appropriate workforce planning.}}<br />
<br />
However, a careful planning of the project is only possible after starting a simulation run, because from this point on trainees get relevant information (costs, employee skills) about the simulation run. The AMEISE - System provides also support information, that is available to trainees only after activities, which means that the student has to finish the work before getting a feedback from the support tools.<br />
<br />
Thereby, errors cannot be avoided, but trainees are alerted to mistakes and can learn from it. The support to the trainees is not to guide a perfect practice, but to give clues, which lead to an improvement of the current situation.<br />
<br />
<br />
<br />
====Common Mistakes====<br />
The analysis of SESAM/AMEISE - simulation runs has shown that the following mistakes are committed very often:<br />
<br />
* '''Objectives are not fulfilled'''<br />
** The students have a big problem to fulfill all objectives of a simulation run.<br />
<br />
* '''Employee Utilization'''<br />
** Occupying their employees constantly, is a great problem for most students. Therefore, employees are often without an activity over a long period of time, but continue to earn money.<br />
<br />
* '''Checking - and corrective actions are missing or only partially carried out'''<br />
<br />
** Trainees forget about the necessary checking- and corrective actions of individual phases during the simulation run. This leads to bad results.<br />
<br />
<br />
<br />
====Support Tools====<br />
<br />
New components were integrated in the AMEISE environment, to reduce this errors and support the trainees. Two options of '''Support Tools''' are available:<br />
<br />
Advisor<br />
Friendly Peer<br />
<br />
The instructor decides, if these support tools are available during a simulation run.<br />
<br />
<br />
<br />
====Overview====<br />
The advisor is a '''passive''' support tool and has to be questioned by the trainee. Therefore the advisor assumes the role of the instructor and answers relevant questions during a simulation run. The friendly - peer is an '''active''' support tool and indicates the trainee if a difficult situation appears. The friendly - peer assumes the role of an experienced colleague who gives advises to trainees.<br />
<br />
<br />
{{NavigatorBar|Learning Objectives|The Advisor}}<br />
[[de:Projektunterstützung in AMEISE]]<br />
[[en:Project Support in AMEISE]]<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Project_Support_in_AMEISE&diff=1805Project Support in AMEISE2013-05-11T08:37:31Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Learning Objectives|The Advisor}}<br />
<br />
<br />
The analysis of the previous simulation runs shows, that trainees who have not performed project planning achieved worse results than trainees who planned the project before a simulation run.<br />
<br />
<br />
<br />
====Project Planning====<br />
{{Box1|Therefore the project should be planned before executing a simulation run. The project design is intended to include the sequence of actions to be undertaken in the project and include an appropriate workforce planning.}}<br />
<br />
However, a careful planning of the project is only possible after starting a simulation run, because from this point on trainees get relevant information (costs, employee skills) about the simulation run. The AMEISE - System provides also support information, that is available to trainees only after activities, which means that the student has to finish the work before getting a feedback from the support tools.<br />
<br />
Thereby, errors cannot be avoided, but trainees are alerted to mistakes and can learn from it. The support of trainees is not to guide a perfect practice, but it will be given guidance as to what activities would lead to an improvement of the current situation.<br />
<br />
<br />
<br />
====Common Mistakes====<br />
The analysis of SESAM/AMEISE - simulation runs has shown that the following mistakes are committed very often:<br />
<br />
* '''Objectives are not fulfilled'''<br />
** The students have a big problem to fulfill all objectives of a simulation run.<br />
<br />
* '''Employee Utilization'''<br />
** Occupying their employees constantly, is a great problem for most students. Therefore, employees are often without an activity over a long period of time, but continue to earn money.<br />
<br />
* '''Checking - and corrective actions are missing or only partially carried out'''<br />
<br />
** Trainees forget about the necessary checking- and corrective actions of individual phases during the simulation run. This leads to bad results.<br />
<br />
<br />
<br />
====Support Tools====<br />
<br />
New components were integrated in the AMEISE environment, to reduce this errors and support the trainees. Two options of '''Support Tools''' are available:<br />
<br />
Advisor<br />
Friendly Peer<br />
<br />
The instructor decides, if these support tools are available during a simulation run.<br />
<br />
<br />
<br />
====Overview====<br />
The advisor is a '''passive''' support tool and has to be questioned by the trainee. Therefore the advisor assumes the role of the instructor and answers relevant questions during a simulation run. The friendly - peer is an '''active''' support tool and indicates the trainee if a difficult situation appears. The friendly - peer assumes the role of an experienced colleague who gives advises to trainees.<br />
<br />
<br />
{{NavigatorBar|Learning Objectives|The Advisor}}<br />
[[de:Projektunterstützung in AMEISE]]<br />
[[en:Project Support in AMEISE]]<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Project_Support_in_AMEISE&diff=1803Project Support in AMEISE2013-05-11T08:35:22Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Learning Objectives|The Advisor}}<br />
<br />
<br />
The analysis of the previous simulation runs shows, that trainees who have not performed project planning achieved worse results than trainees who planned the project before a simulation run.<br />
<br />
<br />
<br />
====Project Planning====<br />
{{Box1|Therefore the project should be planned before executing a simulation run. The project design is intended to include the sequence of actions to be undertaken in the project and include an appropriate workforce planning.}}<br />
<br />
However, a careful planning of the project is only possible after starting a simulation run, because from this point on trainees get relevant information (costs, employee skills) about the simulation run. The AMEISE - System provides also support information, that is available to trainees only after activities, which means that the student has to finish the work before getting a feedback from the support tools.<br />
<br />
Thereby, errors cannot be avoided, but trainees are alerted to mistakes and can learn from it. The support of trainees is not to prescribe a best practice, but it will be given guidance as to what activities would lead to an improvement of the current situation.<br />
<br />
<br />
<br />
====Common Mistakes====<br />
The analysis of SESAM/AMEISE - simulation runs has shown that the following mistakes are committed very often:<br />
<br />
* '''Objectives are not fulfilled'''<br />
** The students have a big problem to fulfill all objectives of a simulation run.<br />
<br />
* '''Employee Utilization'''<br />
** Occupying their employees constantly, is a great problem for most students. Therefore, employees are often without an activity over a long period of time, but continue to earn money.<br />
<br />
* '''Checking - and corrective actions are missing or only partially carried out'''<br />
<br />
** Trainees forget about the necessary checking- and corrective actions of individual phases during the simulation run. This leads to bad results.<br />
<br />
<br />
<br />
====Support Tools====<br />
<br />
New components were integrated in the AMEISE environment, to reduce this errors and support the trainees. Two options of '''Support Tools''' are available:<br />
<br />
Advisor<br />
Friendly Peer<br />
<br />
The instructor decides, if these support tools are available during a simulation run.<br />
<br />
<br />
<br />
====Overview====<br />
The advisor is a '''passive''' support tool and has to be questioned by the trainee. Therefore the advisor assumes the role of the instructor and answers relevant questions during a simulation run. The friendly - peer is an '''active''' support tool and indicates the trainee if a difficult situation appears. The friendly - peer assumes the role of an experienced colleague who gives advises to trainees.<br />
<br />
<br />
{{NavigatorBar|Learning Objectives|The Advisor}}<br />
[[de:Projektunterstützung in AMEISE]]<br />
[[en:Project Support in AMEISE]]<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Project_Support_in_AMEISE&diff=1801Project Support in AMEISE2013-05-11T08:30:56Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Learning Objectives|The Advisor}}<br />
<br />
<br />
The analysis of the previous simulation runs shows, that trainees who have not performed project planning achieved worse results than trainees who planned the project before a simulation run.<br />
<br />
<br />
<br />
====Project Planning====<br />
{{Box1|Therefore the project should be planned before executing a simulation run. The project design is intended to include the sequence of actions to be undertaken in the project and include an appropriate workforce planning.}}<br />
<br />
However, a careful planning of the project is only possible after starting a simulation run, because from this point on trainees get relevant information (costs, employee skills) about the simulation run. The AMEISE - System provides also support information, that is available to trainees only after activities, which means that the student must have already done the work to get feedback from the support tools.<br />
<br />
Thereby, errors cannot be avoided, but trainees are alerted to mistakes and can learn from it. The support of trainees is not to prescribe a best practice, but it will be given guidance as to what activities would lead to an improvement of the current situation.<br />
<br />
<br />
<br />
====Common Mistakes====<br />
The analysis of SESAM/AMEISE - simulation runs has shown that the following mistakes are committed very often:<br />
<br />
* '''Objectives are not fulfilled'''<br />
** The students have a big problem to fulfill all objectives of a simulation run.<br />
<br />
* '''Employee Utilization'''<br />
** Occupying their employees constantly, is a great problem for most students. Therefore, employees are often without an activity over a long period of time, but continue to earn money.<br />
<br />
* '''Checking - and corrective actions are missing or only partially carried out'''<br />
<br />
** Trainees forget about the necessary checking- and corrective actions of individual phases during the simulation run. This leads to bad results.<br />
<br />
<br />
<br />
====Support Tools====<br />
<br />
New components were integrated in the AMEISE environment, to reduce this errors and support the trainees. Two options of '''Support Tools''' are available:<br />
<br />
Advisor<br />
Friendly Peer<br />
<br />
The instructor decides, if these support tools are available during a simulation run.<br />
<br />
<br />
<br />
====Overview====<br />
The advisor is a '''passive''' support tool and has to be questioned by the trainee. Therefore the advisor assumes the role of the instructor and answers relevant questions during a simulation run. The friendly - peer is an '''active''' support tool and indicates the trainee if a difficult situation appears. The friendly - peer assumes the role of an experienced colleague who gives advices to trainees.<br />
<br />
<br />
{{NavigatorBar|Learning Objectives|The Advisor}}<br />
[[de:Projektunterstützung in AMEISE]]<br />
[[en:Project Support in AMEISE]]<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Project_Support_in_AMEISE&diff=1799Project Support in AMEISE2013-05-11T08:30:15Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Learning Objectives|The Advisor}}<br />
<br />
<br />
The analysis of the previous simulation runs shows, that trainees who have not performed project planning, achieved worse results than trainees who planned the project before a simulation run.<br />
<br />
<br />
<br />
====Project Planning====<br />
{{Box1|Therefore the project should be planned before executing a simulation run. The project design is intended to include the sequence of actions to be undertaken in the project and include an appropriate workforce planning.}}<br />
<br />
However, a careful planning of the project is only possible after starting a simulation run, because from this point on trainees get relevant information (costs, employee skills) about the simulation run. The AMEISE - System provides also support information, that is available to trainees only after activities, which means that the student must have already done the work to get feedback from the support tools.<br />
<br />
Thereby, errors cannot be avoided, but trainees are alerted to mistakes and can learn from it. The support of trainees is not to prescribe a best practice, but it will be given guidance as to what activities would lead to an improvement of the current situation.<br />
<br />
<br />
<br />
====Common Mistakes====<br />
The analysis of SESAM/AMEISE - simulation runs has shown that the following mistakes are committed very often:<br />
<br />
* '''Objectives are not fulfilled'''<br />
** The students have a big problem to fulfill all objectives of a simulation run.<br />
<br />
* '''Employee Utilization'''<br />
** Occupying their employees constantly, is a great problem for most students. Therefore, employees are often without an activity over a long period of time, but continue to earn money.<br />
<br />
* '''Checking - and corrective actions are missing or only partially carried out'''<br />
<br />
** Trainees forget about the necessary checking- and corrective actions of individual phases during the simulation run. This leads to bad results.<br />
<br />
<br />
<br />
====Support Tools====<br />
<br />
New components were integrated in the AMEISE environment, to reduce this errors and support the trainees. Two options of '''Support Tools''' are available:<br />
<br />
Advisor<br />
Friendly Peer<br />
<br />
The instructor decides, if these support tools are available during a simulation run.<br />
<br />
<br />
<br />
====Overview====<br />
The advisor is a '''passive''' support tool and has to be questioned by the trainee. Therefore the advisor assumes the role of the instructor and answers relevant questions during a simulation run. The friendly - peer is an '''active''' support tool and indicates the trainee if a difficult situation appears. The friendly - peer assumes the role of an experienced colleague who gives advices to trainees.<br />
<br />
<br />
{{NavigatorBar|Learning Objectives|The Advisor}}<br />
[[de:Projektunterstützung in AMEISE]]<br />
[[en:Project Support in AMEISE]]<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=The_Advisor&diff=1795The Advisor2013-05-11T08:19:23Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Project Support in AMEISE|The Friendly Peer}}<br />
<br />
<br />
<br />
====Advisor====<br />
<br />
The advisor can be asked by the trainee if he/she is in trouble. <br />
<br />
<br />
====Purpose of the Advisor====<br />
<br />
The task of the advisor is giving the trainee a couple of questions from a predefined catalog. If the trainee chooses one of these questions, the advisor will answer it. The advisor has an own interface in the simulation environment. Advises from the advisor are just snap - shot advises. That means he does not have the possibility to give statements about long time aspects of simulation runs.<br />
<br />
<br />
====Questions====<br />
<br />
The following list includes advises, which are delivered by the advisor:<br />
# '''Previous phases should not be forgotten.'''<br/>Phases always need a previous document as a basis. If this document is missing the phase is doomed to failure.<br />
# '''The previous phase should be finished before starting a new phase.'''<br/>It is important for following phases, that the previous phase and the emerged previous document has been finished by more than 50% to enable an overlapping of the phases. If this is not the case, the initiated phase fails. The limit of 50% depends on the model. (QA - Model).<br />
# ''' The previous phase should be reviewed before starting a new phase.'''<br/>To build on results of phases, it is important to review these phases. After the review, trainees know that the result of this phase still contains errors. These errors need to be corrected, in order to not adopt them into the next phase. <br />
# '''The previous phase should be corrected based on the review, before starting a new phase.'''<br/>After the review, it is important to correct the remaining errors to avoid their adoption in following phases.<br />
# '''After testing a correction should be performed'''<br/>Beside the review, trainees also can make a test to find errors in documents. Those errors also have to be corrected in order to obtain a correct document. <br/><br />
# '''Incomplete documents should be subjected to a further revision.'''<br/> During a simulation run it happens that single phases satisfy to less requirements or include too much errors. If the advisor recognizes a situation like this, he can react and deliver trainees an advice to improve the phase.<br />
<br />
<br />
<br />
==== Please note that ====<br />
{{Box1|The '''Feedback''' of the Advisor can be positive or negative!}}<br />
<br />
The feedback of the advisor depends on the '''current state''' of the phase. If asked that specifications have to revised, it depends on the completeness of the specification - document which feedback trainees get from the advisor. If the specifications are already satisfying, it is communicated to the trainees. If not, trainees get the advice to revise the document. <br />
The advisor '''can not''' give statements to phases, which have not been started! In this case, the trainee gets a message, which refers that there are not enough data available to evaluate. <br />
<br />
<br />
[[de:Der Ratgeber]]<br />
[[en:The Advisor]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--><br />
<br />
{{NavigatorBar|Project Support in AMEISE|The Friendly Peer}}<br />
<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=The_Advisor&diff=1794The Advisor2013-05-11T08:18:27Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Project Support in AMEISE|The Friendly Peer}}<br />
<br />
<br />
<br />
====Advisor====<br />
<br />
The advisor can be asked by the trainee if he/she is in trouble. <br />
<br />
<br />
====Purpose of the Advisor====<br />
<br />
The task of the advisor is giving the trainee a couple of questions from a predefined catalog. If the trainee chooses one of these questions, the advisor will answer it. The advisor has an own interface in the simulation environment. Advises from the advisor are just snap - shot advises. That means he does not have the possibility to give statements about long time aspects of simulation runs.<br />
<br />
<br />
====Questions====<br />
<br />
The following list includes advises, which are delivered by the advisor:<br />
# '''Previous phases should not be forgotten.'''<br/>Phases always need a previous document as a basis, on which they are build on. If this document is missing the phase is doomed to failure.<br />
# '''The previous phase should be finished before starting a new phase.'''<br/>It is important for following phases, that the previous phase and the emerged previous document has been finished by more than 50% to enable an overlapping of the phases. If this is not the case, the initiated phase fails. The limit of 50% depends on the model. (QA - Model).<br />
# ''' The previous phase should be reviewed before starting a new phase.'''<br/>To build on results of phases, it is important to review these phases. After the review, trainees know that the result of this phase still contains errors. These errors need to be corrected, in order to not adopt them into the next phase. <br />
# '''The previous phase should be corrected based on the review, before starting a new phase.'''<br/>After the review, it is important to correct the remaining errors to avoid their adoption in following phases.<br />
# '''After testing a correction should be performed'''<br/>Beside the review, trainees also can make a test to find errors in documents. Those errors also have to be corrected in order to obtain a correct document. <br/><br />
# '''Incomplete documents should be subjected to a further revision.'''<br/> During a simulation run it happens that single phases satisfy to less requirements or include too much errors. If the advisor recognizes a situation like this, he can react and deliver trainees an advice to improve the phase.<br />
<br />
<br />
<br />
==== Please note that ====<br />
{{Box1|The '''Feedback''' of the Advisor can be positive or negative!}}<br />
<br />
The feedback of the advisor depends on the '''current state''' of the phase. If asked that specifications have to revised, it depends on the completeness of the specification - document which feedback trainees get from the advisor. If the specifications are already satisfying, it is communicated to the trainees. If not, trainees get the advice to revise the document. <br />
The advisor '''can not''' give statements to phases, which have not been started! In this case, the trainee gets a message, which refers that there are not enough data available to evaluate. <br />
<br />
<br />
[[de:Der Ratgeber]]<br />
[[en:The Advisor]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--><br />
<br />
{{NavigatorBar|Project Support in AMEISE|The Friendly Peer}}<br />
<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=The_Advisor&diff=1793The Advisor2013-05-11T08:16:12Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Project Support in AMEISE|The Friendly Peer}}<br />
<br />
<br />
<br />
====Advisor====<br />
<br />
The advisor can be asked by the trainee if he/she is in trouble. <br />
<br />
<br />
====Purpose of the Advisor====<br />
<br />
The task of the advisor is giving the trainee a couple of questions from a predefined catalog. If the trainee chooses one of these questions, the advisor will answer it. The advisor has an own interface in the simulation environment. Advises from the advisor are just snap - shot advises. That means he does not have the possibility to give statements about long time aspects of simulation runs.<br />
<br />
<br />
====Questions====<br />
<br />
The following list includes advices, which are delivered by the advisor:<br />
# '''Previous phases should not be forgotten.'''<br/>Phases always need a previous document as a basis, on which they are build on. If this document is missing the phase is doomed to failure.<br />
# '''The previous phase should be finished before starting a new phase.'''<br/>It is important for following phases, that the previous phase and the emerged previous document has been finished by more than 50% to enable an overlapping of the phases. If this is not the case, the initiated phase fails. The limit of 50% depends on the model. (QA - Model).<br />
# ''' The previous phase should be reviewed before starting a new phase.'''<br/>To build on results of phases, it is important to review these phases. After the review, trainees know that the result of this phase still contains errors. These errors need to be corrected, in order to not adopt them into the next phase. <br />
# '''The previous phase should be corrected based on the review, before starting a new phase.'''<br/>After the review, it is important to correct the remaining errors to avoid their adoption in following phases.<br />
# '''After testing a correction should be performed'''<br/>Beside the review, trainees also can make a test to find errors in documents. Those errors also have to be corrected in order to obtain a correct document. <br/><br />
# '''Incomplete documents should be subjected to a further revision.'''<br/> During a simulation run it happens that single phases satisfy to less requirements or include too much errors. If the advisor recognizes a situation like this, he can react and deliver trainees an advice to improve the phase.<br />
<br />
<br />
<br />
==== Please note that ====<br />
{{Box1|The '''Feedback''' of the Advisor can be positive or negative!}}<br />
<br />
The feedback of the advisor depends on the '''current state''' of the phase. If asked that specifications have to revised, it depends on the completeness of the specification - document which feedback trainees get from the advisor. If the specifications are already satisfying, it is communicated to the trainees. If not, trainees get the advice to revise the document. <br />
The advisor '''can not''' give statements to phases, which have not been started! In this case, the trainee gets a message, which refers that there are not enough data available to evaluate. <br />
<br />
<br />
[[de:Der Ratgeber]]<br />
[[en:The Advisor]]<br />
<!--<br />
[[sk:Hlavná stránka]]<br />
[[fr:Accueil]]<br />
--><br />
<br />
{{NavigatorBar|Project Support in AMEISE|The Friendly Peer}}<br />
<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Advices_of_the_Support_Tools&diff=1792Advices of the Support Tools2013-05-11T08:12:06Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|The Friendly Peer|Starting the Simulator}}<br />
<br />
<br />
<br />
The following list includes various advises for the relevant QA - Model which is associated to the support tools. Trainees get these advises directly from the advisor or the friendly - peer, to indicate and avoid difficult situations.<br />
<br />
====Allocation of the identifying Advices on the Support Tools====<br />
<br />
{|<br />
|-<br />
| style="text-align:center;background:#FFFFCA" | '''Advice''' <br />
| style="text-align:center;background:#FFFFCA" colspan="2" | '''Tool(s)'''<br />
|-<br />
| style="width:60%;text-align:center;background:#FFFFCA" | <br />
| style="width:20%;text-align:center;background:#FFFFCA" | '''Friendly - Peer'''<br />
| style="width:20%;text-align:center;background:#FFFFCA" | '''Advisor'''<br />
|-<br />
| style="text-align:left;background:#DDE9FF" | The author should not be used as a consultant.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" |The author should perform the correction of documents by himself.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | Previous phases should not be forgotten.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#FFFFCA" | The previous phase should be finished, before starting the next phase.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#DDE9FF" | The previous phase should be checked, before starting the next phase.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#FFFFCA" | The previous phase should be corrected in reference to the review, before starting the next phase.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#DDE9FF" | A new review can only be proceeded after a successful correction of a proceeded review. <br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | A correction should be made after performing a test.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#DDE9FF" | The customer should participate in specification- and manual reviews.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | The manual should be written in an early phase of the project.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | Do not change employees frequently.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | The activity and utilization of your developers should be observed.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | The employment of staff should be observed in each single phase.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | Employees should not be removed prematurely from a phase.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | Removing employees should be considered accurate.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | Employees should get activities which they are qualified for.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | Incomplete documents should be subjected to a further review.<br />
| style="text-align:center;background:#DDE9FF" | <br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
|}<br />
<br />
<br />
{{NavigatorBar|The Friendly Peer|Starting the Simulator}}<br />
<br />
[[de:Hinweise zu den Unterstützungswerkzeugen]]<br />
[[en:Advices of the Support Tools]]<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Advices_of_the_Support_Tools&diff=1791Advices of the Support Tools2013-05-11T08:10:02Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|The Friendly Peer|Starting the Simulator}}<br />
<br />
<br />
<br />
The following list includes various advises for the relevant QA - Model which is associated to the support tools. Trainees get these advises directly from the advisor or the friendly - peer, to indicate and avoid difficult situations.<br />
<br />
====Allocation of the identifying Advices on the Support Tools====<br />
<br />
{|<br />
|-<br />
| style="text-align:center;background:#FFFFCA" | '''Advice''' <br />
| style="text-align:center;background:#FFFFCA" colspan="2" | '''Tool(s)'''<br />
|-<br />
| style="width:60%;text-align:center;background:#FFFFCA" | <br />
| style="width:20%;text-align:center;background:#FFFFCA" | '''Friendly - Peer'''<br />
| style="width:20%;text-align:center;background:#FFFFCA" | '''Advisor'''<br />
|-<br />
| style="text-align:left;background:#DDE9FF" | The author should not be used as a consultant.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" |The author should perform the correction of documents by himself.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | Previous phases should not be forgotten.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#FFFFCA" | The previous phase should be finished, before starting the next phase.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#DDE9FF" | The previous phase should be checked, before starting the next phase.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#FFFFCA" | The previous phase should be corrected in reference to the review, before starting the next phase.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#DDE9FF" | A new review can only be proceeded after a successful correction of a proceeded review. <br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | A correction should be made after performing a test.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#DDE9FF" | The customer should participate in specification- and manual reviews.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | The manual should be written in an early phase of the project.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | Do not execute personal changes all the time.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | The activity and utilization of your developers should be observed.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | The employment of staff should be observed in each single phase.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | Employees should not be removed prematurely from a phase.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | Removing employees should be considered accurate.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | Employees should get activities which they are qualified for.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | Incomplete documents should be subjected to a further review.<br />
| style="text-align:center;background:#DDE9FF" | <br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
|}<br />
<br />
<br />
{{NavigatorBar|The Friendly Peer|Starting the Simulator}}<br />
<br />
[[de:Hinweise zu den Unterstützungswerkzeugen]]<br />
[[en:Advices of the Support Tools]]<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Advices_of_the_Support_Tools&diff=1790Advices of the Support Tools2013-05-11T08:08:33Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|The Friendly Peer|Starting the Simulator}}<br />
<br />
<br />
<br />
The following list includes various advises for the relevant QA - Model which is associated to the support tools. Trainees get these advises directly from the advisor or the friendly - peer, to indicate and avoid difficult situations.<br />
<br />
====Allocation of the identifying Advices on the Support Tools====<br />
<br />
{|<br />
|-<br />
| style="text-align:center;background:#FFFFCA" | '''Advice''' <br />
| style="text-align:center;background:#FFFFCA" colspan="2" | '''Tool(s)'''<br />
|-<br />
| style="width:60%;text-align:center;background:#FFFFCA" | <br />
| style="width:20%;text-align:center;background:#FFFFCA" | '''Friendly - Peer'''<br />
| style="width:20%;text-align:center;background:#FFFFCA" | '''Advisor'''<br />
|-<br />
| style="text-align:left;background:#DDE9FF" | The author should not be used as a consultant.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" |The author should perform the correction of documents itself.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | Previous phases should not be forgotten.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#FFFFCA" | The previous phase should be finished, before starting the next phase.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#DDE9FF" | The previous phase should be checked, before starting the next phase.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#FFFFCA" | The previous phase should be corrected in reference to the review, before starting the next phase.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#DDE9FF" | A new review can only be proceeded after a successful correction of a proceeded review. <br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | A correction should be made after performing a test.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
|-<br />
| style="text-align:left;background:#DDE9FF" | The customer should participate in specification- and manual reviews.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | The manual should be written in an early phase of the project.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | Do not execute personal changes all the time.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | The activity and utilization of your developers should be observed.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | The employment of staff should be observed in each single phase.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | Employees should not be removed prematurely from a phase.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | Removing employees should be considered accurate.<br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
| style="text-align:center;background:#DDE9FF" | <br />
|-<br />
| style="text-align:left;background:#FFFFCA" | Employees should get activities which they are qualified for.<br />
| style="text-align:center;background:#FFFFCA" | {{cross}}<br />
| style="text-align:center;background:#FFFFCA" | <br />
|-<br />
| style="text-align:left;background:#DDE9FF" | Incomplete documents should be subjected to a further review.<br />
| style="text-align:center;background:#DDE9FF" | <br />
| style="text-align:center;background:#DDE9FF" | {{cross}}<br />
|}<br />
<br />
<br />
{{NavigatorBar|The Friendly Peer|Starting the Simulator}}<br />
<br />
[[de:Hinweise zu den Unterstützungswerkzeugen]]<br />
[[en:Advices of the Support Tools]]<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Commands&diff=1785Commands2013-05-11T07:54:56Z<p>Toffler: </p>
<hr />
<div>{{NavigatorBar|Features of the QA Model/Part 2|Evaluation of Project´s Progresses}}<br />
<br />
<br />
====Simulation Runs====<br />
Simulation runs consist of an arbitrary sequence of commands and proceeds. Commands must be entered in English. The outputs are displayed in English too.<br />
For some commands trainees receive feedback immediately(for example determine spent resources). Other commands require a '''Proceed''' before the model delivers a feedback(this includes all commands of performing a task, for example specify).<br />
<br />
<br />
====Classification of Commands====<br />
The following figure shows the '''Commands''' segmented by activities. The group "Others" includes commands which can be used in each single phase.<br />
<br />
<br />
{| style="width:100%;background:#FFFFCA;padding:0.5em" |<br />
|- <br />
| To get a detailed overview of the commands during a phase, please '''click''' on the relevant activity in the Image - Map!<br />
|}<br />
<br />
<br />
[[Image:Kommandos_en.gif|center|frame|Click on an Activity to get an Overview of the related Commands!!]]<br />
<br />
<br />
====Commands Overview====<br />
Here you can find a list of all commands [[Media:commandlist-qa60-en-v1.3.pdf|>> Commands]].<br />
<br />
<br />
{{NavigatorBar|Features of the QA Model/Part 2|Evaluation of Project´s Progresses}}<br />
<br />
[[de:Die Kommandos]]<br />
[[en:Commands]]<br />
[[Category:Tutorial]]<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Download&diff=1782Download2013-05-10T14:52:12Z<p>Toffler: </p>
<hr />
<div>== Client Download ==<br />
[[Image:Client_anmelden_en.png|250px|thumb|right|Ameise Download - Please pay attention to the License Agreement]]<br />
<br />
The AMEISE Client is Free-Ware and distributed as a Java application (there is also an EXE File for Windows). Therefore, the Client runs on almost every operating system. There are no registry changes or changes to the path information. As a consequence, the client can also be installed in restricted environments.<br />
<br />
=== Requirements ===<br />
''Hardware(min)''<br />
* CPU: Pentium III 1 GHz or more <br />
* RAM: 512 MB<br />
* Free space on HDD: 5 MB<br />
<br />
''Software(min)''<br />
* Java Running Environment 1.5 or above <br />
<br />
=== Download Instructions ===<br />
<br />
# Read the [[License Agreement]]<br />
# Agree to the license conditions<br />
# Download the [http://ameise.aau.at/ameise/en/index.php/ClientDownload Client]<br />
<br />
<br />
<br />
== Server Download ==<br />
<br />
[[Image:AmeiseSystem.gif|400px|thumb|right|Typical AMEISE Server Architecture]]<br />
<br />
<br />
The AMEISE Server consists of '''three parts''':the AMEISE database running '''MySQL 5.1''' (innodb Type),<br />
the '''Load Balancing Manager''' (LBMMgr) and one or several '''Simulation cores''' (Wrapper).<br />
For a standalone installation all that has to be done is to start the parts from the Java archive<br />
files(which are tested and running under Windows XP, Linux and Solaris). <br />
<br />
The hardware requirements are basically no problem, but the response times are influenced by the performance<br />
of the SQL database and the network connections between the components. <br />
<br />
For further information please look at the [[FAQ|FAQs]].<br />
You can also find an architecture proposal at the [[AboutTheProject]] page.<br />
<br />
=== Requirements ===<br />
''Hardware(min)''<br />
* CPU: Pentium or AMD with 2.6 GHz or more<br />
* RAM: 2048 MB (1024 possible)<br />
* Free space on HDD: 4 GB<br />
<br />
''Software(min)''<br />
* Java Running Environment 1.4.1 (JDK 1.5 or newer version are accepted.) <br />
<br />
=== Download ===<br />
A registration is required to use the AMEISE server environment. <br />
After registration you will receive a trial - license for the server. <br />
After successful validation you will get an unrestricted license from the AMEISE team.<br />
<br />
<br />
* Please send an email with your contact details to the AMEISE team<br />
*With your Username/PWD you are able to download the Server-SW and the DB-scripts on[http://natuna-isys.uni-klu.ac.at/Entwicklung/ReleaseV42b]. <br />
<br />
<!--<br />
# Create an account ([[Spezial:Registration|Registration]])<br />
# Registration ([[Spezial:Anmelden|Anmelden]])<br />
# Die Seite [[Spezial:MeinKonto|MeinKonto]] besuchen und dort den Server herunterladen<br />
--><br />
<br />
Please make sure that you have read and accepted the [[License Agreement]] when you download the software. If you have any questions, please do not hesitate to contact us(AMEISE team).<br />
<br />
[[de:Download]]<br />
[[en:Download]] <br />
<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Download&diff=1781Download2013-05-10T14:51:33Z<p>Toffler: </p>
<hr />
<div>== Client Download ==<br />
[[Image:Client_anmelden_en.png|250px|thumb|right|Ameise Download - Please pay attention to the License Agreement]]<br />
<br />
The AMEISE Client is Free-Ware and distributed as a Java application (there is also an EXE File for Windows). Therefore, the Client runs on almost every operating system. There are no registry changes or changes to the path information. As a consequence, the client can also be installed in restricted environments.<br />
<br />
=== Requirements ===<br />
''Hardware(min)''<br />
* CPU: Pentium III 1 GHz or more <br />
* RAM: 512 MB<br />
* Free space on HDD: 5 MB<br />
<br />
''Software(min)''<br />
* Java Running Environment 1.5 or above <br />
<br />
=== Download Instructions ===<br />
<br />
# Read the [[License Agreement]]<br />
# Agree to the license conditions<br />
# Download the [http://ameise.aau.at/ameise/en/index.php/ClientDownload Client]<br />
<br />
<br />
<br />
== Server Download ==<br />
<br />
[[Image:AmeiseSystem.gif|right|thumb|Typical AMEISE Server Architecture]]<br />
<br />
<br />
The AMEISE Server consists of '''three parts''':the AMEISE database running '''MySQL 5.1''' (innodb Type),<br />
the '''Load Balancing Manager''' (LBMMgr) and one or several '''Simulation cores''' (Wrapper).<br />
For a standalone installation all that has to be done is to start the parts from the Java archive<br />
files(which are tested and running under Windows XP, Linux and Solaris). <br />
<br />
The hardware requirements are basically no problem, but the response times are influenced by the performance<br />
of the SQL database and the network connections between the components. <br />
<br />
For further information please look at the [[FAQ|FAQs]].<br />
You can also find an architecture proposal at the [[AboutTheProject]] page.<br />
<br />
=== Requirements ===<br />
''Hardware(min)''<br />
* CPU: Pentium or AMD with 2.6 GHz or more<br />
* RAM: 2048 MB (1024 possible)<br />
* Free space on HDD: 4 GB<br />
<br />
''Software(min)''<br />
* Java Running Environment 1.4.1 (JDK 1.5 or newer version are accepted.) <br />
<br />
=== Download ===<br />
A registration is required to use the AMEISE server environment. <br />
After registration you will receive a trial - license for the server. <br />
After successful validation you will get an unrestricted license from the AMEISE team.<br />
<br />
<br />
* Please send an email with your contact details to the AMEISE team<br />
*With your Username/PWD you are able to download the Server-SW and the DB-scripts on[http://natuna-isys.uni-klu.ac.at/Entwicklung/ReleaseV42b]. <br />
<br />
<!--<br />
# Create an account ([[Spezial:Registration|Registration]])<br />
# Registration ([[Spezial:Anmelden|Anmelden]])<br />
# Die Seite [[Spezial:MeinKonto|MeinKonto]] besuchen und dort den Server herunterladen<br />
--><br />
<br />
Please make sure that you have read and accepted the [[License Agreement]] when you download the software. If you have any questions, please do not hesitate to contact us(AMEISE team).<br />
<br />
[[de:Download]]<br />
[[en:Download]] <br />
<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Tofflerhttps://ameise.aau.at/ameise/en/index.php?title=Download&diff=1780Download2013-05-10T14:50:44Z<p>Toffler: </p>
<hr />
<div>== Client Download ==<br />
[[Image:Client_anmelden_en.png|250px|thumb|right|Ameise Download - Please pay attention to the License Agreement]]<br />
<br />
The AMEISE Client is Free-Ware and distributed as a Java application (there is also an EXE File for Windows). Therefore, the Client runs on almost every operating system. There are no registry changes or changes to the path information. As a consequence, the client can also be installed in restricted environments.<br />
<br />
=== Requirements ===<br />
''Hardware(min)''<br />
* CPU: Pentium III 1 GHz or more <br />
* RAM: 512 MB<br />
* Free space on HDD: 5 MB<br />
<br />
''Software(min)''<br />
* Java Running Environment 1.5 or above <br />
<br />
=== Download Instructions ===<br />
<br />
# Read the [[License Agreement]]<br />
# Agree to the license conditions<br />
# Download the [http://ameise.aau.at/ameise/en/index.php/ClientDownload Client]<br />
<br />
<br />
<br />
== Server Download ==<br />
<br />
[[Image:AmeiseSystem.gif|right|250px|thumb|Typical AMEISE Server Architecture]]<br />
<br />
<br />
The AMEISE Server consists of '''three parts''':the AMEISE database running '''MySQL 5.1''' (innodb Type),<br />
the '''Load Balancing Manager''' (LBMMgr) and one or several '''Simulation cores''' (Wrapper).<br />
For a standalone installation all that has to be done is to start the parts from the Java archive<br />
files(which are tested and running under Windows XP, Linux and Solaris). <br />
<br />
The hardware requirements are basically no problem, but the response times are influenced by the performance<br />
of the SQL database and the network connections between the components. <br />
<br />
For further information please look at the [[FAQ|FAQs]].<br />
You can also find an architecture proposal at the [[AboutTheProject]] page.<br />
<br />
=== Requirements ===<br />
''Hardware(min)''<br />
* CPU: Pentium or AMD with 2.6 GHz or more<br />
* RAM: 2048 MB (1024 possible)<br />
* Free space on HDD: 4 GB<br />
<br />
''Software(min)''<br />
* Java Running Environment 1.4.1 (JDK 1.5 or newer version are accepted.) <br />
<br />
=== Download ===<br />
A registration is required to use the AMEISE server environment. <br />
After registration you will receive a trial - license for the server. <br />
After successful validation you will get an unrestricted license from the AMEISE team.<br />
<br />
<br />
* Please send an email with your contact details to the AMEISE team<br />
*With your Username/PWD you are able to download the Server-SW and the DB-scripts on[http://natuna-isys.uni-klu.ac.at/Entwicklung/ReleaseV42b]. <br />
<br />
<!--<br />
# Create an account ([[Spezial:Registration|Registration]])<br />
# Registration ([[Spezial:Anmelden|Anmelden]])<br />
# Die Seite [[Spezial:MeinKonto|MeinKonto]] besuchen und dort den Server herunterladen<br />
--><br />
<br />
Please make sure that you have read and accepted the [[License Agreement]] when you download the software. If you have any questions, please do not hesitate to contact us(AMEISE team).<br />
<br />
[[de:Download]]<br />
[[en:Download]] <br />
<br />
__NOTOC__<br />
__NOEDITSECTION__</div>Toffler