The Web Site Development Process Model illustrates the six general phases for developing a Web site: defining the client's scope and expectations;
through the Web team's strategies for assigning completion requirements; and, finally, delivering the product to the client and establishing maintenance protocols.
But let's get back to the question originally posed when you were introduced to this model:
Question: How does the site get built?
Each development phase integrates four additional elements to implement the design strategy.
These include roles, objectives, deliverables, and activities, and these are the Web team's nuts and bolts for building a Web site.
To give you a real world sense of how a design team assigns the required objectives, deliverables, and activities, you'll be re-introduced to WebTeam,
and learn who on the team is responsible for each of the six phases of development.
Process models are especially useful for a complex procedure involving many participants. By looking closely at ways to break the process down into steps and components,
you will avoid some potentially serious problems you can run into if your team rushes into production without careful consideration and planning.
By the end of this module, you will be able to:
Identify the key elements of the Discovery phase
Identify the key elements of the Definition phase
Identify key success factors and risks of the Discovery and Definition phases
Describe legal, ethical, and regulatory risks in the Definition phase
Describe the documents created during the Design phase
Describe the requirements Definition and the design and architecture specification
Identify the key elements of the Development phase
Identify the key elements of the Delivery phase
Identify the key elements of the Post-delivery phase
In the next lesson, you will learn how the process begins, identifying the key elements in the Discovery phase.