Beruflich Dokumente
Kultur Dokumente
User customer can know the time table of destination and can
make the own choice to booking seat,time and destination.
Customer are always notified of changes timetable of journey.
Goals
2.1 Create a first-cut use case diagram for the two key actors in
the system
User
Print ticket
Booking ticket
Registration
Admin
Check new update of
timetable schedule
Want to make sure that the system will always up with new update
timetable and update company information.
User
Another alternate that can be add , customer can book the ticket
before the day of the journey.
4.0
ADD SERVICE
**Please input a service that you want in the box provided and
click OK
OK
4.2
CANCEL
METROBUS
BOOKING YOUR TICKET HERE
NAME
NO PHONE
TIME
DESTINATION :
RESET
Interface
Common function
User
Admin
+view timetable
destination
Request
+booking
tiket,seat,destination
+add service
<output>
Resit
+time
+destination
+date
+bus plat number
+seat number
Web site
User
Customer
registration
Submit request
Process information
View timetable
Booking ticket
authorize
OK
Print resit/info
Admin
7.1 Draw the overall class diagram for the Metrobus Information
System.
Route
Stop
Id
integer(10)
Fare
Id
integer(10)
Name
varchar(25)
Schedule
Routeid
varchar(25)
Id
integer(10)
Departure
date
Route_stop
Routeid
varchar(25)
Stopid
integer(10)
Bus
Scheduleid
integer(10)
Vehicle
integer(10)
Fleet_id
Firewall
Moderm
intern
et
DatabaseFirewall
Database
Databa
se
Server
Firewall
Moder
Server
Printer
Compute
r
Printer
Computer
User
Web Site
Admin
Portal Web
Submit
Customer Registration
Booking
View timetable
Process Information
9.1 Identify an area of the system where low coupling and high
cohesion
can
be
achieved
through
good
object-oriented