Sample FSD

Al Khor Community (AKC)
Website and Online Services

Functional Specifications
Version 1.0
Mar 09, 2015

This page is left blank intentionally for the double sided printing
Al Khor Community (AKC) Website and Online Services
Document Management & Version Control
Document Title: AKC - Website and Online Services - FSD
Document File Name: AKC - Website and Online Services – FSD.pdf
Issued By: Shahab Juman
Issue Date: 09th March 2015
Reviewed By: Ahmed Sweilem
Approved By: Ahmed Sweilem
Status: Final
Table 1 - Document Management
Date Version Author Remarks
25th February 2015 0.1.0 Shahab Juman Released first draft
26th February 2015 0.1.1 Ahmed Sweilem Reviewed and corrections as required
Addition Of following Section :-
 Master Page
02nd March 2015 0.2.0 Shahab Juman
 Page Layouts
02nd March 2015 0.2.1 Ahmed Sweilem Reviewed

 Site Structure & Navigation
 Home Page
 About Us
05th March 2015 0.3.0 Shahab Juman  News
 Services
 Facilities
 Calendar
 Safety
 Gallery
08th March 2015 0.4.0 Shahab Juman  Contact Us
 Member App
 Sitemap
08th March 2015 0.4.1 AKC Administrative Team Reviewed
Functional Specification I
Addition of following Sections :-

 Hosting and Infrastructure in
08th March 2015 0.4.2 Salahuddin Khatri
Azure
Completion of following Section :-
 Member app section
 Hosting and Infrastructure in
Azure
Addition of following Sections :-
 Membership & Club
09th March 2015 0.5.0 Shahab Juman
Registration
 Recreational Facility Booking
Process
 Banquet / Room Booking
Process
Review and approved Functional
09th March 2015 0.5.1 Kristina Leah How
sections
Fathi A. M. Abu Alam
09th March 2015 0.5.2 Bahaa Abou Kersh Review and suggested corrections
Mostafa Sedki
Modification in accordance to
09th March 2015 0.5.3 Shahab Juman
suggestions from QG IT Team
09th March 2015 0.5.4 Ahmed Sweilem Review and approved
09th March 2015 1.0.0 Shahab Juman Live

Table 2 - Document Version Control
Functional Specification II
Table of Contents
1 Introduction ................................................................................................................................................... 1
1.1 Purpose ............................................................................................................................................... 1
1.2 Scope .................................................................................................................................................. 1
1.3 Reference Documents .................................................................................................................... 1
1.4 Acknowledgement .......................................................................................................................... 2
2 Business Requirements .................................................................................................................................. 3
2.1 Executive Summary .......................................................................................................................... 3
2.2 Proposed Solution ............................................................................................................................. 3
2.3 Solution Overview ............................................................................................................................. 4
2.4 AKC Website and Online services ................................................................................................. 4
3 Branding ........................................................................................................................................................ 5
3.1 Brand Identification .......................................................................................................................... 5
3.2 Browser Specifications ..................................................................................................................... 5
3.3 GUI Templates (User Interface) ...................................................................................................... 5
3.3.1 Home Page ................................................................................................................................... 6
3.3.2 Member’s App Page Layout ...................................................................................................... 7
3.3.3 Safety Page ................................................................................................................................... 8
3.3.4 Inner Page Template ................................................................................................................... 9
3.3.5 Administrative Interface ............................................................................................................ 11
4 Master Page ................................................................................................................................................. 12
4.1 Header .............................................................................................................................................. 13
Functional Specification III

4.1.1 Top Navigation ........................................................................................................................... 13
4.1.2 Logo .............................................................................................................................................. 13
4.1.3 Login section ............................................................................................................................... 14
4.1.4 Search ........................................................................................................................................... 14
4.2 Footer ................................................................................................................................................ 16
4.2.1 Links Section................................................................................................................................. 16
4.2.2 Copyright Information ............................................................................................................... 16
5 Page Layouts ................................................................................................................................................ 17
5.1 Home Page Layout ........................................................................................................................ 17
5.1.1 Section .......................................................................................................................................... 18
5.2 Members App Page Layout ......................................................................................................... 19
5.2.1 Banner .......................................................................................................................................... 20
5.2.2 Breadcrumb ................................................................................................................................ 21
5.2.3 Left Navigation ........................................................................................................................... 21
5.2.4 Page Content ............................................................................................................................. 21
5.3 Safety Page Layout ........................................................................................................................ 22
5.3.1 Banner .......................................................................................................................................... 24
5.3.2 Breadcrumb ................................................................................................................................ 24
5.3.3 Section .......................................................................................................................................... 24
5.4 Inner Page Layouts ......................................................................................................................... 25
5.4.1 Banner .......................................................................................................................................... 28
5.4.2 Breadcrumb ................................................................................................................................ 29
Functional Specification IV
5.4.3 Left Navigation ........................................................................................................................... 29
5.4.4 Page Content ............................................................................................................................. 30
6 Site Structure & Navigation .......................................................................................................................... 31
6.1 Sitemap ............................................................................................................................................ 31
6.2 Navigation ....................................................................................................................................... 34
6.2.1 Top Navigation ........................................................................................................................... 34
6.2.2 Left Navigation ........................................................................................................................... 36
6.2.3 Footer Navigation ...................................................................................................................... 38
7 Home Page ................................................................................................................................................... 40
7.1 Sliding Banner Component .......................................................................................................... 41
7.2 News Component .......................................................................................................................... 42
7.3 Safety Component......................................................................................................................... 42
7.4 Events Component ........................................................................................................................ 43
7.5 Classes Component ....................................................................................................................... 43
7.6 Facebook Component ................................................................................................................. 44
7.7 Instagram Component .................................................................................................................. 44
7.8 Newsletter Subscription Component .......................................................................................... 44
7.9 Alert Messaging .............................................................................................................................. 44
8 About Us ...................................................................................................................................................... 45
8.1 Policies & Forms ............................................................................................................................... 46
8.2 Projects ............................................................................................................................................. 47
8.2.1 Project Listing ............................................................................................................................... 47
Functional Specification V
8.2.2 Project Detail ............................................................................................................................... 48
9 News ............................................................................................................................................................ 49
9.1 News Listing ...................................................................................................................................... 50
9.2 News Detail ...................................................................................................................................... 51
9.3 Safety News ..................................................................................................................................... 51
9.4 Archives ............................................................................................................................................ 52
10 Services ........................................................................................................................................................ 53
10.1 Events ................................................................................................................................................ 55
10.1.1 Event Listing ............................................................................................................................. 56
10.1.2 Event Detail ............................................................................................................................. 57
10.2 Classes .............................................................................................................................................. 58
10.2.1 Classes Listing .......................................................................................................................... 58
10.2.2 Classes Detail .......................................................................................................................... 59
11 Facilities ....................................................................................................................................................... 60
12 Calendar ....................................................................................................................................................... 62
13 Safety ........................................................................................................................................................... 64
13.1 Safety News Component .............................................................................................................. 65
13.2 Campaign Component ................................................................................................................ 65
13.3 Tips Component.............................................................................................................................. 66
13.4 Memos .............................................................................................................................................. 67
14 Gallery ......................................................................................................................................................... 68
14.1 Photo Album Page ......................................................................................................................... 69
14.2 Photo Listing Page .......................................................................................................................... 70
Functional Specification VI
14.3 Photo Detail Page .......................................................................................................................... 71
15 Contact Us .................................................................................................................................................... 72
15.1 Contact Information ...................................................................................................................... 72
15.2 Feedback ......................................................................................................................................... 72
16 Member App ................................................................................................................................................ 73
16.1 Profile................................................................................................................................................. 73
16.2 Booking ............................................................................................................................................. 73
16.2.1 Recreational Facility booking .............................................................................................. 73
16.2.2 Banquet / Room Function booking .................................................................................... 73
16.3 Club Rules & Regulation ................................................................................................................ 74
16.4 Policies & Forms ............................................................................................................................... 74
17 Membership and Club Registration .............................................................................................................. 75
17.1 Website Registration Form ............................................................................................................ 76
17.2 Edit Profile Form ............................................................................................................................... 76
17.3 AKC Club Registration Form ......................................................................................................... 77
17.4 Duplicate Card Request Form ..................................................................................................... 77
18 Recreational Facility Booking Process .......................................................................................................... 78
18.1 User Roles ......................................................................................................................................... 78
18.2 Key Features .................................................................................................................................... 78
18.3 Booking Workflow ........................................................................................................................... 79
18.4 Cancellation Workflow .................................................................................................................. 80
18.5 Request Status ................................................................................................................................. 80
Functional Specification VII

19 Banquet / Room Booking Process ................................................................................................................ 81
19.1 User Roles ......................................................................................................................................... 81
19.2 Key Features .................................................................................................................................... 81
19.3 Booking Workflow ........................................................................................................................... 83
19.4 Cancellation Workflow .................................................................................................................. 84
19.5 Request Status ................................................................................................................................. 85
20 Sitemap ........................................................................................................................................................ 86
21 Assumptions ................................................................................................................................................ 87
22 Out of Scope ................................................................................................................................................ 89
23 Appendix A Browser Support ....................................................................................................................... 90
23.1 Browser Support Matrix .................................................................................................................. 90
23.2 Known Limitations ........................................................................................................................... 91
24 Appendix B EWCM ....................................................................................................................................... 94
24.1 Add CEWP to Page ........................................................................................................................ 94
24.2 Add Content to CEWP .................................................................................................................. 95
24.3 Format Content in CEWP .............................................................................................................. 97
24.4 Configure Common Properties of Web Part ............................................................................. 98
24.4.1 Appearance ........................................................................................................................... 98
24.4.2 Layout ....................................................................................................................................... 98
24.4.3 Advanced ............................................................................................................................... 99
25 Appendix C Document Management .......................................................................................................... 101
25.1 SharePoint Library .........................................................................................................................101
25.2 Types of Libraries ...........................................................................................................................101
Functional Specification VIII

25.3 Create Document Library ...........................................................................................................103
25.4 Add Documents to Library..........................................................................................................105
25.5 Delete Document Library............................................................................................................106
25.6 Restore Document Library ..........................................................................................................107
26 Appendix D Hosting and Infrastructure in Azure ........................................................................................ 108
26.1 Azure virtual machines (IaaS) .....................................................................................................108
26.1.1 Azure Affinity Group .............................................................................................................109
26.1.2 Azure Availability Set ...........................................................................................................109
26.1.3 Storage Accounts ................................................................................................................110
26.1.4 Azure Load Balancing of VMs............................................................................................111
26.1.5 Virtual Machine End Points in Azure .................................................................................111
26.2 Azure Virtual Network ..................................................................................................................112
26.2.1 DNS settings of Virtual Network..........................................................................................112
26.2.2 Point to Site VPN ...................................................................................................................113
26.3 Cloud Services for Virtual Machines .........................................................................................113
26.4 Dedicated Internal IPs .................................................................................................................113
26.5 Reserved IPs ...................................................................................................................................114
26.6 Active Directory Domain Controller ..........................................................................................114
26.7 System Center Data Protection Manager ...............................................................................114
26.8 System Center Operations Manager........................................................................................114
26.9 SharePoint Infrastructure Planning ............................................................................................115
26.9.1 Physical Topology .................................................................................................................115
Functional Specification IX
26.9.2 Server Planning .....................................................................................................................116
27 Appendix E AKC E-Forms ............................................................................................................................ 117
28 Appendix F Document Approval ................................................................................................................. 118
Functional Specification X
1 Introduction
1.1 Purpose
This document contains the functional specifications for the required solution that ‘Qatar
Datamation Systems’ (herein after referred as QDS) is proposing for ‘Al Khor Community’ (herein
after referred as AKC) under ‘Qatar Gas Operating Company Limited’ (herein after referred as
QG). The solution described in this document was devised after a series of requirement gathering
meetings between representatives of QDS and AKC / QG.
Once this document is approved by AKC / QG, it will serve as the definitive statement of scope
and requirements for the Website and Online services. Any modifications or changes to the
requirements after document sign off will be handled via change control procedures.
1.2 Scope
The solution described in this document covers all the specifications of the required Website and
Online services. It majorly describes:
 Design of the website

 Provide easy access for website members / visitors to latest information
 Registration process for website membership
 Banquet / Room Booking process
 Recreational facility booking process
 Easy to use administrative and end-users interface
 QDS will deploy the required SP 2013 farm to serve this solution. Please refer to Appendix D
