Joomla Taxi Component

ickybeetsInternet και Εφαρμογές Web

4 Δεκ 2013 (πριν από 3 χρόνια και 11 μήνες)

67 εμφανίσεις

Joomla Taxi Component


Page
1

of
20

B
B
A
A
R
R
Y
Y
O
O
N
N
S
S


S
S
O
O
F
F
T
T
W
W
A
A
R
R
E
E


S
S
O
O
L
L
U
U
T
T
I
I
O
O
N
N
S
S


P
P
V
V
T
T
.
.


L
L
T
T
D
D
.
.












N
N
O
O
V
V
-
-
1
1
7
7
-
-
1
1
0
0



Joomla Taxi Component

(Customer Name: xxxx)


Functional Design

Draft




Version: 1.0.0


Release date: 13
-
Nov
-
2010















by


Baryons Software Solutions Pvt. Ltd.

39
-
40, 2
nd

Floor, 2
nd

Cross, Govind Reddy Layout,

Opp MICO Arekere Layout, Bannergh
atta Road,

Bangalore, India


560076

www.baryonssoftsolutions.com










The contents of this document and its accompanying documents are confidential in
nature and shall not be revealed to any party other than the ones it is intended for.

The purpose of this document is to provide project specific informat
ion to the client.
Higher versions of this document shall be created as and when required.


Joomla Taxi Component


Page
2

of
20

B
B
A
A
R
R
Y
Y
O
O
N
N
S
S


S
S
O
O
F
F
T
T
W
W
A
A
R
R
E
E


S
S
O
O
L
L
U
U
T
T
I
I
O
O
N
N
S
S


P
P
V
V
T
T
.
.


L
L
T
T
D
D
.
.












N
N
O
O
V
V
-
-
1
1
7
7
-
-
1
1
0
0













Document Information

Author

Nandhaguru

Reviewer

Pranav Kumar

Approver


Effective
Date

13/11/10

File

Joomla
-
Taxi
-
F
RD.doc


















Joomla Taxi Component


Page
3

of
20

B
B
A
A
R
R
Y
Y
O
O
N
N
S
S


S
S
O
O
F
F
T
T
W
W
A
A
R
R
E
E


S
S
O
O
L
L
U
U
T
T
I
I
O
O
N
N
S
S


P
P
V
V
T
T
.
.


L
L
T
T
D
D
.
.












N
N
O
O
V
V
-
-
1
1
7
7
-
-
1
1
0
0







Table of Contents
DO
CUMENT INFORMATION

................................
................................
................................
................................
......

2

DOCUMENT INFORMATION

................................
................................
................................
................................
......

2

DOCUMENT INFORMATION

................................
................................
................................
................................
......

2

DOCUMENT INFORMATION

................................
................................
................................
................................
......

2

DOCUMENT INFORMATION

................................
................................
................................
................................
......

2

DOCUMENT INFORMATION

................................
................................
................................
................................
......

2

2. REFERENCES:
-

................................
................................
................................
................................
.........................

4

3. GLOSSARY:
-

................................
................................
................................
................................
..............................

4

4. FUNCTIONAL REQUIR
EMENTS:
-

................................
................................
................................
.........................

4

4.1

A
N
O
VERVIEW
:
-

................................
................................
................................
................................
........................

4

4.2

U
SE
C
ASES
:
-

................................
................................
................................
................................
.............................

4


4.2.1 USE CASE


01

................................
................................
............................

5


4.2.2 USE CASE


02

................................
................................
............................

7


4.2.3 USE CASE


03

................................
................................
............................

9


4.2.4 USE CASE


04

................................
................................
...........................

11


4.2.5 USE CASE


05

................................
................................
...........................

13



















































1. Purpose:
-

This document details out the Functional Requirements and the High Level Design Details
for t
he proposed ValuNet Application. It has the following sections



Use Cases



User Experience
-

Screens & Navigation



Functional Requirement


System & Technical



System Design Decisions



Questions.



2. References:
-



3. Glossary:
-


4. Functional Requirements:
-

4
.1
An Overview:
-

This document is intended to
provide a detailed understanding of the proposed this project
on
-
line architecture, functionality and work flows; and will be used as a guide for the
development of this Taxi component web site.



4.2
Use Cases
:
-

The list of uses cases are as follows:
-


ID

Name

Description

