The exam consist in the presentation and discussion of a final project.
The project consist in a web application, which needs to be divided into multiple tiers. The application domain can be anything.
There must be a web tier (implemented using J2EE 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. 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 requested.
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 Javascipt, or not discussed, as Spring) is not requested but it is possible and, in case, will be evaluated.
Useful and sensible contributions to the wiki will be evaluated.
During the exam students are expected to run the application on their machine. The application Server (and the web server) must NOT run within an IDE: they will need to be standalone application(s).
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 technologis not necessarily used in an explicit manner in their code(such as Remote Objects or XML) may be asked.
Students are rquired to send their project in a zip file to afogarol@dit.unitn.it and 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. UML should be used whenever possible.
STUDENTS MUST ENROLL TO THE EXAM THROUGH THE ESSE3 SYSTEM!
EXAM DATES:
JANUARY 13 9:00 AM
FEBRUARY 13 9:00 AM
The project consist in a web application, which needs to be divided into multiple tiers. The application domain can be anything.
There must be a web tier (implemented using J2EE 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. 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 requested.
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 Javascipt, or not discussed, as Spring) is not requested but it is possible and, in case, will be evaluated.
Useful and sensible contributions to the wiki will be evaluated.
During the exam students are expected to run the application on their machine. The application Server (and the web server) must NOT run within an IDE: they will need to be standalone application(s).
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 technologis not necessarily used in an explicit manner in their code(such as Remote Objects or XML) may be asked.
Students are rquired to send their project in a zip file to afogarol@dit.unitn.it and 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. UML should be used whenever possible.
STUDENTS MUST ENROLL TO THE EXAM THROUGH THE ESSE3 SYSTEM!
EXAM DATES:
JANUARY 13 9:00 AM
FEBRUARY 13 9:00 AM
RSS
