Categorias: Todos - requirements - testing - design - implementation

por Max OneGogh 4 anos atrás

137

Plan a Web site

The text outlines various aspects of a project, emphasizing the importance of structured planning and execution. It touches on essential requirements, such as understanding user needs and leveraging existing data.

Plan a Web site

Where to next?

Once you have gathered the initial specification for your web site, you can use this map to:

Name of your Website

Type in the name of your web site and press Enter.

Implementation

SLAs

Service Level Agreements define the reliability and capacity of service and are usually part of an agreement with a web site hosting company.

Are there specific terms that you will require? Think about:


Add an action that you need to take to establish SLA metrics for your site.

SLA
Back-end connections

Include a back-end connection from the suggestions or add your own.

CMS databaseAuto-responder systemE-commerce paymentsStock control systemPermissions-based content
Connection
Secure connections

A secure server and HTTPS encryption may be needed if you are handling:


Add notes about actions you will need to take about using a secure server.

Server platform

Web sites can be implemented in a variety of ways. Choose from the suggestions or add your own.

Content Management System (CMS)Custom codedHosted on own serversHosted on third party servers
Platform
Browser support

What browsers will your site need to support?

It is difficult to support all browsers as technologies change. Many web sites declare older browser versions as unsupported.
Add included or excluded browsers and versions.

Browser
Formats

Add information about the formats your site will need to support.

Think about:

Format

Testing

Regression testing

You should carry out a basic regression testing after making significant changes to your site or the back-end technology, in case some disruption has occurred.

Think about:

Link testing

Links tend to go stale over time and need periodic testing. Add a note about on you will detect broken links.

Options include:

Cross-browser testing

You will need to test against your supported browsers, especially after updates. Add some notes about how this will be achieved.

Think about:

Issue tracking

When performing tests, or receiving feedback on the technical aspects of the site, how will you collect and track issues?

Think about:

Acceptance testing


Add some information about acceptance testing.

подтема
Usability testing

You will need to test the usability and user stories that the site should deliver.

Think about:

Maintenance

Monitoring

Your web site will need to be regularly monitored to ensure that problems are detected early.

Think about:


Add actions to establish monitoring and response for your site.

Dynamic content

If your site contains dynamic information such as a blog, a news feed, user forums or regular campaigns, how will these be updated and published?

Think about:

Change control

What will be your process for managing change on your website?

Think about:


Add an action needed to establish change control.

Sources of change

Identify the sources of change on your website.

Think about:


Add a source of change for your website.

Design & content

Wire frames

How will you visualize your site structure and design?

You could use:

Your design should show the flow of typical actions and focus on making these as simple as possible.
Add some notes about communicating your site layout and design.

How?
Business processes

What business processes will your web site trigger? Who will do these, and how?

Think about:

Add some notes about business processes that your web site will link to.

Site assets and content
Content

Identify content and assets that you will need for your site. You can choose from the suggestions or add your own.

Partners & channelsTutorialsRatings and reviewsCase studiesProduct catalogueProduct & service descriptionsBrochures & data sheetsSpecificationsSkills & accreditationsTestimonialsDownloadsImagesVideosLogosOther
Generic features
Feature

You can choose from the suggestions or add your own.

Search functionNavigation & menusSocial media connectorsRegistration and loginUser account supportPermission marketingDiscussion forumsContact formsQuotation systemsReal-time chatAutoresponderseCommerceVideo or Flash® supportCookie opt-in complianceStorage of cookiesSite versioningApproval, publishing & rollbackOther
Generic pages
Page

Add as many generic pages as you will need. You can choose from the suggestions or add your own.

BlogNews and announcementsTerms and conditionsDistance selling regulationsPrivacy policyPermission marketing policyAboutStaff directoryContact detailsContact / enquiry formSupportCopyrights & trademarksPress CentreSite mapFAQsOther
Reference sites

Add references to sites that you like or dislike, with reasons.

Reference
Site style

What website site are you aiming at?


Add some notes about the style for your web site.

Style
Site name

Add the site name, if chosen. If not, then a site name based on preferred keywords should help with search engine optimisation.

Keyword research

What keyword research has been done or needs to be done? What terms are your target audience searching for?

Selected keywords will be needed for page names, body text and alt text for images, which will help with search engine optimization.
Add some notes about keyword research for your site.

Главная тема

Requirements

Milestone

What are the key milestones for your website project? Add a topic and target date for each milestone.

Think about:

A/B testing

Will you use A/B testing?


A/B testing tests the effectiveness of marketing techniques rather than the functioning of the technology. You can use it for:


Add some notes about A/B testing for your site.

Action

Will you use A/B testing?

A/B testing tests the effectiveness of marketing techniques rather than the functioning of the technology.

You can use it for:


Add some notes about A/B testing for your site.

Users
Add a persona

A persona is a type of user who may visit your site.

Think about:

Add objective

Failure

How might 'Add a persona' fail to 'Add objective'? What could go wrong?
You can add multiple topics here.

Resolution

How will Step be detected? How can it be resolved?
You can add multiple topics here.

Process

Step

How will 'Add a persona' be able to 'Add objective'?

What are the steps in the normal (successful) process?
How will the user know they have succeeded?
You can add multiple topics here.

Privileges

What privileges does 'Add a persona' need to 'Add objective'?

Do they need:

Reason

Why would 'Add a persona' need to 'Add objective'?
What would motivate them to do this?

Knowledge

How much will 'Add a persona' know about your products and services?

Source

Where will 'Add a persona' arrive from?
Will 'Add a persona' arrive from a particular location?
Will this mean they need a particular landing page?

Think about:

Existing user data
Existing data

If you have existing marketing data about users and their needs, you can identify it or attach a file here.

Market segments
Market segment

Who are your target users?
Add a market segment that reflects specific users.

Stakeholders

How will you communicate with stakeholders?
Responsible

How will you do the following?

Role

Add a stakeholder role. You can choose from the suggestions or add your own.

Who?

Add a responsible person