Introduction to Web Engineering
A classroom presentation that mirrors the book and presents the core ideas behind the web, its building blocks, lifecycle, and tools.
- Use the deck for teaching, revision, or quick exam preparation.
- The content mirrors the four book sections in a presentation format.
- Use the arrow keys, buttons, or slide dots to move around.
Focus
Week 1 Presentation
Use
Present this page in class or as a quick revision deck.
What students will learn
The deck follows the same teaching flow as the main book, but presents the material in concise slide-sized sections.
- Explain how the web evolved from document sharing to a software platform.
- Describe the browser, server, database, and service layers of a web application.
- Identify the main phases of the web engineering lifecycle.
- Choose tools based on requirements rather than trends alone.
Focus
Overview
Use
Present this page in class or as a quick revision deck.
The web began as linked documents
The first web solved a simple but important problem: sharing information across machines through links, addresses, and a common document format.
- URL gave every resource a stable address.
- HTTP defined how browsers and servers exchange content.
- HTML gave the web a universal document structure and readable semantics.
- These three standards made the web portable across many machines.
Focus
1.1 History
Use
Present this page in class or as a quick revision deck.
From static pages to interactive platforms
The modern web added interaction, data, automation, and real-time services that turned websites into applications.
- Web 1.0 was mostly read-only and static.
- Web 2.0 added dynamic behavior and user-generated content.
- Today the web delivers apps, APIs, cloud services, and mobile experiences.
- Engineering now includes collaboration, persistence, and continuous updates.
Focus
1.1 Evolution
Use
Present this page in class or as a quick revision deck.
Historical choices still affect engineering
Older standards still shape compatibility, accessibility, security, and performance decisions in modern systems.
- Engineers must support older browsers and devices.
- Security and accessibility are easier when standards are understood.
- Backward compatibility is part of modern planning.
- The web grows by building on the standards it already has.
Focus
1.1 Why it matters
Use
Present this page in class or as a quick revision deck.
A web application is a system of parts
The browser, server, database, and external services each play distinct roles in request handling and user experience.
- The browser handles layout, input, and visible interaction.
- The server processes requests, applies business rules, and manages authentication.
- The database stores structured data and supports queries, relationships, and persistence.
- External services add email, payment, caching, and storage capabilities.
Focus
1.2 Components
Use
Present this page in class or as a quick revision deck.
Requests move through clear layers
A single user action can travel through multiple components before the response returns to the browser.
- Input starts in the browser and is captured through forms or interactions.
- The server validates the input and orchestrates work.
- Data may be fetched from a database or a third-party API.
- The final response is rendered back in the browser for the user.
Focus
1.2 Request flow
Use
Present this page in class or as a quick revision deck.
Dependency failures affect the user experience
When one service fails, the whole application can slow down, lose functionality, or break completely.
- Slow queries and missing indexes hurt performance.
- Email, payment, and storage providers can become single points of failure.
- Monitoring and graceful fallback are part of web engineering.
- Engineering quality includes diagnosing and handling failure, not only building features.
Focus
1.2 Reliability
Use
Present this page in class or as a quick revision deck.
Web engineering follows a lifecycle
Projects move through planning, design, implementation, testing, deployment, and maintenance.
- Requirements define the problem and constraints.
- Design shapes the architecture and user flow.
- Implementation and testing turn plans into working software.
- Every stage creates artifacts that support the next stage.
Focus
1.3 Lifecycle
Use
Present this page in class or as a quick revision deck.
The lifecycle is continuous, not linear
After launch, feedback and production data drive the next round of improvements.
- Deployment is not the end of the project.
- Maintenance includes fixes, updates, and new features.
- Iteration reduces risk and improves quality over time.
- Real systems evolve because user needs and environments keep changing.
Focus
1.3 Iteration
Use
Present this page in class or as a quick revision deck.
Testing protects usability and reliability
Good testing checks the behavior users see and the technical details behind it.
- Test correctness, security, accessibility, and performance.
- Use technical tests and user-centered checks together.
- Production feedback should feed future design decisions.
- Testing is part of engineering discipline, not a final extra step.
Focus
1.3 Quality
Use
Present this page in class or as a quick revision deck.
Web engineering uses a full toolchain
Tools support coding, testing, deployment, collaboration, and monitoring.
- HTML, CSS, and JavaScript shape the front end.
- PHP, Python, Node.js, and similar platforms run the back end.
- Git, testing tools, and hosting complete the stack.
- Operational tools such as monitoring and CI/CD are part of the stack too.
Focus
1.4 Tools
Use
Present this page in class or as a quick revision deck.
Good tool choices follow requirements
The best stack is the one that fits the team, deployment model, and project goals.
- Prefer technologies that solve the actual problem.
- PHP remains practical for server-rendered content and simple hosting.
- Monitoring and workflow tools are part of quality, not extras.
- A good stack balances capability, familiarity, and maintainability.
Focus
1.4 Choosing tools
Use
Present this page in class or as a quick revision deck.
How the ideas fit together in one system
A campus portal or learning platform shows every topic working together in one realistic application.
- The browser presents content and interactions to students.
- The server manages logins, course actions, and business rules.
- The database stores users, content, and enrollment data.
- External services can handle email notifications or file storage.
Focus
Applied Example
Use
Present this page in class or as a quick revision deck.
What students should remember
The web is a system, not just pages. Good engineering depends on structure, process, and the right tools.
- The web evolved from documents to applications.
- Web apps are built from multiple cooperating components.
- Lifecycle discipline and tool choice determine long-term quality.
- The strongest systems combine standards, structure, and maintainable workflows.
Focus
Recap
Use
Present this page in class or as a quick revision deck.