Hosting and Infrastructure in Azure for a detailed Infrastructure SOW.
1.3 Reference Documents
No. Title Type Date Issued by
1 LTC-C-ITD-1596-14 pdf 07-09-2014 Qatar Gas

QDS - QatarGas - AKCWebsite - Technical
2 docx 29-09-2014 Naveed Bajwa
Proposal v1 0
QatarGas_AKC Website_Minutes of
3 pdf 05-02-2015 Ahmed Sweilem
Meeting_20150205
QatarGas_AKC Website_Project
4 mpp 09-02-2015 Ahmed Sweilem
Schedule_20150209
Functional Specifications 1
5 Meeting Minutes - QatarGas - AKCWebsite docx 11-02-2015 Shahab Juman

6 docx 12-02-2015 Shahab Juman
Meeting_20150212
Meeting_20150216
Meeting_20150219
Meeting_20150304
Meeting_20150309
11 AKC Website Metadata xlsx 09-03-2015 Shahab Juman
Table 3 - Reference Documents
1.4 Acknowledgement
QDS is extremely thankful to Mr Klaus Tiel, Miss Kristina Leah How, Miss Seth Lospe, Mr Fathi A. M.
Abu Alam, Mr Bahaa Abou Kersh and Mr Mostafa Sedki for their valuable efforts and contribution
in the completion of requirements gathering phase.
2 Business Requirements
2.1 Executive Summary
Al Khor Community is a safe and vibrant environment where residents enjoy a variety of leisure
and recreational facilities. The current AKC website has proven to be incredibly popular since its
launch in 2010; however, the used system has a number of limitations and is unable to cater to the
high volumes of usage now encountered. This has caused the site to crash, be very slow and
labour intensive. In addition, the current site has limited features and lack of security controls,
which appears to be not dynamic and amateur. Hence, Al Khor Community has decided that
the Website should be upgraded with advanced features to reflect the image of Qatargas and
RasGas housing Community.
The business requirement is to create an all new Community website with advanced
features such as online booking systems and a fully interactive site which is user friendly and caters
to the high numbers of users (currently more than 20,000 per month and increasing). The site
should reflect the image which Qatargas (the largest LNG Company in the world) and RasGas
would like to portray. The site should be an information platform for AKC internal and external
stakeholders and customers to receive important information on the Community as well as vital
notices and HSE information.
2.2 Proposed Solution
The aim of this solution is to implement a website for Al Khor Community that will:
 Serve as a user friendly gateway to service provided by AKC for their members and also
information provided by AKC for their member and other external users.
 Allow ease of maintenance and content update.
 Provide effective security controls over information.
 Cater to high number of users.
 Reflect the image of QatarGas and RasGas housing community.
To fulfil these requirements, our proposed solution is based on SharePoint 2013 and Windows Azure
hosting services that will be used to develop the new Al Khor Community Website. The internet
portal will provide information to the AKC members / public and offer a set of online services to
the AKC member only.
2.3 Solution Overview
The main points for implementation are:
 SharePoint 2013 Installation and farm Implementation on Windows Azure Environment,

which include development/UAT environment and Production environment.
 Creating main website along with the branding
 Creating membership database for authentication and which would serve as base
database for future systems.
 Automate Recreational Facility booking process and Banquet / Room Booking process
with state machine workflows.
The proposed solution discussed in this document uses Microsoft Office SharePoint Server 2013 as
the application platform. This solution will use Microsoft SQL Server 2012 as the database engine.
There are no third party applications or add-ons required in the current proposed solution.
2.4 AKC Website and Online services
The purpose of this website is create an information platform for AKC internal and external
stakeholders and member of the website should receive important information on the Community
as well as vital notices and HSE information. Website should also cover online services such as
online booking systems, there would be provision of adding more online services in future, if
required. Website would be fully interactive which is user friendly and caters to the high numbers
of users. The site should reflect the image which Qatargas (the largest LNG Company in the world)
and RasGas would like to portray. Website should be multi-lingual supported but for now it would
be developed only for English content, anyhow support would be added for other languages.
3 Branding
3.1 Brand Identification
User interface of the portal will be customized to comply with branding & design guidelines
provide in tender document. A consistent user experience will be ensured by managing the
master page and page layouts along with the logo. UI specifications are discussed in detail in their
respective sections.
3.2 Browser Specifications
Following browser specifications will apply:
Ideal resolution 1024 x 768
Behaviour Responsive
Target browser Internet Explorer 8 or Higher, Mozilla Firefox, Chrome & Safari
For details see please refer Appendix A Browser Support.
Table 4 - Browser Specification
3.3 GUI Templates (User Interface)
Below are the snapshots of the Website Home and Inner pages, approved with consensus of AKC.
Each section will be discussed detail in the forthcoming sections.
3.3.1 Home Page
Home page of AKC website will use template depicted below, details would be discussed in later
section:
Figure 1 - Home Page Template
3.3.2 Member’s App Page Layout
Member’s App Page will use template depicted below, details would be discussed in later section:
Figure 2 - Member's App Page Template
3.3.3 Safety Page
Safety Page will use template depicted below, details would be discussed in later section:
Figure 3 - Safety Page Layout Template
3.3.4 Inner Page Template
Every content page other than Home Page, Safety Page and Member’s App Page will use inner
page template, there are two inner page templates, one with Left Navigation and other without
it. Examples of both template are below, details would be discussed in later section:
Figure 4 - Inner Page Template with Left Navigation
Figure 5 - Inner Page Template without Left Navigation
3.3.5 Administrative Interface
Default administrative interface of SharePoint 2013 will be used. No customizations will be done to
this interface. This includes all site components (including lists and libraries) being managed
directly by the AKC administration team. A sample snapshot of the default interface for managing
lists is given below.
Figure 6 - Administrative Interface
4 Master Page
Usage of master page will provide for a consistent format (look & feel) throughout the portal.
Master Page will include header and footer along with any other common components that
should be available to each page. Both the header and the footer of AKC Website will be clearly
defined and separated from the rest of the content. They will be present consistently throughout
the portal. Consistency will help users familiarize with the website easily and make navigation
easier for them.
Figure 7 - AKC Website Master Page
4.1 Header
The header will contain following information.
Figure 8 - AKC Website Master Page Header
4.1.1 Top Navigation
Figure 9 - Top Navigation
Top horizontal bar menu will be provided as the universal/primary website navigation method. It
will be located on top of all pages in the website. For details ease refer Top Navigation.
4.1.2 Logo
Figure 10 - AKC Website Logo
This section would show Al Khor Community Logo, which would be dynamic and training would
be provided to AKC administration team on how to change this logo, if required.
4.1.3 Login section
Figure 11 - Login Section
This section would contain username textbox and password textbox along with a button. If a
particular visitor is member of the website and wish to login to avail facility that are there for
members only, that user need to key in username and password that was provided by portal on
registration. On successful authentication username and password textboxes would be replaced
with Name and thumbnail image of logged in user.
4.1.4 Search
Figure 12 - Search
Search Box will be used to provide search functionality. User can enter the text to be searched
and press Enter. Search will be implemented using out of the box SharePoint search features and
will be applicable to website content. Documents can also be searched provided the user has
permissions. Searching will be provided in docx, pptx and xlsx files and text based PDF files. Search
for scanned PDF and OCR based search is not covered as part of this scope. Search results will be
displayed in a new page, displaying top 10 results as per search relevance and option to paging
if there are more than 10 results returned.
The below image illustrate the results page:
Figure 13 - Search Result Illustration
All results will be security trimmed and on permissions based. Application will search from overall
site content. Choosing any public pages like News / Announcements details etc. will redirect user
to respective pages with Portal theme.
Note: This is just an illustration on search functionality, above mentioned result page would be brand in compliance with
approved design of the portal.
4.2 Footer
The footer will contain following information.
Figure 14 - AKC Website Master Page Footer
4.2.1 Links Section
Figure 15 - Footer Link Section
Within footer, there will be fix space for links, for details please refer Footer Navigation
4.2.2 Copyright Information
Figure 16 - Copyright Information
Copyright Information will be available in footer aligned at centre.
5 Page Layouts
5.1 Home Page Layout
Below depicted image is sample of AKC website Home Page.
Figure 17 - Home Page Sample
Apart from Master page components defined in Master Page section, there will be dedicated
space for Home Page components. As shown below, two columns approach has been chosen
for website by AKC team. Regarding dimension of columns, height of both columns will be exactly
same however portion of width will be different as per the design.
Column 01 will have two sections and Column 02 will have six sections. Dimension of every section
will be fixed in layout, so placing a component in any section should meet height and width of
respective section.
Figure 18 - Home Page Layout
5.1.1 Section
The marked area in page layout as sections would be dedicated area to place different
components using webparts.
5.2 Members App Page Layout
Below depicted image is sample of AKC Member App Page.
Figure 19 – Member App Page Sample
There will be dedicated space for Member App Pages components. Member App pages would
have three rows. Row 01 would contain page banner, Row 02 would contain breadcrumb while
Row 03 would contain two columns. Column 01 would contain left navigation and Column 02
would contain page content.
Figure 20 - Member App Page Layout
5.2.1 Banner
Figure 21 - Member App Page Banner
This section would show banner, this banner would be specific for each member app page, which
would be pulled from page’s metadata.
5.2.2 Breadcrumb
Figure 22 - Member App Breadcrumb
It will allow users to keep track of their locations within the portal. All nodes of Breadcrumb will be
clickable for navigation.
5.2.3 Left Navigation
Figure 23 - Member App Left Navigation
This section on member app pages would contain left navigation, for details on left navigation
please refer Left Navigation.
5.2.4 Page Content
Figure 24 – Member App Page Content
This section would be dedicated area to place different components using webparts, in some
pages this section would be used to display page content directly.
5.3 Safety Page Layout
Below depicted image is sample of AKC Safety Page.
Figure 25 – Safety Page Sample
There will be dedicated space for Safety Page components. Safety page would have three rows.
Row 01 would contain page banner, Row 02 would contain breadcrumb while Row 03 would
contain two columns. Each column would contain two sections.
Figure 26 - Safety Page Layout
5.3.1 Banner
Figure 27 - Safety Banner
This section would show banner, this banner would be specific to safety page, which would be
pulled from page’s metadata.
5.3.2 Breadcrumb
Figure 28 – Safety Breadcrumb
clickable for navigation.
5.3.3 Section
The marked area in page layout as sections would be dedicated area to place different
components using webparts.
5.4 Inner Page Layouts
There would be 2 page layouts for inner pages, below depicted image is sample of AKC Inner
Page with Left Navigation.
Figure 29 – Inner Page with Left Navigation Sample
While below depicted image is sample of AKC Inner Page without Left Navigation.
Figure 30 - Inner Page without Left Navigation Sample
There will be dedicated space for Inner Pages components. Inner pages with Left Navigation
would have three rows. Row 01 would contain page banner, Row 02 would contain breadcrumb
while Row 03 would contain two columns. Column 01 would contain left navigation and Column
02 would contain page content.
Figure 31 - Inner Page with Left Navigation Layout
Inner pages without Left Navigation would also have three rows. Row 01 would also contain page
banner, Row 02 would also contain breadcrumb while Row 03 would contain page content.
Figure 32 - Inner Page without Left Navigation Layout
5.4.1 Banner
Figure 33 – Inner Page Banner
This section would show banner, this banner would be specific for each inner page, which would
be pulled from page’s metadata and this section would be in both inner page layouts.
5.4.2 Breadcrumb
Figure 34 – Inner Page Breadcrumb
clickable for navigation and this section would be in both inner page layouts.
Figure 35 – Inner Page Left Navigation
This section on inner pages would contain left navigation for that particular section and this section
would be present only in Inner Page Layout with left Navigation, for details on left navigation
please refer Left Navigation.
5.4.4 Page Content
Figure 36 – Inner Page Content
This section would be dedicated area to place different components using webparts, in some
pages this section would be used to display page content directly and this section would be in
both inner page layouts but width would differ as in inner pages without left navigation content
will utilize 100% of width while in other case width would be share by left navigation.
6 Site Structure & Navigation

