FUNCTIONAL SPECIFICATION

Al-Futtaim Web Experience Suite

P.SER.001

General Information:
Project Start date
July 17, 2011
Project Sponsor
Project Manager
Samer Zananiri
Document Owner
GBM
Version Number
2.1.2

Page 1 of 71

Functional Specification Revision History

Version
Draft 0.1

Date
07/19/2011

Description
Initial Draft Release

Draft 0.2

07/20/2011

Updated review comments

Draft 0.3

07/21/11

Updated review comments

Draft 0.4

07/21/11

Version 1.0

07/24/11

Version 2.0

08/04/11

Version 2.1

08/12/11

Version
2.1.1
Version
2.1.2

08/14/11
08/15/11

Updated with Milind comments and

Template changes
Initial version for Al-Futtaim review
Updated as per the review comments
given by AFG
Updated as per the clarification given by
AFG
Updated as per the clarification provided
by AFG
Updated as per the clarification provided
by AFG on Version 2.1.1

Revision By
Mustaq Baig
Mustaq Baig &
Ramakrishna
Mustaq Baig &
Ramakrishna
Mustaq Baig
Rajneesh Datta
Mustaq Baig &
Ramakrishna
Mustaq Baig &
Ramakrishna
Mustaq Baig &
Ramakrishna
Mustaq Baig &
Ramakrishna

Page 2 of 71

Contents
1

Introduction .................................................................................................................7
1.1 Project Description............................................................................................................. 7
1.2 Project Scope ..................................................................................................................... 7
1.3 Assumptions ....................................................................................................................... 7
1.4 Business Rules................................................................................................................... 8
1.5 Acronyms ............................................................................................................................ 8
1.6 References.......................................................................................................................... 8

Functional Specification ............................................................................................9

2.1 Navigation sets ................................................................................................................... 9
a. Lexus entry model window ............................................................................................. 9
b. Lexus Home page .......................................................................................................... 10
c. Primary Navigation ......................................................................................................... 12
d. Secondary navigation .................................................................................................... 13
e. Tertiary navigation.......................................................................................................... 15
f. Background Image ......................................................................................................... 16
g. Product Description text ................................................................................................ 16
h. Promo Boxes .................................................................................................................. 17
i. Footer links ...................................................................................................................... 17
j. Call to Action ................................................................................................................... 18
2.2 Product Information ......................................................................................................... 19
a. Lexus Range (Primary prodcut categories page)...................................................... 19
b. Product detail page ........................................................................................................ 21
2.3 Buying a lexus .................................................................................................................. 23
a. Lexus Range ................................................................................................................... 23

Page 3 of 71

b. Compare cars ................................................................................................................. 23

c. Compare cars Results................................................................................................ 25
d. Book a test drive ............................................................................................................. 27
e. E- brochures.................................................................................................................... 30
f. Certified pre-owned........................................................................................................ 30
g. Finance & Insurance ...................................................................................................... 31
h. Offers................................................................................................................................ 33
i. Company fleet ................................................................................................................. 34
2.4 Lexus owners ................................................................................................................... 36
a. Book a service ................................................................................................................ 36
b. Benefits ............................................................................................................................ 38
c. Workshops ...................................................................................................................... 39
d. Service Contract ............................................................................................................. 41
e. Service Intervals ............................................................................................................. 42
f. Magazine ......................................................................................................................... 43
g. Manuals & Resources ................................................................................................... 44
h. Warranty .......................................................................................................................... 45
2.5 Love the Brand ................................................................................................................. 46
a. Brand Lexus detailed page ........................................................................................... 46
b. Gallery .............................................................................................................................. 48
a. Gallery - Lightbox ........................................................................................................... 50
2.6 Tertiary Navigation/Header ............................................................................................ 51
a. Al Futtaim Motors ........................................................................................................... 51
b. News ................................................................................................................................ 52

Page 4 of 71

c. Search .............................................................................................................................. 54
i. Locations Find Showroom ........................................................................................ 56
j. Locations Find workshop ............................................................................................ 57
k. Social Links ..................................................................................................................... 57
l. Locale ............................................................................................................................... 58
m. Contact US ...................................................................................................................... 59
2.7 Footer Links ...................................................................................................................... 60
a. About the site .................................................................................................................. 60
b. Privacy & Terms ............................................................................................................. 61
c. Mobile ............................................................................................................................... 61
n. Media................................................................................................................................ 62
o. More of lexus .................................................................................................................. 64
p. Interactive Online chat ................................................................................................... 65
q. Magazine ......................................................................................................................... 65
2.8 Other Requirements ........................................................................................................ 66
a. General requirements .................................................................................................... 66
2.9 Security Requirements .................................................................................................... 66
a. Security Requirements .................................................................................................. 66
2.10

Non functional Requirements .................................................................................... 66

b. Non functional Requirements ....................................................................................... 66

1. Reports ....................................................................................................................... 67
2. User Acceptance Criteria ......................................................................................... 67
3. Changes to Other Systems ...................................................................................... 67
4. Non Functional Requirements ................................................................................. 67

Page 5 of 71

5. Appendices ................................................................................................................ 67
5.1 Appendix............................................................................................................................. 67
5.2 Appendix AFG Web Portal User Access Details ..................................................... 71

Page 6 of 71

INTRODUCTION

This document provides functional requirement of Lexus website. Document covers functional
requirements which will be implemented with the new site to improve the User experience and
usability aspects of current Lexus website. Together With new user experience, new system will
also provide better control over the content management aspects of the site.
1.1 PROJECT DESCRIPTION
Lexus Web Portal Services will allow users to know more about Lexus models, avail services
and get in touch with Lexus brand. This site will be supported in both English and Arabic version
of the content.
1.2 PROJECT SCOPE

1.
2.
3.
4.
5.
6.
7.
8.

Functionality in Scope
Book a Service Appointment
Book a Test Drive
Media Kit Download
Workshops
Locations
Compare Cars
Finance and Insurance Calculators
Company Fleet

1.
2.
3.
4.
5.
6.

Out of Scope (For Phase 1)

Profile Management & Personalization
Social Lexus
Magazine
Interactive Online chat
Certified Pre-Owned
New User Registration

Note: Any other functionality which is not part of Functionality in scope section will be
considered as out of scope for Phase 1 of this project.
1.3 ASSUMPTIONS
1. AFG provides the required content management support to implement web portal
services.
2. CMS Admin user will maintain the content.

