FloridaDisaster.org Redevelopment Project (FDRD)
Website Functional Requirements
Specification
Version:
Date:
By:
1.3
7/22/2011
Levi Owens
Website Functional Requirements Specification
FloridaDisaster.org Redevelopment Project
Revision History
Version
0.1
1.0
1.1
1.2
1.3
Date
06/6/2011
06/10/2011
06/30/2011
07/19/2011
07/22/2011
Author
M. Christovich
M. Christovich
L. Owens
L. Owens
L. Owens
Purpose
Initial Draft
First Release
Added Web Forms line item specs
Modifications from Core Team review
Modified URL shortening requirement
Document Acceptance & Approval
(Specification reviewed by Core Team and accepted by Project Owner on Wednesday, July 20, 2011)
Version 1.3 on 7/22/2011
Page 2 of 11
Website Functional Requirements Specification
FloridaDisaster.org Redevelopment Project
Table of Contents
1
2
Introduction ........................................................................................................ 4
1.1
Document Overview & Purpose ........................................................................ 4
1.2
Objectives ..................................................................................................... 4
1.3
Target Audience ............................................................................................. 4
1.4
Ownership..................................................................................................... 4
1.5
Key .............................................................................................................. 4
Website Functional Requirements ........................................................................... 5
2.1
Search .......................................................................................................... 5
2.1.1
Internal Search........................................................................................ 5
2.1.2
World Wide Web Search............................................................................ 5
2.1.3
Structured Search .................................................................................... 6
2.2
Persons with Disabilities.................................................................................. 6
2.3
SharePoint Document & Multimedia Libraries ..................................................... 7
2.4
Contact Management Database........................................................................ 8
2.5
Social Media .................................................................................................. 9
2.6
RSS (Really Simple Syndication) ...................................................................... 9
2.7
Visitor Contact & Feedback Form .................................................................... 10
2.8
Local Information ......................................................................................... 11
Version 1.3 on 7/22/2011
Page 3 of 11
Website Functional Requirements Specification
FloridaDisaster.org Redevelopment Project
1 INTRODUCTION
1.1 Document Overview & Purpose
This document specifies the functional website requirements for the project.
1.2 Objectives



