Course Code: GNETS5014

Lecture 1
Introduction to Web Interface and its perspectives
Lecture 1: Introduction to Web Interface and its perspectives

Introduction:
In present days the quality, performance, reliability of the web based
system and web application have become very important as the
dependency on them have increased a lot.

And also the demand and expectation from this application have also
increased.

This had led to a much more complex and difficulty to handle the
different phases of web based application.

The phases are development, design, maintenance and deployment.

Lecture 1: Introduction to Web Interface and its perspectives

Introduction:
In this chapter we will give a brief description of the web has evolved and
how the web has been categorized based on its functionality.

Here we also describe the web development limitations and we will also
why there is a need for more sophisticated development model for web.

In the later part of the chapter we will provide a overview of the web
engineering the how the web development model has evolved.

In the conclusion part of this chapter we will see the different challenges
faced by the web engineering researchers and web developers.
Lecture 1: Introduction to Web Interface and its perspectives

Learning Outcome:
At the end of this chapter student will be able to understand the following:

Evolution of web.

Various type of development practices of WEB.

Definition of WEB engineering and how the web engineering is not same as
Software engineering.

WEB development.

Challenges faced in the WEB system and how it can overcome.

Lecture 1: Introduction to Web Interface and its perspectives

Topic:
No. Topic Title
1. Evolution of THE WEB
2. WEB development practices
3. WEB engineering
4. Evolutionary WEB development
5. WEB system design: challenges
Lecture 1: Introduction to Web Interface and its perspectives

Learning Outcome:
No. word Definition
1. website Web site consist of more than one related web page,
it comprises of text, video, image etc. it will be
hosted on one or more web servers. It can be
accessed via network such as internet through
Uniform Resource Locator (Internet Address).
2. Markup Language The markup language was specifically developed so
that they can be used for presentation, definition and
processing of text in the web pages. There are
specific codes that can be used for specifying the
layout and style. This code is contained in the text
file. The code for specifying the formatting of text are
called TAGS. XML and HTML are one of the example
of mark-up language.
3. Hypertext The text is used to connect to other web page. It is
not compelled to be linear.
Lecture 1: Introduction to Web Interface and its perspectives

Terminology:
No. word Definition
4. Hyper Text Markup It is the most widely used mark-up language used in
Language (HTML) the web today. It uses tags for designing the web
pages. It is used to structure the multimedia, text
content in the WebPages. It is also used to construct
hyper link so that they can connect to other pages.
5. XML XML (EXtensible mark-up language), it is similar to
the HTML, but it is used for transporting the data
from one location to another. ity does not display
data and its self-descriptive. It was recommended by
the W3C.
6. Semantic Web The web is used to so that things can be understand
by the computers. It explains the relationship
between two parties A and B and also their attributes
(Price, Size, Weight).
Lecture 1: Introduction to Web Interface and its perspectives

Terminology:
No. word Definition
4. Holistic Holistic means they are concerned with or related to
the complete system rather than on focusing on the
treatment of, analysis of or dissection of individual
parts.
Lecture 1: Introduction to Web Interface and its perspectives

Terminology:
The WEB can be presumed as a large network, which is formed by
interconnecting various parts, this is useful in many ways, it is considered to
be easy to get insode the web, but extremely difficult to come out.

The WEB initial objective was for sharing of information via multiple web
pages and just using the text data.

With the advances in the Web standards, technology and Internet

technology the Web has grown rapidly in a short time. So is its Scope and
uses.

In a matter of 10 years the number of websites has grown from just 100 to
more than 45 million web sites.
Lecture 1: Introduction to Web Interface and its perspectives

Lecture 1.1:Evolution of Web

To many areas of industry are used widely so that they can extend their
operational

capabilities. Some of these areas are:

Database systems and legacy systems.

Mobile web application: these are has developed and evolved a lot
since the advances in the wireless technology, communication devices
and portable computing.

