information technology

The information technology essay below has been submitted to us by a student in order to help you with your studies.

The IT System For Online Booking Systems Information Technology Essay

The Academy Theatre holds the public performance on every evening of the year plus afternoon matinee performances on Saturdays and Sundays. These performances are plays, ballet, musical performances and comedy shows. The theatre wishes to automate its ticket booking and performance planning into a single computerized system. This will simplify ticket sales and the booking of acts for performances throughout the year.

The theatre requires a new IT system in order to manage this. This system is required to record performance dates and times, record customer details, record ticket sales and print tickets.

The theatre manager plans all performances and books the artists who will be performing. There can be only one performance at any time. The manager needs to record details of each performance on the system including:

The name of the performance (e.g. Comedy Night, Swan Lake, etc)

The dates of the performance (this may be one day or several weeks)

The artists booked for each performance

The ticket price of the performance

Up to four clerical assistants may be on duty at any time. Clerical assistants are responsible for general office duties plus taking advance ticket bookings over the telephone or in person at the theatre’s box office. For telephone bookings the tickets are printed, an address label is printed and the tickets are mailed to the customer. At the box office tickets are printed and handed to the customer in person. The theatre has 50 seats. For ticket sales the system must be able to:

Record customer details (name, address, telephone number)

Record tickets sold (seat number, customer, price, date, time, etc)

Print tickets

Print address labels for telephone bookings

Initially the system will only be operational in the theatre. If the system is successful, future plans include a website that allows registered customers to book and print tickets themselves.

We have to analyse and design a system for a theatre including the printing of tickets of customer who order in advance.

Acknowledgement

Since the project has been created successfully, I have to thank many people. First, I have to thank my parents because they gave a chance to learn the IADCS course. Then my teachers (U Nyi Nyi and U Sann Lwin) and my partners, they taught me and guide me. And also, I want to thank the MCC Resource Centre as I can find the needed information for the assignment. And I would like to thank MCC Co. Ltd and NCC education for giving me a chance to learn the IADCS course.

Task 1

1.1. Use Case Diagrams

Figure 1.1.1.Use case diagram for performance planning system

Figure 1.1.2.Use case diagram for ticket sales system

1.2. Use Case Specifications

Number:

UC001

Req Doc Ref:

1.2

Name:

Book Ticket

Status:

Overview

Actors:

Clerical Assistant, Customer

Pre-requisites:

None

Goal:

To make ticket booking

Use-case Relationships:

Extend:

Include:

Association:

Generalisation:

Clerical Assistant, Customer

Description:

Index

Actor event

1

Customer enquiries about performance

2

Customer request ticket

3

Clerical Assistant checks available ticket

4

Clerical Assistant confirms booking

5

Clerical Assistant record ticket sold

Alternatives:

Index

Actor event

A3

Unavailable seat number

A 3.1

Go to step 1

Figure 1.2.1.Use case description for ticket booking

Number:

UC002

Req Doc Ref:

1.2

Name:

Record Customer Detail

Status:

Overview

Actors:

Clerical Assistant

Pre-requisites:

None

Goal:

To add a new customer record

Use-case Relationships:

Extend:

Include:

Association:

Generalisation:

Clerical Assistant

Description:

Index

Actor event

1

Record customer name

2

Record customer telephone

3

Record customer address

Alternatives:

Index

Actor event

A3

Changing customer address

A 3.1

Update customer address (Go to step 3)

Figure 1.2.2.Use case description for recording customer detail

1.3. Activity Diagrams

Figure 1.3.1.Activity diagram for Performance Planning System

Figure 1.3.2.Activity diagram for Ticket Sold System

Task 2

Figure 2.1.1.Class diagram for Theatre System

Task 3

3.1. Sequence Diagrams

Figure 3.1.1.Sequence diagram for Book Ticket use case

3.2. State Machines

Figure 3.2.1.State machine for Ticket

3.3. Communication Diagrams

Figure 3.3.1.Communication diagram for Book Ticket use case

Task 4

