aryabhatta heirs 2

7/30/2019 Aryabhatta Heirs 2

1/35

TEAM NAME:

ARYABHATTA HEIRS

TEAM MEMBERS:-

1.BALAKUMARAN D.

2. ARAVIND MAVURI

3. MAHESH BABU VUNNAM

4. SRUJAN KUMAR GUNTUKA

FACULTY GUIDE:

Mr. RAJ KUMAR

Project Name:

RADIO TAXI MANAGEMENT SYSTEM

14-03-2009.


2/35

Index

Team participants

Solution overview

a) Vision statement

b) Scope

c) Objectives

d) Overview of solution

e) Milestones

f) Key participants

g) Constraints

Infrastructure

Hardware interface

Design Part

a) Class diagram

b) Use case Relationship

c) Entity Relationship

d) Database schema

e) Architectural solution

f) Sequential diagram

Flow charts

a) Configuring driver, duty manager, duty assistant

b) Update current locations of a car

c) Allocate vehicle to customer

d) Driver checking his current job details

e) Hiring a vehicle

f) Hire request

g) Complaints

Non-Functional Requirements

a) Performance requirements

b) Safety requirements

c) Security requirements

d) Software requirements

e) Technical challenges


3/35

Team participants

We people are here to design the web based solution for self help groups in Gujarat,

Balakumaran D.

Aravind Mavuri

Mahesh babu vunnam

Srujan kumar guntuka

Stake holders

The following are the key stake holders of this solution:

CustomersBy using this solution customer can easily register for the vehicle at

reasonable rates and at the required time. This solution will save time and

money of customers.

Administrator(Owner of the website)

This service is managed by administrator so he will be the sole head of

the whole service. Running this service will benefit the administrator as he

will receive revenue from AYS. Then he has to look after all the sub-

officials under him.

Developer

These are the people who are responsible for designing and maintaining

the website.

Customers

By using this solution customer can easily register for the vehicle at

reasonable rates and at the required time. This solution will save time and

money of customers.

Duty Managers

They are responsible for updating drivers day details and updating the

current locations of the vehicles. He is the also the one who having direct

contact with the driver. They will be appointed in the three base locationsnamely Malleeswaram road, Jayanagar and Airport road.


4/35

Duty Assistants

They are responsible for viewing the graphical map and allocating the

vehicles to the customer. He is also the one who receives complaints, if

any, from the commuter.

Drivers

They will be getting money from AYS while they are starting their work and

they need to update the current locations often to the duty manager and

they have to settle back the amount at the end of the day.

Solution Overview

VISION STATEMENT

The vision of this service is to provide a better service to the commuter in the range of

convenience, standard rates and driver courtesy. Our website will help the commuters

to get the above benefits. Our main aim is also to reduce disability of servicing and

complaints regarding our service. If exists, we will take appropriate actions towards that.

We service in such a way the customer should feel comfort.

SCOPE

Most of the services are lacking in customer convenience, providing standard ratesand driver courtesy. So our main scope will be towards rectifying the above drawbacks

of the other services. We want to be the resolution of the above bugs.

OBJECTIVES

Having all these problems in mind, our organisation AT YOUR SERVICE (AYS)-

SAFE & SPEED has decided to come forward with these following services:

AT YOUR SERVICE (AYS)-SAFE & SPEED provides a Customer friendly and

effective transportation system. A Customer can hire a vehicle either by a toll free

number of our customer care or through logging into our official website

(www.safe&speed.com).


5/35

The first factor was Convenience where a commuter can call our customer

care or can register through our official website (www.safe&speed.com) and

the service will be provided within 15 minutes of notice.

The second factor was standard rates. Services will be provided at low and

affordable rates in such a way that even a normal man can make use of them

easily.

The third factor was driver courtesy, which will be kept in mind during each

and every service.

His/her request is taken care and immediately a vehicle is allotted to him based on the

following conditions:

If there is an existing un-occupied vehicle close to the requested pick-uplocation, then that vehicle is assigned.