Travel industry, hospital industry, enterprises, educational, banks,

training institutions, government agencies and entertainment business.
Lecture 1: Introduction to Web Interface and its perspectives

Lecture 1.1:Evolution of Web

In the last few years we have seen some new web standards that have
eveolved some of them are Web Services, XML, Web personalization
techniques, the Semantic Web, Web intelligence, Web mining, context aware
services and mobile etc.

The evolution of Web has brought many different thing together some of
them are study of information, media , communication technology, and use
of different types of information any where and any time and can be used by
different devices such as desktop, tablets, notebooks, mobile phones etc.
Lecture 1: Introduction to Web Interface and its perspectives

Lecture 1.2: WEB development practices

Web development is not similar to the application work , but it is work of
authoring (creation of content and presentation of it).

The process here involves a lot of artistic side just like the process used for
designing layout for park, designing building and their construction. But it
requires much more than this, it requires a following of systemic process and
it not just putting together a set of related web pages together as most of us
think it is.

Initially as we now the web was developed to propagation of text based

information, but it has grown from there to images, image maps, applets,
forms, style sheets and scripts), to online transaction, collaborative work in a
web based environment, and now it also supports mobile web applications,
web services and multilingual web sites.
Lecture 1: Introduction to Web Interface and its perspectives

Lecture 1.2: WEB development practices

Web application development does not mainly depends on the standards of
prctices but mainly depends on the experience and knowledge of the small
group of people working and their personnel development practices.

Development of web based system is not a single time event, but it is

iterative process. The development cannot not be stopped at the beginning
stages as the web is continuously evolving.

While developing the many attributes of web based system are not given
proper attention, some of these attributes are compatibility, maintainability,
security, interoperability and reliability. Some of the web system lack basic
evaluation, testing and documentation.
Lecture 1: Introduction to Web Interface and its perspectives

Lecture 1.2: WEB development practices

Improper goals, vision lacking, design flaws, flowed development process,
improper management of development are some of the reasons why a web
page fail.
Lecture 1: Introduction to Web Interface and its perspectives

Lecture 1.3: WEB engineering

For a web application or system to be successfully developed, deployed,
and higher quality , the engineers need to use systematic approach and
engineering , scientific and management principle.

To have a successful web development, the emerging web engineering

discipline promotes a disciplined and holistic approach.

In order to avoid any serious implication in the web engineering it is

important to manage successfully the diversity and complexity of
development of web applications.
Lecture 1: Introduction to Web Interface and its perspectives

Lecture 1.3: WEB engineering

Web engineering focuses to bring the development of web application
under control, risk minimization, quality improvement, and better
maintainability ( here we calculate the time needed to restore the site back
to normal after the site has crashed) and also the web application scalability.

The software engineering and the web engineering have 2 common phases
the software development and programming phases and both are not similar
to one another.

The web engineering is a multidisciplinary activity has it involves different

areas like human computer interaction, requirements engineering, graphic
engineering, hypermedia or hypertext engineering, design, system analysis,
models for testing and simulation, retrieval, indexing of information,
management of project and more.
Lecture 1: Introduction to Web Interface and its perspectives

Lecture 1.4: Evolutionary Web development

The critical point to be considered while a web application is developed is
the capability for information maintenance, and the web site function and
structure should be scalable as the information presented here can change
few times in a day or change every few minutes.

Most of the web application, it is difficult to mention clearly and fully the
requirement of the systems or what the system should possess as the initial
stages as compared to the final stages. Hence the web application are said to
be evolutionary.

The process of web development should conatain a well defined activities

and steps. This steps and activities should be able to be followed by the
developer and can be trackable and measured at any time.
Lecture 1: Introduction to Web Interface and its perspectives

Lecture 1.4: Evolutionary Web development

Web application characteristics that make the development of web
application challenging are complexity, changeability, real time interaction
and presentation of information etc. because of these factor it is also
difficult to decide accurately the time and man power required to develop
and design these applications.