Since information is an essential resource for all business. Any breakdown in the IT function can have huge consequences, such as Loss of income, Loss of customers, Loss of confidentiality, Loss of computer installation and Loss of the whole business. So the data need to be protected since there may be environmental threats and threats posed by people. Threats posed by people by defining the status of the user such as authorised person and unauthorised person.

To reduce the effects of a physical threat, the working practices which are adopted by an organisation which will have a profound effect upon computer system security, should be used. Such practices involve:

Control of physical access to the computer system;

Division of responsibilities;

Control over the development and amendment of software;

Control over access to the information within the computer system;

Control over data held on PCs;

Measures to minimise human errors;

Regular taking of ‘backup’ copies of information and software, and storage of these;

Measures to counter threats introduced by the use of communication lines;

Regular, thorough audit of the system

These practices are best practices and so we should use them in our developing system.

Task 5

We have to print tickets and address labels based upon customer requirements which are not easy to forge or copy. Moreover we should allow customers to select the location of their seats. We also have to consider the costs and benefits for them. There are some of the cases for printing and choosing paper:

Single- or double-sided printing

Serial numbering

Use of lines

Type faces

Type sizes

Colour

Order quantity

Paper size

Paper weight

To produce tickets those are not easy to forge or copy,

Single- or double-sided printing can be used

Serial numbering is not needed since the seat number is unique

So many lines should not be used

Any type face can be used but it should be readable

Small type sizes should be used

The ticket should be colourful

Paper size should be small so that easy to take

Paper weight should not be too heavy since it is just a ticket and not a serious paper

We will allow customers to choose the location of their seats by showing the seat plan on paper. I think it is cost effective.

Figure: Seat Plan

Task 6

6.1. Normalisation

Figure 6.1.1.Form design for Performance Planning System

UNF

1NF, 2NF

3NF

Performance Code (KEY)

Performance Name

Performance Type

Ticket Price

Performance Date (R)

Artists Code (R)

Artists Name (R)

Artists Address (R)

Performance

Performance Code

Performance Name

Performance Type

Ticket Price

Performance_Artists

Performance Code

Artist Code

Artist Name

Artist Address

PerformanceDate

Performance Code

Performance Date

Performance

Performance Code

Performance Name

Performance Type

Ticket Price

Performance_Artists

Performance Code

*Artists Code

Artist

Artist Code

Artist Name

Artist Address

PerformanceDate

Performance Code

Performance Date

Figure 6.1.2.Normalisation for Performance Planning System

Figure 6.1.3.Form design for Ticket Sold System

UNF

1NF, 2NF

3NF

Performance Code (KEY)

Performance Name

Performance Date (R)

Performance Time (R)

Seat Number (R)

Customer Code (R)

Customer Name (R)

Customer Telephone (R)

Customer Address (R)

Performance

Performance Code

Performance Name

Sale

Performance Code

Performance Date

Performance Time

Seat Number

Customer Code

Customer Name

Customer Telephone

Customer Address

Performance

Performance Code

Performance Name

Sale

Performance Code

Performance Date

Seat Number

*Customer Code

Customer

Customer Code

Customer Name

Customer Telephone

Customer Address

Figure 6.1.4.Normalisation for Ticket Sold System

Optimisation

Performance

Performance Code

Performance Name

Performance Type

Ticket Price

Performance_Artists

Performance Code

*Artists Code

Artist

Artist Code

Artist Name

Artist Address

Sale

Performance Code

Performance Date

Performance Time

Seat Number

*Customer Code

Customer

Customer Code

Customer Name

Customer Telephone

Customer Address

Figure 6.1.4.Optimisation for Planning Performance System and Ticket Sold System

6.2. Data Dictionary

6.2.1. Performance Code

Data

Dictionary

NCC

Title

System

Planning Performance

Document

Name

Sheet

1

Type

Element

Name

Performance Code

Alias

Definition

Occurrence

1 value per performance

Picture

Pic 1000

Range 0001-1000

Notes

Author

MTMN

Date

11.9.2010

Figure 6.2.1.Data Element Entry for Performance Code

6.2.2. Performance Name

Data

Dictionary

NCC

Title

System

Planning Performance

Document

Name

Sheet

2

