Software Development

The requirement

Two part ,are required to carry out design and implementation of a prototype user-interface for a PC system for booking seats in the YourMovie cinema. The cinema’s booking office staff will be the users of the system in response to customers requesting purchases over the counter. The cinema does not carry out telephone or online bookings.

The cinema has two showings a day - one at 6 pm and the other at 2 pm. For each day and for each showing different films may be shown. Seat prices are the same for all showings. The user of the system will be able to find out the title of the film for a particular showing on a particular day. If the showing is sold out, this will be indicated to the user and bookings will not be allowed. Otherwise the user can attempt to book a number of seats for the showing and the system will only disallow the booking if it would result in the cinema’s capacity being exceeded.

For the case where the requested number of seats is available, the system then asks for the customer’s credit or debit card number. For the purposes of the prototype the validation is simply a check on the number of characters. The user can cancel the transaction before submitting the customer’s card details and the system returns to its initial state. If the transaction proceeds then (behind the scenes) the number of seats for the showing is suitably reduced within the system and the transaction details are recorded.

The system will also allow the user to view all transaction details for the day along with total takings for the day. Note this may involve advance bookings as well as bookings for the same day.

Part One

• A brief written guide to the user of how to use the prototype

• Screen layout sketch or sketches to accompany the user-guide

• A State Transition Diagram specifying the behavior of the interface. This should NOT refer to detailed software design but rather to logical aspects of the interface as perceived by the user.

Part Two

You can develop the design as developed in part 1 or else you can carry out a totally new design.

Your implementation should make use of a three-layer architecture. You should plan to implement your design in several stages, each of which produces a partially working version of the artifact. A submission that includes the design and implementation of a partially working version will be graded more favorably than one that attempts too much and fails to deliver a version that works at all.

Your submission should include

• A written guide to the user of how to use the system

• Screen shot(s) to accompany the user guide.

• A State Transition Diagram

• A class diagram showing the three layer model

• A complete listing in a readable format, including javadoc-style comments describing the class and the programming interface for each of its methods.

• An account of the design and implementation decisions taken.

A readable listing should be contained in the submission in an appropriate place. It should be generated from NetBeans, strictly left aligned and left justified and with lines broken so that all parts are readable. It should use consistent and appropriate indentation.

Java Software Architecture Software Development

Project ID: #5551039

About the project