Web Engineering
Swati Patil
Web Engineering
WebE is the process used to create high quality
Web-based applications (WebApps)
WebE draws heavily on the principles and
management activities found in software
engineering processes
There are things that make WebE a unique
endeavor
WebE Process Overview
Formulation of the problem
Planning
WebApp requirements analysis
Architectural, navigational, and interface design
System implementation using specialized
languages and tools associated with the Web
Configuration management, quality control, and
maintenance mechanisms are established early
Continuous
Immediacy
evolution
Content-
Security
driven
Network WebApp Aesthetics
intensive Attributes
WebE Application Categories
Informational Transaction
Downloads Oriented
Customizable Service-oriented
Interaction Portal
User input Database access
Data warehousing
WebApp Enabling Technologies
Component-based development
Security (encryption, firewalls, etc.)
Internet standards
Web programming tools
WebE Process Model:
Formulation
Goals and objectives, scope for first increment
What is the motivation for the WebApp?
Why is the WebApp needed?
Who will use the WebApp?
Informational goals
user's intention for using the content
Applicative goals
ability to perform tasks within the WebApp
WebE Process Model:
Planning
Estimate project cost
Evaluate risks
Define finely granulated schedule for first
increment
Define coarser schedule for subsequent
increments
WebE Process Model:
Analysis
Establishes requirements and identifies content items
Content analysis
content provided by WebApp is identified
Interaction analysis
use-cases developed to describe user interaction
Functional analysis
usage scenarios used to define operations and functions
applied to WebApp content
Configuration analysis
WebApp environment described in detail
WebE Process Model:
Engineering
Content design and
production tasks are Architectural design,
one thread navigation design,
interface are the other
thread
WebE Process Model:
Page Generation and Testing
Content and technical designs are merged to produce
executable web pages
Testing exercises WebApp navigation, attempts to uncover
errors in applets/scripts/forms, and checks for
environment incompatibilities
WebE Process Model:
Customer Evaluation
Each increment of the WebApp is
reviewed
Changes required by customer are
applied to next increment
WebE Best Practices
Take time to understand the business needs and
product objectives, even if WebApp details are vague.
Describe how users will interact with the WebApp
using a scenario-based approach.
Develop a brief project plan.
Spend time modeling what you are going to build.
WebE Best Practices
Review models for consistency and
quality.
Use tools and technology that enable you
to construct the system with as many
reusable components as possible.
Don’t rely on users to debug the WebApp,
design comprehensive tests and execute
them before releasing the system.