Use Case Diagrams are completed and here they are below:
The use case diagram for the Customer will be:
and for the Ticket Manager, Bus Company and ETicket.com will be:
Case Study
ETickets.com is an online company providing a ticketing platform to sell bus tickets to intercity
travellers. This truly digital company is partnered with bus service providers and aims to offer the
most advanced multi-channel ticket sales and distribution network.
ETickets.com enters into contracts with bus operators to offer travel tickets for sale online. After a
contract is signed, the bus operator can access a special interface to list online tickets for sale.
The ticketing manager for the bus company is responsible for informing ETickets.com about all
online offers that can be made through the website. The manager can delegate the tasks of
updating online ticket inventories to a ticketing officer or receptionist.
ETickets.com normally receives the list of available tickets for sale from the ticketing manager
through a special Internet form. ETickets.com can also receive it through e-mail, fax or in person,
and thereafter an officer in ETickets.com manually enters that information into the system.
ETickets.com prefers online listing through the special Internet form by the bus company
because it saves re-entering data.
Information required includes all of the pertinent information about the ticket, bus type, travel
from (origin), travel to (destination), number of available seats, bus service type, ticket type,
promotional sale code to name a few. A bus company may offer as many tickets for sale as they
want through ETickets.com.
The system maintains an index of all tickets in the system so that customers can use the search
engine to search for tickets. They can search by origin and destination, and travel date. They can
also sort the search results by price, travel date/time and bus operator.
The website allows any customer (registered/unregistered) to search for a bus service. The
system response includes all the bus service providers serving the given route and with vacant
seats for the given date. The customer then selects one of the service providers and journey start
time if there are multiple services available on the same date. After selecting the service, the
customer can select a preferred seat from the vacant seats available at the time of booking.
In order to purchase a ticket, the customer should be registered with ETickets.com. The online
purchasing could be a 4-step process: search for tickets, select tickets, enter passenger details,
and payment. Unregistered customers will be asked to enter title, first name, last name, age,
country, physical address, phone number, e-mail address and password in the third step of the
process. However, customers can also purchase a ticket without registration. In the last step, the
customer needs to enter credit card number, expiry date and CCV for payment.
Customers can purchase multiple tickets for groups and other family members. Tickets could be
of type adult, concession, child (3 - 5 years) and infant (0 - 2 years). Tickets can also be flexible
as well as non-changeable. Flexible tickets are normally more expensive than non-changeable
tickets. Tickets can be booked for one way or return.
The system generates printable bus tickets after successful payment. The system also e-mails
an e-ticket along with ticket number and journey details to the customer. An SMS ticket can also
be sent to the customer’s mobile phone. The system should generate an exception message if
purchasing ticket fails.
The management also wants the new system to use emerging technologies, such as mobile
devices, cloud computing, big data and social networks for various business process
improvements, marketing as well as to provide quality services to the clients of ETickets.com.
1.1. Specify Use Case Descriptions for some (minimum of two) important Use Cases
1.2. Develop the Class Diagram for your system
1.3. Develop an Activity Diagram (AD) for one Use Case in your system
1.4. Develop a sequence diagram (SD) for one Use Case in your system
1.5. Develop a State Machine Diagram (SMD) for a Class in your system