Figure 1.1: Process involved in Evolutionary Web development

Lecture 1: Introduction to Web Interface and its perspectives

Lecture 1.4: Evolutionary Web development

Evolutionary Web development process (Figure 1.1)

Help in identifying and noting the requirements

Help developers in recognize the context in which these web
application must be deployed.
Allow integration of disciplines different in nature.
Enables a better communication between the members who are
involved in the process of development.
Make the information content to be managed easily.
Provisions continuous maintenance and evolution.
Aids in successfully managing the diversity and complexity of the
process.
Lecture 1: Introduction to Web Interface and its perspectives

Lecture 1.5: Evolutionary Web development

The internet which is a open platform provides some unequalled and
unique opportunity as they do not control the number of visitors, how they
access and when they access the web applications or web systems.

Some of the challenges faced by the developers of the web application and
the users of this web applications are:

The issues such as security, slow access, failure of threats of web system
may cause loss in number of customers.

Its is difficulty to satisfy all the customer who have different needs and vary
in skill level.
Lecture 1: Introduction to Web Interface and its perspectives

Lecture 1.5: Evolutionary Web development

The user feel frustrated when the web site they are accessing is very
complex, not user friendly, more or confusing information presentation.
Worst part here is that these customers will spread to other how frustrated
they feel about the web site.

The different stakeholder that need to be satisfied by these web systems

are people funding the web site, people maintaining the web site, and the
organization that is using the system.

Reliability, scalability, flexibility, availability, usability, maintainability,

performance, testability, evolution, integrity, comprehension etc. are the
some of the factor that describe how the system meets future and current
need of the system and the expected service level.
Lecture 1: Introduction to Web Interface and its perspectives

Summary:
In this lesson, the following has been discussed:

Many Web systems also lack proper testing, evaluation and document.
Causes of failure of Web applications include lack of vision and improper
goals, flawed design and development process and poor management of
development effort. Web Engineering uses scientific, engineering, and
management principles and systematic approaches to successfully develop,
deploy, and maintain high-quality Web systems and applications. The
emerging discipline of Web engineering advocates a holistic, disciplined
approach to successful Web development. It aims to bring Web-based system
development under control, minimize risks and improve quality,
maintainability, and scalability of Web applications. Web engineering and
software engineering both involve programming and software development
but it cannot be considered as recreation of software engineering.
Lecture 1: Introduction to Web Interface and its perspectives

Summary:
Diverse areas like requirements engineering, human computer interaction,
hypermedia/hypertext engineering, graphics engineering, systems analysis
and design, testing modeling and simulation, information indexing and
retrieval, project management etc contribute and make web engineering a
multidisciplinary.
Lecture 1: Introduction to Web Interface and its perspectives

Exercises & Self-assessment

1. An agile team:
A) Is collaborative
B) Manages change well
C) Focuses on rapid delivery
D) All of the above
E) None of the above

2. A WebE framework is composed of

A) Activities, actions, and tasks

B) Organizations, teams, and people
C) Architecture, structure and components
D) All of the above
E) None of the above
Lecture 1: Introduction to Web Interface and its perspectives

Exercises & Self-assessment

3. Which of the following is not one of the 12 agility principles:

A) Business people and developers must work together daily throughout the
project.
B) Working software is the primary measure of progress.
C) The best architectures, requirements, and designs emerge from self–
organizing teams.
D) Avoid all documentation in order to eliminate bureaucracy
E) Welcome changing requirements, even late in development. Agile
processes harness change for the customer's competitive advantage.
Lecture 1: Introduction to Web Interface and its perspectives

Exercises & Self-assessment

4. The five WebE framework activities are:

A) Listening, gathering, defining, building, implementing

B) Defining, modeling, constructing, testing, deploying
C) Communicating, planning, modeling, constructing, deploying
D) None of the above