Describe website functional requirements
Organize functional specifications for new FD.org
Assign and present priority to each functional requirement
1.3 Target Audience
This document is directed towards the Core Project Team to assist them in the
formulation of a Request for Proposal connected with the FloridaDisaster.org
ReDevelopment project.
1.4 Ownership
This document is authored and maintained by the Business Analyst, Matthew
Christovich.
1.5 Key
Each requirement table below contains the following information:
Item
Requirement Number
Feature/ Requirement
Description
Priority
Version 1.3 on 7/22/2011
Description
Unique Identifier for Each Requirement
The unique name for each requirement which identifies which category
the requirement belongs in and also describes its basic function
A brief description to aid in development
One of three priority identifiers:
1 – High
2 – Medium
3 - Low
Page 4 of 11
Website Functional Requirements Specification
FloridaDisaster.org Redevelopment Project
2 WEBSITE FUNCTIONAL REQUIREMENTS
2.1 Search
Currently, the FloridaDisaster.org presents the option to visitors of searching both the World
Wide Web and the FloridaDisaster.org website as separate searches. The user may select to
search either the World Wide Web or FloridaDisaster.org. These searches are limited to
simple text searches using the Google search engine.
2.1.1 Internal Search
2.1.1.1 Requirements
In order to allow searches to be conducted:
Number
1.1
Feature/Requirement
Website Search
Description
The website must include a tool for a Google
search of FloridaDisaster.org.
Priority
1 - High
2.1.2 World Wide Web Search
2.1.2.1 Requirements
In order to help a user find the information they are seeking, even if that information is not
found on FloridaDisaster.org:
Number
1.2
Feature/Requirement
Internet Search
Version 1.3 on 7/22/2011
Description
The website must include a tool for a Google
search of the World Wide Web. This search
must be conducted simultaneously with the
search of FloridaDisaster.org and presented
below the results from the
FloridaDisaster.org search in a format that is
easy to for the user to distinguish the
difference between the search results.
Priority
3 - Low
Page 5 of 11
Website Functional Requirements Specification
FloridaDisaster.org Redevelopment Project
2.1.3 Structured Search
2.1.3.1 Requirements
In order to guide a user to find the information they are seeking:
Number
1.3
Feature/Requirement
Structured Search
Description
The website must provide structured search
capability. This structured Search must
guide users through what types of content
are available using drop-down menus or
check boxes to display available sites
categorized by author-defined meta-data.
Priority
1 - High
2.2 Persons with Disabilities
Currently, the FloridaDisaster.org website is not compliant with Section 508. Any user with
visual impairment browsing the website using assistive technology must listen carefully to
discern content as the technology audibly reads all of the signs and symbols of HTML and
content simultaneously.
2.2.1.1 Requirements
Number
2.1
Feature/Requirement
Disability Compliance
2.2
Disability Forms
2.3
2.4
2.5
2.6
Disability Color
Disability Navigation
Disability Graphics and Text
Disability Applications
Version 1.3 on 7/22/2011
Description
The website must meet the requirements of
Section 508 of the Rehabilitation Act.
The website must ensure that users using
assistive technology can complete and
submit online forms.
The website must ensure that all information
conveyed with color is also available without
color
The website must provide a means for users
using assistive technology to skip repetitive
navigation links.
The website must provide a text equivalent
for every non-text element that conveys
information.
The website must require all applets, plugins, or other applications required to
interpret page content to be accessible by
assistive technologies.
Priority
1 - High
1 - High
1 - High
1 - High
1 - High
1 - High
Page 6 of 11
Website Functional Requirements Specification
FloridaDisaster.org Redevelopment Project
2.3 SharePoint Document & Multimedia Libraries
Currently, documents, templates, forms, audio, video, and photo image files included in the
FloridaDisaster.org website are placed in website folders and linked using static HTML
coding. Updating, tracking authorship, and managing these files is a decentralized process
done by hand.
What is desired is a centralized MS SharePoint repository for documents and multimedia
providing authorized users with functionality for uploading, downloading, modifying,
tagging, indexing, searching, filtering, routing for reviews, approving, updating, and
collaboration.
2.3.1.1 Requirements
In order to facilitate comprehensive document and multimedia management:
Number
3.1
Feature/Requirement
Document Library
3.2
Multimedia Library
3.3
Library Security
3.4
3.5
Library Predefined Tags
Library File Management
3.6
Library Version Tracking
3.7
Library Archiving
3.8
Library Auto Thumbnailing
3.9
Library Geocode Locations
3.1
Library Custom Galleries
Version 1.3 on 7/22/2011
Description
The website must use a SharePoint
Document Library
The vendor must use a SharePoint
Multimedia Library
The Libraries must provide Role Based
Security for file access, modification, and
deletion; also provide “reviewing” and
“approving” functionality and oversight
specifically to the uploading, downloading,
and tagging activities
The Library must provide users with
predefined tags. This will help prevent typos
and ensure consistency.
The Library must provide the ability for
authorized end users to upload, download,
view, modify, tag (with approval), index,
search, filter, route, approve, and
collaborate with documents and multimedia
files
The Library must provide the ability for
managing and tracking authorship and
access
The Library must provide the ability to
archive “old” or “out of date” documents
The Library must provide the ability to auto
thumbnail photos. (Review Picasa
(http://picasa.google.com).)
The Library must provide the ability to
geocode the location of where the
photograph was taken. (Review Picasa
(http://picasa.google.com).)
The Library must provide the ability to
create custom galleries.
Priority
1 - High
1 - High
1 - High
1 - High
2Medium
2Medium
2Medium
2Medium
2Medium
2Medium
Page 7 of 11
Website Functional Requirements Specification
FloridaDisaster.org Redevelopment Project
Number
3.11
3.12
3.13
Feature/Requirement
Library Video Player
Library Video Download
Library Video Transcript
Description
The Library must provide the ability to use
JW Player
(http://www.longtailvideo.com/players/jwflv-player/); not YouTube.
The Library must provide the ability to
download the video (for example,
www.fema.gov/medialibrary/).
The Library must provide the ability to
download the video transcript where
available (for example,
www.fema.gov/medialibrary/).
Priority
1 - High
1 - High
2Medium
2.4 Contact Management Database
FDEM currently maintains a contacts database containing tables for Counties, Emergency
Coordinating Officers (ECOs) of the SERT, and division staff. Each of those tables interface
with the current website to dynamically present contact information.
Going forward, the business requires a centralized information clearinghouse for contact
information that interfaces with the new FD.org website. The solution must dynamically
present structured contact information within the website and role based security must be
implemented to allow maintenance by various staff, both from within the division and from
external emergency management partners. The solution must also provide the following
features to improve the division’s contact management capabilities
2.4.1.1 Requirements
In order to provide a single point of update functionality for contact information:
Number
4.1
4.2
Feature/Requirement
Contact Information
Database
4.3
Contact Information
Management
Contact Information Security
4.4
Contact Information Masking
4.5
4.6
Contact Information Filtering
Contact Information Access
Version 1.3 on 7/22/2011
Description
The website must contain a contacts library
or database for the SERT, FDEM, and all 67
County EM Programs.
The contact information library allows
uploading and editing of contact information.
The contact information library allows rolebased security.
The contact information library must allow
administrators to designate which fields of
contact information can be viewed by which
content authorship roles.
The contact information library must allow
administrators to designate which fields of
contact information can be posted by which
content authorship roles.
The contact information library allows
designated contact fields to be accessed and
linked from multiple webpages within the
website.
Priority
1 - High
1 - High
1 - High
2–
Medium
1 – High
1 - High
Page 8 of 11
Website Functional Requirements Specification
FloridaDisaster.org Redevelopment Project
Number
4.7
4.8
Feature/Requirement
Contact Information Position
Creation
Contact Information Position
Deletion
The contact
positions to
The contact
positions to
Description
information library allows
be created and edited.
information library allows
be deleted.
Priority
1 - High
1 - High
2.5 Social Media
Currently, FloridaDisaster.org allows visitors to “follow” their Twitter account and “Like”
their Facebook page.
What is desired is the ability for any visitor to the site to share, via email and social media,
any information they find on the FloridaDisaster.org website to increase awareness and
proliferation of potentially life-saving information. Also, supply URL shortening with a
custom domain name (from a free service such as Bitly.com or similar).
2.5.1.1 Requirements
Number
5.1
Feature/Requirement
Social Media URL Shortening
5.2
Social Media Sharing
5.3
Social Media Widget
Description
The website must provide native URL
shortening with a custom domain name for
use with social media applications
The website must provide the ability to email
and to share information via common social
networking applications such as Facebook,
Twitter, LinkedIn, Google+, etc.
The website must provide the ability for
other websites to use a floridadisaster.org
widget (for example,
http://www.fema.gov/help/widgets/)
Priority
2–
Medium
3 – Low
3 - Low
2.6 RSS (Really Simple Syndication)
Currently, there is limited support for RSS Feeds on the FloridaDisaster.org website. What
is desired is the ability to designate pages that are frequently updated and may be timecritical to visitors to the FloridaDisaster.org website. Content administrators desire the
ability to set up which pages contain this information and for content authors to keep up-todate information that will be pushed out to any RSS subscribers.
2.6.1.1 Requirements
Number
6.1
Feature/Requirement
RSS Feed
6.2
RSS Feed Authorship
6.3
RSS Feed Administration
Version 1.3 on 7/22/2011
Description
The website must provide the ability to
distribute content via RSS Feeds.
The RSS feed system must allow for
administrators to specify whether a web
page can be subscribed to.
The RSS feed system must allow
administrators to manage RSS Feeds.
Priority
1 - High
2–
Medium
2–
Medium
Page 9 of 11
Website Functional Requirements Specification
FloridaDisaster.org Redevelopment Project
Number
6.4
Feature/Requirement
RSS Feed Subscription
Description
The RSS feed system must allow visitors to
the site to subscribe to and receive updates
to those pages designated as available for
RSS distribution.
Priority
1 – High
2.7 Visitor Contact & Feedback Form
Currently, there is an online Contact Us form on the FloridaDisaster.org website. What is
desired is the ability for visitors to send a website generated email to SERT/FDEM staff that
includes information that allows this contact to be electronically routed to the appropriate
personnel or section.
2.7.1.1 Requirements
Number
7.1
Feature/Requirement
Visitor Contact & Feedback
Form
7.2
Visitor Contact & Feedback
Navigation
Visitor Contact & Feedback
Administration
7.3
7.4
Visitor Contact & Feedback
Routing
7.5
Visitor Contact & Feedback
Form Security
Description
The website must include a Visitor Contact &
Feedback form that allows visitors to the
website to submit information to, or request
from, the webmaster or FDEM staff
The website must provide the ability for
visitors to designate the subject of contact
The website must provide the ability for the
Administrator to add, delete, change, and
arrange subject icons
The website must provide the ability to route
appropriate communication subjects to
appropriate email locations
The website must provide the ability to use
CAPTCHA
(http://www.google.com/recaptcha/captcha)
that generates and grades tests that humans
can pass but current computer programs
cannot
Priority
1 - High
1 - High
1 - High
1 - High
1 - High
The purpose of this requirement is to
prevent comment spam
Version 1.3 on 7/22/2011
Page 10 of 11
Website Functional Requirements Specification
FloridaDisaster.org Redevelopment Project
2.8 Local Information
Currently, there is no dynamically presented content based upon visitor location on the
FloridaDisaster.org website.
2.8.1.1 Requirements
Number
8.1
Feature/Requirement
Local Information
Version 1.3 on 7/22/2011
Description
The website must include the ability to
resolve user location (actively and
passively), to the county level, and
dynamically provide locally relevant content
such as weather, events, press releases,
county emergency management contacts,
etc.
Priority
1 - High
Page 11 of 11