Page 7 of 71

1.4 BUSINESS RULES

1. AFG will provide the business rules if any.
1.5 ACRONYMS
Term
AFG
AFM
CMS
FB
TW
LN
YT

Description
Al-Futtaim Group
Al-Futtaim Motors
Content Management System
Facebook
Twitter
LinkedIn
YouTube

1.6 REFERENCES
1.
2.
3.
4.
5.

Existing Lexus website www.lexus.ae

Lexus wireframes Lexus v9.pdf
Proposed Lexus sitemap Lexus_Sitemap May01_v9.pdf
Proposed Lexus UI designs Lexus_.Designupdatepdf.pdf
template-reference 13-06-2011.pdf

Page 8 of 71

2
2.1

FUNCTIONAL SPECIFICATION
NAVIGATION SETS
A. LEXUS ENTRY MODEL WINDOW

Description
Assumption &
Pre-Requisites
Functional
Requirement

Allow user to choose one of the profile from 3 profiles types or skip the
personalization.
1. Personalization is out of scope for Phase 1
1. On load of the website homepage, the user is presented with 3 profile
types
1.1. Lexus Buyer
1.2. Lexus Owner
1.3. Love the Brand
2. The user has the option of choosing either one of the profiles.
3. Initially when the page loads, all the profile icons will be of the same size,
however on mouse-over, the icon size enlarges to show the user
interaction.
4. On clicking of a particular profile icon, the page reloads with the

Page 9 of 71

personalized options set by the administrator of the website for that

particular profile user - for e.g.; the promo boxes can be interchanged
from the backend CMS for each profile type.
5. Customization would be same across roles or profiles for all users.
6. Background will be in disable mode including Primary navigation.
7. The user will have the option to skip the personalization by clicking SKIP
button.
Clarification/
Comments/
Suggestions

B. LEXUS HOME PAGE

Description
Assumption&
Pre-Requisites
Functional
Requirement

Allow user to navigate through the complete website

1. Homepage will get loaded with the following components which are
detailed in the following requirement sections
Primary Navigation
Secondary Navigation

Page 10 of 71

 Tertiary Navigation
Background Image
Product text with brief description
Promo boxes
Footer links
2. External links could be outside of Al-Futtaim site and will be opened in
new window.
3. When user clicks on Al-Futtaim logo/link system should bring the user to
the AFG corporate website.
4. When user clicks on Al-Futtaim Motor image system should bring the user
to the Al-Futtaim Motor website.
5. Page color depends on the image color and the CMS user should be able
to pick the color. (Please refer to Annexure 5.1 for more details)
6. Images will change across pages and same functionality is required
across pages.
7. On some pages there will be multiple images. Background color of the
section would depend on the master image and should not change as the
images change.
8. The master navigator content or section can change in future.
9. The items at the bottom could have different content, call to action, etc.
These would be dynamic and would change. The number of images
would also change
10. The CMS user should be given the option to freeze any number of these
content holders. Technical design should take care of this requirement.
11. The pages would have links for Twitter, Facebook YouTube and LinkedIn
12. Product text with brief description would be managed at design level. End
users would not be able to change it.
13. Online Users should not be able to tamper with corporate content.
Workflow would be designed to take care of it
Clarification/
Comments/
Suggestions

Page 11 of 71

C. PRIMARY NAVIGATION

Description
Assumption&
Pre-Requisites
Functional
Requirement

Allows users to navigate through all product categories

1. Primary Navigation will have the following product categories within

the Lexus range
a. Sedans
b. Convertibles
c. Luxury Utility
d. Hybrids
e. Performance
f. All (option to select categories)
2. On mouse-over, a mega drop menu is shown with the products within
that particular category. The user will be able to browse between each
model within a particular category.
3. For each model shown, the following details will be shown within the
mega drop down menu
Model name
Short Description
Link to detailed page

Page 12 of 71

 Thumbnail image
4. The categories of Primary navigator should be flexible to future
changes for admin user.
5. When user clicks on both the top and bottom social icons i.e.
Facebook, Twitter, LinkedIn & YouTube links then it will take the user
to the corresponding Lexus UAE social page in a new window.
6. Al-Futtaim team confirmed that the models in the mega drop down
can change in future.
7. Al-Futtaim team also confirmed that navigation should happen on
clicking on the image and the explore button
Clarification/
Comments/
Suggestions
D. SECONDARY NAVIGATION

Description
Assumption&
Pre-Requisites

Allow user to navigate to a particular profile type

Functional

Page 13 of 71

Requirement

1. Secondary Navigation should have the following menu items

a. BUYING A LEXUS
b. LEXUS OWNERS
c. BRAND LEXUS
2. Under a BUYING A LEXUS following are the sub items
a. Lexus Range
b. Compare Cars
c. Book Test Drive
d. E- Brochures
e. Certified Pre-owned
f. Finance & Insurance
g. Offers
h. Company Fleet
3. Under a LEXUS OWNER following are the sub items
a. Service
Book a Service
Service Intervals
Workshops
Service Contract
b. Magazine
4. Under a BRAND LEXUS following are the sub items
a. The Lexus Story
b. Commitment
c. Progressive Luxury
d. Environment
e. YET Philosophy
f. Campaigns
g. Hybrid
h. F Performance
i. Lexus Shop
5. For Phase 1 all the roles would be visible and have same functionality,
but design should take care of the future functionality of having
differing content and workflow for each role in Phase 2
6. Secondary navigation menu items has to become brighter or a little bold
on hover AND on click/select

Clarification/
Comments/
Suggestions

Page 14 of 71

E. TERTIARY NAVIGATION

Description
Assumption&
Pre-Requisites
Functional
Requirement

Clarification/
Comments/
Suggestions

Allows user to navigate within the website and outside

1. This is a set of standard links which will aid the user navigation within
the website and outside
2. Tertiary Navigation should have the following links
a. Al-Futtaim Motors
b. Locations
c. Social Lexus
d. News
e. Arabic/English
f. Contact Us
g. Search
3. When user clicks on social icons i.e. TW, LN & YT then it will take the
user to the corresponding Lexus UAE social page in a new window.
1. Considered Lexus_Sitemap May01_v9.pdf