6.1 Sitemap
Following is the hierarchy of sitemap.
 Home
 About Us
Director’s Note
AKC History
Policies & Forms
Projects
AKC Social Responsibility
FAQs
Maps
 News
News
Safety
Archive
 Services
Safety
Admin & Contracts
Security
Housing
Maintenance
Landscaping
Transport
 Bus Timetable
Environment
Events
Classes
 Facilities
General Facilities
 Lucy’s Beauty Salon
 Barber Shop
 Ladies Days & Evenings
 Societies, Committees
 Medical & Dental Center
 Bank Office and ATM
 Grocery Shops
 Mosques
 Library
 Teddy Bear Club
Sports Facilities
 Aerobics Room
 Gymnasium
 Outdoor Volleyball Court
 Snooker Room
 Squash Court
 Tennis Court
 Badminton Court
 Football Field
 Astro Turf
 Outdoor Basketball Court
 Recreation Area
 Sports Hall
 Swimming Pools
 Table Tennis Room
Schools
Medical & Dental
 Laboratory
 Pharmacy
 Specialized Clinics
 Dental Services
Banqueting & Conferencing
Club
 Al Waha Club
 Al Dhakhira Club
 Al Nakheel Club
 Youth Club
Restaurant
 Fountain Bleu
 Menu
 Cafe De Paris
 Menu
 La Veranda
 Menu
 Birds of Paradise
 Menu
 The Olive Grove
 Menu
 Calendar
 Safety
 Gallery
 Contact Us
Contact Information
Feedback (Website feedback for all users)
 Members
Profile
Online Booking
 Recreational Facility Booking
 Banquet / Room Booking
*Suggestion / Feedback (AKC feedback for members only)
*Order Form for a Photo (Linked to the Gallery)
*Online Souq
*Online Registration.
*Online Request.
Club Rules & Regulations
Policies & Forms
* Currently out of scope
6.2 Navigation
6.2.1 Top Navigation
Figure 37 - Site Structure Top Navigation
Top menu which would be presented at top of all pages would be universal, it would be 2 level of
navigation following is the illustration of second level item in top navigation.
Figure 38 - Site Structure Top Navigation Sub Menus
Following would be hierarchy of Top Navigation.
 Home
 About Us
 Director’s Note
 AKC History
 Policies & Forms
 Projects
 AKC Social Responsibility
 FAQs
 Maps
 News
 News
 Safety
 Archive
 Services
 Safety
 Admin & Contracts

 Security
 Housing
 Maintenance
 Landscaping
 Transport
 Environment
 Events
 Classes
 Facilities
 General Facilities
 Sports Facilities
 Schools
 Medical & Dental
 Banqueting & Conferencing
 Club
 Restaurant
 Calendar
 Safety
 Gallery
 Contact Us
 Contact Information
 Feedback (Website feedback for all users)
 *Members
 Profile
 Online Booking
 **Suggestion / Feedback (AKC feedback for members only)
 **Order Form for a Photo (Linked to the Gallery)
 **Online Souq
 **Online Registration.
 **Online Request.
 Club Rules & Regulations
 Policies & Forms
 Sitemap
* Would be visible to logged in users only
** Currently out of scope
Left navigation would be 2 level of navigation, it would be relative and would change according
to section on which user is currently standing at.
Sections Left Navigation Menu Items

 About Us
 Director’s Note
 AKC History
 Policies & Forms
About Us
 Projects
 AKC Social Responsibility
 FAQs
 Maps
 News
News  Safety News

 Archives
 Safety
 Admin & Contracts
 Security
 Housing
 Maintenance
Services
 Landscaping
 Transport (Bus Timetable)
 Environment
 Events
 Classes
 General Facilities
 Beauty Salon
 Barber Shop
 Ladies Days & Evenings
Facilities
 Societies, Committees
 Bank Office and ATM
 Grocery Shops
 Mosques
 Library
 Teddy Bear Club
 Sports Facilities
 Aerobics Room
 Gymnasium
 Outdoor Volleyball Court
 Snooker Room
 Squash Court
 Tennis Court
 Badminton Court
 Football Field
 Astro Turf
 Outdoor Basketball Court
 Recreation Area
 Sports Hall
 Swimming Pools
 Table Tennis Room
 Schools
 Medical & Dental
 Laboratory
 Pharmacy
 Specialized Clinics
 Dental Services
 Banqueting & Conferencing
 Clubs
 Al Waha Club
 Al Dhakhira Club
 Al Nakheel Club
 Youth Club
 Restaurants
 Fountain Bleu
 Cafe De Paris
 La Veranda
 Birds of Paradise
 The Olive Grove
Calendar No Left Navigation
Safety No Left Navigation
Gallery No Left Navigation

 Contact Information
Contact Us
 Feedback (Website feedback)
 Profile
 Bookings
 Recreational Facility Booking
 Banquet / Room Booking
 *Suggestion / Feedback (AKC feedback
for members only)
Member App  *Order Form for a Photo (Linked to the

Gallery)
 *Online Souq
 *Online Registration.
 *Online Request.
 Club Rules & Regulations
Sitemap No Left Navigation

Table 5 - Left Navigation Details
* Currently out of scope
6.2.3 Footer Navigation
Figure 39 - Site Structure Footer Navigation
Footer link would be pulled out from Top menu, only top most link would be shown here. Following
would be links available in footer navigation.
 Home
 About Us
 News
 Services
 Facilities
 Calendar
 Safety
 Gallery
 Contact Us
 *Members
 Sitemap
* Would be visible to logged in users only
7 Home Page
Below depicted image in will act as a new default landing area of AKC website. In this section of
the document, components placed on home page will be discoursed which will form the resulting
functionality available to the website visitors / members.
Figure 40 - Home Page
7.1 Sliding Banner Component
Figure 41 - Sliding Banner Component
In the top left corner of the home page of AKC website a Sliding Banner will be implemented with
moving images and clicking on that image will redirect to hyperlink associated in Banner’s Meta
data. Sliding Banner will show up to three images at a time.
Image Links, picture selection, redirection behaviour and target audience will be configurable by
Administrator of Portal, for details each field please refer “AKC Website Metadata.xlsx” excel file
and in that file “Sliding Banner” sheet. It should be responsibility of Administrator to upload images
with appropriate dimensions for better interface and performance. Content publishing workflow
will be implemented for this content. Whenever the new banner is published it will be available on
home page if target audience is matched for that user.
7.2 News Component
Figure 42 – News Component
Just below “Sliding Banner Component” there would dedicated section for “News Component”.
It will contain 4 latest active news based on “Date” metadata associated with news item, news
would filtered by “target audience” metadata associated with news item, regardless of whether
that news is Safety Related or not. Each news item displayed in this component would contain
“Thumbnail image”, “Title”, “Date” and “Description”. Read more would be a link that will take
user to news detail page. Size of the images will be predefined and it is responsibility of AKC to
upload the images of that predefined size to maintain image quality. For further details please
refer News.
7.3 Safety Component
Figure 43 – Safety Component
In the top right corner of the home page of AKC website there would be a dedicated section for
“Safety Component”. It consists of 3 latest active news based on “Date” metadata associated
with news item, news would be filtered by target audience metadata associated with news item,
it would only show safety related news. Each news item displayed in this component would
contain “Title” only. News title will be a link that will take user to news detail page. User can view
all safety related news by clicking “Read more” link. For further details please refer Safety News.
7.4 Events Component
Figure 44 – Events Component
Just below “Safety Component” there would dedicated section for “Events Component”. It will
contain 4 rotating latest active events based on “Date” metadata associated with event item,
only event that are selected to be shown on homepage with filtration by target audience
metadata associated with event item would be displayed in this component. Each event in this
this rotating event component would “Thumbnail image” and link to attached registration form.
Image will be a link that will take user to event detail page. Size of the images will be predefined
and it is responsibility of AKC to upload the images of that predefined size to maintain image
quality. For further details please refer Events.
7.5 Classes Component
Figure 45 - Classes Component
Just below “Event Component” there would be a dedicated section for “Classes Component”. It
consists of 3 latest active classes based on “Date” metadata associated with class item, only
classes that are selected to be shown on homepage with filtration by target audience metadata
associated with class item would be displayed in this component. Each class item displayed in this
component would contain “Title” only. Class title will be a link that will open a popup displaying
class poster. User can view all classes by clicking “Read more” link. For further details please refer
Classes.
7.6 Facebook Component
Figure 46 - Facebook Component
Just below “Classes Component” there would be a dedicated section for “Facebook
Component”. Script would be provided by AKC team.
7.7 Instagram Component
Figure 47 - Instagram Component
Just below “Facebook Component” there would be a dedicated section for “Instagram
Component”. Clicking “Alkhorcommunity” will show few images from instagram in a popup
window. Script would be provided by AKC team.
7.8 Newsletter Subscription Component
Figure 48 - Newsletter Subscription Component
Just below “Instagram Component” there would be a dedicated section for “Newsletter
Subscription Component”. On clicking the link “Receive Weekly Newsletter”, a popup windows
would prompt user to key in Email Address, There would be a list to keep these email addresses for
record, AKC would integrate some code to send bulk email to these addresses. For details of each
field in this list please refer “AKC Website Metadata.xlsx” excel file and in that file “Newsletter
subscription” sheet.
7.9 Alert Messaging
There would be a list where AKC administrator would use administrative interface to key in alerts.
These alerts would have target audience, if target audience matched for logged in user, a popup
window would prompt user to show that alert after logging in. For details of each field in this list
please refer “AKC Website Metadata.xlsx” excel file and in that file “Alerting” sheet.
8 About Us
Separate Site would be created for “About Us” section, to navigate to this section user can either
use Top Navigation or Footer Navigation, where clicking on “About Us” will take user to landing
page of this section, there would be following sub sections in about us
 About Us
 Director’s Note
 AKC History
 Projects
 AKC Social Responsibility
 FAQs
 Maps
Where all sub section would with be static contents except Policies & Forms and Projects,
description of which is stated below. Inner page with left navigation layout would be used for this
section, for details on page layout please refer Inner Page Layout. Left navigation would show
above stated sub sections.
8.1 Policies & Forms
Figure 49 - Policies & Forms
This section would be dedicated for users to download all active applications (e.g. club
membership and library card), Request forms (e.g. maintenance request), Feedback forms
(comments and suggestions), policies and rules & regulations documents. These items would be
available based on target audience set by AKC administrators on the metadata for these
document. There would be a dedicated document library to manage these document. For
details of each field in this list please refer “AKC Website Metadata.xlsx” excel file and in that file
“Policies & Forms” sheet.
8.2 Projects
8.2.1 Project Listing
Figure 50 - Project Listing
User needs to select project from “About Us” section’s left navigation, this will redirect user to
project listing page. All active project items filter by target audience will be displayed on this page.
Following will be the features of this page.
 Latest 5 items will showcase in a single display with facility of paging.

 Each item will contain thumbnail, title, date and description, along with a link “Read more”
 Clicking on “Read more” will redirect to respective content detail page.
 Paging will allow user to navigate back and forth to view all available published items.
 Only published, active items that fulfil target audience for that user will be available.
For adding new project, AKC Administration team need to fill in project metadata and upload
image separately in “Project Images” library with linking that particular image with a specific
project. For details of each field in this “Projects” list please refer “AKC Website Metadata.xlsx”
excel file and in that file “Projects” sheet, while for Project Images please refer same file’s “Project
Images” sheet.
8.2.2 Project Detail
Figure 51 - Project Detail
Information about a particular project item will be displayed on detail page. Following will be the
features of the detail page.
 Original sized Image, Title (as page heading and title), Date, Description and Content
