Chapter 1

Need for Web Engineering: (Page 1)

In early days, websites were built using
1. Informality – easy work environment
2. Urgency – rapid action
3. Intuition–quality that will guide through complex
Situations.
4. Art- leads to aesthetic form and function
But there were problems…

1
Approach Problem

Informality Some amount of requirement

Gathering and planning are
necessary
Urgency Decisions may have broad
consequences
Intuition Management and technical skills are
required
Art leads Solid design is also required

2
WebApp Attributes (Page 5)

1. Network Intensiveness:
Every WebApp resides on a network and must
serve the needs of a diverse community of clients.
The network will enable communication between client-
based features of the WebApp and the and the servers.

3
2. Concurrency:
A large number of users may access the WebApp at one
time.
The actions of one user or one set of users may have an
impact on the actions of other users.

3. Unpredictable load.

The number of users of the WebApp may vary by orders of

magnitude from day to day.
WebApp must be capable of handling an indeterminate
number of events simultaneously.

4
4. Performance.

If a WebApp user must wait too long the user may decide to
go elsewhere.
If the WebApp responds too slowly to an event, litigation may
result.
5. Availability.

Although an expectation of 100 percent availability is

unreasonable, users of popular WebApps often demand
access on a “24/7/365” basis.
The WebApp must be designed to achieve this ideal.

5
6. Data driven.
The primary function of many WebApps is to use
hypermedia to present text, graphics, audio, and video
content to the end user.
The WebApp must access a database that contains
information about each customer.

7. Content sensitive.
The quality and aesthetic nature of content remains an
important determinant of the quality of a WebApp. The
users are nontechnical people who demand simple, yet
meaningful content presentation.
6
8. Continuous evolution.
WebApps evolve continuously in a planned and orderly
way.
The evolution of the WebApp will demand an “incremental”
approach to its development.

9. Immediacy.
Immediacy means the compelling need to get software to
Market.
Web engineers must use methods for planning, analysis,
design, implementation, and testing that are required for
WebApp development in a short period of time.

7
10. Security.
WebApps are available via network access, in order to
protect sensitive content and provide secure modes of data
transmission, strong security measures must be
implemented throughout the infrastructure that supports a
WebApp.

11. Aesthetics.
An undeniable part of the appeal of a WebApp is its look
and feel.
WebApp must be both simple and elegant.
Aesthetics is a key element for the acceptance of the
system.
8
Categories of WebApp (Page 8)

1. Informational WebApps.
An informational WebApp—one that contains read only
content with simple navigation and links.
2. Download WebApps.
WebApp with a capability that allows visitors to to download
the product specs.
The WebApp now incorporates informational and download
capability.

9
3. Customizable WebApps.
You want to tailor the content presented at the website to
the specific needs of each customer type, using jargon and
presenting content
that will meet their needs.
WebApp that is customizable for each user.

4. Interaction WebApps.
A WebApp where people can chat, ask and answer
questions, provide product testimonials, and the like.
A WebApp that supports a chat room feature.

10
5. User Input WebApps.
A WebApp that implements forms-based input so that every
request for information is organized in a predictable
manner.

6. Transaction-Oriented WebApps.
WebApp provides a series of algorithms for computing
hardware and monitoring pricing based on forms-based
input.
The user is provided with an instant information based on
the input provided via the forms.

11
7. Service-Oriented WebApps.

The user inputs a description of a problem and is then

assisted in the design of a solution.
This service can lead directly to sales revenue.
8. Portals.

To help solve the problem of users WebApp provides links

to appropriate websites that do have answers.
The WebApp guides users to a wide variety of useful
information sources.

12
11. Database Access.

The WebApp provides

(1) All product details
(2) All customer-related information
(3) All monitoring related information.
These databases can be queried using aspects of the user
input elements of the WebApp.

12. Data Warehousing.

The WebApp has access to multiple databases and to extract
information that will be useful for customers.
13
Web Engineering: (Page 12)

Web engineering proposes an agile, yet disciplined

framework for building industry-quality WebApps.

The meaning of Agile:

 Business strategies and rules change rapidly.

 Management demands quick response.
 Stakeholders keep changing their minds.
 An Agile way of working helps to solve these problems.

14
Agile Process:

Agile Web engineering combines a philosophy and set of

guidelines. The philosophy encourages
 Customer satisfaction
 Early delivery of WebApp
 Small, highly motivated development teams
 Informal methods
 Simplicity
Agile process gives importance to delivery over analysis and
design.

15
The WebE process framework: (Page 13)
A WebE process framework is a set of activities that are
applicable to all WebApp projects, regardless of their size or
complexity.
The following WebE activities are part of framework:
Communication. Involves heavy interaction and collaboration with
the customer.
Planning: Making an incremental plan for the WebE work.
Modeling: The creation of models that assist the developer
and the customer to better understand WebApp requirements.
Construction: Combines both the generation of HTML, XML, Java,
and similar code with testing.
Deployment: Delivers a WebApp increment to the customer.

16
 Figure: A WebE process Framework
In addition, the framework also includes a set of umbrella
activities that are applicable across the entire WebE
process.

17
The Components of Web Engineering. (Page 16)
The influence of Software Engineering.

Figure: Software Engineering Layers

Quality: It demands a continuous process improvement.
Process: It holds the different technology layers together
Methods: They provides the technical how tos.
Tools: They provide support for process and methods.
18
WebE Methods Reside within the Process Framework: (Page-19)
Communication methods.
Define the approach used to facilitate communication between Web engineers and
all other WebApp stakeholders.
Requirements analysis methods.
Provide a basis for understanding the content to be delivered by
a WebApp.
Design methods.
A series of design techniques that address WebApp content, application and
information architecture, interface design and navigation structure.
Construction methods.
Apply a broad set of languages, tools, and related technology to the creation of
WebApp content and functionality.
Testing methods.
It is the technical reviews of both the content and design model and many testing
techniques.

19
Exercise Questions:
1. Write about the need for Web Engineering.
2. Explain in detail the attributes that a Web application usually has.
3. What are the different categories of Web applications?
4. What is Web Engineering?
5. State the meaning of Agile.
6. Write about WebE process framework.
7. What are the components of Web Engineering?
8. How many WebE Methods Reside within the Process Framework?
9. Explain the Web Engineering process framework?

20