-
7/31/2019 Topek ( Subsystem Achitechture )
1/35
SUBSYSTEM
1 ) REGISTER
2) SCHEDULING
3) PURCHASING
4) BOOKING
5) TICKETING
3.2. System Design Description
Bus Ticket Booking System consists of 5 subsystems there are register,
purchasing ticket, booking ticket, scheduling and ticketing .
3.2.1 Register subsystem (1stsubsystem)
Figure 13.0 shows the register subsystem via class diagram.
a. This subsystem consists of 3 classes which are Main/Admin, Display CustomerInformation and Register Form.
-
7/31/2019 Topek ( Subsystem Achitechture )
2/35
Figure 13.0
3.2.2 Purchasing ticket subsystem (2nd subsystem)
Figure 13.1 shows the purchasing subsystemvia class diagram.
a. This subsystem consists of 4 classes which are Main / Admin, Purchas Info, DisplayPurchase Info and Payment.
b. Main class is like controller class, use to associate with other class.c. Display Purchase Info is let the cashier to view all the bus information (price ,
destination, date, time and seat)
d. Purchase Info class is key in the data based on customer purchasing request.e. Payment class is after confirm the customer purchase information then calculate the total
ticket price.
REGISTER SUBSYSTEM
Register Form
Main / Admin
Display Customer Information
-
7/31/2019 Topek ( Subsystem Achitechture )
3/35
-
7/31/2019 Topek ( Subsystem Achitechture )
4/35
Figure 13.2
3.2.4 Scheduling subsystem (4th subsystem)
Figure 13.3 shows the scheduling subsystem via class diagram.
a. This subsystem consists of 2 classes which are Main / Admin and Schedule.b. Main / Admin class is as a controller that uses to receive the event from other
class.
c. Display Schedule class is let the staff (driver) view all the information of theschedule details and can manage their time to work.
BOOKING TICKET SUBSYSTEM
Booking Form Main / Admin Display Info Booked
-
7/31/2019 Topek ( Subsystem Achitechture )
5/35
-
7/31/2019 Topek ( Subsystem Achitechture )
6/35
Figure 13.4
3.2.6 Manage Staff subsystem (6th subsystem)
TICKETING TICKET SUBSYSTEM
Main / Admin Ticket Information
-
7/31/2019 Topek ( Subsystem Achitechture )
7/35
-
7/31/2019 Topek ( Subsystem Achitechture )
8/35
-
7/31/2019 Topek ( Subsystem Achitechture )
9/35
-
7/31/2019 Topek ( Subsystem Achitechture )
10/35
-
7/31/2019 Topek ( Subsystem Achitechture )
11/35
-
7/31/2019 Topek ( Subsystem Achitechture )
12/35
-
7/31/2019 Topek ( Subsystem Achitechture )
13/35
-
7/31/2019 Topek ( Subsystem Achitechture )
14/35
-
7/31/2019 Topek ( Subsystem Achitechture )
15/35
-
7/31/2019 Topek ( Subsystem Achitechture )
16/35
-
7/31/2019 Topek ( Subsystem Achitechture )
17/35
-
7/31/2019 Topek ( Subsystem Achitechture )
18/35
-
7/31/2019 Topek ( Subsystem Achitechture )
19/35
-
7/31/2019 Topek ( Subsystem Achitechture )
20/35
-
7/31/2019 Topek ( Subsystem Achitechture )
21/35
-
7/31/2019 Topek ( Subsystem Achitechture )
22/35
-
7/31/2019 Topek ( Subsystem Achitechture )
23/35
-
7/31/2019 Topek ( Subsystem Achitechture )
24/35
-
7/31/2019 Topek ( Subsystem Achitechture )
25/35
-
7/31/2019 Topek ( Subsystem Achitechture )
26/35
-
7/31/2019 Topek ( Subsystem Achitechture )
27/35
-
7/31/2019 Topek ( Subsystem Achitechture )
28/35
-
7/31/2019 Topek ( Subsystem Achitechture )
29/35
-
7/31/2019 Topek ( Subsystem Achitechture )
30/35
-
7/31/2019 Topek ( Subsystem Achitechture )
31/35
-
7/31/2019 Topek ( Subsystem Achitechture )
32/35
-
7/31/2019 Topek ( Subsystem Achitechture )
33/35
-
7/31/2019 Topek ( Subsystem Achitechture )
34/35
-
7/31/2019 Topek ( Subsystem Achitechture )
35/35
4