5. An umbrella activity

A) Shields the project when problems arise

B) Is deployed only on a "rainy day"
C) Occurs throughout a WebE project
D) None of the above
Lecture 1: Introduction to Web Interface and its perspectives

Exercises & Self-assessment

6. Software engineering

A) Has had no effect on WebApp development

B) Has had no influence on the WebE process
C) Is the underlying philosophy from which WebE has emerged
D) None of the above

7. WebE methods and tools

A) Are similar in some respects to software engineering methods and tools

B) Should be used only in conjunction with the WebE process
C) Should be selected based on the needs of the WebApp project
D) All of the above
E) None of the above
Lecture 1: Introduction to Web Interface and its perspectives

Exercises & Self-assessment

8. A WebE development process should:

A) Embrace change
B) Suppress creativity and dependence of developers
C) Emphasize incremental development using short development cycles
D) All of the above
E) Some of the above
F) None of the above.
Lecture 1: Introduction to Web Interface and its perspectives

Exercises & Self-assessment

9. Which of the following is not a recommended development best
practice?

A) Take the time to understand business needs and product objectives, even
if the details of the WebApp are vague.
B) Minimize opportunities for the client to suggest changes.
C) Develop a project plan, even if it’s very brief.
D) Don’t reinvent when you can reuse.
E) Don’t rely on early users to debug the WebApp—design comprehensive
tests and execute them before releasing the system.
Lecture 1: Introduction to Web Interface and its perspectives

Exercises & Self-assessment

10. You're about to embark on a WebApp development project. How
should you begin:

A) Sketch out the design of the home page and build a prototype that you
think will meet user’s needs
B) Collect all of the content that you think will be needed
C) Talk with potential users in an effort to understand what they want how
they’ll interact with the WebApp
D) None of the above
 Lecture 2
A Practical Process For Web Engineering
Lecture 2: A Practical Process For Web Engineering

Introduction:
The web application is a information system that is made of more than one
web pages which is generated when requested by a user and it can be used
to deliver a complex functionality and content to large population of end
user.

Some of examples of such applications are search engines, online stores,

industrial sites, auctions, games and news sites. These web application have
the following features a) complex navigation model, a complex data design,
various computation model, consideration for security and substantial
published content.
Lecture 2: A Practical Process For Web Engineering

Introduction:
In this chapter we will look explain in details the AWH (Augmented
WebHelix) that extents the WH (WebHelix), it does so by allowing a
continuous and release feature at the end of each phase and by giving a
qualitative evaluation framework which is know as PEF (Project Evaluation
Framework) and evaluating the status of the project using a systematic
approach; and capability to evaluate the project after every phase of helix
slice. In the second part of the chapter we will describe the PEF process and
framework and derivatives.

Finally we look at the application and consequences of augmented

WebHelix process.
Lecture 2: A Practical Process For Web Engineering

Learning Outcome:

At the end of this chapter, student will be able to understand:

Development process of the current Web applications.

