Web Development Functional Specifications Document

Website Functional Specification Document

Version 1.0

Description of Change

Author

Date

PURPOSE [Provide an overall description of the FRD, its purpose. Reference the system name and identifying information about the system to be implemented.] SCOPE [Discuss the scope of the document and how it accomplishes its purpose.] BACKGROUND [Describe the organization and its overall responsibilities. Describe who is producing the document and why.] REFERENCES [List references and controlling documents, including: meeting summaries, white papers, other deliverables, etc.] ASSUMPTIONS AND CONSTRAINTS [Provide a list of contractual or task level assumptions and/or constraints that are preconditions to preparation of the FRD. Assumptions are future situations beyond the control of the project, whose outcomes influence the success of a project.] A. Assumptions Examples of assumptions include: availability of a technical platform, legal changes and policy decisions. Section/ Requirement ID

Requirement Definition

ASSUM-1

The system shall [parent requirement group 1].

ASSUM-1

The system shall [child/parent requirement].

ASSUM-1.1.1

The system shall [child requirement].

ASSUM-1.2

The system shall [child requirement].

B. Constraints Constraints are boundary conditions on how the system must be designed and constructed. requirements, technical standards, strategic decisions.

Examples include: legal

•

Constraints exist because of real business conditions. For example, a delivery date is a constraint only if there are real business consequences that will happen as a result of not meeting the date. If failing to have the subject application operational by the specified date places the organization in legal default, the date is a constraint.

•

Preferences are arbitrary. For example, a date chosen arbitrarily is a preference. Preferences, if included in the FRD, should be noted as such.]

Section/ Requirement ID

Requirement Definition

CONS-1

The system shall [parent requirement group 1].

CONS -1

The system shall [child/parent requirement].

CONS -1.1.1

The system shall [child requirement].

CONS -1.2

The system shall [child requirement].

WEBSITE REQUIREMENTS A. Site Navigation and Organization [Discuss the intent of the site navigation / information.] Example: The user interface should intuitively guide the visitor to the information they seek, including web accessibility. The site should include the following navigation strategies: -

Menu System as the primary navigation method of the site that is always displayed on each page. A hierarchical menu content divided into related functional areas based on the current Organization site map. Please refer to site map in Appendix A. Each section must have a main page where visitors can navigate to the sub items under the sections, but still be able to get back to any of the other main section home pages. Full site search, with administrator control. Navigation, category, section, and link names and link design.

B. Automated Content Management [Discuss whether the content will be managed through a content management system (CMS). Note what purpose this content management system will serve, as well as the specific system, if known. Specify if the CMS will have a built in workflow to facilitate content publishing. If it will have workflow, specify roles for content authors as well as content approvers.] Example: The web site content must easily be able to manage dynamically by non-technical department staff in as simple a method as possible. The staff will be able to add, change and delete site content without manipulating any HTML or scripting code. Personnel should be able to access designated templates and easily update information in pre-designed formats, including the use of databases to hold and change dynamic information. This includes formatted text, hyper-links, digital pictures, as well as providing downloadable documents in Word, Excel, PDF, and other formats. Most documents will age and lose relevancy over time, and need to be routinely updated or removed. C. Web Site Reporting [Discuss what type of web metrics platform you will be using to measure usage and traffic. Who will need to have access to the reporting system and what kind of reports do you want to create.] Example: In order to maintain a quality site that continues to meet organization needs, a quality web site reporting system that provides types and features of management reports, including traffic counts, orgin or domain names sources of visitors, or other useful information regarding the website is required. D. Video/Audio Streaming [Discuss whether the site will need to support on-demand, live streaming, podcasts (or all types) as well the encode format the server will need to support (Real, Windows Media, Quicktime, etc.] Example: Organization product demonstrations will be available for demand-access by users of the website through video/audio streaming or a similar technology. The website shall address this capability and shall specify any requirements to enable V/A. D. Search Engine Optimization [Discuss how SEO will be implemented into the site. Note whether there are certain backend (hidden) HTML components that the users should be able to modify via the CMS (e.g., meta keywords, meta description, and Title.] The SEO requirements examples below assume that there is a CMS: 1. 2.

3. 4. 5.

The title of each page should be unique to each page and not be longer than 70 characters. Each content author must have the ability to customize the META-DESCRIPTION and META-KEYWORDS in the CMS All page URLs , especially dynamically generated ones, must have friendly URL aliases so that they are picked up by search engines. The CMS must employ semantic HTML (h1, h2, p, etc.) The CMS should allow the content author to specify ALT text for all images

E. Website Elements:

Section/ Requirement ID BREQ-1

Home Page

BREQ-1.1

Interactive Widgets

BREQ-1.2 BREQ-2

Brand / Imagery About Us

BREQ-2.1

Interactive Widgets

BREQ-2.2

Brand / Imagery Online Store

BREQ-3

Requirement Definition The company logo will be located at the top left hand corner of the page A global navigation bar will be located below the logo Rollovers will be used for the global links to the other web pages Reservations Facilities Directions About Us Events Online Store Contact Employment Site/Map Legal/ Privacy The bottom of the page will contain links to information regarding copyright and privacy statement.

The company logo will be located at the top left hand corner of the page A global navigation bar will be located below the logo The bottom of the page will contain links to information regarding copyright and privacy statement The logo and home text link will provide a link back to the home page

-

-

BREQ-3.1

Interactive Widgets

BREQ-3.2

Brand / Imagery Legal/Privacy

BREQ-4

-

BREQ-4.1

Interactive Widgets

BREQ-4.2

Brand / Imagery

The company logo will be located at the top left hand corner of the page A global navigation bar will be located below the logo This link will provide a calendar of events A shopping cart feature will be available here for customers wanting to make the purchase Shopping cart will be made available and a link to allow coupons for discounts to input The bottom of the page will contain links to information regarding copyright and privacy statement The logo and home text link will provide a link back to the home page

The company logo will be located at the top left hand corner of the page A global navigation bar will be located below the logo Users will be transferred to a page where they will be given an overview of the privacy and legal policies of the website They will be provided with links to various legal documents Privacy agreement Affiliate Agreement Legal notice Terms of Use The bottom of the page will contain links to information regarding copyright and privacy statement The logo and home text link will provide a link back to the home page

Examples of Additional Web Pages -

Store Locator Event Page Contact Careers Site Map