along with any attachment will be displayed on the page.
 Project images’ thumbnail would be shown in image slider where clicking on an image
would open original size image in a popup.
 “Back” link will allow user to go to the last visited page in browser history.
 “Back to Top” link will allow user to go to top of the page without manually scrolling up.
9 News
Separate Site would be created for “News” section, to navigate to this section user can either use
Top Navigation or Footer Navigation, where clicking on “News” will take user to landing page of
this section, there would be following sub sections in news
 News
 Safety News
 Archives
Inner page with left navigation layout would be used for this section, for details on page layout
please refer Inner Page Layouts. Left Navigation of this section would show above mention sub
section.
To add/edit a News, a page layout will be provided. Title, description, Image, Date, content and
target audience will be configurable by Administrator of Portal, while adding a news administrator
need to select “For Safety” to mark that news as “safety related news”. Using the page layout,
users (with proper permissions) can create/edit News Pages. Content publishing workflow will be
implemented for this. Whenever the new news page is published it will be available on home
page of the website and on landing page of News section as well to user if target audience is
matched.
For details of each field please refer “AKC Website Metadata.xlsx” excel file and in that file “News”
sheet.
9.1 News Listing
Figure 52 - News Listing
This page would act as landing page of News section. All news filtered by target audience
matching for that user will be displayed on listing page. Following will be the features of the listing
page.

9.2 News Detail
Figure 53 - News Detail
Information about a particular News item will be displayed on detail page. Following will be the
9.3 Safety News
Safety news page would show news that were marked as safety related news, same news listing
page to be used with just one additional condition to filter out safety related news.
9.4 Archives
Figure 54 - News Archive
This page would be using news listing page with additional textboxes at the top, for selecting news
from archived records.
10 Services
Separate Site would be created for “Services” section, to navigate to this section user can either
use Top Navigation or Footer Navigation, where clicking on “Services” will take user to landing
page of this section, there would be following sub sections in services
 Safety
 Admin & Contracts
 Security
 Housing
 Maintenance
 Landscaping
 Transport (Bus Timetable)
 Environment
 Events
 Classes
Where all sub section would with static contents using inner page layout except Events and
Classes, description of which is stated below. Inner page with left navigation layout would be used
for this section, for details on page layout please refer Inner Page Layout. Left navigation would
show above stated sub sections.
Following is screen of inner page, an example of “Transport” page which is one of the sub section,
where sample content of transport is displayed along with an attached file link at the bottom, in
case no file has been attached inner page wouldn’t show any file
Figure 55 - Inner page content section
10.1 Events
Event list would be used to keep event records, where image, title, description, registration form,
location, category, start date, end date, content and target audience will be configurable by
Administrator of Portal. Content publishing workflow will be implemented for this. Whenever the
new event is published it will be available on home page if target audience is matched for that
user.
While adding an event, AKC administrator can select publish news, which would show news form
at the bottom of event form, which would facilitate AKC administration team to publish an event
and news for that event on single screen.
For details of each field please refer “AKC Website Metadata.xlsx” excel file and in that file
“Events” sheet.
10.1.1 Event Listing
Figure 56 - Event Listing
All events filtered by target audience matching for that user will be displayed on listing page.
Following will be the features of the listing page.

 Each event would be denoted with a colour legend, placed on left side of thumbnail
image. This legend would be used to classify events by their category.
 Legends association with categories would be shown at bottom of this page, which would
show that which category is denoted by a particular colour.
 There would be textboxes for start date and end date along with a dropdown for event
category, these field would be used to filter out events.
10.1.2 Event Detail
Figure 57 - Event Detail
Information about a particular event item will be displayed on detail page. Following will be the
 Event would be denoted with a colour legend, placed on left side of image. This legend
would be used to classify events by their category.
10.2 Classes
Classes list would be used to keep class records, where poster, title and target audience will be
configurable by Administrator of Portal. Content publishing workflow will be implemented for this.
Whenever the new class is published it will be available on home page if target audience is
matched for that user.
“Classes” sheet.
10.2.1 Classes Listing
Figure 58 - Classes Listing
All classes filtered by target audience matching for that user will be displayed on listing page.
Following will be the features of the listing page.

 Each item will contain poster’s thumbnail and title, where thumbnail would act as a link.
 Clicking on poster’s thumbnail will open respective content detail page in a popup
window.
10.2.2 Classes Detail
Figure 59 - Classes Detail
Poster for a particular class item will be displayed on popup as class detail, when a class title is
clicked from home page or poster’s thumbnail is click from classes listing page. Following will be
the features of the detail page.
 Original sized poster and Title (Popup title) would be displayed in this popup window.
11 Facilities
Separate Site would be created for “Facilities” section, to navigate to this section user can either
use Top Navigation or Footer Navigation, where clicking on “Facilities” will take user to landing
page of this section, there would be following sub sections in facilities
 General Facilities
 Beauty Salon
 Barber Shop
 Ladies Days & Evenings
 Societies, Committees
 Bank Office and ATM
 Grocery Shops
 Mosques
 Library
 Teddy Bear Club
 Sports Facilities
 Aerobics Room
 Gymnasium
 Outdoor Volleyball Court
 Snooker Room
 Squash Court
 Tennis Court
 Badminton Court
 Football Field
 Astro Turf
 Outdoor Basketball Court
 Recreation Area
 Sports Hall
 Swimming Pools
 Table Tennis Room
 Schools
 Medical & Dental
 Laboratory
 Pharmacy
 Specialized Clinics
 Dental Services
 Banqueting & Conferencing
 Clubs
 Al Waha Club
 Al Dhakhira Club
 Al Nakheel Club
 Youth Club
 Restaurants
 Fountain Bleu
 Cafe De Paris
 La Veranda
 Birds of Paradise
 The Olive Grove
Where all sub section would be static contents. Inner page with left navigation layout would be
used for this section, for details on page layout please refer Inner Page Layout. Left navigation
would show above stated sub sections. AKC Administrators team need to attach files with inner
page item if there is a need to provide a file for downloading, For example in Restaurants sub
section, each restaurant page would have a menu attached with its inner page so user can
download restaurant menu if required. In case no file has been attached inner page wouldn’t
show any file.
12 Calendar
Figure 60 - Calendar Component
Dedicated section would be created for calendar, inner page without left navigation layout
would be used for this section, for details on page layout please refer Inner Page Layouts. In this
section there would a single calendar component which would be linked to events, for detail
please refer Events. Following would be features of this page
 This calendar would show highlighted dates, if there is some event on that date.
 Highlighting would be done with a single colour, without any legend.
 Hovering on that date would showing event title with legends of event category.
 Clicking that date would open Event listing page, showing all events planned for that
particular date.
 Month could be changed from header of the calendar using (<) and (>) buttons.
 “View All” button would open Event listing page showing all events planned for that
particular month.
 Only published, active items that fulfil target audience for that user will be available on
calendar page and event listing page.
Following is the illustration of hovering balloon for calendar component
Figure 61 - Calendar Component Hovering Balloon
13 Safety
Dedicated section would be created for safety components, safety page layout would be used
for this section, for details on page layout please refer Safety Page Layout. In this section of the
document, components placed on safety page will be discoursed which will form the resulting
functionality available to the visitors / members for this section.
Figure 62 - Safety Page
13.1 Safety News Component
Figure 63 - News Component for Safety Page
In the top left corner of the Safety page of AKC website a there would dedicated section for
“Safety News Component”. It will contain 2 latest active news based on “Date” metadata
associated with news item with facility of paging, news would filtered by “target audience”
metadata associated with news item, it would only show safety related news. Each news item
displayed in this component would contain “Thumbnail image”, “Title”, “Date” and “Description”.
Read more would be a link that will take user to news detail page. Paging will allow user to
navigate back and forth to view all available published safety related news. Size of the images
will be predefined and it is responsibility of AKC to upload the images of that predefined size to
maintain image quality. For further details please refer Safety News.
13.2 Campaign Component
Figure 64 - Campaign Component
Just below “Safety News Component” there would dedicated section for “Campaign
Component”. It will contain 1 latest active campaign poster based on “Date” metadata
associated with campaign item with facility of paging, campaign would be filtered by “target
audience” metadata associated with campaign item. Each campaign item displayed in this
component would contain “poster’s thumbnail” only. Clicking on poster’s thumbnail will open
original sized poster in popup window. Paging will allow user to navigate back and forth to view
all available published campaigns. Size of the images will be predefined and it is responsibility of
AKC to upload the images of that predefined size to maintain image quality.
“Campaign” sheet.
13.3 Tips Component
Figure 65 - Tips Component
In the top right corner of the safety page of AKC website there would be a dedicated section for
“Tips Component”. It will contain 1 latest active Tip based on “Date” metadata associated with
Tip item with facility of paging, tips would be filtered by “target audience” metadata associated
with tip item. Each tip item displayed in this component would contain “Description” only. Paging
will allow user to navigate back and forth to view all available published tips.
For details of each field please refer “AKC Website Metadata.xlsx” excel file and in that file “Tips”
sheet.
13.4 Memos
Figure 66 - Memos Component
Just below “Tips Component” there would dedicated section for “Memos Component”. It will
contain 6 latest active memo documents on “Date” metadata associated with memo document
with facility of paging, memos would be filtered by “target audience” metadata associated with
memo document. Each memo displayed in this component would contain “Name” only. Clicking
on name will allow user to download that memo. Paging will allow user to navigate back and
forth to view all available published memos.
“Memos” sheet.
14 Gallery
There would a separate and dedicated section “Gallery” for maintaining and displaying photos,
uploaded AKC Administration team, inner page without left navigation layout would be used for
this section, for details on page layout please refer Inner Page Layouts. There would be 3 pages
for displaying these pictures “Photo Album Page”, Photo Listing Page” and “Photo Detail Page”
Picture Gallery list would be used to keep photo records, where image, title and target audience
will be configurable by Administrator of Portal. Content publishing workflow will be implemented
for this. Whenever the new image is published it will be available on “Gallery” section if target
audience is matched for that user.
For details of each field please refer “AKC Website Metadata.xlsx” excel file and in that file “Photo
Gallery” sheet.
14.1 Photo Album Page
Figure 67 - Photo Album
Any album containing images that matches with the target audience for that user will be
displayed on Photo Album page. Following will be the features of this page.
 Latest 16 albums will showcase in a single display with facility of paging.

 Each album would be showing first image, thumbnail, of that album framed where framed
thumbnail would act as a link.
 Clicking on framed thumbnail will open respective content detail page in a popup
window.
 Only album that contain published, active pictures that fulfil target audience for that user
will be available.
14.2 Photo Listing Page
Figure 68 - Photo Listing
Images on a particular album filtered by target audience matching for that user will be displayed
on photo listing page. Following will be the features of the listing page.

 Each item will contain image’s thumbnail and title, where thumbnail would act as a link.
 Clicking on image’s thumbnail will open respective content detail page in a popup
window.
14.3 Photo Detail Page
Figure 69 - Photo Detail
Image will be displayed on popup as photo detail page, when a thumbnail is click from photo
listing page. Following will be the features of the detail page.
 Original sized image and Title (Popup title) would be displayed in this popup window.
15 Contact Us
Separate Site would be created for “Contact us” section, to navigate to this section user can
either use Top Navigation or Footer Navigation, where clicking on “Contact us” will take user to
landing page of this section, there would be following sub sections in contact us
 Contact Information
 Feedback
Where contact information would be static contents while feedback would be a form to be used
by users for providing feedback of the website itself. Inner page with left navigation layout would
be used for this section, for details on page layout please refer Inner Page Layout. Left navigation
would show above stated sub sections.
15.1 Contact Information
Inner page with left navigation page layout would be used where contact information would be
set in page content metadata associated with the page. AKC Administrators team need to
update any information in the page content in page’s metadata directly, if required.
15.2 Feedback
There would a form to take user’s feedback on website, following would be the question that
would be in feedback form to take proper feedback:-
 Is this the first time you have visited the website?

 What is the primary reason you came to the site?
 Did you find what you needed?
 If you did not find any or all of what you needed, please tell us what information you were
