Page 1 of 11

E-TICKET.COM (Part-2)

Table of Contents

Entity Relationship diagram

Context diagram

Level – 1: Register customer

Level - 1: Book ticket

Data dictionary

Process specification

Structured English

Process: Validate username

Decision table

Process: Validate password

Decision tree

Process: Validate Payment

Assumptions

References

Entity Relationship diagram

ERD diagram depicts that the proposed system contains following key entities:

  • Bus
  • Type
  • BusType
  • BusService
  • Ticket
  • BusinessOperator
  • Purchase
  • Customer
  • Payment

Following are key relationships among these entities:

  • Bus can be of one type only.
  • Ticket can have only one type of bus.
  • Ticket can have one to many services.
  • A ticket can be purchased once only.
  • A customer can purchase one to many tickets.
  • A customer can purchase one to many payment.

Context diagram (DFD)

The context diagram of DFD depicts that there are two external entities to the proposed system:

  • Customer
  • Business Operator

Level-0 (DFD)

Level-0 of DFD depicts that the proposed system has following processes:

  • Register
  • Search ticket
  • Book ticket
  • Payment
  • Manage ticket

Level – 1: Register customer

Level-1 REGISTER depicts that the proposed system has following sub-processes:

  • Validate username
  • Validate password
  • Validate email
  • Create new customer

Level - 1: Book ticket

Level-1 BOOK TICKET depicts that the proposed system has following sub-processes:

  • Choose ticket
  • Check availability
  • Finalize Ticket

Data dictionary

Type

Column Name / Type / Size / Primary Key / Foreign Key
typeID / NUMBER / 9 / Y / -
typeName / VARCHAR / 15 / - / -

BusService

Column Name / Type / Size / Primary Key / Foreign Key
serviceID / NUMBER / 9 / Y / -
serviceName / VARCHAR / 15 / - / -

BusType

Column Name / Type / Size / Primary Key / Foreign Key
busTypeID / NUMBER / 9 / Y / -
busTypeName / VARCHAR / 15 / - / -
Description / VARCHAR / 255 / - / -

Bus

Column Name / Type / Size / Primary Key / Foreign Key
busNo / NUMBER / 9 / Y / -
busCode / VARCHAR / 10 / - / -
busName / VARCHAR / 255 / - / -

Ticket

Column Name / Type / Size / Primary Key / Foreign Key
ticketID / NUMBER / 9 / Y / -
ticketType / NUMBER / 9 / - / Y
busServiceType / NUMBER / 9 / - / Y
typeID / NUMBER / 9 / - / Y
travelFrom / DATETIME / - / - / -
travelTo / DATETIME / - / - / -
Price / DECIMAL / (4,2) / - / -
businessOperator / NUMBER / 9 / - / Y

BusinessOperator

Column Name / Type / Size / Primary Key / Foreign Key
businessOperatorID / NUMBER / 9 / Y / -
contactName / VARCHAR / 20 / - / -
Email / VARCHAR / 255 / - / -
phoneNo / CHAR / 8 / - / -

Purchase

Column Name / Type / Size / Primary Key / Foreign Key
ticketID / NUMBER / 9 / Y / Y
customerID / NUMBER / 9 / Y / Y
pDate / DATETIME / - / Y / -

Customer

Column Name / Type / Size / Primary Key / Foreign Key
customerID / NUMBER / 9 / Y / Y
firstName / CHAR / 20 / - / -
lastName / CHAR / 20 / - / -
Age / NUMBER / 2 / - / -
Country / CHAR / 50 / - / -
Email / VARCHAR / 255 / - / -
Username / VARCHAR / 30 / - / -
Password / VARCHAR / 30 / - / -
phoneNo / CHAR / 8 / - / -

Process specification

Structured English

Process: Validate username

IF length(username) > 8 AND length (username) < 30

THEN IF startWithCharacter(username) == TRUE

THEN IF hasCapitalLetter(username) == TRUE

THEN create(user)

ELSE DISPLAY ERROR “Username must contain atleast 1 letter in capital”

ELSE ERROR = “Username must start with an alphabet”

ELSE ERROR = “username can be of 8 to 20 characters only.”

Decision table

Process: Validate password

Action
Create / X
Error / X / X / X / X
Conditions
length(password) > 8 / Y / N
length (pasword) < 30 / Y / N
hasSpecialCharacter(username) / Y / N
hasCapitalLetter(username) / Y / N

Decision tree

Process: Validate Payment

Assumptions

Following are key assumptions of the proposed project:

  • A customer can book many zero-to-many tickets.
  • A ticket can be booked to one customer only.
  • A business operator can enter zero-to-many tickets.
  • A customer can make zero-to-many payments.
  • A bus can be of one-to-many types.
  • A ticket can be of one and only one type

References

Dennis, A., Wixom, B. and Tegarden, D. (2002).Systems analysis and design, an object-oriented approach with UML. New York, NY: Wiley.

Dennis, A., Wixom, B., Tegarden, D. and Dennis, A. (2009).Systems analysis design, UML version 2.0. Hoboken, NJ: J. Wiley.

Saif, D 2015, Cover sheet for Group Assignment, viewed 11 Sep. 15, <

Vinh, P 2014, Elabor8, viewed 11 Sep. 15, <

Kaye, S 2015, BetterEvaluation, viewed 11 Sep. 15, <