Scribd
Upload
9 views

Chapter 2- Introduction

Chapter 2 of Web Engineering defines an agile framework for building industry-quality WebApps, emphasizing customer satisfaction and responsiveness to changing requirements. It outlines the principles of an agile process, including frequent delivery of working software and collaboration between developers and stakeholders. The chapter also discusses the importance of adapting the framework to project needs and highlights best practices for effective WebApp development.

Uploaded by

ayabahaa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
9 views

Chapter 2- Introduction

Chapter 2 of Web Engineering defines an agile framework for building industry-quality WebApps, emphasizing customer satisfaction and responsiveness to changing requirements. It outlines the principles of an agile process, including frequent delivery of working software and collaboration between developers and stakeholders. The chapter also discusses the importance of adapting the framework to project needs and highlights best practices for effective WebApp development.

Uploaded by

ayabahaa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 15

Web Engineering

Chapter 2
Chapter 2: WebEngineering

• We define it this way:


– an agile, yet disciplined framework for buildingindustry‐
quality WebApps.

• We must understand the meaningof:


– Agile
– Disciplined framework
– Industry quality
Why Agility?

• Business strategies and rules changerapidly

• Management demands near‐instantaneous


responsiveness (even whensuch demands are
completely unreasonable

• Stakeholders often don’t understand the


consequences of the Web and keep changing their
mind even as they demand rapid delivery

• An agile approach helps cope with this fluidity and


uncertainty.
What is an AgileProcess?

• Agile Web engineering combines a philosophy and a


set of development guidelines. The philosophy
encourages:
– customer satisfaction
– early incremental delivery of theWebApp
– small, highly motivated projectteams
– informal methods
– minimal work products
– overall development simplicity.
What is an Agile Process?(cont’d)

• An agile process stresses delivery over analysis and


design (although these activities are not
discouraged), and active and continuous
communication between developers andcustomers.
• Our highest priority is to satisfy the customer through early and
continuous delivery of valuablesoftware.
• Welcome changing requirements, even late in development. Agile
processes harness continuous change for the customer'scompetitive
advantage.
• Deliver working software increments frequently, from as often as every
few days to every few months, with a preference to the shorter
timescales.
• Business people and developers must work together daily throughout the
project.
• Build projects around motivated people. Give them the environment and
support they need, and trust them to get the job done. The most efficient
and effective method of conveying information to and within a
development team is face‐to‐faceconversation.
Underlying AgilityPrinciples - II

• Working software is the primary measure of progress.


• Agile processes promote sustainable development. The sponsors,
developers, and users should be able to maintain a constant pace
indefinitely.
• Continuous attention to technical excellence and good design enhances
agility.
• Simplicity—the art of maximizing the amount of work not done—is
essential.
• The best architectures, requirements, and designs emerge fromself‐
organizing teams.
• At regular intervals, the team reflects on how to become more effective,
then tunes and adjusts its behavioraccordingly.
What is a WebEFramework?

• A framework is a set of activities that will always be


performed for every Web engineering project – though the
nature of the activities might vary to suit the project.
• Each framework activity is composed of a set of actions
• Actions encompass
– work tasks
– work products
– quality assurance points,and
– project milestones

• A framework also has a set of “umbrella activities”


A Generic Framework
The WebE Framework: Activities

• Communication. Involves heavy interaction and collaboration with


the customer (and other stakeholders) and encompasses
requirements gathering and other relatedactivities.
• Planning. Establishes an incremental plan for the WebEwork.
• Modeling. Encompasses the creation of models that assist the
developer and the customer to better understand WebApp
requirements and the design
• Construction. Combines both the generation of HTML, XML, Java,
and similar code with testing that is required to uncover errors in the
code.
• Deployment. Delivers a WebApp increment to the customer
who evaluates it and provides feedback based on the evaluation.
Adapting the Framework

• Adapt to the problem, to the project, to the team, and to the


organizational culture
• And continue to adapt throughout the project as circumstances change!

• Adaptation leads to:


• Overall flow of activities, actions, and tasks and the interdependencies among them
• Degree to which work tasks are defined within each framework activity
• Degree to which work products are identified and required
• Manner in which quality assurance activities are applied
• Manner in which project tracking and control activities are applied
• Overall degree of detail and rigor with which the process is described
• Degree to which customers and other stakeholders are involved with the project
• Level of autonomy given to the software project team
• Degree to which team organization and roles are prescribed
The Influence of SoftwareEngineering

• Quality: foster a continuous process improvement culture

• Process: the glue that holds the technology layers together

• Methods: provide the technicalhow‐to’s

• Tools: support for the process and the methods


WebE Methods

• Communication methods

• Requirements analysis methods

• Design methods

• Construction methods

• Testing methods
What about Tools and Technology?

… tools and technology are very important,


but they’ll work well only if they’re used within
the context of an agile framework for Web
engineering and in conjunction with proven
methods for understanding the problem,
designing a solution, and testingit thoroughly.
WebE Best Practices

• Take the time to understand business needs and product objectives, even
if the details of the WebAppare vague.
• Describe how users will interact with the WebApp using a scenario‐based
approach.
• Always develop a project plan, even if it’s verybrief.
• Spend some time modeling what it is that you’re going to build.
• Review the models for consistency andquality.
• Use tools and technology that enable you to construct the system with as
many reusable components aspossible.
• Don’t reinvent when you canreuse.
• Don’t rely on early users to debug the WebApp—design and use
comprehensive tests before releasing thesystem.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy