Hi Kathy,

Well funnily enough, I'm doing this as we speak. What I found is that you still need to capture the requirements but more importantly you need to do your audience analysis as input into determining the Information Architecture of the website. From the BA point of view, the audience analysis is key. It drives everything else. Still the same BA techniques but a website has extra types of information you need to capture. 

I'm a bit drunk now cause its Sunday night and I've been away for the weekend. If you want more information, say so and I'll reply tomorrow.

Kimbo

 Hi Kathy,

We're doing a corporate website that is basically a brochure site. Little functionality other than searching and some online forms entry.

I think when doing website requirements you have to extend the normal BA activities to include some other activities. The main things to consider are:

1. Business requirements - same old, same old. What does the business want, what are the objectives, what functionality is needed. Remember to define your publishing processes. Do you have a Content Management System or are you going to acquire one?

2. Audience Analysis - including:

2.1 who are the main website users

2.2 what information are they looking for when they come to the website

2.3 How often do they come

2.4 what are the differences between each audience group

2.4 etc

3. Information Architecture - audience analysis is a pre-requisite. Defines the structure, navigation, look and feel, etc. We're hiring experts to help with this.

4. Content review and creation - if its based on an existing website do a content audit, content to-be and gap the difference. Someone has to write the content too eventually

5. Change management plan - including the processes to keep the website up to date when you go live, cultural change, new roles and responsibilities, process changes / new processes, etc

Jump in anyone else out there if I've missed anything.

Very high level Kathy. Hope it helps.

Kimbo