User Tools

Site Tools


Java Project ID 2006

Recent Changes

27 March 2006 Release 1.8 is available
21 March 2006 Background information about emergent behaviour added (Workshops)
23 February 2006 Slides and documents of Workshop 3 “What is expected?” added (Workshops)


This site contains information for the P-students of the faculty of Industrial Design at the Eindhoven University of Technology who follow the JAVA project. The project consists of 4 assignments; one for each domain. Each assignment has an introduction and workshops in the first week, a small assignment to get acquainted with the simulation environment and base classes (3 weeks) and finally a larger assignment in which the students should try to visualize emergent behaviour (4 weeks). The project is concluded with a presentation by each student group. There are additional workshops and presentations. See the Project Schedule below.

Project Descriptions

Project descriptions are different for the various domains. You can find them here.


  • (20-03-06) The code of version 1.8 has been released. Please download the new version and make sure that you replace the idSimulation folder with the new idSimulation folder. Note that you also have to delete the .class files in your workDir (not your .java files!) and recompile your workDir.


The current version of the simulation environment is available on the code release page. This page also contains an overview of the bugs and their status. Regurlarly check this page so you have the most recent version.

  1. Jaspis is available at
  2. The latest release of idSimulation is available at code release


Support for the content of the assignment and creative design process is provided by the project coaches. Each student group is assigned to a project coach. A deviation from the given assignment should first be deliberated with the project coach.

Support for the simulation environment, the software design process and the coding in JAVA is provided by a group of student assistents of the faculty of Mathematics and Computer Science. They are available during project days at HG 4.60. First read the coding requirements and the Frequently Asked Questions (FAQ) list that are provided on this site before seeing them. Also note that they will not do any coding for your assignment.

Duty Roster student assistants

The duty roster below shows when each student assistent is available.

During their duty, the assistents will be located in HG 4.60. The first half of the morning and the afternoon they will visit one of the domains.

Monday Thursday Friday
David - Health 4.60 - - Health 4.60 -
Eugen Home 4.60 - Home 4.60 - - -
Jordi - - - - Ent 4.60 Work 4.60
Frits Ent 4.60 Work 4.60 Work 4.60 Work 4.60 - -
Berry - - Health 4.60 - Home 4.60
Name E-mail Domain
David Coppens Health
Eugen Schindler Home
Jordi de Vos Entertainment (Work)
Frits Zwegers Work (Entertainment)
Berry Zwerts Health / Home

Project Schedule

About half way of the project, every team (pair of students) will give an interim presentation of their reuslts so far. Furthermore, two general sessions are planned. General session 3 will deal with problems many students have encountered and explain more about the tool and Java if necessary. General session 4 will treat advanced topics on technology that teams may want to use in the remainder of the project. Afterwards, workshops will be held to get experience. The topics of these sessions will be announced later.

Date Time What Where
23 Feb 9.00-11.00 General session 3 AUD collegezaal 1
9/10 Mar Whole day Interim presentation HG 3.02 DE
HG 3.04 DH
HG 3.21 DW
HG 3.18 DT
13 Mar 9:00-11.00 General session 4 AUD collegezaal 1
(possibly parallel sessions)
13.00-15.00 Workshops 3 HG 3.02
HG 3.04
15.00-17.00 Workshops 3 HG 3.02
HG 3.04
6/7 Apr Whole day End presentation HG 3.02 DE
HG 3.04 DH
HG 3.21 DW
HG 3.18 DT

Coding requirements

  1. Before you start coding, try to write down what you will code: what will this class be for, what functions should it have, what should these functions do, …
  2. Your code must be documented. A good standard for in-code documentation is javadoc. It is also good practice to provide clear comments at while-loops, if-statements and complex calculations in the code. Poorly documented code will not be accepted.
  3. Try to choose proper names for variables, functions and classes. Some examples can be found on the naming page.



If you have a problem, follow the steps below:

  1. Look on the FAQ page if your problem is already resolved.
  2. Check if you have the most recent version on the code release page.
  3. Try find a solution on the net. For example on the SUN home page.
  4. Make sure you have elaborate documentation to make clear what your intentions are.
  5. See the student assistents.


This section is for the student assistents only.


id/wiki_2006.txt · Last modified: 2013/05/02 12:49 (external edit)