Lesson 5

This module gave a fundamental understanding of the models that were introduced in the first course of this series, Web Site Planning Models. You will see both models applied throughout this course, as a way of making the complex concepts of Web development concrete.
In addition, it is hoped that WebTeam continues to put a human face on the Web development process.

Website planning models provide a structured approach for information architects to design and organize websites. These models vary in complexity and focus, catering to different project needs and objectives. Here are some of the prominent types:

1. Linear Model: This model follows a straightforward, sequential approach. It starts with defining the website's purpose, followed by content development, design, testing, and deployment. This model is best suited for small-scale projects with a clear vision and limited complexity.
2. Waterfall Model: Similar to the Linear Model but more structured, the Waterfall Model divides the project into distinct phases: requirements analysis, design, implementation, testing, deployment, and maintenance. Each phase must be completed before moving to the next. It's suitable for projects with well-defined requirements and minimal changes during development.
3. Agile Model: Contrasting with the Waterfall Model, the Agile Model emphasizes flexibility and iterative development. It involves continuous collaboration with stakeholders and rapid prototyping. The project is divided into small, manageable parts, allowing for regular feedback and adjustments. This model is ideal for projects requiring adaptability and those with evolving requirements.
4. Spiral Model: This model combines elements of both linear and iterative approaches. It focuses on risk assessment and reduction, iterating through planning, risk analysis, engineering, and evaluation phases. With each iteration, the project progressively evolves. The Spiral Model is particularly effective for large, complex projects with significant risks.
5. V-Model: Also known as the Verification and Validation model, this approach emphasizes quality control. Each development phase (e.g., requirements specification, design) is directly linked to a testing phase. It's a disciplined model ensuring that each stage is thoroughly vetted before proceeding. Suitable for projects where quality assurance is paramount.
6. Hybrid Model: This model blends elements of various models to suit specific project needs. For instance, it might combine the structured approach of the Waterfall Model with the flexibility of Agile methodologies. The Hybrid Model is adaptable to a wide range of projects, particularly those that require a balance between strict planning and adaptability.

Each model has its strengths and weaknesses, and the choice depends on the project's size, complexity, stakeholder requirements, and team dynamics. Information architects must evaluate these factors to select the most suitable planning model for their website projects.

You will begin learning about planning a web deployment in the next module, which introduces network architecture, the fourth layer of the Web Interaction Model. Although the standards are not yet fully supported by all browsers in all circumstances, creating standards-compatible pages is the best way to ensure good rendering. As always, learning to use new technologies will take some time and will give you some challenges. Nonetheless the results will be well worth the investment. Big companies are just starting to realize the tangible benefits from the technological investments they made in the past couple of years. Spending money on things that save money is a specialty of American business. This country does not manufacture a whole lot as a result of globalization, but it has the best people working to make sure that imports are delivered cheaply and on time. This is not the ideal scenario where everyone ends up wealthy at the end of the day, but in the evening consumers will be able to receive more rest.

1. Budget: What is the client's budget? The clearer this is, the more helpful it will be for everybody.
2. Design requirements: If a website is needed, how many pages and what features are required? Will an email marketing template also be needed, or company branded banners for social media pages? Decide on the full scope of the project before starting.
3. Purpose of this project: What is the goal of this design project?
4. Target market: Who are you trying to reach with this design project or campaign?
5. Deadline: Set a deadline and allow plenty of time (weeks or months) for the design work to be done.
6. High quality images: For logos, a vector format (.eps or .ai) is required. For photographs, a high resolution (300dpi - dots per inch) is ideal.
7. Content: Text, images, video, infographics and any other content should be provided in its final form early in the life of the design project.
8. Copyright information for content: Who owns the content, what permission has been obtained to use it, and will attribution be required?
9. Samples of previous design work: How will this design project need to comply to the company's style guide? What has the client done in the past, and will this project reflect past designs or take a new path?