Enterprise web programming

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

ENTWA coursework 2015-2016

Introduction

The coursework consists of a software development exercise. You are given a problem to solve that requires the development of a dynamic web application using Java EE technologies.

Students are expected to draw on material taught (and material otherwise learned) during all the units on their course in tackling this problem. This assessment thus integrates many of the elements covered during the course.

Problem

Design and implement a web interface to one of the following problems:

The UK Telemedicine and E-health Information Service (TEIS)

Two web interfaces to the TEIS data already exist. The first one (no longer available) was launched in 2000 and was implemented in PL/SQL (Oracle's database programming language). The second one was launched in 2004 and provides a different look and feel. This second one is implemented in JSP.

Requirements specification

FAQ about the problem.

Rules change suggestions

IFAF is the world governing body for American football. Each year, proposals for rule changes are invited. A new system is required to support the proposal making and voting process.

Requirements specification

FAQ about the problem

Project ideas

The School of Computing's MSc project ideas database is currently implemented in a non-MVC style. It also has limited searching functionality. It does not permit people who submit ideas to be able to edit them or withdraw them.

Thr requirement is to implement better searching and user editing of ideas. Only the owner of an idea (the person who created it) or a designated administrator can edit or withdraw an idea.

FAQ about the problem.

FAQ common to all problems.

In each case, your aim is to design and implement a Java web application that is superior to any existing systems. That superiority may be in terms of one or more of the following:

Deliverables and deadlines

The coursework has 3 intermediate deliverables and 2 final deliverables (on the formal deadline date).

Deadline Date Deliverable(s) Submission arrangements Marks
Week 4 practical Friday 29th January
  • First draft of requirements specification (see example of format)
  • Bring printed copy to practical session
5%
Week 6 practical Friday 12th February
  • First draft of user interaction design (organisation structure diagrams and/or storyboards and/or architecture maps)
  • Bring printed copy to practical session
5%
Week 9 practical Friday 4th March
  • Alpha version of the web application (demonstrating some subset of the functionality)
  • Demonstrate it at practical session
  • Ensure your web application is in the specified format
10%
Week 11

 

Friday 18th March
  • Demonstrable web application
  • Completed documentation
  • Source code listings and Javadocs
  • Submission will be made electronically through GitHub or Moodle.
  • Ensure your web application is in the specified format
40%
  • Report on coursework
  • Submission will be made electronically through Moodle.
40%
Week 12 Tuesday 22nd March Peer review
  • Students will assess each other's work
Students who do not fully participate in the peer review have their coursework mark halved

Reasonable special arrangements will be made for students with valid extenuating circumstances for parts of the coursework. Contact the unit co-ordinator if you think you will not meet a deadline for valid reasons.

Notes on deliverables

 

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.