Goals

In this module you will learn to design, implement and test a scale model and a GUI simulation of an elevator system using UML, Java and Design Patterns. Module description in English.

Connecting the hardware

Connecting the iowarrior to the elevator simulator is identical to what you did in MOD2 laundry simulator, so look there. To use it with the elevator, use the packaged elevator.properties file.

Time keeping

During the project you must keep a record of the times you estimate and you really use on the project. To be able to determine the realism of your entries, you should also enter these values for your other study related activities.
For this timekeeping you should use the spreadsheet that is available in timesheet_template in Open Office and timesheet_template in Microsoft excel format. Upload the filled out sheet into the repository each time at the end of the week. Deadline is typically at the end of the week (Sunday evening).

Repositories

For each group, a svn repository will be available named after the pattern: https://www.fontysvenlo.org/svn/2009/prj32/g<grpnum>
as in https://www.fontysvenlo.org/svn/2009/prj32/g5.
All groups have a repository. The project itself also has a shared repository, https://www.fontysvenlo.org/svn/2009/prj32/svnroot, in which we share the documentation and the libraries to use. The use of this supplied repository is mandatory.

The authentication is taken from peerweb, meaning you will have to log in with your student number (2xxxxxx) and your peerweb password.

The svnroot repository contains the documentation and the source code version of the utility classes to use with the elevator along with a simple IO warrior test gui to test the configuration for the elevator system. To get you started some widgets are also available.

• Group 1at https://www.fontysvenlo.org/svn/2009/prj32/g1
• Group 2at https://www.fontysvenlo.org/svn/2009/prj32/g2
• Group 3at https://www.fontysvenlo.org/svn/2009/prj32/g4
• Group 4at https://www.fontysvenlo.org/svn/2009/prj32/g4
• Group 5at https://www.fontysvenlo.org/svn/2009/prj32/g5
• svnroot at https://www.fontysvenlo.org/svn/2009/prj32/svnroot, which contains the project documentation and the libraries (javaio2009) to use. Check out this project (javaio2009/trunk) as a seperate project (e.g. javaio2009) and link to it from your elevator project. It is a bad idea to simply copy the library sources into your project, as it will make it difficult to import any improvements in the library.

Products

The products of this assignment are:

1. Report
2. Model
3. Implementation

How to deliver your assignment products:

1. Report: one document describing your analysis, design and its implementation to be handed in on paper, properly bound. The document should also contain a reference to the repository.
   The design diagrams, user interface illustrations etc. are copied into and explained in the report document. In the document code fragments are shown only when relevant. E.g.  when the implementation is discussed in the describing text.
2. Models: One model file in the Visual Paradigm UML tool. Hand in by svn.
   The models should contain analysis, design and implementation as well as a reverse engineered model of the complete implementation. For practical reasons you may use more then one model file for each of the phases analysis, design and implementation.
3. Implementation: All (re)sources needed to build the project should be in the project repository at all times. The sources should be accompanied with an ant build script. Most of the time the Netbeans build.xml script will do.
   For all but the first week you should produce a executable artefact or runnable program.
   By checking out the project and calling ant jar should result in a functional and runnable jar file. Say the produced jar file is called 'dist/SuperElevator.jar'
   I will use the file like this:
   java -cp dist/SuperElevator.jar nl.fontys.sevenlo.prj32.DemoWeekX.
   The prefix nl.fontys.sevenlo.prj32 is mandatory for all your packages. You may (maybe should) have additional packages under this top package name. You may also create several Netbeans projects with additional package and directory structures to reflect your functional decomposition.
   Each week that has an executable will have a Main class named nl.fontys.sevenlo.prj32.DemoWeek<weeknr>.

Each week has one ore more products to be delivered using the repository. The Tutor will tag the repository for all groups on the same time. This TAG is read only. All that is in the tag is considered as handed in. Missing material is considered as too late.

The final products should be handed in in different form. The report must be in PDF, the software product in a java webstart package and the presentation should be given live of course. Any files used during the presentations should be in the repository too.

Deadline for the delivery of your report is: Friday January 15^th 2010 12:00 using peerweb. The presentations will taken place on January 20^th 2010 from 13:00 till 17:00.