SOFTWARE ENGINEERING ASSIGNMENT 1
Table of Contents
Table of Contents
Introduction
Assumptions
AN ER Diagram for the Theatre System
Attribute Analysis
Context DFD
Level One DFD
Data Dictionary Elements
Data Dictionary/ Data Flows
Pseudo Code for the Level One DFD Above
Evaluation
Introduction
The following report clearly outlines and illustrates several design documents and models the theatre booking system in question. The whole design has been based on the structured systems analysis hence the logical outline of the report. The report includes:
- The whole design of the required system as stated by the user.
- Clear and proper full documentation of the designed system.
- A full-blown ER diagram showing all the entities for the designed system.
- Attribute analysis and relational schema for the entities identified
- A context and level one data flow diagram for the system in question
- A data dictionary showing all the data flows and data stores in the data flow diagram.
Assumptions
Below is a list of all the assumptions, which have been considered in the design of the system. The design has been based on the given specification and also the following assumption:
- Authorisation of credit cards is done out side the system hence it has not been included in the design.
- The Ticket Booking System does not have any interfaces with any
accounting/payments system. - Agency sales are automatically confirmed because if their account is
creditworthy it is assumed the agency will pay. - Once an Agency booking has been invoiced the tickets are sent out with
the invoice. - A ticket reservation/booking will only be for one performance. If a
customer wishes to make bookings for several performances then their request
will be handled as a series of transactions, each for one performance. - There is no requirement for the Ticket Booking System to record and
manage performances. The Ticket Booking System will however refer to the
data on scheduled performances. - Bookings cannot be cancelled
- Discounts are calculated at the end of the booking process. Discounts are cumulative. Eg: Agency books a set of 30 OAP tickets
within one hour of the performance = 5% (agency) + 5% (>20) + 25% (OAPs) +
10% (< 1hr) = 45% discount. - Concessions & discounts are maintained by some system other than the
Ticket Booking System. The Ticket Booking System simply uses the
information regarding concessions and discounts. - The same discounts apply to all performances