Page 15 of 71

F. BACKGROUND IMAGE
Description
Assumption&
Pre-Requisites

It describe the background image behavior

Functional
Requirement

1. Page color depends on the image color and the CMS user should be able
to pick the color. E.g. If the car image is in blue color the background
should be gradient of image.
2. Whenever the image changes across pages the background color should
change.
3. On some pages there will be multiple images. Color from master image
only should be there in the page and should not change as the images
change.

Clarification/
Comments/
Suggestions

Please refer to Annexure 5.1 for more details

G. PRODUCT DESCRIPTION TEXT

Description
Assumption&
Pre-Requisites
Functional
Requirement

It describes the short description of the product shown

1. The system should accommodate the future changes to the models in

mega drop menu
2. Admin user should be able to add or modify the model description,
thumbnail image in mega drop menu
3. Navigation to the detail page should happen on clicking on the image
or the EXPLORE button

Clarification/
Comments/
Suggestions

Page 16 of 71

H. PROMO BOXES
Description
Assumption&
Pre-Requisites
Functional
Requirement

It describes the Promo Boxes behavior

1. Since profiles are not being considered in Phase 1 of the project, point
number 2 of the functional requirement will not be valid at this point in
time.
1. The CMS user should be given an option to freeze any content in the
promo boxes but other promos content should keep
changing/rotating.
2. Content of promo should get change based on which profile user has
entered in to website.
3. Twitter, Facebook, YouTube and LinkedIn links would be there in
Connect with Lexus promo box, when user click on any link the
corresponding website should open with Lexus profile.
4. The Promo boxes at the bottom could have different content, call to
action, etc. These would be dynamic and would change. The content
author would be able to make these changes, but the end user to the
site will not be able to change the content.

Clarification/
Comments/
Suggestions

I.

FOOTER LINKS

Description
Assumption&
Pre-Requisites
Functional
Requirement

Describes the Footer links

1. Footer should have the following links

a. About The Site
b. Privacy & Terms
c. Mobile
d. Media
e. More of Lexus
f. Interactive Online Chat
g. Magazine The format of the magazine is pdf and on clicking
the link it will open a new window with the pdf
h. Career - In case user clicks on Career, should it take the user
to an external site

Clarification/
Comments/
Suggestions

Page 17 of 71

J. CALL TO ACTION

Description
Assumption&
Pre-Requisites
Functional
Requirement
Clarification/
Comments/
Suggestions

Allows user to reach Lexus instantaneously

** TBD

Page 18 of 71

2.2

PRODUCT INFORMATION
A. LEXUS RANGE (PRIMARY PRODCUT CATEGORIES PAGE)

Description
Assumption&
Pre-Requisites
Functional
Requirement

Allows user to find out the information about all model within Lexus range

1. The user comes to primary product categories page either by

accessing the menu item 'All' on the primary navigation or the drop
down menu item 'Lexus Range' option in 'Buying a Lexus' menu in the
Secondary navigation.

Page 19 of 71

2. Within the page, each of the categories is held within collapsible

containers. On page load, the first container is expanded by default
and the rest of the containers are collapsed. When user opens
another panel the previously opened panel will collapse. Only one will
remain open at one time
3. On clicking the container header or the arrow on the right, the
container expands to reveal the models within that particular category.
4. Within each container, the model is shown with a thumbnail image,
model name and description.
5. On clicking the thumbnail or the title of the model, the user can go to
the detailed page of that particular model. Both model image and
model name are links
6. Admin user has the flexibility to add the major categories. At least 2.
(E.g. Convertibles etc.)
7. In the mega drop down for "Sedans, Convertibles, etc. flexibility to
add or remove items should be there.
Clarification/
Comments/
Suggestions

Page 20 of 71

B. PRODUCT DETAIL PAGE

Page 21 of 71

Description

Allows user to find out information about a specific model when user choose
one of the model from the primary product categories page

Assumption&
Pre-Requisites
Functional
Requirement

1. The detailed page of any model consists of a standard set of

collapsible panels
a. Overview
b. Exterior
c. Interior
d. Performance
e. Safety
f. Specification
g. Warranty
2. Additional options for the chosen model will be listed here. The +
button is only image with links inside for Compare, Book test drive and
Brochure
3. Admin user can able to create the link for specific panel in the model.
4. Exterior is highlighted and Interior dimed when Exterior images (small
doted buttons under Exterior) is shown and vice versa. Images keep
changing with time delay.
5. Exterior and Interior can accommodate maximum of six images
6. If a user clicks on the bottom links (round buttons) then that particular
image should become the highlighted image. Post which the normal
functionality of rotation with time delay continues.
7. An additional panel will be featured for model that have offers
associated with them. If there are no offers associated, then this panel
is not shown at all.
8. Offer panel will show offers specific to model and offers which are
applicable across the product ranges. E.g. offer which is common for
all models will also be displayed here.
9. Offers panel is not expandable. It should only be visible if there is
content in it.
10. Once a collapsible panel is open it should remain open unless user
collapses by clicking on right arrow or whole bar.
11. In image gallery the dots are the image links which will keep rotating
and can also be clicked. Gallery can accommodate maximum of six
images.
12. Three seconds will be the time interval between each image rotations
13. Exterior and interior could also have 360 degree view animation, if
user clicks on it , it will display 360 degree view animation in new
window as a popup
14. In this page once a section is open it should remain open
15. The content for remaining panels is the static text content sections

Page 22 of 71

and please refers the lexus.com for these sections.

16. In the Overview section by selection of the doted images the image
and the content associated to it gets updated. It should happen in the
time interval also.
Clarification/
Comments/
Suggestions

2.3

BUYING A LEXUS
A. LEXUS RANGE

Description
Assumption&
Pre-Requisites
Functional
Requirement
Clarification/
Comments/
Suggestions

Allows user to find out more information about all model within Lexus range

** Covered in requirement 2.2 A

B. COMPARE CARS

Page 23 of 71

Description
Assumption&
Pre-Requisites
Functional
Requirement

Allows user to compare selected cars against different features

