RE: process of a site development

Would add
1.	define requirements and scope where this will discuss the players,
functionality, infrastructure, software and hardware.
2.	Define deliverables for example, functional specification, test
requirements, quality assurance requirements, change request process
3.	Define configuration management and file release process
4.	either make a make a separate bullet for quality assurance or add a slash
to Testing and couple it there

-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org]On Behalf
Of Lisa Seeman
Sent: Thursday, January 25, 2001 4:45 PM
To: WAI
Subject: process of a site development

Here is a  preliminary draft of a some type of diagram for Jason's
introduction to the guidelines.
We intend to discuss the process of a site development and were
accessibility can be incorporated into this process.
Try to imagine this as a flow diagram. Please add omissions comments.....
Cycle of Development: (flow down)
*	Brainstorm
*	Storybook
*	Prototype
*	Content
*	Testing
*	Usability testing
*	Promote
*	Evaluate
*	Maintain
Areas of Development: ( flow in parallel)

Server Side: Programming, scripting and installation

Client or Sever  Side: Graphical, text and semantic content (data models),
page design/layout,   markup, coding, scripting, formalization of languages,
templates,  style sheets and rendering information, coordination.