UC
-
01

Reservation Over view & Ride
Details

Provides an Overview of different transactions
involved in taxi reservation and details the Ride
Details transaction.

UC
-
02

Reservatio
n
-

Vehicle Selection

Describes the Vehicle Selection flow

UC
-
03

Reservation
-

Login/Registration

Describes Login / Registration flow at the time of
Reservation



ID

Name

Description

UC
-
04

Reservation
-

Contact Details &
Confirmation

Describes the users reservation Contact Deta
ils and
Confirmation .

UC
-
05

Reservation Details


Describes Reservation details dynamic display flow

UC
-
06

User Menu

Describes various option provided to the users.

UC
-
19

Contact Us


Describes about contact us page

UC
-
20

Miscellaneous

Related to Use
-
Cases

4.2.1
USE CASE


01


Use Case

UC
-
01

Use Case
Name

Reservation Overview and Ride Details

Actors

Guest User,Registered Users, Administrator

Description

Provides an overview of different transactions involved in the taxi reservation flow
and detai
l out the Ride Transaction.

Pre
-
Condition



Basic Flow
(Steps)

Reservation of Taxi involves following transactions


a)Ride Details


Users will provide the ride information under this transaction

b
)Vehicle Selection


Users wil select desired vehicle listed to them under this flow.

c)Login/Registration


Users will prompted for login or registration if they are not
logged in and still they are in booking flow.

d)Contact Details


Users will be re
quested to provide Payment information like Card
& billing information under this transaction flow.

e)Confirmation.
-

This is the final flow of reservation where users will confirm their
order by selecting the payment mode and submitting the order


Let us

see the Ride Details flow in details as follows



Ride Details


Under this transaction users will provide input for the following fields

1)

Pick Up Address *:

User will type in the pickup address. From the third character on type, system
will show an auto
suggest drop down box with address list related to type in
value. So users can select their desired address shown from the suggestion
list.

Note
: Auto suggest List is populated by using Google API


2)

Drop off Address* :

This field is similar to “Pick Up A
ddress” field where else user will type Drop of
Address instead.

Note:
This field also display “Auto Suggest List” using Google API



3)

Additional Stops :

In case user needs to add more stops between their Pick Up and Drop Of
location, they can always add add
itional stops by clicking
on the “Add stop

button “Additional Stops” filed. On every click of the button will open a new
text field with “Remove Stop” link next to it. So users can type in their
additional stops address and if they want to remove the tex
t field, they can
click on “Remove Stop” link.

Note:
This field also display “Auto Suggest List” using Google API

4)

Check For Airport Arrival :

This a check field where user can do selection in case they need taxi service
from airport. Here they need to p
rovide input to following fields

1) Airline Name

2)Flight Number

3)Arrival Time


5)

Date & Time *:

Using these fields users will select the Pickup date and time.

6)

Passenger :

Passengers count will be provided by user selecting count from passenger
drop down
field.

7)

Luggage :

Users will select their Luggage count using the luggage drop down field.

8)

Additional Service :

Users can request for additional services like Baby Seat by selecting the check
box against services shown under this field

9)

Special Instructions
:

This is a text field where users can enter their special instructions to service
providers.

Post
-

Condition

Distance fare will be calculated for the distance covered by the given address.

Business
Validation
Cases/Rules

Pick UP Address Validation

Drop
Off Address Validation

Date & Time Validation

All the mandatory fields are entered

Related Use
Cases


Questions





Ride Details Screen:


4.2.2
USE CASE


02


Use Case

UC
-
02

Use Case
Name

Reservation
-

Vehicle Selection

Actors

Guest User,Registered Us
ers, Administrator

Description

Describes the Vehicle Selection flow


Pre
-
Condition

Ride Details should be filled up by the user.

Basic Flow
(Steps)

After successfully submitting the Ride details,

users will be redirected to Vehicle
Selection Screen.

Vehicle Selection screen will show list of vehicles with following details

1)Vehicle Image

2)Vehicle Description

3)Vehicle Cost in USD

4)Select Button


And also the Reservation Details in right side
block.

Users can select desired vehicle by clicking on the select button against the vehicle


list. Also on mouse hover of select button will show you the complete reservation
details and total cost for that particular vehicle on right side block.


Rate

Calculation Logic


The total cost of vehicle is calculated on basis of

Vehicle cost =