1. The user can click on the comparison menu, each time he visits a
particular model detailed page or he can come to this page directly
and then choose the models to compare. At a time, the user can
compare 3 cars.
2. The user has to choose a particular model from the first drop down
menu and choose a style from the 2nd drop down menu. The items in
the 2nd drop down menu will change based on the user selection on
the first drop down menu.
3. If the user comes from a specific model page by clicking on compare,
then that should be the first model selected.
4. On clicking the button 'Add', the user adds his selected model to the
comparison.
5. The user can then proceed to view the compare results, by clicking
the 'Compare' button.
6. Comparison could be across the Lexus range but not against
competition.
7. If user clicks on remove image, the remaining image should adjust to
left.
8. If the number of models are not fitting in the screen then there should

Page 24 of 71

be vertical scroll bar provided.

9. REQUEST A CALL would be like a popup which should disappear if
the user hovers away from it.
10. REQUEST A CALL should have the following fields
a. Name
b. Number (+971)
c. email
d. What Car Do you Drive?
e. City
f. Submit Button
11. Downloads would have option of online reading and pdf download
12. User will simply set the selected model in the drop down user will
select the style and click on Add button. Selected model will not be
added by default
1.Clarification/
Comments/
Suggestions

Data Elements & Validation

Dropdowns
Values/
Metadata

Minimum
Length

Maximum
Length

Is
mandat
ory?

Data
Element

Default
Value

Model
dropdown

Select
Model

Style
dropdown

Select Style

Data
Type

Other
Validation

C. COMPARE CARS RESULTS

Page 25 of 71

Description
Assumption&
Pre-Requisites

Allows users to view the comparisons of selected car features

1. The compare cars structure and UI has been changed, the wireframe
will be updated according to the design shown to you.
2. Build your GS will not be there in design and new wireframes

Functional
Requirement

1. Start over will start the whole new comparison and will not add the
existing models
2. Find a dealer takes the user to the location page. Where user can
check the dealers location.
3. Compare GS Series will be in the GS series comparison, Maximum 4
cars can be compared.
4. When user clicks on Change Menu, Model popup will be displayed, it
shows the previous page, user can replace with new model

Clarification/
Comments/
Suggestions

Page 26 of 71

D. BOOK A TEST DRIVE

Page 27 of 71

Description
Assumption&
Pre-Requisites
Functional
Requirement

Allows user to book a test drive

1. Questionnaire will not be changed dynamically.

1. To book a test drive, the user can choose this option from a detailed
page or come directly to this page.
2. The user has to choose a particular model he/she is interested in and
then choose a nearest available location.
3. Required Information section should collect all required user
information and sends an email to the concerned person or
department in Al-Futtaim and a confirmation mail to the user.
4. When user selects location from choose your emirate system shows
the showrooms pointed on Google map right side of the panel. When
user mouse over or clicks on the point the corresponding showroom
address is shown on the left side of the panel.
5. Required information section should have the following fields, left side
section is mandatory and right side section is optional
Left side:
Title Title will be drop down of standard titles.
First Name 50 characters with special characters
Last Name 50 characters with special characters
Phone - only UAE numbers (+971), max. 12 field length, only
digits, no characters
Email - with standard email validations with max length of 100
A check box with description Would you like to be the first to know
about new vehicle launches, competitions and events and
opportunities for drivers, such as track days or Lexus
Experiences?
Right side:
List box with description When are you looking to replaces your
vehicle? - With values up to 3 months, 3 to 6 months, 6
months to 1 year, +1 year
Text box with description What vehicle do you currently drive? The user must type in the car model and make

List box with description What other vehicles are you interested
in? Type of vehicle like Sedan, Performance, etc.
Four check boxes with description What made you consider a
Lexus? : 1. Styling , 2. Refinement, 3. Full Hybrid, 4. Value for
money Multiple check boxes can be selected at a time
Submit Button
6. The user information needs to be saved in database and email to be
sent to the respective people once the user submits the data
7. Data should be captured only if the user clicks on submit.
8. After clicking on submit a Thank you message should be displayed
with an option for the user to go back to home page and the form

Page 28 of 71

should get cleared

9. The email is based on location and should be sent to multiple people
10. Questionnaire could change in future
11. Cancel button to be removed
Clarification/
Comments/
Suggestions
Data Elements & Validation

Data
Element

Default
Value

Dropdowns
Values/
Metadata

First Name

50

Phone

12

Email

100

Choose
your
Emirate
dropdown

Replace
vehicle
dropdown

Maximum
Length
50

Last Name

Title
dropdown

Minimum
Length

Is
mandat
ory?

Other
Validation

Data
Type
Chara
cter

with special
characters

Chara
cter

with special
characters

Chara
cter

only digits, no
characters

standard email
validations

Mr.

Mr.
Mrs.
Miss
MS

Up to 3
months,
3 to 6
months,
6 months to
1 year,
+1 year

Currently
drive
vehicle text

Page 29 of 71

box
Other
vehicle
interested
dropdown

Sedan
Performance

E. E- BROCHURES
Description
Assumption&
Pre-Requisites
Functional
Requirement
Clarification/
Comments/
Suggestions

E-brouchers

Please refer to Annexure 5.1 for more details

F. CERTIFIED PRE-OWNED
Description
Assumption&
Pre-Requisites

Certified Pre-Owned
1. Will covered in Phase 2

Functional
Requirement
Clarification/
Comments/
Suggestions

Page 30 of 71

G. FINANCE & INSURANCE

Description
Assumption&
Pre-Requisites

Functional
Requirement

Allows users to view finance and insurance information and allows them to
calculate monthly installments
1. Logic for the finance calculator would be given at a later date
2. Design we need to follow, they will send the design on AUG 22nd , but
what ever the wireframe we have it contains all the information.
1. Finance & Insurance, the user can choose this option from a detailed
page or come directly to this page.
2. This page consist of two collapsible panels
2.1 Finance & Insurance
This panel gives a brief description of the various finance and
insurance options

Page 31 of 71

2.2 Finance Calculator

This panel should have the following controls/fields
Amount Financed - Only positive numbers, max of 10 million,
in AED
Interest Rate
Deposit
Loan Term (Years)
Repayment frequency
3. The user can calculate the monthly installment that he needs to pay, if
he chooses to obtain a certain amount. The monthly installment is
automatically calculated based on the parameters given by the user
i.e. on fly of the data filling, the finance should be calculated, page
should not get refresh.
4. REQUEST TO CALL should be consistent across pages and should
have email also.
Clarification/
Comments/
Suggestions
Data Elements & Validation