Type

Element

Name

Performance Name

Alias

Definition

Occurrence

1 value per performance

Picture

Notes

Author

MTMN

Date

11.9.2010

Figure 6.2.2.Data Element Entry for Performance Name

6.2.3. Performance Type

Data

Dictionary

NCC

Title

System

Planning Performance

Document

Name

Sheet

3

Type

Element

Name

Performance Type

Alias

Definition

Occurrence

1 value per performance

Picture

Notes

Author

MTMN

Date

11.9.2010

Figure 6.2.3.Data Dictionary for Performance Type

6.2.4. Ticket Price

Data

Dictionary

NCC

Title

System

Planning Performance

Document

Name

Sheet

4

Type

Element

Name

Ticket Price

Alias

Definition

Occurrence

1 value per performance

Picture

Notes

Author

MTMN

Date

11.9.2010

Figure 6.2.4.Data Dictionary for Ticket Price

6.2.5. Performance Date

Data

Dictionary

NCC

Title

System

Planning Performance

Document

Name

Sheet

5

Type

Element

Name

Performance Date

Alias

Definition

Occurrence

More than 1 value per performance

Picture

Notes

Author

MTMN

Date

11.9.2010

Figure 6.2.5.Data Dictionary for Performance Date

6.2.6. Performance Time

Data

Dictionary

NCC

Title

System

Planning Performance

Document

Name

Sheet

6

Type

Element

Name

Performance Time

Alias

Definition

Occurrence

More than 1 value per performance

Picture

Pic Evening

Range Afternoon and Evening

Notes

Author

MTMN

Date

11.9.2010

Figure 6.2.6.Data Dictionary for Performance Time

6.2.7. Seat Number

Data

Dictionary

NCC

Title

System

Ticket Sold System

Document

Name

Sheet

7

Type

Element

Name

Seat Number

Alias

Definition

Occurrence

1 value per record

Picture

Pic 150

Range 1 to 150

Notes

Author

MTMN

Date

11.9.2010

Figure 6.2.7.Data Dictionary for Seat Number

6.2.8. Customer Code

Data

Dictionary

NCC

Title

System

Ticket Sold System

Document

Name

Sheet

8

Type

Element

Name

Customer Code

Alias

Definition

Occurrence

1 value per customer

Picture

Pic 10000

Range 00001-10000

Notes

Author

MTMN

Date

11.9.2010

Figure 6.2.8.Data Dictionary for Customer Code

6.2.9. Customer Name

Data

Dictionary

NCC

Title

System

Ticket Sold System

Document

Name

Sheet

9

Type

Element

Name

Customer Name

Alias

Definition

Occurrence

1 value per customer

Picture

Notes

Author

MTMN

Date

11.9.2010

Figure 6.2.9.Data Dictionary for Customer Name

6.2.10. Customer Telephone

Data

Dictionary

NCC

Title

System

Planning Performance

Document

Name

Sheet

10

Type

Element

Name

Customer Telephone

Alias

Definition

Occurrence

1 value per customer

Picture

Notes

Author

MTMN

Date

11.9.2010

Figure 6.2.10.Data Dictionary for Customer Telephone

6.2.11. Customer Address

Data

Dictionary

NCC

Title

System

Planning Performance

Document

Name

Sheet

11

Type

Element

Name

Customer Address

Alias

Definition

Occurrence

1 value per customer

Picture

Notes

Author

MTMN

Date

11.9.2010

Figure 6.2.11.Data Dictionary for Customer Address

6.2.12. Artist Code

Data

Dictionary

NCC

Title

System

Ticket Sold System

Document

Name

Sheet

12

Type

Element

Name

Artist Code

Alias

Definition

Occurrence

1 value per artist

Picture

Pic 100

Range 001-100

Notes

Author

MTMN

Date

11.9.2010

Figure 6.2.12.Data Dictionary for Artist Code

6.2.13. Artist Name

Data

Dictionary

NCC

Title

System

Ticket Sold System

Document

Name

Sheet

13

Type

Element

Name

Artist Name

Alias

Definition

Occurrence

1 value per artist

Picture

Notes

