Lesson 1

Here's a breakdown of the typical roles, objectives, deliverables, and activities involved in a Website Development Process Model. Keep in mind that specific models and methodologies can vary.
Roles

• Project Manager: Oversees planning, budget, timelines, and team coordination.
• Web Designer: Responsible for UI/UX design, visual layout, and aesthetics.
• Web Developers:
  • Front-end Developers: Implements design using HTML, CSS, JavaScript.
  • Back-end Developers: Handles server-side logic, databases, and functionality.
• Content Writer: Creates compelling and optimized website copy.
• SEO Specialist: Ensures the website is search-engine friendly.
• Quality Assurance (QA) Tester: Tests functionality, usability, and cross-browser compatibility.
• Client/Stakeholders: Provide input, feedback, and approvals.

Objectives

• Meet the User's Needs: Create a website that aligns with target audience needs and expectations.
• Deliver on Business Goals: Achieve the organization's objectives for the website (e.g., generating leads, sales, brand awareness).
• On Time and On Budget: Complete the project within agreed-upon constraints.
• High Quality: Develop a well-structured, functional, and visually appealing website.

Deliverables (Can Vary Based on Project)

• Planning Documents: Project scope, requirements, sitemaps, wireframes.
• Design Assets: Mockups, prototypes, style guides.
• Website Code: HTML, CSS, JavaScript, server-side scripts.
• Database: Database structure and data (if applicable).
• Content: Text, images, videos.
• Documentation: User manuals, technical documentation.
• Test Reports: Results of QA testing and bug fixes.

Activities (Common Phases in Many Models)

1. Information Gathering/Planning: Defining project scope, requirements, target audience, sitemap.
2. Design: Creating wireframes, mockups, visual design.
3. Development: Front-end and back-end coding, database integration.
4. Content Creation: Writing copy, preparing images and media.
5. Testing: QA testing for functionality, usability, compatibility.
6. Launch/Deployment: Making the website live.
7. Maintenance: Ongoing updates, bug fixes, security monitoring.

Important Considerations:

• Methodology: Website development models can be linear (e.g., Waterfall) or iterative (e.g., Agile). The methodology chosen influences the structure of these phases.
• Team Size and Complexity: Roles might be combined or expanded based on the project.

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.

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.