If there is an existing occupied vehicle approaching the requested pick-uplocation and is likely to be free at least 15 minutes earlier than the requestednew hire pick-up time, then this vehicle is assigned.

If there is an un-occupied vehicle available at the base (other than theemergency vehicle), then this is assigned.

The base location will then check with the other base locations to determine iftheir vehicles which satisfy Rule 1 and 2 are available. If so, that vehicle isassigned.

If no vehicles are available for all the above criteria, then the Duty Assistantwill first establish when the first vehicle would become free under all theabove criteria. The customer would then be contacted and an inquiry wouldbe made if the earliest available time were suitable. If the Customer insists onthe requested time, then the emergency vehicle would be sent. Otherwise,the earliest available vehicle would be assigned.

If criteria 5 also could not be satisfied for some reason, the base may requestother bases for their emergency vehicle, which may be assigned purely ontheir discretion and schedules. If this also were not forthcoming, the Customerwould be informed about their inability to service the request, which should bein the rarest of rare cases.


6/35

OVERVIEW OF SOLUTION

This solution will be a WEB based application which will provide GUI for customers,

administrator, duty managers, duty assistants and drivers.

It will provide facilities like online registration for customers and for officials too.Administrator will have to look after every official in order to guide them to provide a

better service to the commuter.

Customer can order for a vehicle by getting logged after registration into our website.

For deploying all these functionalities database is maintained, which contains various

information like details of customers, duty managers, duty assistants, administrator, and

drivers.

MILESTONES

Functional specification complete:13/02/09

Working prototype:15/02/09

Code complete:20/03/09

Testing complete:30/03/09

Acceptance testing complete:05/04/09

Implementation:07/04/09

Documentation:12/04/09

KEY PARTICIPANT

Administrator

Customer

Duty Manager

Duty Assistant

Driver.


7/35

CONSTRAINTS

GUI is only in English.

Britain English will be used in a very simple way so that all thecustomers could able to login in a easier way. But many otherorganizations websites are lacking in this. Each and every customer and official must login before startingtheir desired processes. Usernames could be in a desired manner for everyone. Availabilityshould be checked before registering for the first time. Creating passwords are applicable to AYSs rules and regulations. Passwords are not case-sensitive. Once the order is placed over a vehicle, it cannot be changed orcancelled. He/she should have to pay for the vehicle after registering even

though he/she doesnt travel.

INFRASTRUCTURE:Hardware interface:

SERVER/SOLUTION PLATFORM:

Operating System Windows XP, VISTA

Bandwidth 40mbps to 60mbps

Requisite Applications IIS, MSSQL

CLIENT SIDE:

Operating System Any(preferred OS will be Windows

based)

Browser Internet Explorer 6 or above, Mozilla

FireFox 2.0 or above

RAM 64 MB or above

Processor Pentium 4 or above


8/35

Diagrammatic Representations:

Class diagram

Use case diagram

Entity Relationship

Database schema diagram

Architecture Diagram

Sequential diagram

Flow charts


9/35

Class diagram:

This diagram consists of the following classes: customer, administrator, duty manager,

duty assistant, web portal and driver. All these classes are inter-related to the web

portal. Each and every class has its own attributes and operations. Lets see the

functions carried by those classes.

Customer:As we know that the customer class is about hiring a vehicle,

therefore its attributes and operations will be regarding to hiring. The main

attributes include Name, username, password, age, address, E-mail, ph.no.,

no. of passengers, driver id, complaints, etc.. whereas its operations include

register, login, booking, vehicle status, logout etc.

Administrator: We all know that the function of this class is to administrate the

other classes from its name itself. Its main attributes include username,

password and logged. Its operations include change password, configure dutymanager, configure duty assistant, configure driver, view fuel consumption,

view complaints, etc..

Duty assistant: The function of this class is mainly to allocate vehicles to the

customer by viewing the graphical map. The attributes of this class are

username, password, base locations and logged whereas the operations are


10/35

view graphical map, receive phone calls and updates, receive complaints, notify

when service unavailable, change password, etc

Duty manager:The main function of this class is to configure driver day

details, and vehicle assessment. The main attributes of this class are