AWH (Augmented WebHelix).
The PEF (project Evaluation Framework(.
AWH process applications.
Lecture 2: A Practical Process For Web Engineering

List of Topic:

No. Topic Title

1. Current WEB application development processes
2. The augmented webhelix process
3. Project evaluation framework
4. Application of THE augmented webhelix process
Lecture 2: A Practical Process For Web Engineering

Terminology:
No. word Definition
1. Web Application It is a collection of web pages, which is generated to a
request from the user, it is also used to deliver
content of complex nature and functionality to a
large end user population.
2. Waterfall Model This describes software engineering method which
follows a development model that is sequential and
linear.
3. Spiral Method It’s a evolutionary version of the well known
development model the incremental prototyping.
4. Framework In term of software engineering the term framework
means a concept where the generic functionality
provided by the software can be changed by code,
hence a providing software which are specific to
application.
Lecture 2: A Practical Process For Web Engineering

Terminology:
No. word Definition
5. Information System A collection of components used for collecting,
processing, storing and information
communication.
Lecture 2: A Practical Process For Web Engineering

Lecture 2.1: Current WEB application development processes

Current Web application development processes are based on the business
oriented approach. Web engineering provides a balance between publishing,
programming and aspects of business of web application development. Web
engineering is used for defining the theory involved in web application
development.

Web application has all the modules required for performing the functions
of business. All the implementation must follow a systematic and practical
methodology. We may also later use some kind of approach toward project
management which is required for application building.

Consider all the merits of the currently available design processes of

web application.
Lecture 2: A Practical Process For Web Engineering

Lecture 2.1: Current WEB application development processes

There is no one “THE” web application process that can be accepted
universally.

All most all the currently available model are a extension of the software
engineering processes standards.

Waterfall model is ideal for developing a program for maintaining file in

main frame. But this can be restrictive is used for building web application.

Spiral model is a iterative process, this will be ideal for developing web
application.
Lecture 2: A Practical Process For Web Engineering

Lecture 2.1: Current WEB application development processes

.NET framework is a object oriented development model which has been
proposed for developing web application. UML model is been proposed for
adding stereotypes to navigation of Web.

UML are object oriented and iterative. They have been used in the Agile
Unified process (AUP) and Rational Unified Process (RUP).

XP (Extreme Programming) is considered to be a natural fit for developing

the web applications. This is because it required minimum design, accetance
testing and a quick prototype development.
Lecture 2: A Practical Process For Web Engineering

Lecture 2.2: The augmented webhelix process

WebHelix (WH) process used for system development is a modified version
of the spiral model.

It is not considered good for developing a straight forward application

because.

It does not consider metrics which is used for determining when to

continue or release to the next helix slice.

Moving from one helix slice to another depends on the ROI.

Lecture 2: A Practical Process For Web Engineering

Lecture 2.2: The augmented webhelix process

Figure 2.1: The original WebHelix process

Lecture 2: A Practical Process For Web Engineering

Lecture 2.2: The augmented webhelix process

Process of AWH is as follows:
It uses PEF evaluation frame work. This is used to qualitatively
evaluate to decide on whether to continue in the present state or jump
to the next helix slice of the project.

The evaluation is performed at the end of every stage, instead of at the

end of slice stage. It assists in keeping the project in track.

The bellow mentioned choices are given to the project at the end of
each slice so that the project better reflect the real world.

Stop from going to next slice and project is released (go to

maintenance and deployment phase of project).
Lecture 2: A Practical Process For Web Engineering

Lecture 2.2: The augmented webhelix process

Process of AWH is as follows:
It uses PEF evaluation frame work. This is used to qualitatively
evaluate to decide on whether to continue in the present state or jump
to the next helix slice of the project.

The evaluation is performed at the end of every stage, instead of at the

end of slice stage. It assists in keeping the project in track.

The bellow mentioned choices are given to the project at the end of
each slice so that the project better reflect the real world.

Stop from going to next slice and project is released (go to

maintenance and deployment phase of project).
Lecture 2: A Practical Process For Web Engineering

Lecture 2.2: The augmented webhelix process

Go to the next slice and project is release ( released part of project
will enter the maintenance and deployment phase).

Go to next slice while not releasing the project as further features

must be added.
Lecture 2: A Practical Process For Web Engineering

Lecture 2.2: The augmented webhelix process

Figure 2.2: The Augmented WebHelix process

Lecture 2: A Practical Process For Web Engineering

Lecture 2.2: The augmented webhelix process

As illustrated in Figure 2.2 :

The process will start with the PreHelix1 (Business analysis) and PreHelix2
(Planning phase).

The process enter the initial phase after the planning phase. Each slice
consist if the analysis phase, design phase, coding phase and testing phase.
Analysis is the first phase of the slice.

After every stage of the slice there exist a evaluation phase (ε used for
representing the evaluation phase). Here a decision is take to whether to
continue to next phase or not using the PEF.
Lecture 2: A Practical Process For Web Engineering

Lecture 2.2: The augmented webhelix process

During the evaluation phase of the final stage (test phase) a decision had to
be made to whether to release the project or to proceed to the next helix
slice or perform both.

After completing the last helix slice PostHelix1(deployment phase) and

PostHelix2 (Maintenance phase).

If we decide to continue at the end of helix slice, then there exist 2 possible
path for the project. To proceed to the Analysis phase or other one is to
proceed to the development phase of the project.
Lecture 2: A Practical Process For Web Engineering

Lecture 2.3: Project evaluation framework (PEF).

The PEF is used to determine following in the current state of project:

Is it ok to jump to next phase of helix slice.

Is the project ready to be released.
Or is it required to jump to next helix slice.

PEF is based on NFR ( Non Functional Requirements) framework.

NFR can be used for software artifacts, evaluating process and establishing
traceability. It is

Goal oriented
Process oriented
Qualitative.
Lecture 2: A Practical Process For Web Engineering

Lecture 2.3: Project evaluation framework (PEF).

PEF is used to check whether the current stage is complete or not. This is
performed at the end of every stage on Helix. This process is called phase-
stage evaluation.

When it is determined as completed, the project can either repeat the

process or jump to the next phase.

Factor Independence Graph (FIG) is produced after the testing phase after
completing the steps of the Project Evaluation Framework. It is used to create
a relation among the factor that will affecting the continue and release stage.
Lecture 2: A Practical Process For Web Engineering

Lecture 2.4: Application of THE augmented webhelix process

With respect to designing the information system, the web application can
be build while giving less attention to coding and more attention is paid to
design and system analysis.

Application where AWH are used are:

A website that contains message board, updatable newsletters,

specialized search engine, and e portfolio for all former and current
students.

AWH was used by the Information system e-commerce programing for

developing five different web application projects like e-realty store, e-
book store, e-ball store, e-jersey shop and e-T-shirt store. Example
Games E-Store project.
Lecture 2: A Practical Process For Web Engineering

Lecture 2.4: Application of THE augmented webhelix process

Figure 2.3: The flow of the Games E-Store Project through AWH process
Lecture 2: A Practical Process For Web Engineering

Summary
In this lesson, the following has been discussed

A business-oriented approach is the basis of today’s Web application

development processes. Web engineering strikes a balance among the
programming, publishing and business aspects of developing Web
applications. - Release the project and continue to the next slice. The process
starts with the Business Analysis and Planning phases, respectively, the
PreHelix1 and PreHelix2 phases. After the Planning phase, the project enters
the first slice of the helix at the Analysis phase and then proceeds clockwise
round the slice through the Design, Coding, and Test phases. After each
phase in a slice there is an Evaluation phase, where in the PEF is applied to
decide whether to proceed to the next phase in the slice or not. During the
evaluation the Test phase the major decision of whether to release the
product Release or to continue to the next slice of the helix (Continue) or
both is determined.
Lecture 2: A Practical Process For Web Engineering

Summary
After the final slice the post helix phases of deployment (Deploy or
PostHelix1) and maintenance (Maintain or PostHelix2) are performed. If a
Continue decision is made at the end of a slice then the project can proceed
along two paths simultaneously— one taking it to the Analysis phase of the
subsequent slice and the other taking the project to the deployment phase.
Lecture 2: A Practical Process For Web Engineering

Exercises & Self-assessment:

1. The "old school" approach for the development of WebApps refers to

A) The use of HTML as the only development language

B) The use of informality, urgency, intuition, and art as the driving forces for
WebApp development
C) The creation of content-driven websites
D) All of the above

