Introduction to Systems Analysis: Soundsoft Ticketing System

This document provides a comprehensive solution to the Soundsoft Ticketing System assignment for the Introduction to Systems Analysis and Information Systems module (COBC1149). The assignment requires the design and implementation of a database using Microsoft Access to manage event ticketing. The solution includes the creation of a context diagram, data flow diagrams (DFDs), and entity-relationship diagrams (ERDs) to model the system. It also involves normalization to 3NF, the creation of a data dictionary, and the implementation of tables, data entry forms, and a ticket layout within Access. Furthermore, the assignment requires the development of queries and reports to extract and present data, such as venue listings and booking summaries. Finally, an evaluation section reflects on the design and implementation process, discussing potential improvements and extensions to the database, supported by screenshots and references.

Assignment Submission Form
Hand in with each completed assignment
Student ID:
Programme: FdSc Computing and Information Technology
Module Title: Introduction to Systems Analysis and Information Systems
Module Code: COBC1149 Credit value: 20 Level: 4
Module Leader: Phil Bambridge
Assignment Title: Soundsoft Ticketing System
Student declaration:
I declare that:
1. I have read and understand the plagiarism warning on the assessment brief.
2. The whole of this assignment is my own work and is written in my own words.
3. That all sources and quotations from published or unpublished work are
acknowledged and appropriate reference is made.
Signed: _________________________________ Date: ________________

Assignment Brief
Student ID:
Programme: FdSc Computing and Information Technology
Module Title: Introduction to Systems Analysis & Information Systems
Module Code: COBC1149 Credit value: 20 Level: 4
Module Leader: Phil Bambridge
Assignment Title: Resit Assignment
Assessment Weighting: 100%
Handout Date: 22/07/16
Submission Date: 18/08/16
Submission Details: 16.00 submissions needs to be emailed to
[e-mail]
Return Date (normally within 20 working days) : 01/09/16
Intended Learning Outcomes:
1. Demonstrate awareness of the types of management information and nature
of typical management information systems
3. Understand how to determine requirements
4. To be able to model and specify solutions to these requirements.
5. Implement a relational database in Microsoft Access or SQL from a given
specification.

Assessment Requirements:
Please read this assignment document in conjunction with the Module and Course
Handbook.
To receive credits for this work you must submit the work by the stated deadline
and:
 Produce work that meets the format required by the assessment mode.
 Work that is word-processed, use a font size of 11 or larger and leave a 3
cm margin on the left hand side of each sheet.
 Insert a header or footer on all pages containing your student ID number
and the page number.
 Use the Harvard convention for referencing your work.
 Attach a completed assignment submission form with a signed plagiarism
declaration.
You must observe the assessment requirements. Working within such
specifications is an essential part of academic and professional discipline and you
will lose marks if you do not observe them.
Soundsoft Ticketing System
Scenario
Various concerts and other events have been organised during the summer months at
different venues around the south-west of England. These performances include different
types of event and artist. Typical types of event are concerts, variety shows, comedy shows
etc. For a concert, the artist will be the band name; for a comedy show the
comedian/comedienne; for a variety show the leading name will appear.
You are required to develop a database that can be used to hold details of the various
events being held at different venues. The information held on the database will be used to
create the tickets for the events.
Prior analysis shows that the ticket issued should (at least) show the:
 venue name
 performance date and time
 seat number
 price of ticket
 type of event
 name of the artist performing
Task
Design
Design the system as follows:
 Draw a context diagram and any other dataflow diagrams (DFDs) necessary.
 Identify the data attributes and entities of this system and perform normalisation to
3NF on the system.
 Draw all ERDs necessary as part of this process, according to the college style.

 Write attribute schema (Data Dictionary) for all entities, identifying the primary and
foreign keys for each one.
Implementation
Implement your design as follows:
1. Using Microsoft Access 2013 or newer, create the tables and design the data entry forms
that the system requires.
2. Design a ticket layout and use an appropriate method in Access to extract the necessary
data and print it in the form of a ticket.
3. Create a query that will show all the venues for a particular type of event, e.g. all the
venues where a concert is being held
4. Create a report that lists the number of bookings for each event at each venue.
Evaluation
Reflect upon the success of your design and implementation stages, and note where you feel
there was room for improvement. Use screenshots and references to books and resources
to justify your conclusions.
You may also wish to discuss how you would extend the database beyond the original
specification, to enhance functionality, or to make it suitable for more ticketing/booking
situations.
This portion of the assignment should be around 800 words (+/- 20%)

Additional notes for assignment
You will need to perform some research to find out what information you might
reasonably expect to find on a ticket; your ticket layout should be clearly justified
using your sources of reference. There are a number of possible ways of using
Access to print the ticket itself; you may care to look at the label printing/mail merge
facilities.
Submission
You should submit the following items:
1. Contents page
2. Design Documents
 An introduction to the requirement and your database solution
 Context Diagram
 DFD with all data stores identified
 Entity-Relationship diagrams
 Data Dictionary
3. Implementation
 Table Structure in design view
 Relationships print out
 Query printouts in design view
 Testing showing sample data in forms and reports
 Samples of output from the system (tickets, queries and reports).
4. Evaluation
 A reflective evaluation of your implementation
 A list of information sources consulted.
Submit the printed report as above to the HE Centre.
You should also submit a copy of the implemented database via the TurnItIn Assignment set
up on Moodle. The link can be found in the module’s main folder.
You must write your ID number and sign the plagiarism statement on the front page of this
assignment brief, and hand it in with your submission. Your submission will not be
accepted without it.

Grading Criteria
Band Indicators
0 – 39% Typically a submission that contains only limited analysis of the problem,
incorrect context diagram and dataflow diagrams, incorrect or no ERDs, no
demonstration of implementation in Access, is poorly organised and difficult
to follow.
40 – 59% A submission that is largely complete and correct with the main tables
implemented in MS-Access and a ticket or tickets produced by the system
from the test data. The data used demonstrates good understanding of how
the system works and the requirements. There is an attempt at a
constructive evaluation containing relevant comments and criticisms.
60 – 79% A submission that is complete, with few errors and with the almost all
required functions implemented in MS-Access. There is good evidence of a
working system and the test data shows tickets and reports that are suitable
for their purpose. There is a constructive evaluation identifying any
weaknesses in the design and suggestions for improvements.
80 – 99% A submission that is complete, with no errors and all functions implemented
in MS Access. The system is user-friendly and needs little or no knowledge
of MS Access to exploit its features. There is evidence of thorough testing of
a working system and the sample output shows all relevant information (i.e.
tickets and reports). In addition there is evidence of attempts to extend the
output from the system (perhaps by additional reports) or a deeper analysis
of the problem. The evaluation is thorough and contains proposals for
improving and extending the system, including references to other
documents that could be produced by the system.