Enterprise web programming

Units ENTWA (Level 6) and APSW (Level 7)

Feedback on APSW SWS 1 2015-2016

Task B

Task B was not carried out well by any group - the achievements this year were nowhere near those of best groups in the past on similar exercises. The teamwork shown by both groups this year was significantly sub-optimal. This confirms my initial feedback that I think it was a mistake for groups to split the work by layer - you would have been better allocating certain functionality to implement to each group member.

Generally, each group seemed confident with JPA, EJB and JSF. The biggest technical problems seemed to be around the implementation of the functionality required.

Note that these marks are provisional until approved by a Unit Assessment Board.

Common issues

Group A

Category

Out of

Mark

Comments

Overall functionality

10

5 Only basic functionality implemented.

Input validation

5

4 Allows blank description in Appointment and blank street in Address.

User interface utility

5

3 Pretty basic but works.

Entity and relationship storage

10

8 Pretty good.

Structure of classes within tiers

5

5 Fine.

Quality of code written

15

9 Fairly good. Methods like "PersonService.checkPerson" don't really tell what they are checking for.

TOTAL

50

34 Very good structurally, but weak on the functionality side.

Group B

Category

Out of

Mark

Comments

Overall functionality

10

3 Only very basic functionality implemented.

Input validation

5

2 Regex for passwords is far too complicated and doesn't implement the rule that is stated in the error message. No effective validation on appointments.

User interface utility

5

2 Difficult to use.

Entity and relationship storage

10

6 Does not use Date or Calendar for dates/times.

Structure of classes within tiers

5

4 Generally OK.

Quality of code written

15

6 Uses EE6 @ManagedBean rather than EE7 @Named. Not all code properly formatted. Little effective business logic implemented. AppointmentFacade.create is totally inappropriate and would result in infinite recursion if ever it was called.

TOTAL

50

23 Not great but at least you got something working.
 

Last updated by Prof Jim Briggs of the School of Computing at the University of Portsmouth

 
The enterprise web programming units include some material that was formerly part of the WEB1P and WEB2P units.