Total Cost of Reservation is calculated on basis of

Total Cost =



Post
-

Condition

Complete Reservation Cost is calculated and shown to user.

Business
Validation
Ca
ses/Rules

1.Vehicle Selection Validation

2.Login Validation.

Related Use
Cases

Reservation Details

Questions




Vehicle Selection Screen




4.2
.3
USE
CA
SE


03


Use Case

UC
-
03

Use Case
Name

Reservation


Login / Registration



Actors

Guest User,Registe
red Users

Description

Describes Login / Registration flow at the time of Reservation

Pre
-
Condition


Basic Flow
(Steps)

If user Click on Select button against a vehicle then system will validate for login, if
users are logged in then they will be redire
cted to Contact Details page else they will
be shown with login form.


If users are registered already then they can login int the login form shown


Login

1.The User can login using the user
-
name and password.

2.If the User name and password informations

entered are correct then he/she will
be logged into the system and will be redirected to Contact details Page.

3.If they enter wrong details, they will be redirect back to vehicle page with error
message.


If users are not registered then they can regist
er by clicking on the New user button
and can continue the reservation flow


Registration

Users should provide valid information for Registration as follows

1)First Name*

2)Middle Name

3)Last Name*


4)E
-
mail ID*

5)Password*

6)Confirm Password *

7)Phone

8)
Street no./name line 1

9)Street no./name line 2

10)City

11)Country

12)State

13)Zip/Postal Code

Fields marked * are mandatory fields


Once they submit the registration form with valid
information, system will register

the user and auto login them and will redirect to Contact Details page.



Post
-

Condition

User are logged and also registered if not an existing user.

Business
Validation
Cases/Rules

Login

1.Valid User
-
name,Password


Registration

1.Valid First Name

2.Valid Last Name

3.Valid Email
-
Id

4.Valid Password




Related Use
Cases


Questions












Login Screen


Registration




4.2.4
USE CASE


04


Use Case

UC
-
04

Use Case
Name

Reservation
-

Contact Details and Confirmation

Actors

Administrator, Registered Users

Description

Displays Reservation Contact Details and Confirmation.

Pre
-
Condition

User should be logged in

Basic Flow
(Steps)

Once user select vehicles then they will be redirected to Contact Details/Confirmation
p
age where they are supposed to provide Payment information (I.e) Card
information and Billing Information.


Payment Information

Card Information

User can add card information by providing the input to the fields listed below

1)Card Info Name*

2)Card Type
*

3)Card Number*



4)Expiration Date*

5)
Name on Card*


Billing Information

2..User can view/edit the personal information entered at the time of registration
which are listed below


1)Company Name

2)Phone No*

3)
Street no./name line 1*

4)Street no./name li
ne 2

5)City*

6)Country*

7)State

8)Zip/Postal Code*


Note:
* Denotes Mandatory fields


Payment Mode

By default users will be show with two modes of Payment so that they can pay to
their reservation accordingly. The two modes of payment are

Would you like to
make payment ?

1.Now(selected by default)

2.
At the time of service







Post
Condition

Users card Information and billing information are updated

Business
Validation
Cases/Rules

1)Valid Card Info Name

2)Valid Card Type

3)Valid Card Number

4)Valid Expir
ation Date

5)Valid
Name on Card

6)Valid Phone No

7)Valid
Street no./name line 1

8)Valid City

6)Valid Country

7)Valid
Zip/Postal Code


Related Use
Cases


Questions

1.Do we need to have the option for changing the email
-
id?

2.Do we need to have my orders l
ink in this page?











Contact Details & Confirmation Screen






4.2.5
USE CASE


05


Use Case

UC
-
05

Use Case
Name

Reservation Details

Actors

Guest Users, Registered Users and Administrator

Description

Describes Reservation details dynamic displa
y flow

Pre
-
None



Condition

Basic Flow
(Steps)

On the right side of the Reservation Transcation flows users will be shown with a
block showing two tabbed views namely Reservation Details and User Menu.

Under the tab reservation following details will be s
hown

a)Route Details

If users are in Ride Details page no details will be shown under this section.But if
users are through with ride details and move to Vehicle selection and contact and
confirmation page following details will be shown

1.Pick Up address

2.Drop Off address

3.Date

4.Time

5.Passenger

6.Luggage


b)Vehicle Details

No details will be shown under this section in Vehicle Selection page.

But in Contact Deatil & confirmation page ollowing details will be shown

1.Vehicle Name

2.Service Level


c)Cha
rge Details

If the Vehicle selection page loads for first time then no data will be shown under this
section. But if user do mouse hover on select button against any vehicle then folowing
details will be shown along with Grand total calculated for selected

vehicle. Also this
details will be shown by default in Contact Details & Confirmation page

1.Trip Cost


2.Web Discount


d)Additional Charge

Will display additional charges like Baby seat and other facilities.

e)Grand Total

Display Total cost for com
plete reservation.


Logic

Web Total =

Grand total =






Post
-

Condition

None

Business
Validation
Cases/Rules

None

Related Use
Cases


Questions



R
eservation Details in Right Block


















C
omplete Reservation Detail
































4.2.6
USE CASE
-
06:


Use Case

UC
-
06

Use Case
Name

User Menu

Actors

Administrator, Guest User, Registered users

Description

Describes various option provided to the users.

Pre
-
Condition

None



Basic Flow
(Steps)

Under the User Menu tab following
are the links shown to users

a)Reservation:

Onclick of this link,users will be redirected to Ride details page for booking taxi.

b)MyAccount:

Onclick of this link, system will validate for user login, if users are logged in then they
will be shown with f
ollowing fields with prefilled data(entered at the time of
registration), so that they can edit the values of the each fileds

1)First Name*

2)Middle Name

3)Last Name*

4)E
-
mail ID*

5)
Password*

6)Confirm Password *

7)Phone

8)
Street no./name line 1

9)Street no./name line 2

10)City

11)Country

12)State

13)Zip/Postal Code.


Also users can edit their card and billing information details by clicking on the “My
Billing Information” button whi
ch will redirect to payment information page.


c)My Reservation

User will be shown with list of of their reservation history with following details when
clicked on My Reservation link

1.Reservation Id

2.Booking No

Under this field , Reservation booking no
link will be shown to user

3.Pick UP Date/Time

4.Amount

5.Status

Users can also view,edit and print their reservation details by clicking on the Link
shown under Booking No filed.


d)My Receipts

User will be shown with list of of their reservation histor
y with following details when
clicked on My Reservation link

1.Reservation Id

2.Booking No

Under this field , Reservation booking no link will be shown to user

3.Pick UP Date/Time

4.Amount

5.Status

Users can also view,edit and print their reservation det
ails by clicking on the Link
shown under Booking No filed.


f)Feedback



Clicking on this link, users will be redirected to a feedback form with following fields
where they can send feedback to system admin

1.Your Name

2.Your Email Id

3.Feedback /Comments


Post
-

Condition

None

Related Use
Cases


Questions



User Menu



























Extra


Database/Framework Information


1. MySQL used as database

2.

Django framework & Satchmo shopping framework used for ecommerce shopping solution

3.Wordpress
Blog Used for Blog entries





Compatibility Information


The website will provide
W3C standards

The Platforms support provided are



Windows


Linux


mac

Browser support provided are Version:



Internet Explorer v7,v8


Firefox v3+


Opera v10+


Safari v5+


Google C
hrome v7+


Point will be consider while creating HTML/CSS for the bilingual site.


Please see english and arabic versions of taw9eel.com to understand why this is important.


1. Do not use float if not necessary. Only outer divs of the columns,images and u
nordered lists are
suppose to be floats to arrange horizontally. Floats directions are reverted in rtl to have reverse
horizontal arrangement. In IE cascading right floats

(required in rtl) behaves unpredictably.

2. Round corner containers have to be fluid
, so that a single container is used in all pages, they
should fit in all columns with different height and width.

3. Use h1, h2, h3 … tags, the page title have to be h1 or h2, sub titles h3 or h3, so on..

4. Do not use bullets as image, use them as css ba
ckground image, so that they can be changed or
rearranged in different pages and different directions.

5. Avoid inserting images in html, use css, so images can be changed easily.

6. Clear both side ( clear: both; ) with a empty div after use of floats.

7.

Font should be forced to be fixed size and type on all OSes and browsers"

8. Best practises must be used to reduce site load time. For eg the black background at the top need
to be a small image of black repeated throughout so that its rendered by the bro
wser quickly instead
of downloading the whole

background in black.





Website taxonomy