username, password, base locations and logged whereas its operations include

configure driver day details, vehicle assessment, change password, logout,

update current locations, configure vehicle details, etc

Driver:The main function of this class is updating the current locations to the

duty manager often and to settle back the money at the end of each day. The

main attributes of this class are username, password and base locations

whereas its operations include view profile details, view current job details, view

petrol used, view km travelled, and view complaints(if any).

Web portal: The most important class in the whole class diagram is the web

portal which acts as a major interface between all the other classes. Its main

function is that it interconnects all the classes. The main operations of this class

are customer registration, customer login, duty assistant login, duty manager

login, driver login and administrator login.


11/35

Use-case diagram:


12/35

Similar to the above class diagram we discussed, the use-case diagram also consists of

5 common classes namely the customer, duty assistant, duty manager, administrator

and driver. Their functions are as follows:

Customer: The main functions of this use-case are registering into

safe&speed website, log for booking, confirm booking, view vehicle status,

and post complaints(if any).

Duty assistant: The main functions of this use-case are to allocate thevehicle to customer, to view the graphical map about the car locations, to

receive the phone call from the commuter, to receive the complaints from the

customer, and to notify when service unavailable.

Administrator: The main functions of this use-case are to configure driver,

duty assistant, duty manager, to view profile complaints, fuel consumption

and unable to service.

Duty manager: The main functions of this use-case are to assign the

vehicle to driver, update the current location of car, and to edit the details of

driver.

Driver: The main functions of this use-case are to update the current

locations of vehicle, to settle the account, to view the profile, to check the

current job details, to view petrol used, to view km travelled, and to view

complaints(if any).


13/35

Entity diagram:

Similar to the above two diagrams we discussed above, this entity diagram also

consists of the same 5 common classes i.e.. customer, administrator, duty assistant,

duty manager, and driver. In addition to this, this diagram also has a class called

vehicle. Their functions are as given below:

Customer: We know already that the main function of a customer is to hire a

vehicle after logging into our website. So obviously the main attributes will be


14/35

Name, username, password, age, address, E-mail, ph.no., no. of passengers,

driver id, complaints, etc.. He, after registering, can able to log in for booking

a vehicle. He can have a contact with the duty assistant through phone, in

case of any urgency.

Duty assistant: This entity is responsible for viewing the graphical map and

allocating vehicles. The main attributes of this entity include username,

password, base locations, view graphical map, receive phone calls and

updates, receive complaints, notify when service unavailable, change

password, etc..

Administrator: This entity, as the name indicates, is used to administrate all

the officials under him in a proper way to provide a better service to the

customer. Its main attributes include username, password, logged, change

password, configure driver, duty assistant, duty manager, to view profilecomplaints, fuel consumption and unable to service. He appoints/deletes all

the officials under him.

Duty manager:This entity will have a direct contact with the driver. The main

functions of this entity are to assign the vehicle to driver, update the current

locations of car, and to edit the details of driver. The main attributes of this

class are username, password, base locations logged, configure driver day

details, vehicle assessment, change password, logout, update current

locations, configure vehicle details, etc

Driver: This entity will always be directed by the duty manager. The main

functions of this entity are to update the current locations of vehicle, to settle

the account, to view the profile, to check the current job details, to view petrol

used, to view km travelled, and to view complaints(if any). The attributes of

this would be name, driver id, kms travelled, extra duty, duty end time, fuel

consumption, etc The driver has to update the current locations often to the

duty manager and to settle back the amount at the end of each day.

Vehicle: This entity will also be directed by the duty manager only. The

attributes of this entity will be car model, car no. etc


15/35

DatabaseSchemadiagram:


16/35

Architecture solution:


17/35

The solution architecture is mainly divided into five parts.

Client side: This part describes the users of this solution.

User interface: For each type of user what are the interfaces are provided is shown in

this section. To perform the various functions appropriate GUI is provided for each typeof user.

User process: This section provides the information about the processes that will take

place when user performs action. For each type of user all the processes are shown in

solution architecture.

Web server: This part provides the information about the server used on which