Data
Element

Default
Value

Dropdowns
Values/
Metadata

Amount
Financed

Minimum
Length

Maximum
Length

10,2

Is
mandat
ory?

Deposit

Interest rate
dropdown

Loan
Term(year)
dropdown

Repayment
Frequency
dropdown

Monthly
Yearly

Data
Type

Other
Validation

Money

Only positive
numbers, max
of 10 million, in
AED

Money

Only positive
numbers, max
of 10 million, in
AED

Page 32 of 71

H. OFFERS

Description
Assumption&
Pre-Requisites
Functional
Requirement

Allows user to view all the offers currently available

1. The user can choose this option from a detailed page or come directly
to this page.
2. This page lists all the offers currently available.
3. Current offers across Lexus Brand will change periodically.
4. Clicking on Find out more should take to the relevant page or section.
5. The relevant page or section should open in the new page

Clarification/
Comments/
Suggestions

Page 33 of 71

I.

COMPANY FLEET

Description
Assumption&
Pre-Requisites
Functional
Requirement

Allows user to contact the Fleet team

1. Company Fleet, the user can come directly to this page.

2. Company Fleet form consist of following fields
2.1 Title - Title will be drop down of standard titles
2.2 First Name 50 characters with special characters
2.3 Last Name 50 characters with special characters
2.4 Phone - only UAE numbers (+971), max. 12 length, only digits, no
characters
2.5 Email - with standard email validations with max length of 100
2.6 Company name 100 characters with special characters
2.7 Company type - Industry (Airlines, Car Rental, etc.)
2.8 Submit button
2.9 Reset button
3. This page allows the user to contact the Fleet team. On submission of
the form, the information get saved in the database and an email goes
out to the concerned person within the Fleet team and to the user
4. Email ids should be in CMS. Email ids Should be configurable

Page 34 of 71

5. When user clicks on Reset button, it clears the fields whatever he

entered
6. Admin User can be able to export the Company Fleet registered users
information in csv format
Clarification/
Comments/
Suggestions
Data Elements & Validation

Data
Element

Default
Value

Dropdowns
Values/
Metadata

First Name

Minimum
Length

Maximum
Length
50

Last Name

50

Phone

12

Email

100

Company
Name

100

Title
dropdown

Mr.
Mrs.
Miss
MS

Company
Type
dropdown

Airlines
Car Rental

Is
mandat
ory?

Other
Validation

Data
Type
Chara
cter

with special
characters

Chara
cter

with special
characters

Numb
ers

only digits, no
characters
standard email
validations

Chara
cter

with special
characters

Page 35 of 71

2.4

LEXUS OWNERS
A. BOOK A SERVICE

Description
Assumption&
Pre-Requisites
Functional
Requirement

Allows user to book a service

1. The above wireframe will get updated with new one

1. Book a Service, the user can choose this option in Secondary

navigation menu. This section allows the user to book a service for his
car.
2. Book a Service panel consist following fields
Left side:
2.1 Two check boxes 1. Service & 2. Body Repairs with description
What would you like to be carried out?

Page 36 of 71

3.
4.
5.
6.
7.

2.2 Free flow text box with description anything else you would like
us to look at? - limited to 1000 characters and it shows the
dynamic count
2.3 Date text box, Select a date along with calendar control with
description When would you like the service? The earliest
service available is 3 days from today. If you require a service
sooner, please call us on +971-##### . Admin user would be
able to configure Days option based on bandwidth at their side.
2.4 Two radio buttons 1. Morning & 2 Afternoon
2.5 A location dropdown to be added to allow the user to select the
nearest service location
2.6 A dropdown with description How many kilometers service? Values like 5000, 10000, etc. till 100000+ and others
2.7 Submit & Cancel buttons
Right side:
2.8 Title - Title will be drop down of standard titles.
2.9 First Name 50 characters with special characters
2.10 Last Name 50 characters with special characters, optional
2.11 Phone - only UAE numbers (+971), max. 12 length, only digits,
no characters
2.12 Email -with standard email validations with max length of 100
Select the date validation would depend on the number of days shown
in the static text.
Default date should be the date as per the static text with a calendar
control next to it.
On submit the data will be stored in the database table.
Confirmatory email to be sent to the user as well as concerned AlFuttaim staff.
Book a service user information should be exported to csv format by
admin user

Clarification/
Comments/
Suggestions
Data Elements & Validation

Data
Element

Default
Value

Dropdowns
Values/
Metadata

Free flow
text box

Minimum
Length

Maximum
Length
1000

Is
mandat
ory?

Data
Type
Chara
cter

Other
Validation
with special
characters

Location
dropdown
5000
Kilometers

Page 37 of 71

dropdown

10000
Etc.
Till 100000+

First Name

50

Last Name

50

Phone

12

email

100

Select a
Date calendar
control

Title
dropdown

Chara
cter

with special
characters

Chara
cter

with special
characters

Numb
ers

only digits, no
characters

standard email
validations

Current
Date
Mr.
Mrs.
Miss
MS

Mr.

B. BENEFITS
Description
Assumption&
Pre-Requisites
Functional
Requirement
Clarification/
Comments/
Suggestions

Benefits

Please refer to Annexure 5.1 for more details

Page 38 of 71

C. WORKSHOPS

Description
Assumption&
Pre-Requisites
Functional
Requirement

Allows users to find the nearest Workshop

1. Request test drive button is removed in new design

1. Workshops, the user can choose this option in Secondary navigation

Lexus Owner menu. This section allows the user to find the nearest
available workshops within a particular emirate.
2. Add one more drop down contains the locations, if the user selects the
emirates, locations drop down will be displayed. By selecting the
locations and click on submit, all the results will be displayed on left
side and Map on right side, in the map, it displays only bulb icons.
this is the recommended approach from GBM
3. Address should be pulled from database

Page 39 of 71

4. Once a workshop is pin-pointed, the user is provided with three

options
3.1 Email location map Current State of the map should be mailed.
3.2 Print Map Current State of the map should be print
3.3 GPS Export The GPS co-ordinates can be generated by Google
Maps and it can be sent to any desired email account provided by
the user
4. When user clicks on Email Location Map or GPS Export system
should ask the user to enter the their desired email id
Clarification/
Comments/
Suggestions
Data Elements & Validation