looking for.
 Please tell us how easy it is to find information on the site.
 What is the likelihood that you will visit the website again?
 Please add any comments you have for improving the website. We welcome suggestions
on specific areas for improvements.
“Website Feedback” sheet.
16 Member App
Separate Site would be created for “Member App” section, to navigate to this section user can
either use Top Navigation or Footer Navigation and where clicking on “Member App” will take
user to landing page of this section, there would be following sub sections in member app
 Profile
 Bookings
 Recreational Facility Booking
 Banquet / Room Booking
 Club Rules & Regulations
Where club rules & regulation would be static contents while all other would be dynamic content.
Member app page layout would be used for this section, for details on page layout please refer
Members App Page Layout. Left navigation would show above stated sub sections.
16.1 Profile
Member app page layout would be used where profile of current logged in user would be display,
there would a button to edit profile which would open edit profile E-Form which would allow user
to update the profile. For details on this please refer Membership and Club Registration.
16.2 Booking
16.2.1 Recreational Facility booking
Member app page layout would be used where recreation facilities requests by logged in user
would be display, showing reference number, name of the facility, venue, Booking date and time
and status of the request. There would a button to add new request which would open
recreational facility request E-Form. For details on this please refer Recreational Facility Booking
Process.
16.2.2 Banquet / Room Function booking
Member app page layout would be used where banquet function requests by logged in user
would be display, showing reference number, name of the function, venue, function date and
time and status of the request. There would a button to add new request which would open
banquet function request E-Form. For details on this please refer Banquet / Room Booking Process.
16.3 Club Rules & Regulation
Member app page layout would be used where club rules & regulation would be set in page
content metadata associated with the page. AKC Administrators team need to update any
information in the page content in page’s metadata directly, if required.
16.4 Policies & Forms
This page would show exactly same content as policies & forms page in about us section but
page layout to be used for this page would be member app page layout with same left
navigation showing all member app sub sections. For details on content please refer Policies &
Forms.
17 Membership and Club Registration

AKC website would user to apply club registration online, book recreational facilities online and
book banquet functions online. To avail these functionalities along with viewing content published
for members only user must have account on the website to become member of AKC website.
For requesting account user must be eligible to become member, eligibility includes residents of
AKC who are employed at Qatar Gas, Ras Gas, Shell & Dolphin or contractors (where applicable)
and non-residents who are employed at Qatar Gas, Ras Gas and other 3rd parties.
AKC website would allow a self – registration process, there would be 2 website account, one for
employee and other one is for spouse of that employee, where applicable. If accounts for multiple
spouses are required, employee need to request AKC administration team manually.
AKC administration team can create bulk users by uploading excel data, provided that excel
data should database schema.
Club registration request could also be done while filling out website registration E-Form but there
would be separate form as well to request club registration in later stage if not requested at the
time of website registration.
For record management for membership and club registration there would be 5 lists that would
be used to keep data
 Employee Information
 Spouse Information
 Children Information
 Employee Workers Information
 Website Account
Where employee information would act as parent record for all remaining 4 lists, for details of
each field in these lists please refer “AKC Website Metadata.xlsx” excel file and in that file
respective sheet for that list. There would be 4 E-Forms
 Website Registration Form

 Edit Profile Form
 AKC Club Registration Form
 Duplicate Card Request Form
These forms would be interlinked and above mentioned lists would be used to store “employee’s
data”, “employee’s spouse data”, “employee’s children data”, “employee’s workers data”,
“website account data for employee & spouse of that employee” and “club registration data for
employee and dependents of that employee”.
For detail of fields available in each form from above mentioned lists please refer “AKC Website
Metadata.xlsx” excel file and in that file respective sheet for that list.
17.1 Website Registration Form
Page content without left navigation page layout would be used form to display website
registration form, for details on page layout please refer Inner Page Layouts. For illustration on look
and feel of the form please refer Appendix E AKC E-Forms. Following would be features of this form
 Creating employee profile along with employee’s spouse, children and workers
 Requesting club registration
 Requesting subscription of weekly newsletters
This form would go through 1 level approval, requestor would fill out the form and email would be
send to AKC administration team for approval. Once request is approved, email would be send
to requestor with account credentials. Comments field for both requestor and AKC administrative
team would be there in the form and workflow history would be provided to note time stamping
and comments.
17.2 Edit Profile Form
Page content without left navigation page layout would be used form to display edit profile, for
details on page layout please refer Inner Page Layouts. For illustration on look and feel of the form
please refer Appendix E AKC E-Forms. Following would be features of this form
 Updating employee profile along with employee’s spouse, children and workers. Spouse
would be allowed update information associated with spouse.
 Requesting subscription / un-subscription of weekly newsletters
This form wouldn’t go through any approval process.
17.3 AKC Club Registration Form
Page content without left navigation page layout would be used form to display AKC club
registration form, for details on page layout please refer Inner Page Layouts. For illustration on look
 Requesting club registration for employee, employee’s spouse, employee’s children and
employee’s worker.
to reception for card printing. Comments field for both requestor and AKC administrative team
would be there in the form and workflow history would be provided to note time stamping and
comments.
17.4 Duplicate Card Request Form
Page content without left navigation page layout would be used form to display duplicate card
request form, for details on page layout please refer Inner Page Layouts. For illustration on look
 Requesting duplicate card for clubs for employee, employee’s spouse, employee’s
children and employee’s worker.
to reception for card printing. Comments field for both requestor and AKC administrative team
would be there in the form and workflow history would be provided to note time stamping and
comments.
18 Recreational Facility Booking Process

Website members could make Recreational Facility booking requests online, E-Form for this
request would be placed in page content without left navigation page layout, for details on page
layout please refer Inner Page Layouts. For illustration on look and feel of the form please refer
Appendix E AKC E-Forms.
18.1 User Roles
User Action
Member  Initiate the request

 Cancel Booking
Operator  Can initiate the request on behalf of the user
 Do bulk Booking
 Edit Booking Details
 Cancel Booking
Approval  Approve bulk booking
Table 6 - User Roles for Recreational Facility Booking Process
18.2 Key Features
 Booking can be made in the same date depend on availability.

 Booking can be made 1 month in advance.
 Form can be submitted by the member or the Operator.
 If the member submitted the form the system will retrieve the user data from the employee
/ spouse list.
 If the Operator submits the form he needs to select the requested user from the Members
Database.
 If the requested user doesn’t exist in the database the operator will create a new account
for the user.
 One recreation facility for each request.
 User can have a maximum of two bookings at the same time.
 Bulk days booking can be done only by the club operator.
 Request can be cancelled by the user or the operator.
For details of Recreational Facility booking request’s metadata please refer “AKC Website
Metadata.xlsx” excel file and in that file “Recreational Facility Booking” sheet.
18.3 Booking Workflow
New Request
By Operator
No
Yes
Create a new
user account in No Requested User exist Get User Data
the Database in the Database By member Yes automatically
From Database
Yes
Select user from

Database
Fill the form
Fill the form
Declare
understanding the
Can request bulk club ruls
dates
Submit the form

Submit the form
No
Bulk Booking
Yes
Send to approval
Approved
No
Send Conformation
Yes
to the user
End
Figure 70 – Recreational Facility Booking Request Workflow
18.4 Cancellation Workflow
Cancelation
By Member or
Operator
Cancel request
Send notification
End
Figure 71 - Recreational Facility Booking Cancellation Workflow
18.5 Request Status
Status Description
In progress Operator initiate bulk request
Approved Request approved
Rejected Request rejected
Cancelled Request cancelled by Member or Operator

Table 7 - Recreational Facility Booking Request Status
19 Banquet / Room Booking Process

Website members could make Banquet / Room booking requests online, E-Form for this request
would be placed in page content without left navigation page layout, for details on page layout
please refer Inner Page Layouts. For illustration on look and feel of the form please refer Appendix
E AKC E-Forms.
19.1 User Roles
User Action
Member  Initiate the request

 Confirm the booking details
 Cancel Booking
Operator  Can initiate the request on behalf of the user
 Make booking arrangements (Room, Charges…)
 Edit Booking Details
 Cancel Booking
Approval  Approve the booking
 Approve cancelation
Preparer  Select distribution and additional arrangements.
Table 8 - User Roles for Banquet / Room Booking Process
19.2 Key Features
 Any booking must be made at least 72 hours prior to date of event.

 Private Booking can be made 1 month in advance.
 Company booking can be made 3 months in advance.
 Form can be submitted by the member or the Operator.
 If the member submitted the form the system will retrieve the data from the employee /
spouse list.
 If the Operator submits the form he needs to select the requested user from the Members
lists.
 If the requested user doesn’t exist in the database the operator will create a new account
to the user.
 If the booking request for a company he needs to provide the following information
 Department
 Organization
 Cost Center.
 User can select preferred venue.
 User will request the preferred Date and Time.
 Operator will send the Booking details which include:
 Available Date and Time
 One Room or more
 Charges.
 User can cancel the request, operator have to update the charges if charges will be
applied.
 If the request for company the operator needs to attach the invoice to the requested
form.
 If it’s a private booking, the Operator needs to update the booking request when the
payment is collected.
For details of banquet / room booking request’s metadata and please refer “AKC Website
Metadata.xlsx” excel file and in that file “Banquet & Room Booking” sheet.
19.3 Booking Workflow
By Operator
No
Yes New Request
Create a new Requested User

user account in No exist in the
the Database Database
Get User Data
By Member Yes automatically
From Database
Yes
Select user from

Fill the form
Database
Declare
Fill the form understanding the
club ruls
Provide:
Company
 Department Payment Cash or
Company Or Private
 Organization Credit
Private
 Cost Center
Submit the Form
Operator review
Notify the user No and approve the
request
Yes
Operator sending No
booking details to
the user
User Confirm
No Yes
Send to Approval
Approved
Yes
Send conformation
to the user
Send to Preparer
Select Distributuion
Notify Distribution
User Need to
Pay charges
Yes
Send Invoice Yes Company No Send to Use
No
No
Collected
Payment
Yes
End
Figure 72 - Banquet / Room Booking Request Workflow
19.4 Cancellation Workflow
Cancelation
Cancel booking
request by Member
or Operator
Request
Approved
allready
Yes
48 hours before the

date of function
Yes
No
Pay 50% of the

charges
Send to Operator
Send to Preparer
No Send to Approval
Notify Distribution Approved
Yes
No
Send to Preparer
Notify Distribution
User Need to
Pay charges
Yes
Send Invoice Yes Company No Send to Use
No No
Collected
Payment
End Yes
Figure 73 - Banquet / Room Booking Cancellation Workflow
19.5 Request Status
Status Description
In progress Member or Operator initiate the request

and waiting for Operator to revise the
booking details.
User confirmation Waiting for the confirmation from the user
Pending Approval Waiting for approval
Approved Request approved
Rejected Request rejected
Cancelled Request canceled by user or operator

Table 9 - Banquet / Room Booking Request Status
20 Sitemap
There would be a dedicated section for “Sitemap” which would show complete hierarchy of AKC
website, this will also reflect complete site structure implemented on SharePoint 2013, inner page
without left navigation layout would be used for this section, for details on page layout please
refer Inner Page Layouts. For details on the hierarchy of site structure to be shown on this section
please refer Sitemap.
21 Assumptions
In providing this document to QG, consultant team has made the following assumptions regarding
the Functional Specifications. These assumptions should be validated or correct with QG prior to
commencement of this development phase.
 This document along with scope of works / services section from the contract document
will override all verbal / written communications and reference documents made
between QDS and QG regarding requirements
 This document along with scope of works / services section from the contract document
forms the scope of the complete solution; changes to the scope will be handled through
Change Management Process. Time and cost effect of these changes will be agreed
mutually between QDS and QG.
 QG will ensure the availability of support and resources required for testing the system on-
site.
 QG will be responsible for providing the required H/W infrastructure on the agreed-upon
dates as agreed during the initial project schedule dated 09th February 2015. Any delay
on availing the H/W will directly impact the project delivery dates.
 QG will be responsible for providing the required software licenses (Microsoft SQL Server
2012 and SharePoint 2013) and will ensure that all necessary software licenses are in place
prior to the start of UAT and training.
 It is assumed that QG would configure their Email server to allow emails to be received
from AKC website, adding AKC email address to white list to avoid marking emails from
AKC website as spam emails.
 Installation of SharePoint 2013 and Microsoft SQL Server 2012 will be responsibility of QDS.
 It will be the responsibility of QG to provide the resources as per the project plan for the
timely completion of the project. Any delay in providing the agreed resources will directly
affect the project delivery timelines.
 For Supported Browser for application refer Appendix A Browser Support.
 It is the QG responsibility to provide content and images with specific size for the website
in electronic format. QDS will not be responsible for content generation and translation.
 The estimated number of working days is based on 8 hour per day.
 Obtaining of Digital Certificates, if any, is responsibility of QG.
 The project warranty will be void; if there will be any change in application codebase by
QG until the complete project handover.
 Any communication with vendors of existing applications, if any, will be done via QG.
 Functional Specification Document, other Documents and Trainings as part of deliverables
will be provided out in English.
22 Out of Scope
The following are considered out of scope of the project:
 Installation / configuration of any third party software which are not part of the scope.
 Any variation / deviation from this document along with scope of works / services section
in contract document will be out of scope. If any change is required, it will be taken up
through change management process.
 Integration with any other system that is not mentioned in Requirements Compliance
Matrix in Technical Proposal is out of scope.
 Content authoring will be responsibility of QG. QG would provide content in digital format,
while content publishing will be responsibility of QDS.
 Any kind of workflow development, other than those mentioned in this document, is out of
scope.
 QG would provide SSL certificate, while implementation/configuration of SSL will be
responsibility of QDS.
 No solution for document scanning will be provided.
 Anything not achievable by SharePoint branding & Theme will not be accomplished.
 Administration pages lying under “_layouts” folder will not be customized, if that
customization will violate Microsoft support.
 No Web service will be created for integration. Any web service required to complete any
integration functionality will be provided by QG.
23 Appendix A Browser Support
SharePoint 2013 supports several commonly used web browsers, such as Internet
Explorer, Google Chrome, Mozilla Firefox, and Apple Safari. However, certain web
browsers could cause some SharePoint 2013 functionality to be downgraded, limited, or available
only through alternative steps.
23.1 Browser Support Matrix
The following table summarizes the support levels of typically used web browsers.
Browser Supported Not supported
Internet Explorer 11 X
Google Chrome v X.X X
Mozilla Firefox v X.X X
Apple Safari v X.X X
Table 10 - Browser Compatibility Matrix
23.2 Known Limitations
Some functionality in SharePoint 2013 requires ActiveX controls. This produces limitations on
browsers which do not support ActiveX. Currently only 32-bit versions of Internet Explorer support
this functionality. All other browsers have the following limitations. Internet Explorer 10 does not
support Active X controls when in immersive mode. The functionality for the controls listed below
should only be expected to work in desktop mode.
DLL Supported browser Known

Plugin name What it does
Filename version limitations
Digital Dsigctrl.dll, Digital signing takes Internet Explorer An inability

Signature dsigres.dll place in both the versions 8, 9 and 10 to verify a
InfoPath client and on form
the InfoPath Forms produces
Services server. Make an error that
sure that the following states that
conditions exist: the form
Forms that are signed cannot be
on the client can be signed.
verified on the server.
Forms that are signed
on the server can be
verified on the client.
NameCtrl Name.dll Enables a web page to Supported in Internet

display a contact card Explorer versions 8, 9,
and presence status for and 10.
people. Integrates Firefox, Google
through client-side APIs Chrome are also
with Office 2013. supported by using a
plug-in.
Internet Explorer
version 10 immersive
mode is not
supported.
TaskLauncher Nameext.dll Used to export items in All browsers If software

a task list to Project requirement
Server if Project 2010 is s are not
installed on the client met, an
computer. error
message
states that
you need to
install
Project
Server.
SpreadSheetL Owssupp.dll Used to verify whether Internet Explorer If Excel is not

auncher Excel is installed for versions 8, 9, and 10 installed, an
Export to Excel feature. error
message
states that a
list cannot
be imported
because a
compatible
spreadshee
t
application
is not
installed or is
not
compatible
with the
browser.
StssyncHandler Owssupp.dll Enables Internet Explorer

synchronization of lists versions 8, 9, and 10
of events and lists of
contacts in SharePoint
with a messaging
application such as
Outlook 2013.
ExportDatabas Owssupp.dll Enables a user to use an Internet Explorer To export a

e application such as versions 8, 9, and 10 list, the
Access to create or client
open a database that computer
contains SharePoint list must have a
data. SharePoint
compatible
application.
OpenDocume Owssupp.dll Starts Office client All except Internet If a

nts applications so that a Explorer version 10 in compatible
user can create a immersive mode. Office
document or edit a application
document. Enables or browser is
users to create not installed
documents that are on a client,
based on a specified an error
template, open message
documents as read- states that
only, or open the feature
documents as requires a
read/write. SharePoint
compatible
application
and web
browser.
UploadCtl Stsupld.dll Enables drag-and-drop Internet Explorer

in SharePoint Server versions 8, 9, and 10
2013 visual mode
"upload multiple files"
dialog box.
CopyCtl Stsupld.dll Enables a user to copy Internet Explorer In Firefox,

a document on a versions 8, 9, and 10 Google
SharePoint site to one Chrome,
or more locations on a and
server. immersive
mode of
Internet
Explorer
version 10,
the copy
progress
dialog box is
not
displayed.
PPActiveX PPSLAX.dll Starts PowerPoint to Internet Explorer Does not

open presentations versions 8, 9, and 10 work on
from a slide library or Click-to-Run
publish individual slides installations
to a slide library. of Office
and version
of Office
that run on
Windows for
ARM.
BCSLauncher BCSLaunch. Starts the Visual Studio Internet Explorer

dll Tools for Office installer versions 8, 9, and 10
to install a Visual Studio
Tools for Office
package that has been
generated on the
server.
Table 11 - ActiveX Known Issues
24 Appendix B EWCM
The Content Editor Web Part (CEWP) is intended for adding content to a page which may include
formatted text, tables, hyperlinks, images, and Google maps etc.
24.1 Add CEWP to Page
1) From a page, in the ribbon, click the ‘Page’ tab, and then click the ‘Edit’ command.
Figure 74 - Edit Site Pages
Note: If the ‘Edit’ command is disabled, you may not have the permissions to edit the page. You need to contact your
administrator.
2) Click the ‘Insert’ tab, and then click ‘Web Part’ command.
Figure 75 - Insert Web Part
3) Under ‘Categories’ heading, select ‘Media and Content’ item. Then under ‘Web Parts’
heading select ‘Content Editor’ item.
Figure 76 – Content Editor Web Part
4) Click ‘Add’ button.
Figure 77 - Adding Web Part
Note: When you select a web part, information about the web part is displayed in ‘About the Web Part’ section.
24.2 Add Content to CEWP
There are three ways to add content to the CEWP.
1) Type content directly into the Web Part – To do this, point to the CEWP, click the down
arrow, and then click ‘Edit Web Part’. Once you are in Edit mode, you can type text
directly into the CEWP.
Figure 78 – CEWP; Typing Directly into Web Part
Note: Make sure your cursor is inside the text area for the CEWP.
2) Type content into the Web Part HTML Editor – To do this we need to turn to the ribbon.
First, make sure your cursor is inside the text area for the CEWP.
Figure 79 - CEWP; Typing Content into Web Part HTML Editor
Then go to the ‘Editing Tools  Format Text’ ribbon. Next, look for the HTML dropdown
in ‘Markup’ section.
3) Link to existing content by entering a hyperlink to a text file that contains HTML source
code – To do this, point to the CEWP, click the down arrow, and then click ‘Edit Web
Part’. In the tool pane, type the URL in the ‘Content Link’ text box.
Figure 80 - CEWP; Link to Existing Text
Note: The two valid hyperlink protocols that you can use are http and https. You can use an absolute URL or a relative
URL. However, you cannot use a file path.
24.3 Format Content in CEWP
You can format the content, typed directly into the CEWP, using the editing tools available from
the ribbon. To access these editing tools, from the Page tab, in the ribbon, click Edit. The ribbon
includes six groups of formatting options which are described in the table that follows.
No. Group Description
1 Font Use these tools to format selected text in the Web Part. You can
modify the font type, size, and color, make text bold or italicized,
highlight selected text, and strike through it, among other things.
2 Paragraph Use these tools to format selected paragraphs in the Web Part. You
can modify the alignment of the text, indent it, create a numbered
or bulleted list, and change the order in which information in the
paragraph is displayed.
3 Styles Apply a preformatted style to selected text. To preview a style, select
the text you want to format, and then drag your cursor over the style
option you want to preview.
4 Spelling Check the spelling of text on the page. This option is available only
when the spell checking feature is installed.
5 Layout Create or remove columns, headers, or footers on the page.
NOTE This option affects the entire page, not just the content in the
Content Editor Web Part.
6 Markup Use these tools to insert specific HTML elements into the content. You
can select a preformatted style from the Markup Styles drop-down
menu, or create your own by accessing the HTML Editor from the
HTML drop-down menu. You can also mark text as being in a specific
language.
Table 12 - CEWP; Content Formatting Groups
24.4 Configure Common Properties of Web Part
Web parts share a common set of properties that control their appearance, layout, and
advanced characteristics. You can change CEWP properties in the tool pane.
Note: For a specific Web Part, a Web Part developer may have chosen not to display one or more of these common
properties or may have chosen to create and display additional properties that are not listed below in the Appearance,
Layout, and Advanced sections of the tool pane. To see the advanced section in the tool pane, you must have
appropriate permission. Some permission and property settings may disable or hide Web Part properties.
24.4.1 Appearance
No. Property Description
1 Title Specifies the title of the Web Part that appears in the Web Part
title bar.
2 Height Specifies the height of the Web Part.
3 Width Specifies the width of the Web Part.
4 Chrome State Specifies whether the entire Web Part appears on the page
when a user opens the page. By default, the chrome state is set
to Normal and the entire Web Part appears. Only the title bar
appears when the state is set to Minimized.
5 Chrome Type Specifies whether the title bar and border of the Web Part frame
are displayed.
Table 13 - Web Part Properties; Appearance
24.4.2 Layout
1 Hidden Specifies whether the Web Part is visible when a user opens the page.
If the check box is selected, the Web Part is visible only when you are
designing the page and has the suffix (Hidden) appended to the title.
You can hide a Web Part if you want to use it to provide data to another
Web Part through a Web Part connection, but you do not want to
display the Web Part.
2 Direction Specifies the direction of the text in the Web Part content. For example,
Arabic is a right-to-left language; English is a left-to-right language. This
setting may not be available for all types of Web Parts.
3 Zone Specifies the zone on the page where the Web Part is located. Zones
on the page are not listed in the list box when you do not have
permission to modify the zone.
4 Zone Specifies the position of the Web Part in a zone when the zone contains
Index more than one Web Part. To specify the order, type a positive integer in
the text box. If the Web Parts in the zone are ordered from top to
bottom, a value of 1 means that the Web Part appears at the top of
the zone. If the Web Parts in the zone are ordered from left to right, a
value of 1 means that the Web Part appears on the left of the zone.
For example, when you add a Web Part to an empty zone that is
ordered from top to bottom, the Zone Index is 0. When you add a
second Web Part to the bottom of the zone, its Zone Index is 1. To move
the second Web Part to the top of the zone, type 0, and then type 1 for
the first Web Part.
Each Web Part in the zone must have a unique Zone Index value.
Therefore, changing the Zone Index value for the current Web Part can
also change the Zone Index value for other Web Parts in the zone.
Table 14 - Web Part Properties; Layouts
24.4.3 Advanced

1 Allow Minimize Specifies whether the Web Part can be minimized.
2 Allow Close Specifies whether the Web Part can be removed from the
page.
3 Allow Hide Specifies whether the Web Part can be hidden.
4 Allow Zone Specifies whether the Web Part can be moved to a different
Change zone.
5 Allow Specifies whether the Web Part can participate in connections

