Better Taxi Cab System

Introduction

This project is specifically initialised to develop BETTER Taxi Cab System for each individual branch of BETTER Taxi Cab. Developing the swift and smart work-shift schedule per day for drivers in the branch is the major objective of the project. In addition, the project also covers the details of drivers and vehicles of the organization. The main head office the organization of BETTER Taxi Cab is in Toowoomba, Queensland and the owner of the organization Ms Alice Carter can view all the data of 30 branches around the Australia immediately via internet.

This document specially focuses on the overall processes in the system including required data and information. The types of data are also considered during this document preparation with along with specific necessity. The document reveals the key major events with their types, triggers, sources, primary actors, activities, system outputs, and destinations. The document also reveals how these events are practically used by different objects along with their happening schedule and time duration. However the project doesn’t include any business information regarding customers. The project is developed assuming just two types of taxi cab, either standard sedan or modified in a various ways. However, the modified taxi cab always needs to be check for safety requirement. The project assumes that every work-shift is developed at the morning on the same day before 8 am. The project also needs external Licensing system to check the validity of the driver’s licence.

It is also assumed that the project begins from 1 March, 2008. And within every 15 days, it has targeted to review every step. The project is also assumed to be finished by end of the year.

System Requirements:

Event Table

Event Event Type Trigger Source Primary Actor Activity/Use Case System Response/

Output Destination

Initialization of branch office E New branch office Branch office manager Branch office manager Create branch New branch details Administration

Update branch changed details E Update branch Administration officer Administration officer Update branch Updated branch details Administration

Enter new taxi cab details E New taxi cab Administration officer Administration officer Create taxi cab New taxi cab details Administration

Update taxi cab changed details E Update taxi cab Administration officer Administration officer Update taxi cab Updated taxi cab details Administration

Taxi cab safety check S Modified taxi cab Nil Branch office manager Confirm safety Accept / Reject flag Administration

Enter new driver E New driver Administration officer Administration officer Create driver New driver details Driver

Update driver changed details E Update driver Administration officer Administration officer Update driver Updated driver details Driver

Schedule work shift T Every day Booking clerk Booking clerk Create work-shift Developed shift rosters for drivers Administration & driver

Allocate driver to taxi cab E Scheduled work-shift Booking clerk Booking clerk Allocate driver to taxi Ready for service Administration & driver

Licence clearance verification E New/Update driver External Licensing system External Licensing system Check licence Accept / Reject flag Driver

Time to generate driver work shift report T Each week Nil Time/Clock Produce driver work shift report Work shift report Administration

Package Diagram

Use case diagram

Use Case diagram

Straight forward use case

USE CASE DESCRIPTION

Author/Analyst Niroj Maharjan (Great System Creations) Date 21/04/2008

Use case name Create branch

Brief description This use case describes the processes involved in creating a new branch.

Use case ID 1.1

Actor(s) * Branch office manager

Trigger New branch is initialized

Preconditions * Branch is independent and only responsible toward head office.

System outputs * New branch is created

Typical course of events

Actor action System response

Step 1: This use case is initiated when a new branch is opened. Branch office manager is allowed to access New Branch menu.

Step 3: Branch office manager enters the data like branch office id, address, telephone, branch office manager name, number of staff.

Step 5: This use case concludes when the branch office manager saved the details and the new created branch office displayed on the screen.

Step 2: The new branch screen is displayed, and ready for data entry.

Step 4: The details are saved and new branch office is displayed on the screen.

Exception/Error/

Alternate course of events * Step 3: If any data entered is invalid, then display error message.

Use case attached to an <<extends>> and an External system

USE CASE DESCRIPTION

Author/Analyst