Development Models   «Prev  Next»

Lesson 1

Applying Phases of the Web Site Development Model

# Website Development Process Model: Roles, Objectives, Deliverables, and Activities Developing a website is a multidisciplinary endeavor that entails a sequential process involving distinct phases. Each phase is characterized by specific roles, objectives, deliverables, and activities that contribute to the creation of a functional, aesthetically appealing, and user-friendly website. Here we delineate the six general phases of the Website Development Process Model. ## Phase 1: Planning ### Roles: - Project Manager - Business Analyst - Stakeholders ### Objectives: - Define the purpose and scope of the website - Identify target audience - Conduct a feasibility analysis ### Deliverables: - Project Charter - Requirements Specification Document - Sitemap ### Activities: 1. Initial consultation between stakeholders and project team 2. Market research and feasibility study 3. Drafting the project charter and requirement specifications ## Phase 2: Design ### Roles: - UI/UX Designer - Graphic Designer - Content Strategist ### Objectives: - Create a wireframe or prototype - Develop a cohesive visual theme ### Deliverables: - Wireframes - Design Mockups - Style Guide ### Activities: 1. Sketching initial design concepts 2. Prototype creation and validation 3. Finalizing design elements, typography, and color schemes ## Phase 3: Development ### Roles: - Front-end Developer - Back-end Developer - Database Administrator ### Objectives: - Translate design into code - Implement functionality and interactivity - Database design and integration ### Deliverables: - Source Code - Database Schema - API Endpoints ### Activities: 1. Setting up development environment 2. HTML, CSS, and JavaScript coding for front-end 3. Back-end logic implementation and database integration ## Phase 4: Testing ### Roles: - QA Tester - Developers - Project Manager ### Objectives: - Identify bugs and performance issues - Validate code against requirements ### Deliverables: - Test Cases - Bug Reports - Performance Metrics ### Activities: 1. Unit, integration, and system testing 2. Cross-browser and cross-device testing 3. Performance and security assessment ## Phase 5: Deployment ### Roles: - System Administrator - DevOps Engineer - Project Manager ### Objectives: - Launch the website - Monitor initial performance ### Deliverables: - Deployed Website - Deployment Script - Initial Performance Report ### Activities: 1. Configuration of hosting environment 2. Data migration 3. Code deployment and initial monitoring ## Phase 6: Maintenance ### Roles: - Support Engineer - System Administrator - Stakeholders ### Objectives: - Ensure smooth operation - Implement updates and improvements ### Deliverables: - Periodic Maintenance Reports - Software Patches - Content Updates ### Activities: 1. Monitoring server performance and error logs 2. Applying patches and security updates 3. Content updates and stakeholder feedback integration By diligently following these phases, involving the designated roles, achieving the stated objectives, delivering on the expected deliverables, and engaging in the outlined activities, an organization ensures the successful execution of a website development project from inception to completion.
The Website Development Process Model illustrates the six general phases for developing a Web site, such as defining the client's scope and expectations. Through the Web team's strategies for assigning completion requirements and delivering the product to the client and establishing maintenance protocols. But let us 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
  1. roles,
  2. objectives,
  3. deliverables, and
  4. 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 will be re-introduced to the Web Team, and learn who on the team is responsible for each of the six phases of development.
Process models are especially useful for a complex procedures involving many participants. By looking closely at ways to break the process down into steps and components, you will avoid some potentially serious problems that may run into if your team rushes into production without careful 1) consideration and 2) planning. Focus on the requirements of the website, create the architecture, and then implement the required tasks which will fulfill the functionality of the website.

Module Objectives

By the end of this module, you will be able to:
  1. Identify the key elements of the Discovery phase
  2. Identify the key elements of the Definition phase
  3. Identify key success factors and risks of the Discovery and Definition phases
  4. Describe legal, ethical, and regulatory risks in the Definition phase
  5. Describe the documents created during the Design phase
  6. Describe the requirements Definition and the design and architecture specification
  7. Identify the key elements of the Development phase
  8. Identify the key elements of the Delivery phase
  9. 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.

Software Architecture