Students MUST enroll via the Esse3 system.


Projects must be dilivered 4 days befor the exam date, After project delivery, students will receive an e-mail with the exact time of the exam (so that they will not have to wait for the other exams to finish). Location of the exam will be the teacher's office, in the old faculty building.

PLEASE READ CAREFULLY THIS SECTION!

The exam consist in the demonstration of understanding and command of the technologies we examined in the course. This will happen through the presentation of a final project and a discussion.

The project consist in a web application, which MUST to be divided into multiple tiers. The application domain can be anything of your choice. The project is INDIVIDUAL: no joint projects.

There must be a web tier (implemented using JEE technology), a business logic tier (implemented using EJB) and a persistency tier (implemented with a database and accessed through a persistency layer, which must be implemented using Hibernate. We expect the BL tier to be composed by both stateless and stateful beans - justification for the choices will be asked. The student will have to solve the problem of how to split the state persistency between the web and the application server, and will have to justify the choices. Sensible use of design patterns is required.

The system should show an as clean as possible separation between content and presentation.

A nice look and an attention to the user friendliness will be poitively evaluated.

The existence of transactions (or their absence) must be justified.

Sensible use of other optional technologies (whether they were discussed in the course, like XSLT, or not discussed, as Spring) is not requested but it is possible and, in case, will be positively evaluated.

During the exam students are expected to run the application on their machine.

The student will be asked to describe and demonstrate their system. They can be asked to explain or modify portions of their code. Questions about other technologies discussed in the course  (such as Remote Objects or XML) will be asked - even if they are not  used in an explicit manner in the project.

Students are rquired to send their project in a zip file to marco.ronchetti@unitn.it at least THREE days before the exam date. The zip file should include the source code, configuration files, and a report describing the project. The report should briefly describe the domain, the allowed operations, the system architecture. the used patterns and UML should be used. Students are highly encouraged to keep a blog where they report the progress of their work, the problems encountered and the solutions found (look at blogspot or wordpress to get one free). The presence of a blog will be positively evaluated.

The starting point in your evaluation will be based on the project. A standard, well done, basic project, without extra technologies will give a starting score of 28/30. Additional technologies will allow you to reach 30/30. Failure to respond correctly to questions, conceptual shortcomings in the implementation, failures in the understanding the used technologies on in the ability of explaining the choices and poor reports will then decrease the score.