Data
Element

Choose an
Emirate

Default
Value

Dropdowns
Values/
Metadata
Abu Dhabi
Al Ain
Dubai
Rasal
Khaima
Sharja

Minimum
Length

Maximum
Length

Is
mandat
ory?

Data
Type

Other
Validation

Page 40 of 71

D. SERVICE CONTRACT

Description
Assumption&
Pre-Requisites
Functional
Requirement

Service Contract
1. This section will display content from content management system
based on Service Contract content created by content Authors.
1. This section will display content from content management system
based on Service Contract content created by content Authors.
2. User can download the PDF

Clarification/
Comments/
Suggestions

Page 41 of 71

E. SERVICE INTERVALS

Description
Assumption&
Pre-Requisites
Functional
Requirement
Clarification/
Comments/
Suggestions

Service Intervals

**TBD

Page 42 of 71

F. MAGAZINE
Description
Assumption&
Pre-Requisites
Functional
Requirement
Clarification/
Comments/
Suggestions

Magazine

**TBD

Page 43 of 71

G. MANUALS & RESOURCES

Description
Assumption&
Pre-Requisites
Functional
Requirement
Clarification/
Comments/
Suggestions

Manuals & Resources

**TBD

Page 44 of 71

H. WARRANTY

Description
Assumption&
Pre-Requisites
Functional
Requirement
Clarification/
Comments/
Suggestions

1. This section will display content from content management system

based on Warranty content created by content Authors.
2.
1. Warranty content going to be different across the Models
Please refer to Annexure 5.1 for more details

Page 45 of 71

2.5

LOVE THE BRAND

A. BRAND LEXUS DETAILED PAGE

Page 46 of 71

Description
Assumption&
Pre-Requisites
Functional
Requirement

Allows users to know more about brand Lexus

1. All panels will have static content with images (optional). CMS admin
user will manage this
1. Brand Lexus, the user can choose this option in Secondary navigation
menu. This allows the users who are interested to know more about
the brand 'Lexus'.
2. This page consists of multiple expandable/collapsible panels
2.1 The Lexus Story
2.2 Commitment
2.3 Progressive Luxury
2.4 Environment
2.5 YET Philosophy
2.6 Campaigns
2.7 Hybrid
2.8 F Performance
2.9 Lexus Shop
3. Open panels should remain open unless the user specifically closes it
4. All redirections should open in a new windows if there are any links in
the static content

Clarification/
Comments/
Suggestions

Page 47 of 71

B. GALLERY

Page 48 of 71

Description
Assumption&
Pre-Requisites
Functional
Requirement
Clarification/
Comments/
Suggestions

Gallery

**TBD

Page 49 of 71

A. GALLERY - LIGHTBOX

Description
Assumption&
Pre-Requisites
Functional
Requirement
Clarification/
Comments/
Suggestions

Gallery

**TBD

Page 50 of 71

2.6

TERTIARY NAVIGATION/HEADER
A. AL FUTTAIM MOTORS

Description
Assumption&
Pre-Requisites
Functional
Requirement

Allows users to see information about Al-Futtaim Motors

1. Al-Futtaim Motors, the user can open this page from header. This
page gives an overview of 'Al-Futtaim Motors'
2. This page should have the link/image A Future with Us Find your
ideal career today!
3. Users who are interested in having a career with Al-Futtaim can avail
more information by visiting the above link. This is external website
and will open in a new window.

Clarification/
Comments/
Suggestions

Page 51 of 71

B. NEWS

Description

Allows users to read news articles related to Al Futtaim Motors and their
latest models

Assumption&
Pre-Requisites
Functional
Requirement

1. News, the user can open this page from header. This page Allows
users to read news articles related to Al-Futtaim Motors and their
latest models
2. The news articles are categorized model wise along with other
categories such as 'awards', 'events', 'press releases' etc...And the
content Author defined those categories.
3. Default articles to be display are all the categories and latest news

Page 52 of 71

date wise
4. Page should show five news headlines at a time along with article
date, short description and Read More link.
5. News articles are presented in pagination format when more than 5
articles in archive
6. News items will be displayed in Latest news first order
7. User should navigate next or previous articles using Next & Prev links
8. On clicking on Read More link, Content should be displayed in the
same page, on left hand side, the categories section and right hand
side the complete news details. User can see the other result by
clicking on categories again or the browser back button.
9. When user clicks on Read More link it should be a popup with share,
print and close buttons. On clicking on share a small drop down with
email, FB, TW, LI links should open.
10. When user clicks on a category where there are no articles It displays
the message saying that No Articles found.
11. Page should have search functionality and it allows user to search
news article.
12. The search should look at the page tags as well as keywords for the
results
13. News head line is a link and has the same Read More link behavior
14. Search in news pages is limited to news article
Clarification/
Comments/
Suggestions

Page 53 of 71

C. SEARCH

Description
Assumption&
Pre-Requisites
Functional
Requirement

Allows users to search the content within the website

1. Within the CMS, the admin user can choose content that can be
searched by the users.
1. User lands in Search page when a keyword/ text is typed in search
box in the header
2. Search result page should have search box with Search again label
3. The results are presented in a paginated format, with the search
keyword highlighted in each result.
4. Maximum of 8 results will be displayed on a result page when multiple
search results are in queue.
5. All searches are within Lexus website and not a global search i.e.

Page 54 of 71

outside of the website.

6. The search functionality should be based on the page tags as well as
keywords for the results
7. When user clicks on any search results it goes to the related page for
example if the user searches for LS then the LS page, a related offers,
and article etc will be displayed. ON click it will take you to the
products page, the offers page or the article page.
Clarification/
Comments/
Suggestions
Data Elements & Validation

Data
Element

Default
Value

Dropdowns
Values/
Metadata

Minimum
Length

Maximum
Length

Is
mandat
ory?

Data
Type

Other
Validation

Keyword
Search
Search
Again

Page 55 of 71

I.

LOCATIONS FIND SHOW ROOM

Description
Assumption&
Pre-Requisites
Functional
Requirement

Allows users to find the nearest Showroom

1. User lands in Showroom page when user clicks on Location link in the
header and this allows the user to find the nearest available
Showroom within a particular emirate.
2. Add one more drop down contains the locations, if the user selects the
emirates, locations drop down will be displayed. By selecting the
locations and click on submit, all the results will be displayed on right