Connections with other Web Parts.
6 Allow Editing in Specifies whether the Web Part properties can be modified in a
Personal View personal view.
7 Export Mode Specifies the level of data that is permitted to be exported for
this Web Part. Depending on your configuration, this setting may
not be available.
8 Title URL Specifies the URL of a file containing additional information
about the Web Part. The file is displayed in a separate browser
window when you click the Web Part title.
9 Description Specifies the ScreenTip that appears when you rest the mouse
pointer on the Web Part title or Web Part icon. The value of this
property is used when you search for Web Parts by using
the Search command on the Find Web Parts menu of the tool
pane.
10 Help URL Specifies the location of a file containing Help information
about the Web Part. The Help information is displayed in a
separate browser window when you click the Help command
on the Web Part menu.
11 Help Mode Specifies how a browser will display Help content for a Web Part.
Select one of the following:
Modal – Opens a separate browser window, if the browser has

this capability. A user must close the window before returning to
the Web page.
Modeless – Opens a separate browser window, if the browser
has this capability. A user does not have to close the window
before returning to the Web page. This is the default value.
Navigate – Opens the Web page in the current browser
window.
12 Catalog Icon Specifies the location of a file containing an image to be used
Image URL as the Web Part icon in the Web Part List. The image size must
be 16 by 16 pixels.
13 Title Icon Image Specifies the location of a file containing an image to be used
URL in the Web Part title bar. The image size must be 16 by 16 pixels.
14 Import Error Specifies a message that appears if there is a problem importing
Message the Web Part.
Table 15 - Web Part Properties; Advanced

25 Appendix C Document Management

25.1 SharePoint Library
A SharePoint library is a location where you can create, store, update, and collaborate on files. It
also allows you to store Meta information about the files, so that it can be used among different
team members. You can create, store and manage almost every type of file (i.e. Word
documents, spreadsheets, presentations, forms etc.) in different kinds of libraries. You can choose
from several types of libraries, depending on the types of files that you want to store and how you
plan to use them. You can choose from a number of ready-to-use libraries and library templates
that provide a good starting point for organizing your files. Once you are done with a library, you
can archive files, delete the unused library, and save server disk space.
You can control how documents are viewed, tracked, managed, and created. You can track
versions, including how many and which type of versions, and you can limit who can see
documents before they are approved. You can even create custom views and forms to make
your projects go much smoother. To streamline a business process, you can use workflows to
collaborate on documents in libraries. To reduce clutter, you can specify information
management policies to manage the handling and expiration of documents within libraries.
25.2 Types of Libraries
You can create as many types of libraries as you want. There are specialized types of libraries
available in SharePoint Server 2013 to store specific types of content as depicted below. You can
customize these libraries for your purposes, or you can create your own additional libraries.
Figure 81 - Type of Document Libraries

Each type of library has a specific purpose and some have a different set of behaviour and
features. Further information about them is as follows:
No. Type of Library Description
1 Asset Library Asset Library allows you to create a rich media library and lets
you create, browse, share, organize and manage images,
audio and video files. An asset library makes it easier for users to
discover and reuse digital media files that others have already
created.
2 Data Connection Here you can create, browse, share, organize and manage files
Library that contain information about connecting to external data
connections. It is a centralized way to store Office Data
Connection (ODC) files. Each of these files (.odc) contains
information about how to locate, log on, query, and access an
external data source.
3 Document Library Here you can create, browse, share, organize and manage
documents or other files. It also allows creating folders,
versioning of documents and check-in/check-out of files. You
can store other kinds of files in a document library, although
some file types are blocked for security reasons.
4 Form Library Here you store and manage Microsoft Office InfoPath forms (or
XML files for use with Microsoft Office InfoPath) for instance
business forms like a status report, purchase orders, etc. After
people fill out forms, you can merge the form data or export it
for analysis.
5 Picture Library Here you can upload and share pictures with others and it
includes a built-in image viewer. Although pictures can be
stored in other types of SharePoint libraries, picture libraries have
several advantages.
6 Report Library Here you can create web pages and reports to track business
metrics, goals, KPIs (Key Performance Indicators) and BI
(Business Intelligence) information. When you publish an Excel
workbook to a reports library, it is single-click enabled to open
in browser view, which is a convenient way to see the workbook
without adding it to a Web Parts Page.
7 Slide Library It allows you to create a library for storing and sharing Microsoft
PowerPoint slides or a compatible application. When you
publish a presentation to a Slide Library, the slides upload as
individual files, so they can be independently modified and
tracked.
8 Wiki Page Library It allows you to create and store customizable pages of content
that are linked together and can be edited by several people.
Table 16 - Type of Libraries and their Features

25.3 Create Document Library
1) In your SharePoint Web application, select the site under which you want to create the
Document Library and expand the settings cog menu on the top right side as shown
below. And click Site contents
Figure 82 - Site Contents
2) On Site Content screen choose ‘Add an App’.
Figure 83 - Add an App
3) Select the option ‘Document Library’ and then specify the name of the library and
finally click on the ‘Create’ button.

Figure 84 - Creating Document Library
4) Additionally, If you want to specify different properties or behaviors of your library, you
can click on the ‘More Options’ button which will open a screen as shown below.
Figure 85 - Document Library More Options
5) Click on the ‘Create’ button and wait for your library to be created. Below is document
library ribbon for a Library that was created.
Figure 86 - Document Library Ribbon

25.4 Add Documents to Library
1) Click on the “Add document” link to add documents to your library. You can also
upload existing document, either upload one document at a time or have multiple
documents uploaded in a batch.
Figure 87 - Creating a New Document
Figure 88 - Selection of Documents Types for New Document

25.5 Delete Document Library
1) Select the library and then the ‘Library Tools’ menu will appear in the context sensitive
ribbon style menu. Select the ‘Library’ sub-menu and on the right side you will see the
‘Library Settings’ option as shown below, click on this option.
Figure 89 - Document Library Ribbon; Library Settings
2) The Library setting page allows you to change different settings for your library. For
example you can change the versioning option, change permissions, delete the
library, etc. Click on “Delete this document library” to delete it and you will be
prompted for confirmation, then click “OK”. If you delete your library, then your library
will move into the Recycle Bin.
Figure 90 - Library Settings

25.6 Restore Document Library
1) You can restore your library from the “Recycle Bin”. If your library does not appear
under Libraries after restoration you can go to the Site Content and change the option
to appear in Quick Launch.
Figure 91 - Site Content; Recycle Bin
Figure 92 - Recycle Bin
Note: From here you can also delete your document library permanently.
All the administrative pages described in this section will use SharePoint OOTB theme.

26 Appendix D Hosting and Infrastructure in Azure

26.1 Azure virtual machines (IaaS)
Remote Access
Azure Point to Site

VPN
Microsoft Azure
Virtual Network
Cloud Service Cloud Service Cloud Service Cloud Service
Front End App server Database

Active Directory & DNS A B C D
Availability Set Availability Set Availability Set Availability Set
Cloud Service 0 Cloud Service Cloud Cloud Service

Azure Add-Ons Service
SharePoint Database
Monitoring Backup
Development I H E F
Production
Common
VM Size: VM Size:
A Medium (A2)
D Extra Large (Standard D13)
VM Size:
Windows Server + DNS + Active Directory Windows Server + SQL Server + Mirroring
H Large (A3)
Windows Server + DPM
VM Size: VM Size:
B Extra Large (Standard D3)
Windows Server + SharePoint E Extra Large (A5)
Windows Server + SharePoint

VM Size:
VM Size: VM Size:
I Extra Large (A4)
Windows Server + SCOM + SQL Server for
C Extra Large (Standard D12)
Windows Server + SharePoint

F Extra Large (A4)
Windows Server + SQL Server

System Center
Figure 93 - Azure Architecture

All virtual machines of SharePoint, SQL Server, Active Directory, System Center Operations
Manager and Data Protection Manager will be deployed in Azure on virtual machines. There will
be total 12 virtual machines deployed in Windows Azure as the following:
1) Two VMs for SharePoint WFE Servers

2) Two VMs for SharePoint Application Servers
3) Two VM for SharePoint SQL Servers with always on
4) One VM for SharePoint WFE Server and App server for development
5) One VM for SharePoint development SQL Server
6) Two VMs for Active Directory and DNS
7) One VM for System Center Data Protection Manager
8) One VM for System Center Operations manager and SQL (SQL will be used for System
Center products)
26.1.1 Azure Affinity Group
Affinity groups allow to group Azure services to optimize performance. All services and VMs within
an affinity group will be located in the same region.
One Affinity Group will be created in Azure Subscription, Affinity group will be assigned with a
region either West Europe or North Europe. If more than one Storage accounts will be created
then Affinity group will be created and will be bound with the affinity group so that virtual
machines will be deployed as nearest as possible.
26.1.2 Azure Availability Set
An availability set helps keep virtual machines available during downtime, such as during
maintenance. Placing two or more similarly configured virtual machines in an availability set
creates the redundancy needed to maintain availability of the applications or services that virtual
machine runs.
To provide redundancy to the applications, two virtual machines identical to each other in an
Availability Set will be deployed and configured. This configuration ensures that during either a
planned or unplanned maintenance event, at least one virtual machine will be available and
meet the 99.95% Azure SLA. Each virtual machine in an Availability Set is assigned an Update
Domain (UD) and a Fault Domain (FD) by the underlying Azure platform.

Following Virtual machines will be kept in a single Availability Set which are identical to each other,
there will be total four availability sets created as follows, those virtual machines which are not
identical to each other will not be configured in Availability set.
 SharePoint WFE servers in production will be created in single Availability Set

 SharePoint App Servers in production will be created in single Availability Set
 SharePoint SQL Servers in production will be created in single Availability Set
 Active Directory Servers in production will be created in single Availability Set
By configuring at least two virtual machines in an Availability Set for each tier, it guarantee that at
least one virtual machine in each tier will be available.
26.1.3 Storage Accounts
An Azure storage account is a secure account that gives access to services in Azure Storage.
Storage account provides the unique namespace for the storage resources. Each standard
storage account can contain up to 500 TB of combined blob, queue, table, and file data. Data
in the storage account is replicated to ensure durability that is also highly available, meeting
the Azure Storage SLA even in the face of transient hardware failures. There are several options
for replicating the data in storage account:
1) Locally redundant storage (LRS) maintains three copies of the data within a same
region
2) Geo Redundant Storage (GRS) With GRS, the data is replicated three times within the
primary region, and is also replicated three times in a secondary region hundreds of
miles away from the primary region
3) Read-access geo-redundant storage (RA-GRS) provides all of the benefits of geo-
redundant storage noted above, and also allows read access to data at the
secondary region
As In the standard tier of virtual machine in Azure, the maximum IOPS is 500 per disk. When planning
for a high I/O virtual machine, it is also needed to take into consideration the Azure storage
accounts’ 20,000 total request rate limit. Therefore, we should not place more than 40 highly
utilized VHDs in a storage account (20,000/500 = 40 VHDs).
As virtual machines will be deployed which is why Blob Storage as Page Blobs will be used which
will allow to store VHDs. Each VHD can be up to 1023GB in Size. Geo Redundant Storage will be

