Chapter Two Outline

User Centered Web Development Lifecycle (UCWDLC?)

1. Classic SDLC (examples in book)

   1. Project Identification and Selection

   2. Project Initiation and Planning

   3. Analysis

   4. Logical Design

   5. Physical Design

   6. Implementation

   7. Maintenance

2. Other Models: Evolutionary, Waterfall, Prototyping, etc.

3. Where Does the User Fit In?

   1. Traditionally only in the early and late phases

   2. Ideal extreme is participatory design

   3. Best to find a balance for each project

4. Uniqueness of Web Development Projects

   1. Different browsers behave differently

      1. Microsoft, for example, uses its own “standards”

   2. Different connections to the Internet

   3. Different displays

   4. Usability is even more important

      1. Frequency of use

      2. Level of interactivity

      3. Users will leave and never come back

   5. Users and their input

      1. Must use a process or model even for redesigns

      2. Must include the users

      3. Preferably in all stages of development, but at least requirements gathering and testing phases

   6. Clients

      1. These are not necessarily the users

      2. Managing conflict can be tricky

5. Models for Web Development Projects

   1. These address the certain needs of the web

   2. Fleming model as an example (others in book) (good to compare to SDLC)

      1. Information gathering

      2. Strategy

      3. Prototyping

      4. Implementation

      5. Launch

      6. Maintenance and growth

   3. Changes and additions to models

      1. Iterate over early stages

      2. Joint Application Development

      3. Certain stages are more important for user involvement

         1. Requirements gathering

         2. Usability testing

6. The User Centric Lifecycle Model

   1. From Dr. Lazar, adapted from other models

   2. Beneficial for Web projects and current for today's environment

   3. Seven main stages

      1. Define the Mission of the Web Site and the User Population

         1. What are you doing and for whom are you doing it?

      2. Collect the User Requirements for the Web Site

         1. User technology, type or category of site, content

      3. Create the Conceptual Design of the Web Site

         1. Logical design, prototypes, general features

      4. Create the Physical Design of the Web Site

         1. Start coding and functional testing

      5. Perform Usability Testing of the Web Site

         1. Task completion, feedback, make changes now!

      6. Implement and Market the Web Site

         1. Hosting issues, getting the word out

      7. Evaluate and Improve the Web Site

         1. Periodic assessment, maybe even redesigns

7. Project Management

   1. Objectives

      1. Clarify

      2. Clarify

      3. Clarify

   2. Responsibilities

      1. Staff appropriately and evenly.

   3. Documentation

      1. Most important and must be communicated to appropriate parties.

   4. Progress Reports

      1. Milestones help to keep things moving.