Website Requirements Specification Template

[dhaughey]

This requirements specification is used to record the user requirements for website development. The document describes why the website is needed and how it is to be created, implemented and maintained.

Website Requirements Specification Template

[ysagrt]

Any explanation of this template?

[dhaughey]

Use this template to collect customer requirements for new websites or for website redesigns. You can easily adapt it to meet your needs.

Here is a brief explanation for each section:

1. 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.
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.

Hope this helps.

Duncan

[Divya2701]

Hi Duncan,

Thanks for the document. Do you have sample effort estimation template as well? That will be very handy and useful to start baseline effort estimation.

Best Regards,
Divya

[dhaughey]

Hi Divya,

You might find this Budget Analysis and Forecasting Template useful.

Duncan

[Pavan Vamsee]

Hi,
Could you provide a sample for the website requirements specifications template? An example of what one fills in the tables.

Thank you,
Pavan Vamsee

[martinaiphs]

Every website project should begin considering a specification. This should outline the objectives for your website, along with any previously agreed deadline or budget constraints. Below we've outlined an example template for consideration. Follow these steps:

1. Introduce yourself
2. Start with the objectives
3. Key audiences
4. Provisional site structure
5. Technical specifications
6. Non-functional requirements
7. Websites you like and don't like
8. Who are your competitors?
9. Budget
10. Timescales
11. What is your procurement process?