enabled on Storage account by having SQL Database and Log files on the same disk, if SQL
database and Log files will be placed on different disks then a separate storage account will be
created only for SQL and LRS will be selected for Storage account as a best practice of practice
of SQL. As a best practice one storage account in Azure for Al Khor Website will be created and
will have not more than 25 VHDs to provide the space for the future VHDs to be created in the
same Storage account and if required one dedicated Storage account will be created for
Backup.
26.1.4 Azure Load Balancing of VMs
Virtual machines in the same cloud service or virtual network can communicate with each other
directly using their private IP addresses. Computers and services outside the cloud service or virtual
network can only communicate with virtual machines in a cloud service or virtual network with a
configured endpoint. An endpoint is a mapping of a public IP address and port to that private IP
address and port of a virtual machine or web role within an Azure cloud service.
The Azure Load Balancer randomly distributes a specific type of incoming traffic across multiple
virtual machines or services in a configuration known as a load-balanced set. For example, the
load of web request traffic across multiple web servers or web roles can be speeded. Similar to
Azure load balancing, internal load balancing is facilitated by configuring an internal load-
balanced set.
In Azure for SharePoint website Front End servers within the same availability set will be configured
with Azure Load balancer to load balance the traffic, as well as internal Load balancer might will
be configured for internal traffic between virtual machines like SQL server for always on, for the
request generated from virtual machines with in the same internal network.
26.1.5 Virtual Machine End Points in Azure
All virtual machines that are created in Azure can automatically communicate using a private
network channel with other virtual machines in the same cloud service or virtual network.
However, computers on the Internet or other virtual networks require endpoints to direct the
inbound network traffic to a virtual machine.
When virtual machine is created in the Azure Management Portal, endpoints for Remote Desktop,
Windows PowerShell Remoting, and Secure Shell (SSH) are automatically created. Additional

endpoints can be configured as additional endpoints while creating the virtual machine or
afterwards as needed.
Each endpoint has a public port and a private port:
 The public port is used by the Azure load balancer to listen for incoming traffic to the virtual
machine from the Internet.
 The private port is used by the virtual machine to listen for incoming traffic, typically
destined to an application or service running on the virtual machine.
Those virtual machines like Front End Servers requires same public port and private port end points
so that it can accept traffic from Internet. Those virtual machines like SQL servers in always on
group requires internal end points to listen for incoming traffic from internal traffic. End Point will
be created for SharePoint with Front End Servers which will be published over the internet and End
Point will be created for SQL servers for always on for internal traffic.
26.2 Azure Virtual Network
A virtual network is a network overlay that can be configure in Azure. VMs and services that are
part of the same virtual network can access each other. There are no one-size-fits-all virtual
network designs. However, every solution falls into one of 3 basic configuration categories: No
VNet, Cloud-Only VNet, or Cross-Premises VNet (which includes Hybrid solutions). It’s best to know
that if a virtual network is needed before deploying VMs and cloud services. VMs and cloud
services acquire their network settings during deployment.
Cloud only virtual network will be deployed and configured in Azure for Al Khor Website which will
have no Site to Site VPN connectivity with on premises as per the requirements because Cloud-
Only virtual network configurations are VNets that don’t use a virtual network gateway to connect
back to on-premises network or directly to other Azure VNets. Virtual Network (VNET) will be
created as regional virtual network.
26.2.1 DNS settings of Virtual Network
If it is required to connect to the VMs services by hostname or SRV records, rather than using the
IP address and/or port number, it is always needed some name resolution. When a VM is deployed
and cloud services to a virtual network it is recommended to use own DNS solution, For the
SharePoint virtual machines and other virtual machines deployed on the same VNET will use DNS

solution from Active directory Domain Controller, There will be two domain controllers deployed
and both domain controllers IPs will be defined on the VNET so that VMs can resolve using names
through Active Directory DNS.
26.2.2 Point to Site VPN
It’s a great way to have a secure connection from computer to a virtual network without acquiring
and configuring a VPN device. There are 3 main parts to configuring a point-to-site VPN: the virtual
network and gateway, the certificates used for authentication, and the VPN client that is used to
connect to the virtual network. Point to Site VPN will be configured so that administrators can
securely connect to Azure virtual machines remotely.
26.3 Cloud Services for Virtual Machines
Every virtual machines has its associated cloud services in which there are options to scale up and
scale down the virtual machines, defining the fault domain and update domain, Monitoring
points, instances, Public IPs. Those virtual machines which are in an availability set shares the same
Cloud Service and those virtual machines which are not in an availability set can be separated
by a cloud service or can be placed on a same cloud service. Those virtual machines which are
in a separate cloud service cannot be added in one availability set because of having separate
cloud services. For Al Khor Website, those workloads or virtual machines which are identical will
be placed on a same cloud service in order to create the availability set, those virtual machines
which are not identical in terms of services will be placed on a separate cloud service, those virtual
machines which require same port to publish over the internet will not be deployed on a same
Cloud service because Cloud service will have Public IP address and all virtual machines inside
that cloud service will use the same Public IP address with different ports.
26.4 Dedicated Internal IPs
Microsoft Azure allows virtual machines to have Dedicated Internal IPs so that virtual machines
can have the same IP addresses once they are shutdown from the Azure Portal. Although there is
no way to define or assign the IP address from the NIC of the OS and all IPs are being assigned to
virtual machines using DHCP, even if the IP is assigned as dedicated to a virtual machine that IP is
also assigned to a virtual machine using DHCP but the IP will not be de assigned from VM. All virtual
machines in Azure for Al Khor Website will be assigned with the dedicated internal IPs.

26.5 Reserved IPs
Every Cloud Service is assigned with a Public IP through DHCP, these Public IPs are de-assigned as
soon as the virtual machine is Shutdown from the portal. It is possible to reserve a Public IP for
virtual machines which are published over the internet for web services. In Azure for Al Khor website
Reserved IPs will be used for those cloud services / virtual machines which will be published over
the internet.
26.6 Active Directory Domain Controller
There will be two domain controllers which will be deployed in Azure for Al Khor website, two
domain controllers will provide the redundancy and will also allow to achieve the Azure SLA. One
domain controller will be primary domain controller and second domain controller will be
additional domain controller. FMSO roles will be divided between both domain controllers. Virtual
machines will be joined to the domain and name resolution will also be used through these
domain controllers. Both domain controllers will be deployed in same cloud service and will be
added in an availability set.
26.7 System Center Data Protection Manager
System Center 2012 – Data Protection Manager (DPM) is an enterprise backup system that
enables disk-based and tape-based data protection and recovery for servers such as SQL Server,
Exchange Server, SharePoint, virtual servers, file servers, and support for Windows desktops and
laptops. DPM can also centrally manage system state and Bare Metal Recovery (BMR).
As part of this solution, DPM will be deployed as virtual machine in Azure and will be configured
for the backup of SharePoint, SQL Servers and Active Directory Servers. Protection groups, backup
policies and retention periods will be configured.
26.8 System Center Operations Manager
System Center 2012 – Operations Manager provides infrastructure monitoring that is flexible and
cost-effective, helps ensure the predictable performance and availability of vital applications,
and offers comprehensive monitoring for the datacenter and cloud, both private and public.
As part of this solution, Operations Manager will be deployed as virtual machine in Azure will be
configured for the monitoring of SharePoint Servers, SQL servers, Active Directory Servers, DPM

Servers, SharePoint Website. Operating System Management packs, SQL Server management
packs, Active Directory, DNS management packs, DPM server management packs, SharePoint
Management packs will be deployed and configured in order to monitor the infrastructure.
26.9 SharePoint Infrastructure Planning
26.9.1 Physical Topology
Visitor / Member AKC Administration Team
WFE 1 WFE 2
Azure Farm
APP 1 APP 2
DB 1 DB 2
Always On
Figure 94 - Physical Topology
Server Role Description

Name
WFE 1 Web Front End Software load balanced web server; Primary interaction
surface for website content
WFE 2 Web Front End Same like WFE 1
APP 1 Application Application server responsible for hosting various SharePoint

Server 2013 services in a redundant fashion
APP 2 Application Same like APP 1
Server
DB 1 Database SQL Server responsible for hosting all SharePoint 2013 content
Server and configuration databases; Mirrored with DB 2
DB 2 Database SQL Server responsible for hosting all SharePoint 2013 content
Server and configuration databases; Mirrored with DB 1
Table 17 - Physical Topology

26.9.2 Server Planning
Server Name CPU RAM Count Software

(Cor (GB)
es)
Production WFE 4 14 2 Windows Server + SharePoint
Production APP 4 28 2 Windows Server + SharePoint
Production DB 8 56 2 Windows Server + SQL Server +

Mirroring
Development SharePoint 2 14 1 Windows Server + SharePoint
Development DB 8 14 1 Windows Server + SQL Server
Table 18 - Servers Configuration

27 Appendix E AKC E-Forms

Following is sample e-form for AKC website to illustrate look and feel of the e-form with compliance
to approve design
Figure 95 - Sample E-Form

28 Appendix F Document Approval

Submitted To Submitted By
Deliverable Approval / Acceptance
Deliverable acceptance Accept Deliverable
Reject Deliverable with Reason
Date reviewed
Comments/Reason
Signature:
I have read the document and I agree with the all the details mentioned in the document on which the workflow will be
developed. I agree that all the details related to the mentioned workflows are stated in this document.
For Consumer Protection
Approver Name
Approver Signature
For IT
Approver Name
Approver Signature

Sample FSD

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sample FSD

Uploaded by

Copyright:

Available Formats

Al Khor Community (AKC)

Website and Online Services

Mar 09, 2015

Document Management & Version Control

Document Title: AKC - Website and Online Services - FSD

Document File Name: AKC - Website and Online Services – FSD.pdf

Issued By: Shahab Juman

Issue Date: 09th March 2015

Reviewed By: Ahmed Sweilem

Approved By: Ahmed Sweilem

Date Version Author Remarks

25th February 2015 0.1.0 Shahab Juman Released first draft

02nd March 2015 0.2.1 Ahmed Sweilem Reviewed

08th March 2015 0.4.1 AKC Administrative Team Reviewed

Addition of following Sections :-

09th March 2015 1.0.0 Shahab Juman Live

1.1 Purpose ............................................................................................................................................... 1

1.2 Scope .................................................................................................................................................. 1

1.3 Reference Documents .................................................................................................................... 1

1.4 Acknowledgement .......................................................................................................................... 2

2 Business Requirements .................................................................................................................................. 3

2.1 Executive Summary .......................................................................................................................... 3

2.2 Proposed Solution ............................................................................................................................. 3

2.3 Solution Overview ............................................................................................................................. 4

2.4 AKC Website and Online services ................................................................................................. 4

3.1 Brand Identification .......................................................................................................................... 5

3.2 Browser Specifications ..................................................................................................................... 5

3.3 GUI Templates (User Interface) ...................................................................................................... 5

3.3.1 Home Page ................................................................................................................................... 6

3.3.2 Member’s App Page Layout ...................................................................................................... 7

3.3.3 Safety Page ................................................................................................................................... 8

3.3.4 Inner Page Template ................................................................................................................... 9

3.3.5 Administrative Interface ............................................................................................................ 11

4 Master Page ................................................................................................................................................. 12

4.1 Header .............................................................................................................................................. 13

Functional Specification III

4.1.1 Top Navigation ........................................................................................................................... 13

4.1.2 Logo .............................................................................................................................................. 13

4.1.3 Login section ............................................................................................................................... 14

4.1.4 Search ........................................................................................................................................... 14

4.2 Footer ................................................................................................................................................ 16

4.2.1 Links Section................................................................................................................................. 16

4.2.2 Copyright Information ............................................................................................................... 16

5 Page Layouts ................................................................................................................................................ 17

5.1 Home Page Layout ........................................................................................................................ 17

5.1.1 Section .......................................................................................................................................... 18

5.2 Members App Page Layout ......................................................................................................... 19

5.2.1 Banner .......................................................................................................................................... 20

5.2.2 Breadcrumb ................................................................................................................................ 21

5.2.3 Left Navigation ........................................................................................................................... 21

5.2.4 Page Content ............................................................................................................................. 21

5.3 Safety Page Layout ........................................................................................................................ 22

5.3.1 Banner .......................................................................................................................................... 24

5.3.2 Breadcrumb ................................................................................................................................ 24

5.3.3 Section .......................................................................................................................................... 24

5.4 Inner Page Layouts ......................................................................................................................... 25

5.4.1 Banner .......................................................................................................................................... 28

5.4.2 Breadcrumb ................................................................................................................................ 29

5.4.3 Left Navigation ........................................................................................................................... 29

5.4.4 Page Content ............................................................................................................................. 30

6 Site Structure & Navigation .......................................................................................................................... 31

6.1 Sitemap ............................................................................................................................................ 31

6.2 Navigation ....................................................................................................................................... 34

6.2.1 Top Navigation ........................................................................................................................... 34