STUDENTS MUST ENROLL TO THE EXAM THROUGH THE ESSE3 SYSTEM!
FUTURE EXAM DATES:
JUNE 8, Wed, 8:30 deadline for project presentation via e-mail: Jun 4
JULY 6, Wed, 8:30 deadline for project presentation via e-mail: Jul 3
SEPTEMBER 14, Wed, 8:30 deadline for project presentation via e-mail: Jan 9
The following dates (February) will be available through ESSE3.
PAST EXAM DATES:
JANUARY 12, 9:00 deadline for project presentation via e-mail: Jan 9
FEBRUARY 9, 9:00 deadline for project presentation via e-mail: Feb 6
The exam consist in the demonstration of 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 needs to be divided into multiple tiers. The application domain can be anything of your choice.
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 evaluated.
During the exam students are expected to run the application on their machine.
The student will be asked to describe and demonstarte their system. They can be asked to explain or modify portions of their code. Questions about other technologies discussed in the course but not necessarily used in an explicit manner in the project (such as Remote Objects or XML) will be asked.
Students are rquired to send their project in a zip file to email@example.com 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. UML should be used whenever possible. Students are highly encouraged to keep a blog where they teport 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.