Page 56 of 71

side and in the map, it displays only bulb icons. this is the
recommended approach from GBM
3. Once a Location is pin-pointed, the user is provided with three options
3.1 Email location map Email the location to the user
3.2 Print Map - Print the location map
3.3 GPS Export The GPS co-ordinates can be generated by Google
Maps and it can be sent to any desired email account provided by
the user
4. When user clicks on Email Location Map or GPS Export system
should ask the user to enter the their desired email id
5. The text shown in wireframe choose your emirates is a hardcode text
6. Color coded icons should be displayed on the map for workshops and
show rooms separately but it should not be a red color
Clarification/
Comments/
Suggestions
J. LOCATIONS FIND WORKSHOP
Description
Allows users to find the nearest Workshop
Assumption&
1. Wireframe for Showroom and Workshop is same
PreRequisites
Functional
Requirement
Clarification/
Comments/
Suggestions

** Covered in requirement Lexus Owner 2.4 C

K. SOCIAL LINKS
Description
Assumption&
Pre-Requisites
Functional
Requirement

Allows users to connect to social network sites

1. Respective social network website should open in a new window
when user clicks on any social network site image on the header (e.g.
Facebook website opens when user clicks on Facebook image)
1. Links to other sites like face book, twitter.
2. Share functionality need to be implemented, it look like the add plus
functionality
3. Share is limited to the face book, twitter and linked in.

Clarification/
Comments/
Suggestions

Page 57 of 71

L. LOCALE
Description
Assumption&
Pre-Requisites

Functional
Requirement

Allows users to switch from English to Arabic and vice versa

1. When the Arabic selected in the header the complete website should
switch to Arabic language and vice versa.
2. The HTMLs shared with GBM team will have the inherent capability to
switch to Right to Left mode without any effort to be spent by
developers. For this DIV tags should not be used in the HTMLs.
Further details can be shared by GBM team with the Al-Futtaim
design team, if required.
1. When the Arabic selected in the header the complete website should
switch to Arabic language and vice versa.

Clarification/
Comments/
Suggestions

Page 58 of 71

M. CONTACT US

Description
Assumption&
Pre-Requisites
Functional
Requirement
Clarification/
Comments/
Suggestions

Allows users to view the AFG/AFM contact information

1. This section will display content from content management system
based on Privacy & Terms content created by content Authors.
1. User lands in Contact Us page when he clicks Contact Us link in the
Header and this allows the user to view the AFG/AFM contact
information
Please refer to Annexure 5.1 for more details

Page 59 of 71

2.7

FOOTER LINKS
A. ABOUT THE SITE

Description
Assumption&
Pre-Requisites
Functional
Requirement

Allows users to know about Lexus

1. This section will display content from content management system
based on About the Site content created by content Authors.
1. User lands in About the site page when he clicks on About the site
link in the Footer and this allows the user to view the details on Lexus
site as entered in the CMS

Clarification/
Comments/
Suggestions

Page 60 of 71

B. PRIVACY & TERMS

Description
Assumption&
Pre-Requisites
Functional
Requirement

Allows users to know about Privacy & Terms of the website

1. This section will display content from content management system
based on Privacy & Terms content created by content Authors.
1. User lands in Privacy & Terms page when he clicks on Privacy &
Terms link in the Footer and this allows the user to know Privacy &
Terms of the website

Clarification/
Comments/
Suggestions
C. MOBILE
Description
Assumption&
Pre-Requisites

Allows users to access the Lexus site from their mobile devices
Phase 2 functionality

Functional

Page 61 of 71

Requirement
Clarification/
Comments/
Suggestions

This requirement is being currently considered as a separate project.

N. MEDIA
Description
Assumption&
Pre-Requisites
Functional
Requirement

Allows users from Press / Media to access and download information from
Lexus site
1. This is part of Phase I as per the IA

1. When Media is clicked login page to open as a popup with new user
and forgot password links
2. Registration has to be done through Registration request page for
Media/Press people to access the restricted pages.
3. Registration Request page will capture the following information in
new user registration
3.1 Name 50 characters with special characters
3.2 Email Address with standard email validations with max length
of 100
3.3 Company Name 50 characters with special characters
3.4 Business Telephone only UAE numbers (+971), max. 12 field
length, only digits, no characters
3.5 Mobile Number only UAE numbers (+971), max. 12 field length,
only digits, no characters
3.6 Submit button
3.7 Reset button
4. PR department will be the custodian of this section.
5. On clicking of Submit button after filling the required field, information
will be saved in the database and Request will sent to the PR
department.
6. PR department will Approve or Reject the request
7. On Approval, user is provided with access to the media.
8. On approving/rejecting the request, an email notification is sent to the
user
9. Whenever the new media uploads, all the media users are notified via
email.
10. When user clicks on Reset button, all the text boxes in the page will
be clear off.

Clarification/
Comments/
Suggestions
Data Elements & Validation

Page 62 of 71

Data
Element
Name
Business
Phone
Mobile
Number

Email
Company
Name

Default
Value

Dropdowns
Values/
Metadata

Minimum
Length

Maximum
Length
50

12

12

100

100

Is
mandat
ory?

Other
Validation

Data
Type
Chara
cter

with special
characters

Numb
ers

only digits, no
characters

Numb
ers

only digits, no
characters
standard email
validations

Chara
cter

with special
characters

Page 63 of 71

O. MORE OF LEXUS

Description
Assumption&
Pre-Requisites
Functional
Requirement
Clarification/
Comments/
Suggestions

Allows users to access additional information on Lexus brand

1. This section will display content from content management system
based on More of Lexus content created by content Authors.
1. Same behavior as in www.lexus.com , need to the more of Lexus.
New page, external link.

Page 64 of 71

P. INTERACTIVE ONLINE CHAT

Description
Assumption&
Pre-Requisites

Allows users to chat with Customer Service Agents

1. Will covered in Phase 2

Functional
Requirement
Clarification/
Comments/
Suggestions

TBD**

Q. MAGAZINE
Description
Assumption&
Pre-Requisites

Allows users to view and download eMagazine on Lexus

1. Will covered in Phase 2
2. The format of the magazine is pdf and on clicking the link it will open a
new window with the pdf

Functional
Requirement
Clarification/
Comments/
Suggestions

