[Project]

Website Requirements Specification

Created by [Author]
Version 1.0 - Issued March 15, 2013
This requirements specification is used to record the user requirements for a website.

Website Requirements Specification

[Project]

BACKGROUND
Brief description here about what this website is for and why it is needed.
EXAMPLE USE CASE

(UML Notation created using Microsoft Visio)

1. Visitor Interaction
Req

Description

Comments

1.1
1.2
1.3
Website Requirements Specification

[Project]

1.4

2. Editing, Updates and Administration

Req

Description

Comments

2.1
2.2
2.3
2.4

3. Sitemap and Navigation

Req

Description

Comments

3.1
3.2
3.3
3.4

Website Requirements Specification

[Project]

4. Content Management
Req

Description

Comments

4.1
4.2
4.3

5. Tracking (website statistics)

Req

Description

Comments

5.1
5.2
5.3

6. Search Engine Optimisation (SEO)

Req

Description

Comments

6.1
6.2
6.3

Website Requirements Specification

[Project]

7. Editor Interface (Web Content Management System)

Req

Description

Comments

7.1
7.2
7.3

8. Accessibility
Req

Description

Comments

8.1
8.2
8.3

9. Styling and Design

Req

Description

Comments

9.1
9.2
9.3

Website Requirements Specification

[Project]

10. Security
Req

Description

Comments

10.1
10.2
10.3

11. Hosting
Req

Description

Comments

11.1
11.2
11.3

12. Maintenance and Support

Req

Description

Comments

12.1
12.2
12.3

Website Requirements Specification

[Project]

13. Other Requirements

Req

Description

Comments

13.1
13.2
13.3

14. Exclusions:

Here

15. Considerations:

Here

16. Assumptions:

Here

Visitor Interaction: what will visitors be able to do on this website? List all the activities they will
complete while visiting.
2.Editing, Updates and Administration: how will the website be updated? Define the process for adding
new content and making editorial changes.
3.Sitemap and Navigation: what is the structure of the website? List the sections and content categories
of the website.
4.Content Management: how will content be managed on a day-to-day basis? Is there a need for a Web
Content Management System?
5.Tracking: what are the reporting needs of the website? Define a list of Key Performance Indicators
that stakeholders and other interested people need.
6.Search Engine Optimisation: how will the website be 'promoted' in organic search results? List the
items and activities to enable this, such as, a unique title and description tag on every page.
7.Editor Interface: how will editors update website content? Define the editor environment and
everything required to allow editors to do their job.
8.Accessibility: how will people with special needs use the website? List the requirements to allow
access by screen-readers etc.
9.Styling and Design: what is the look, feel and brand of the website? Identify the broad styling and
design considerations.
10.Security: what will be in place to make sure the website is secure and safe for visitors to use? List all
security considerations.
11.Hosting: how will the website be hosted? Identify the type of hosting (cloud or physical servers) and
the site (own hosting or third-party).
12.Maintenance and Support: what are the requirements for supporting the website? Define the time
periods and level of support needed, including disaster recovery and service continuity.
13.Other Requirements: list anything not covered in other sections of the document.
14.Exclusions: anything that will not be delivered as part of this project.
Website Requirements Specification

[Project]
15.Considerations: list anything that needs accounting for as part of this work and any constraints that
may exist.
16.Assumptions: list any assumptions made about the proposed website.

Website Requirements Specification