|
Documentation
|

Documentation for both client and instructor should include the
work done so far. Brief projects need only contain the highlighted
and starred* items.
- Web Site Objectives and Project Scope*
- Audience Definition*
- Production Timeline/Schedule
- Success Criteria
- User Needs and Task Analysis*
- Content Inventory*
- Quality Assurance Plan
- Information Architecture*
- Branding, Design, Look, and Feel*
- Usability Test Plan
- Technical Specifications
- Web Hosting Report
- Maintenance Plan
- Usability Test Findings and
- Quality Test Findings
- Site Revision Report
The team's Document specialist or Editor should
proofread the printed copies and make any changes necessary to
insure proper spelling, grammar, and page layout.
Tips
- These reports should be printed, and the client's copy should
be bound in a report folder.
- Since they were initially created in HTML, the individual
parts of the report will probably not print to best advantage.
Suggestion: open them in MS-Word so you can conveniently
specify where you want the page-breaks and perform other necessary
paper-formatting.
|
|
Submitting Final Materials
|
- Team leader: Inform the instructor and other team
members when the site is on the public server by emailing
them the URI.
- Document specialist / Editor: After document text
has passed QA and copies are assembled (with all pages in
order), distribute copies to each team member and submit one
copy to the instructor. Client copy should be given to the
instructor as well, unless you are directed otherwise.
|