Enterprise web programming
Modules ENTWA (Level 6) and APSW (Level 7)
|
Enterprise web programmingModules ENTWA (Level 6) and APSW (Level 7) |
|
Note that these marks are provisional until approved by a Unit Assessment Board.
Category |
Out of |
Mark |
Comments |
Overall functionality |
10 |
4 | Not much functionality completed. |
Input validation |
5 |
3 | Facelets contain some validation only for dates. |
User interface utility |
5 |
3 | Looks OK, but navigation not very intutitive. |
Entity and relationship storage |
10 |
4 | Appointment start and end times stored as SQL DATE when should have been TIMESTAMP. The constructors used to create initial data are deprecated (and you got the year wrong!). No entity relationship defined between Appointment and Owner or between SystemUser and Address. Not clear why you choose to annotate methods rather than fields. |
Structure of classes within tiers |
5 |
4 | Clear separation of concerns. |
Quality of code written |
15 |
10 | Generally code well written. |
TOTAL |
50 |
28 |
|
Last updated by Prof Jim Briggs of the School of Computing at the University of Portsmouth |
||
| The enterprise web programming modules include some material that was formerly part of the WEB1P and WEB2P units. |