solution would be run.

Database server: This section provides information about database server used in

solution.

DETAILED SYSTEM DESIGN:

SOLUTION ARCHITECTURE:

USERS: In this section users of this solution will be described in detail. We have

categorized the users of this solution in four main groups:

CUSTOMER: Any person who wants to hire a vehicle comes under this category.

All he/she needs to do for that is to get logged into our website

(www.safe&speed.com) by registering in it in advance. He/she, then, can hire a

vehicle by ordering through his/her login. They are also given the option of calling

to our customer care toll free no. for hiring a vehicle, in case of any urgency.

They could also post complaints on the driver on his rude contact . Each and

every option is explained clearly in their profile.

ADMINISTRATOR: He is whole controller and manager of this service. He has

been provided with rights to manage all officials under him and the vehicles

owned by our service. He has also the privileges to track the orders placed bycustomers. Generation of report based on different categories comes under his

part. Configuring everyone is his main function.

DUTY MANAGER: He is the person who is having direct contact with the driver.

He is responsible for assigning the vehicle to the driver, updating the current


18/35

locations and to edit the details of driver. He is also having a profile for him to get

logged and to do his work.

DUTY ASSISTANT: He is responsible for viewing the graphical map and

allocating the vehicles accordingly. He is also responsible for receiving phone

calls, complaints from the commuter and hence he is having a direct contact with

the customer. He is also owning a profile on his own to do his work. In each and

every base location, there will be a duty assistant.

USER INTERFACES:

This part of the solution architecture deals with the different interfaces

being provided to different users of this solution. User interface here refers to

how these users can interact with system. User interfaces are in the form of

dynamic web pages. User interfaces of this solution have been designed while

keeping in mind the various functionalities to be performed by the users.

Interfaces of different users have been described below.

ADMINISTRATOR:

Configure Driver:

This interface enables the administrator to do operations and

functions related to the configuration of the driver. Here he will be able to

view the complaints given by the customers over a particular driver and he

can able to remove him temporarily or permanently based on the

complaints given.

Configure Duty assistant:


functions related to the configuration of the duty assistant. He can able to

configure the duty assistants in order to provide a better service.

Configure Duty manager:


functions related to the configuration of the duty manager. He can able to

configure the duty manager in order to provide a better service.

View overall report:


functions related to the overall report of the service. He can able to take

appropriate actions based on the finalized report.


19/35

DUTY ASSISTANT:

View graphical map:

Before allocating the vehicles to the customer the duty

assistant will have to view the graphical map based on the locations of

different vehicles.

Allocating vehicles to customers:

After viewing the graphical map, the duty assistant can able

to allocate the vehicle to the customer based on the received orders or

phone calls.

Receive complaints:

The duty assistant can able to receive complaints from the

commuters over the driver and take appropriate actions over him.

Allocate vehicles through phone calls:

The customer through this facility can hire a vehicle through

phone calls. The duty assistant is responsible for attending the phone calls

and allocating vehicles.

DUTY MANAGER:

Update driver day details:

The duty manager can update driver day details regardingthe money given to him, overtime, etc..

Update locations of car:

He has also wants to update the current locations of car in

order to provide a better service to the customer at his desired time.

Update graphical map:

He also wants to update the graphical map to make the

duty assistant to view his graphical map to allocate vehicles.

CUSTOMER:

Registering and checking status:

For hiring a vehicle the customer must have to register

first. Then he can view the vehicle status for ordering for a vehicle.


20/35

Hiring a vehicle and posting complaints (if any):

After registering for a vehicle, he can hire it most

probably within 15 min notice and he can also able to post complaints on a

driver if his behaviour is rude.

USER PROCESSES:

This part of the solution architecture mainly deals with the processes

that will be performed when the users will interact with this portal.

ADMINISTRATOR:

Configure driver:

This module consists of processes like adding, editing and

removing drivers respectively.

Configure duty manager:This module also consists of processes like adding, editing

and removing duty manager.

Configure duty assistant:

This module also consists of processes like adding, editing

and removing duty assistants respectively.

View overall report:

This module consists of processes like view overall profit,

fuel consumption and complaints on driver respectively.

DUTY ASSISTANT:

View graphical map:

This module consists of processes like checking the

graphical map and checking vehicle in the base locations.

Allocate vehicles to customer:

This module enables the duty assistant to allocate vehicles

to the customer either by his registration in his login or through his phone

call.

Receive complaints:

Through this module, the duty assistant can receive

complaints regarding driver by the customer.


21/35

DUTY MANAGER:

Updating:

This module enables the duty manager to update driver day

details, locations of car, and the graphical map.

CUSTOMER:

This module enables the customer to register, hire a vehicle

by checking the vehicle status and to send complaints (if any).


22/35

Sequence diagram:


23/35

Sequence Diagram:

The Actors in the Sequence Diagram are listed below:

Customer

Duty Assistant

Duty Manager

Driver

Administrator

Web portal

The Sequence diagram is explained below:

At first the administrator will login in to the website and appoints all users like (Duty

Assistant, Duty Manager, Driver).Administrator will configure all vehicles.

Every day morning Duty Manager will login and will perform vehicle assignment

transaction to each and every driver. Driver as soon as they are logged in, will check


24/35

their vehicle assignment transaction. Duty Manager will update the drivers current

location details to the database.

Customer will first register their details if they are not registered earlier. In registration,

they have to submit their phone no, e-mail id and their address. His data is stored in

customer data base by duty assistant. And then Customer will login to book theirjourney. If the booking is made by a phone call, then login and booking details are filled

by the Duty Assistant.

When the booking is made, Duty Assistant will check the Drivers current location details

and using the given set of rules a vehicle is allotted to the customer. And the

confirmation of booking is sent to customer along with the vehicle details that is allotted

to him. Hire charges are also mentioned during booking. Complaints about drivers can

be submitted by any customer. After this, Customer will be logged out.

Complaints are passed to Duty Assistant, Duty Manager, Driver, and Administrator. Ifappropriate reason is not given by the driver, necessary actions are taken. If the

complaints about a driver exceed 2 then he is removed from his job.

At the end of the day, Duty Manager will update vehicle return transaction and it is

confirmed with Driver. Everyone except driver will be logged out at last except

Administrator. He is provided services to check the profits and different statistics of all

bases and all cars. After checking everything, Administrator will also log out.


25/35

Flow charts:

Configuring duty managers, drivers, assistants

Name of Use Case:Configure his drivers, duty managers, assistants.Description:The administrator will configure drivers, Duty assistant, Duty managercheck overall profits of the company.

.Preconditions:Administrator is already logged in.

Normal flow of events: Configure his managers with base location Check overall profits Check complaints regarding driver.

Alternate flow of events:NonePost condition:None


26/35

Updating current locations of a car:

Name of Use Case: Updating the current locations of a car.Description: The duty manager will configure driver day details, assess vehiclesand he will update the current locations of the car.

.Preconditions:Duty manager is already logged in.

Normal flow of events: Configure driver day details. Assess the vehicles. Update the current locations of the car.



27/35

Allocate vehicles to customer:

Name of Use Case:Allocate vehicle to customer.Description: The duty assistant will view the graphical map, allot vehicles tocustomers, and receive complaints (if any).

.Preconditions:Duty assistant is already logged in.

Normal flow of events: View the graphical map. Allot vehicles to customers. Receive complaints



28/35

Driver checking his current job details:

Name of Use Case: Driver checking his current job details.Description:The drivers will get the money from the service while starting the work,updates the current locations to the duty manager and they can view complaints onhim, if any, km travelled, fuel consumption, and current job details.

.Preconditions:Driver is already logged in.

Normal flow of events: Getting money from the service in the morning.

Update the current locations. View complaints (if any), fuel consumption, current job details, view

km travelled.Alternate flow of events:NonePost condition:None


29/35

Hiring a vehicle:

Name of Use Case: Hiring a vehicle.Description: The customers can hire a car by registering into our official websiteand he can hire it by viewing the vehicle status.

.Preconditions: Customer should register before logging in.

