Group C1 A Project PART 2 3 1 PDF

m
er as
VAAL UNIVERSITY OF TECHNOLOGY
co
eH w
Faculty of Applied and Computer Sciences
o.
rs e
Department of Information and Communication Technology
ou urc
o
ONLINE TICKET SALE

aC s
vi y re
ONLINE MOVIE TICKET SALE- PART 2 & 3

GROUP NUMBER: Group_A
ed d
Student Number Student Name Initials Mark

ar stu
217240461 ND Dlamini
217232175 JP Mabitsela
216143772 TN Malele
218189958 FO Babatunde
is
219016798 MM Nekhubvi
Th
LECTURER’S TITLE & SURNAME: MS. MALENKELO THAPELI

SUBMISSION DATE: 16th October 2020
sh
This study source was downloaded by 100000824247663 from CourseHero.com on 05-07-2021 09:14:10 GMT -05:00
https://www.coursehero.com/file/74525759/Group-C1-A-Project-PART-23-1pdf/
TABLE OF CONTENTS
ERD, DFD(PHYSICAL) AND USE CASE ............................................................................................................. 2
SYSTEM FUNCTIONS...................................................................................................................................... 4
SYSTEM DESIGN APPROACH ......................................................................................................................... 4
DEFINITION: .............................................................................................................................................. 4
TYPES OF SYSTEM DESIGN: ....................................................................................................................... 4
LOGICAL DESIGN: .................................................................................................................................. 5
DBMS ARCHITECTURE ................................................................................................................................... 5
DB DISTRIBUTION SCHEME ........................................................................................................................... 6
DB CAPACITY PLAN........................................................................................................................................ 6
DATA COLLECTION TECHNOLOGIES .............................................................................................................. 6
m
er as
co
eH w
o.
rs e
ou urc
o
aC s
vi y re
ed d
ar stu
is
Th
sh
1|Page
ERD, DFD(PHYSICAL) AND USE CASE
m
er as
co
eH w
o.
Figure 1: ERD DIAGRAM
rs e
ou urc
o
aC s
vi y re
ed d
ar stu
is
Th
sh
Figure 2: DFD DIAGRAM
2|Page
m
er as
co
eH w
o.
rs e
ou urc
o
aC s
vi y re
ed d
ar stu
Figure 3: USE CASE MODEL

is
Th
sh
3|Page
SYSTEM FUNCTIONS
The system’s function is to keep track of our customer’s details, transactions, and services offered. It
also gives reports on the type of transaction made by our customers.
The main function of ZIMA cinema theatre is to eliminate queues at the theatre when customers want
to book their tickets. Our system provides a site where you can purchase for a ticket anywhere, anytime.
Our customers can buy/book a ticket using any device that is compatible for internet use anytime
anywhere. We sell more tickets to customers online.
SYSTEM DESIGN APPROACH

DEFINITION:
System design is the process of defining the architecture, components, modules, interfaces and data for
m
a system to satisfy specified requirements. System design is therefore the process of defining and
er as
developing systems to satisfy specified requirements of the user.
co
eH w
o.
TYPES OF SYSTEM DESIGN:
rs e
There are two types of system design mainly:
ou urc
Physical Design
Logical Design
o
PHYSICAL DESIGN:
aC s
vi y re
The physical design is a graphical representation of a system showing the system’s internal and external
entities, and the flows of data into and out of these entities. The system Internal entities include, for
ed d
example, accounting clerks (persons), departments (places), and the ticket interface, login interface, the
ar stu
booking page and the payment interface while an external entity finance department, booking
department, technical department, ticket person and snack vendor. Actually, the physical design relates
to the actual input and output processes of the system. This is laid down in terms of how data is given as
is
an input into a system, how it is authenticated, how it is processed, and how it is displayed as output.
The physical portion of systems design can generally be broken down into three sub-tasks:
Th
 User Interface Design

 Data Design
sh
 Process Design