Author

MTMN

Date

11.9.2010

Figure 6.2.13.Data Dictionary for Artist Name

6.2.14. Artist Address

Data

Dictionary

NCC

Title

System

Planning Performance

Document

Name

Sheet

14

Type

Element

Name

Artist Address

Alias

Definition

Occurrence

1 value per artist

Picture

Notes

Author

MTMN

Date

11.9.2010

Figure 6.2.14.Data Dictionary for Artist Address

6.2.15. Performance

Data

Dictionary

NCC

Title

System

Planning Performance

Document

Name

Sheet

15

Type

Structure

Name

Performance

Alias

Definition

Performance=Performance Code + Performance Name + Performance Date + Performance Time + Ticket Price

Occurrence

Picture

Notes

Flow in: Performance planning

Flow out: Performance cancelling

Author

MTMN

Date

11.9.2010

Figure 6.2.15.Data structure entry for Performance

6.2.16. Customer

Data

Dictionary

NCC

Title

System

Planning Performance

Document

Name

Sheet

16

Type

File

Name

Customer

Alias

Definition

Customer=Customer Code + Customer Name + Customer Telephone + Customer Address

Occurrence

Picture

Notes

Flow in: Customer addition

Flow out: Customer deletion

Author

MTMN

Date

11.9.2010

Figure 6.2.16.Data store entry for Customer

Task 7

The following are some of the best examples of well-defined methods for system development.

SSADM;

Object Orientation;

Rapid Application Development;

SSADM (Structured Systems Analysis and Design)

SSADM uses three viewpoints (Functions, Events and Data) when analysing and developing system. This makes the developer a clear understanding of the business requirements and helps to remove errors. There are four SSADM module descriptions:

RA module : Requirements Analysis concerns with information gathering in order to understand fully the business area which is the subject of the proposed system.

RS module : Requirements Specification concerns with taking the agreed business system option and develop it in order to add precise details of data, functions and events to be present in the future system.

LSS module : Logical System Specification consists of two stages. They are Technical Systems Options (TSO) and Logical Design (LD).

PD module : Physical Design (PD) module specifies the physical data processes, inputs and outputs, using the language and features of the chosen physical environmental and incorporation installation standards.

Object-oriented

Object-oriented modelling uses three view points:

Object model;

Dynamic model;

Functional model;

En example of object-oriented modelling is UML (Unified Modelling Language). UML uses a number of diagrams to describe the system:

Static Structured Diagrams (Class diagrams, Object diagrams)

Use Case Diagrams

Sequence Diagrams

Collaboration Diagrams

State Diagrams

Activity Diagrams

Implementation Diagrams (Component diagrams, Deployment diagrams)

Task 8

Report

In this System Analysis and Design Assignment, we have to use Object Oriented.

In Task 1, firstly, I analysed the system using object-oriented methods and produce a Functional Model. I drew the Use Case Diagrams, Use Case Specifications and Activity Diagrams.

Then I produce a Structural Model. Text 2 involves Class Diagrams and its Attributes and Operations.

In Task 3, I drew Sequence Diagrams, State Machines and Communication Diagrams. I Produced a Behavioural Model by using them.

Text 4 involves Data Protection Laws, regulations and best practice, state how these would apply to the computer system being developed and recommend methods that should be utilised to ensure that data protection best practice is implemented in the new system. I researched the data protection issues that apply to the system. Since there is no such data protection issues in our country, I researched it form other countries.

Text 5 describes in detail how the system will print tickets and address labels based upon customer requirements explaining how to produce tickets that are not easy to forge or copy and allowing customers to select the location of their seats. I also researched the hardware and print media available for printing labels and tickets for the theatre.

In Text 6, I made a set of fully normalised tables showing normalisation process for each system and Data Dictionary entries for all items included in the database design.

In Task 7, I studied the differences between the SAD (System Analysis and Design) and OO (Object Oriented) methodologies and also their advantages and disadvantages.


Request Removal

If you are the original writer of this essay and no longer wish to have the essay published on the UK Essays website then please click on the link below to request removal:

Request the removal of this essay


More from UK Essays