2. The CPI "business manager" becomes really interested in Safe Home

because

A) It's an interesting new product

B) It will require the application of cool technology
C) There are good people to do the job
D) It will add substantially to the bottom line
Lecture 2: A Practical Process For Web Engineering

Exercises & Self-assessment:

3. Which of the following statements differentiates WebApps from
conventional software?

A) Performance can be a critical aspect of the application

B) Load is unpredictable
C) Immediacy is often a primary goal
D) All of the above
E) None of the above
4. Apple's iTunes site has downloaded more than 4 billion songs over the
past few years. What WebApp category best describes the site:

A) It is a download WebApp
B) It is an interaction WebApp
C) It is a transaction-oriented WebApp
D) All of the above
E) None of the above
Lecture 2: A Practical Process For Web Engineering

Exercises & Self-assessment:

4. Apple's iTunes site has downloaded more than 4 billion songs over the
past few years. What WebApp category best describes the site:

A) It is a download WebApp
B) It is an interaction WebApp
C) It is a transaction-oriented WebApp
D) All of the above
E) None of the above

5. Any WebApp can begin as a simple informational site and evolve into
another category over time.

A) True
B) False
Lecture 2: A Practical Process For Web Engineering

Exercises & Self-assessment:

6. An incremental process implies that

A) The entire WebApp is delivered at one time but progress is measured

