Slide Set to accompany
Web Engineering: A Practitioner’s Approach
by Roger S. Pressman and David Lowe
copyright © 2009
Roger S. Pressman and David Lowe
For Education Use Only
May be reproduced ONLY for student use at the university level when used in
conjunction with Web Engineering: A Practitioner's Approach.
Any other reproduction or use is expressly prohibited.
This presentation, slides, or hardcopy may NOT be used for short courses, industry
seminars, or consulting purposes without the express written permission of the authors.
These slides are designed to accompany Web Engineering: A Practitioner’s Approach 1
(The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009
Chapter 3: The WebE Process
The process must be agile and adaptable, but it must
also be incremental
Why incremental?
Requirements evolve over time
Changes will occur frequently (and always at inconvenient
times
Time lines are short
Incremental delivery allows you to manage this change!
These slides are designed to accompany Web Engineering: A Practitioner’s Approach 2
(The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009
Incremental Delivery
Repeat the development
cycle for each
increment!
These slides are designed to accompany Web Engineering: A Practitioner’s Approach 3
(The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009
WebE Process Activities & Actions
These slides are designed to accompany Web Engineering: A Practitioner’s Approach 4
(The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009
Conducting Framework Activities-I
The first iteration
define business context
establish overall requirements
create a set of usage scenarios
negotiate conflicting needs among stakeholders, and
from this information derive the set of WebApp
increments that is to be delivered.
Develop a broad outline of all components,
recognizing that it will change
These slides are designed to accompany Web Engineering: A Practitioner’s Approach 5
(The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009
Conducting Framework Activities-II
The second iteration
You’ve learned that the first increment is an informational WebApp and
it must be delivered in one week!
You meet with stakeholders and later review your notes:
• Logo and graphics—need aesthetic design.
• One- or two-paragraph introduction.
• CPI mission statement (file exists)
• A word to visitors (someone will write this tomorrow)
• Basic navigation bar will look like …
• About the company
• Our offerings
• Home security products (hierarchical at next level)
• Monitoring services (a list)
• Our Technology (the new sensor)
• Contact us
• Other issues:
• Informational content will change over time.
• This “home page” will be the navigation starting point for content and functions
required for subsequent increments.
These slides are designed to accompany Web Engineering: A Practitioner’s Approach 6
(The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009
Conducting Framework Activities-III
The second iteration
You spend a few minutes developing a plan
• Day 1: Create a prototype layout (a model) of the WebApp.
• Collect and review all existing CPI content and graphics.
• Get stakeholder feedback on prototype, if possible.
• Day 2: Using the prototype as a guide, begin construction of the
increment.
• Build navigation bar.
• Lay out content areas.
• Integrate graphics, links, etc.
• Test all links for validity.
• Review all content for completeness and correctness.
• Day 3: FTP all files to (an existing) domain.
• Perform navigation tests.
• Deployment: Inform selected stakeholders that the
increment is available.
• Day 4: Poll stakeholders for feedback.
• Make modifications based on stakeholder feedback.
These slides are designed to accompany Web Engineering: A Practitioner’s Approach 7
(The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009
Conducting Framework Activities-IV
The next iteration
You’ve deployed the informational WebApp
the communication activity during this second iteration will identify
the requirements (including content and functionality)
assume that the second increment delivers the capability to select and
download product specifications and related information
the process flow is restarted at the beginning, performing the
communication activity for this increment.
The tasks you select to populate each framework activity for the
increment may differ from the tasks performed for the preceding
increment, but the overall process flow remains the same
These slides are designed to accompany Web Engineering: A Practitioner’s Approach 8
(The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009
Revisiting the Framework Activities
WEPA pp. 32 - 42 presents a breakdown of the generic
actions and tasks for each of the five framework
activities
Recognize that a WebE team must refine and adapt
these generic tasks to the problem at hand
And continue to refine them throughout the project
These slides are designed to accompany Web Engineering: A Practitioner’s Approach 9
(The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009
Umbrella Activities
Background activities which occur in parallel with the
main development activities
Equally important to the success of a project
And so should be considered explicitly.
Many umbrella activities can be defined
But only four are crucial for a successful Web engineering
project:
These slides are designed to accompany Web Engineering: A Practitioner’s Approach 10
(The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009
Umbrella Activities
Change management. Manages the effects of change
as each increment is engineered, integrating tools that
assist in the management of all WebApp content
Quality assurance. Defines and conducts those tasks
that help ensure that each work product and the
deployed increment exhibits quality
Risk management. Considers project and technical
risks as an increment is engineered
Project management. Tracks and monitors progress as
an increment is engineered
These slides are designed to accompany Web Engineering: A Practitioner’s Approach 11
(The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright 2009
