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. The LaTeX sources of this manual can be found in the svnroot respository of this module, see below.

Connecting the hardware

To be able to use the hardware elevator /usb combination we provide a set of libraries. They are described in the module manual and come with javadoc documentation.

See the netbeans documentation and the module manual on how to create libraries in netbeans and install binary, javadoc and sources.

We will be using the IOWarrior chip to connect the hardware through USB. If you want to experiment with this library, you can find it here including its java doc documentation. I have used and tested it with Linux.

Installation under Linux

Installing the kit for Linux boils down to installing both native library libiowkit.so and codemercs.jar. On my machine this results in the following locations:

1. Directory /usr/lib for libiowkit.so
2. Directory /usr/lib/jvm/java-6-sun/jre/lib/ext for the utility jar codemercs.jar

All this has been arranged in the repackaged iowSDK.zip. Unpack it in some convenient place like ~/Desktop or /tmp, enter the newly created iowSDK directory and sudo ./buildall.sh. You might need to do a modprobe iowarrior to load the iowarrior kernel module that comes with modern Linuxen. There after you can remove this iowSDK directory.

Installation under windows

The following has been tested under Windows XP, Vista and Windows 7 (excerpt from the readme file in the iowarrior kit)

• Copy ...\Windows\library_1_5\iowkit.dll to system DLLs directory (winnt\system32 directory in Windows 2000, windows\system32 in Windows >= XP.
  For a 64 bit windows, select the dll from the appropriate directory SDK\Windows\iowkit 64Bit\
• Include the ..../Java/jar/codemercs.jar from the iorwarrior SDK in your project or in your java classpath.

Sample application to test your connections

Once you have installed the OS specific part (the libiowkit.so or iowkit.dll) You should then be able to run the samples.jar test program. It should blink the led on the interface printed circuit board.

I also made a warriortester application that can be used to read the inputs and write the outputs of the hardware elevator. It should run if you have installed the os part (dll and lib on windows and .so and .a files on linux). Here is a webstart version.

You can also fetch the zip file which comes with a set of property files, one for the laundry application and one for the elevator application.
Example: starting the application with ./wt.sh sets the inputmask and the pin descriptions according the hardware for the 2011 elevator, with which you can test the driver and java lib.

There is a sample on how to use the sevenlohwio library under the bitfactoryexample in the root repository.

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 as well as the Office 2007 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/2011/prj32m1/g<grpnum>
as in https://www.fontysvenlo.org/svn/2011/prj32m1/g5.
All groups have a repository. The project itself also has a shared repository, https://www.fontysvenlo.org/svn/2011/prj32m1/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/2011/prj32m1/g1
• Group 2at https://www.fontysvenlo.org/svn/2011/prj32m1/g2
• Group 3at https://www.fontysvenlo.org/svn/2011/prj32m1/g3
• Group 4at https://www.fontysvenlo.org/svn/2011/prj32m1/g4
• Group 5at https://www.fontysvenlo.org/svn/2011/prj32m1/g5
• Group 6at https://www.fontysvenlo.org/svn/2011/prj32m1/g6
• Scratchpad group Atticat https://www.fontysvenlo.org/svn/2011/prj32m1/Attic
• svnroot

The svnroot repository lives at https://www.fontysvenlo.org/svn/2011/prj32m1/svnroot, and contains the project documentation (including the L^AT_eX sources of the module manual) and the libraries (sevenlo*) to use under trunk and/or tags and branches. 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. Define libraries as above with the propesed naming conventions, so you may share names instead of installation locations over your project team members.

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, test installationand user manuel to be handed in on paper too, properly bound at the copy shop. The document should also contain a reference to the repository.
   See the module_manual for what the document should contain. 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. You may hand in three distinct models.
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>. For each week, except the first, there will be a hand in of a runnable jar file.

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 a different form. The report must be in PDF, printer ready, the software product in a java webstart package and the presentation should be given live of course. You must also hand in one properly bound paper copy of the report at my desk. Any files used during the presentations (including the presentation file) should be in the repository too.

Note that the language of all products and presentations is to be (British) English.

Deadline for the delivery of your report is: Friday December 23^rd 2011 12:00 using peerweb and post box. The presentations will taken place on Thursday Januari 12^th 2012 from 9:35 till 11:30. Room 1.01