User Interface Design – Users will have to add their full details and the system will respond back with
their User ID and password
Data Design – After the user logins in with their User ID and password, they will be taken to the
homepage in order for them to see the movie available and then make their bookings. They will also
4|Page
make payments when taken to the payment interface to make an online purchase via EFT or Internet
banking.
Process Design – In order for the payment to be validated, an OTP (one-time pin) will be sent to the
user.
To use an analogy, a personal computer's physical design involves input through a keyboard,
processing within the CPU, and output via a monitor, printer, etc. It would not concern the actual
layout of the tangible hardware, which for a PC would be a monitor, CPU, motherboard, hard
drive, modems, video/graphics cards, USB slots, etc. It involves a detailed design of a user and a
product database structure processor and a control processor.
LOGICAL DESIGN:
The logical design of a system pertains to an abstract representation of the data flows, inputs and
outputs of the system. This is often conducted via modeling, using an over-abstract (and
m
er as
sometimes graphical) model of the actual system.
Logical design is a graphical representation of a system showing the system’s processes and the
co
eH w
flows of data into and out of the processes. The logical design used to document the information
systems is Entity-Relationship Diagram, Data-Flow Diagram and Use-Case Modeling. In this way, we can
o.
rs e
furnished an abstraction of the total system through the logical design in an orderly explanatory way.
ou urc
DBMS ARCHITECTURE
o
Three-tier layer is a Client-Server architecture in which the user-interface, business rules, data storage
aC s
and data access are developed and maintained as an independent modules or most often on separate
vi y re
platforms.
 The system has three tiers which include:

 Presentation tier- Web browser and images.
ed d
 Middle tier- (PHP) Middleware.

ar stu
 We have considered the Three-tier architecture for “Online Movie Ticket Sale” as follows:
 Management of data is independent from physical storage support.
 Migration to a new graphical environment is faster.
is
 If there is a minor change in the business logic, we do not have to install the entire
Th
system in the individual user’s computers.

 Reusability
Reusability of business logic is greater for the presentation layer. As this component is
sh
developed and tested. We can use it in any other projects and it would be of great help for
future purposes.
 Security
More secured architecture since the customers cannot easily get the access to databases
directly.
5|Page
DB DISTRIBUTION SCHEME
Database distribution : “Online Movie Ticket Sale” system will use horizontal distribution in which each
table would be assigned to different server and location thus this results in different access security
safety. When the data and DBMS software are distributed over several sites, one site may fail whilst the
other site will continue to operate effectively, data in a failed site cannot be accessible and due to this
reliability is improved and availability of data .
DB CAPACITY PLAN
Table Customer Ticket Payment Room Schedule Assistance
Record Size:
Sum of field 250 200 150 150 20 50
size
Total size: 1800 1200 1050 1050 40 200
m
Database The sum of
er as
size: all table size
co
is: 5340
eH w
o.
rs e
ou urc
DATA COLLECTION TECHNOLOGIES
• Mobile data collection is the use of digital devices such as mobile phones, tablets, or laptops for data
o
collection.
aC s
• Programming language such as JavaScript, java, Html, relational database (such as Microsoft SQL,
vi y re
Access)
• The system implemented using a 3-tier approach, with server and JSP thus resulting in web browser as
the front and client.
ed d
• The system uses SSP (java server pages a technology that helps software developers create
ar stu
dynamically generated web pages based on HTML.xml, or other document types) and servlet
technology, with c3po connection that enables connection to the development of MySQL, database, the
front interface design is to use dream wear cs6 to achieve, and the page effect using the JavaScript
is
language. Its library function, query and enchanted user interact with the interface experience.
Th
sh
6|Page
Powered by TCPDF (www.tcpdf.org)

Group C1 A Project PART 2 3 1 PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Group C1 A Project PART 2 3 1 PDF

Uploaded by

Copyright:

Available Formats

m

ONLINE TICKET SALE

ONLINE MOVIE TICKET SALE- PART 2 & 3

Student Number Student Name Initials Mark

LECTURER’S TITLE & SURNAME: MS. MALENKELO THAPELI

Figure 2: DFD DIAGRAM

Figure 3: USE CASE MODEL

SYSTEM DESIGN APPROACH

 User Interface Design

 The system has three tiers which include:

 Middle tier- (PHP) Middleware.

system in the individual user’s computers.

You might also like