Normal flow of events: Register for logging in.

View the vehicle status. Hire the vehicle.



30/35

Hire request:


31/35

Name of Use Case: Hiring a vehicle.Description:Based on given conditions, the vehicle is allocated to the customer.Preconditions: Duty assistant is logged in to website and check the graphical mapto allocate the vehicle to the customer.

Normal flow of events:

If there is an existing unoccupied vehicle close to the pickuplocation.

If there is an existing occupied vehicle approaching the requestedpick up location going to be free in 10 minutes.

If there is unoccupied vehicle at the base, then enquire the customerfor the earliest car to be hired.



32/35

Complaint:

Name of Use Case: Complaints on driverDescription:The customer can complain the driver regarding his misbehavior, rashdriving, and any other reason

.Preconditions: if complaints are more then 3 , then the driver is removed from his

job.Normal flow of events:

Complain regarding driver. If explanation is proper from the driver , complain not added Complaints exceeds more than two, driver is removed from his job Hire the vehicle.


33/35


NON FUNCTIONAL REQUIREMENTS

PERFORMANCE REQUIREMENTS

For hiring a vehicle Customer must have to register, so the registration of the

Customer must be confirmed within seconds i.e. there should be no latency by

the side of server.

Queries regarding searching of vehicles will take least amount of time.

For each transaction, the values should be updated frequently in the database so

that database should be consistent.

User should be able to login instantaneously into their accounts; there should not

be much delay.

Efficiency of this service will be better if every modules of this solution

architecture is well synchronized.

SAFETY REQUIREMENTS

The customer should be cautious enough while hiring for the vehicles because

once the hiring is made it cant be modified in any circumstances.

Users of this solution are required to maintain privacy of their credentials in

order to safeguard their interest.

Report should be generated by the administrator depicting the transactionsmade each day in order to monitor the various ongoing activities.

Redundancy should be maintained to recover in case of database failure.

A unique reference number is provided for each order placed. This serves to

safeguard the interests of the customers.


34/35

Every vehicle being hired by any AYSs is verified by the administrator so that

correct information is displayed in the service portal.

SECURITY REQUIREMENTS

Every customer is provided with username and password to access his/her

account in a secure way.

Passwords are stored in an encrypted form to prevent it from any intrusion

activities.

While hiring a vehicle, all the details provided by the customers are kept

confidential.

Multiple logins of a single user is not allowed to provide better security.

Automatic session out is provided, so if any user forgets to logout also, its

account is closed after the predefined time.

SOFTWARE QUALITY ATTRIBUTES

This portal is available for 24x7 to users; it can be accessed any time.

The service will be a better comfort to all.

As this architecture is very much flexible so functionalities can be modified to

the solution.

Interactive user interface with highly normalized database adds to robustness

to the service.

The information about the vehicles and service displayed on this website

have been verified and all the information of the customers are stored in

secure way, the solution architecture of this portal are designed in such a

way such that this portal can serve for a long period of time. Thus all these

features make this portal reliable.

As new functionalities can be added easily to this solution it is scalable.


35/35

Technical challenges

Duty Assistant views the graphical map, to find the current location of the

vehicle.

Showing strategically data in form of graph.

Technical specification

TEST SAMPLE DATA PLAN

To test the solution no third party tool is used, the testing is done

manually.

This portal would be made to run on different versions of windows OS to

check compatibilities with different desktop environment.

The solution would be made to run on various desktop with different

hardware configurations to test its efficiency and compatibility with

different hardware configuration.

GUI of this solution is will be tested in different web browsers.

To verify the proper functioning of this portal, a set of test cases will be

designed, and portal will tested against those test cases to ensure itsfunctioning and performance.

To test the search performance and relevance of this portal search is

made based on different criteria.

Since this portal is designed in modules hence each module can be

tested separately on various grounds.

After the testing of each module these modules are integrated and again

tested for different sample test cases.

Different hacking techniques are adapted to ensure the security of this

portal.

We will shortly come up with the codes

Thanks!!!!!

aryabhatta heirs 2

Documents