incrementally
B) The WebApp is delivered in separate operational increments over a period
of time
C) The process incrementally grows more complex
D) None of the above

7. The communication activity is comprised of three actions:

A) Formulation, elicitation, and negotiation

B) listening, teaching, and prototyping
C) Research, definition, and action
D) None of the above
Lecture 2: A Practical Process For Web Engineering

Exercises & Self-assessment:

8. It is reasonable to state that the communication activity is iterative in
nature.

A) True
B) False

9. Which of the following tasks would be performed as part of the

communication activity?

A) Identify user categories

B) Identify the problem
C) Gather requirements
D) Develop usage scenarios
E) all of the above
F) None of the above
Lecture 2: A Practical Process For Web Engineering

Exercises & Self-assessment:

10. Since changes will only be requested after the first WebApp increment
is delivered, it's recommended that you delay planning your approach to
change management until work on second increment commences.

A) True
B) False

11. In order to perform WebApp planning, all you need to do is define an

informal project schedule.

A) True
B) False
Lecture 2: A Practical Process For Web Engineering

Exercises & Self-assessment:

12. Your goal in modeling is to develop a conceptual representation that
can include everything except:

A) Verbal descriptions
B) Executable prototypes
C) Sketches
D) Graphical representations

13. Which of the following is not a requirements modeling task:

A) Presenting content and content relationships

B) Refining detailed functional components
C) Establishing interface requirements
D) Refining usage scenarios
Lecture 2: A Practical Process For Web Engineering

Exercises & Self-assessment:

14. Which of the following is a design modeling task?

A) Developing the navigation scheme

B) Establishing WebApp constraints and performance
C) Developing content
D) Construction of functional components

15. Every well-designed WebApp should exhibit:

A) Flash, animation and color

B) Layout, spacing, and orderly text
C) Functionality, graphing, and form-based input
D) Firmness, commodity and delight
Lecture 2: A Practical Process For Web Engineering

Exercises & Self-assessment:

16. The overall intent of a design model is to:

A) Provide a means to assess WebApp quality before it is built

B) Provide a construction road map for Web engineers
C) Provide representations of content, functional and navigation
D) Provide a representation of the WebApp architecture
E) all of the above
F) None of the above

17. The construction activity incorporates both code generation and testing.

A) True
B) False
Lecture 2: A Practical Process For Web Engineering

Exercises & Self-assessment:

18. Which of the following is not a deployment task:

A) Deliver the WebApp increment to a server

B) Establish an online feedback mechanism
C) Test navigation
D) Evaluate end-user interaction

19. Which of the following is not an umbrella activity

A) Change management
B) Design
C) Quality assurance
D) Risk management