Page 65 of 71

2.8

OTHER REQUIREMENTS
A. GENERAL REQUIREMENTS

Description
Assumption&
Pre-Requisites
Functional
Requirement
Clarification/
Comments/
Suggestions

2.9

Describe the other/general requirements

1. In the database design we need to capture what page the data has
been captured from.

1. Add a link in all pages where info is being captured to register users
for Newsletter.

SECURITY REQUIREMENTS
A. SECURITY REQUIREMENTS

Description
Assumption&
Pre-Requisites
Functional
Requirement

Describe the Security requirements of the website

1. Users should not be able to tamper with corporate content.

2. Workflow should be designed to take care of the Admin user access
aspects.

Clarification/
Comments/
Suggestions

2.10 NON FUNCTIONAL REQUIREMENTS

B. NON FUNCTIONAL REQUIREMENTS
Description
Assumption&
Pre-Requisites
Functional
Requirement
Clarification/
Comments/

Describe the Non Functional requirements of the website

These requirements shall be elaborated in the Addendum to this functional

specification.

Page 66 of 71

Suggestions

1. REPORTS
Please refer to Annexure 5.1 for more details
2. USER ACCEPTANCE CRITERIA
This would be documented in the over-arching Project Management Plan
3. CHANGES TO OTHER SYSTEMS
Such instances shall be documented in the Addendum to this Functional Specification
4. NON FUNCTIONAL REQUIREMENTS
These requirements shall be elaborated in the Addendum to this functional
specification.
5. APPENDICES
5.1 APPENDIX

Back Ground Image

We propose 3 alternate solutions to address this technical requirement:
Option 1: The author will upload the background image along with the product image. This will allow the
author to change the background image to best fit the new product.
Option 2: Each product will has its portal page. Each portal page may be configured to have a different
style (CSS files, colors) for the whole page components (menus, header, footer). The advantage of this
option is that the whole page style will change to suit the background color.
Option 3: The author will choose from a predefined set of background images to suit the product color.
The advantage is that the author does not have to upload background image for each product.
Each of the alternate solutions needs to be weighed against its benefits viz-a-viz ease of use and
implementation. Therefore we recommend that the final design be jointly arrived at with business team;
and documented subsequently in the Addendum to this Functional Specification.
Reference: Section 2.1.f
Comments from Business:

Page 67 of 71

E-Brochure
We have a high level understanding of this business requirement. Detailed design would be documented
in the Addendum to this Functional Specification once the implementation team reviews the wire-frames
and/or mock-ups submitted by business team.
As per the discussion the E-brochure format is the PDF. In future it might get change to flash or flip
content. Business team will get back on this.

Reference: Section 2.3.e

Comments from Business:

Benefits
We have a high level understanding of this business requirement. Detailed design would be documented
in the Addendum to this Functional Specification once the implementation team reviews the wire-frames
and/or HTML mock-ups submitted by business team.
Reference: Section 2.4.b
Comments from Business:

Warranty
We have a high level understanding of this business requirement. Detailed design would be documented
in the Addendum to this Functional Specification once the implementation team reviews the wire-frames
and/or mock-ups submitted by business team.
Reference: Section 2.4.e
Comments from Business:

Contact us
We have a high level understanding of this business requirement. Detailed design would be documented
in the Addendum to this Functional Specification once the implementation team reviews the wire-frames
and/or mock-ups submitted by business team.
Reference: Section 2.6.j

Page 68 of 71

Comments from Business:

Media
We have a deep understanding of business requirement and shall revert with workflow alternatives to
achieve functionality in the Addendum to this Functional Specification.
Reference: Section 2.7.k
Comments from Business:

Browser Support
The following browsers are supported viz. Internet Explorer, Mozilla Firefox and Google Chrome.
Recommended versions: Internet Explorer 8.0. Mozilla Firefox 3.6 and Google Chrome 8.
The version that needs to be supported will be jointly discussed with business team. This section shall
then documented in Addendum to this Functional Specification.
Portal 7.0 supports Safari 4.0 , Lexus site can support Safari 4.0 not 5+

Reference: Section 2.10.b

Comments from Business:

Reporting and Analytical Support

We have a high level understanding of your Reporting & Analytics requirements viz.
1. Web Server analytics (E.g. where the traffic came from etc.)
2. Site related analytics (How many pages the user visited on the site etc.)
3. ERMS (Email Response Management System ) related capabilities and reporting (e.g. bounce related
reports)
We are currently evaluating the product capabilities to support the above 3 requirements. The same will
be shared with business team and will jointly design the functionalities that shall be deployed. The design
shall be documented in Addendum to this Functional Specification.
Reference: Section 1
Comments from Business:

Page 69 of 71

Customer Suggestions & Customer Help

This requirement needs to be jointly discussed and documented in the Addendum to this Functional
Specification
Reference: No reference
Comments from Business:

2.3 H Offers
In the product details pages contains the promo boxes, if particular model has the offer, this offer should
be displayed in promos as static content, if user clicks on the offer promo, it takes the user to specific
offer page.
If particular model does not have any offer, random promotions should be displayed, it should be
dynamic. Content can change on page load.
This requirement is discussed and documented in the Addendum to this Functional Specification

Reference: No reference
Comments from Business:

2.6 C Search
Search functionality should be based upon the tags which admin user can add the tag along with content
when he is creating the content. Tag has the highest priority in search
This requirement is discussed and documented in the Addendum to this Functional Specification

Reference: No reference
Comments from Business:

Captcha
Catcha functionality discussed, GBM will provide the open source captcha which will be implemented in
server side.
This requirement is discussed and documented in the Addendum to this Functional Specification
Reference: No reference
Comments from Business:

Page 70 of 71

Friendly URLs
Business needs the friendly urls for the specific content in the model details page. Container should

have a separate link which should be user friendly. Admin team can able to create friendly URL
for the containers in the model specific page.
Reference: No reference
Comments from Business:

5.2 APPENDIX AFG WEB PORTAL USER ACCESS DETAILS

Each role will have a set of privileges. Based on the role the user is assigned, his/her
privileges will be decided. The template for this is shared below.

Power User

Standard
User

Privilege
A
B
C
D
E
F

X
X
X
X
X
X

X
X

X
X
X
X

X
X
X
X

X
X
X
X
X

Page 71 of 71