SafeHome Products Security and M

Case Study - Overview

Web Engineering:
A Practitioners Approach
Roger Pressman, David Lowe

This website is a partial prototype of the fictional SafeHome Products application - a case study developed to support the book: Web Engineering: A Practitioners Approach, written by Roger Pressman and David Lowe.

The website prototype is only a partial implementation, and aims to illustrate the main components of the site and some of the design elements. On each of the prototype pages there is a link in the top right corner which, when clicked, provides some additional information regarding the design of that page.

Note: Where the real WebApp would contain a link, but in this prototype the link isn't implemented, it will be shown with a dotted underline.


Dummy Link

This website is only a partial prototype of the fictional SafeHome Products application. As such this link is not yet operational. Non-operational links are shown with a dotted underline.


SafeHome Products
Security and Monitoring Systems for Home and Office

WEPA Book Home
Case Study Overview




Bonus Information
Evaluating Quality: Evaluating the User Response

No matter how many quality criteria a WebApp meets, it will fail if end-users do not like it or are unhappy with it. For this reason, it is important to establish a "user-centric" model for WebApp quality. The following table lists a key set of criteria which can be used in evaluating users' responses to a WebApp design. This is based on TAM (Technology Acceptance Model) - a widely used model which looks at how users accept and use a new "technology" (in this case a new WebApp is the "technology" under consideration). The model includes two key measures: perceived usefulness (PU)—the extent to which the user believes that the technology will help achieve operational goals; and perceived ease-of-use (EOU)—he extent to which the user believes that the system is easy to use (takes minimum effort).

Performance expectancy
U6: I would find the WebApp useful in my job.
RA1: Using the WebApp enables me to accomplish tasks more quickly.
RA5: Using the WebApp increases my productivity.
OE7: If I use the WebApp, I will increase my chances of getting a raise.

Effort expectancy
EOU3: My interaction with the WebApp would be clear and understandable.
EOU5: It would be easy for me to become skillful at using the WebApp.
EOU6: I would find the WebApp easy to use.
EU4: Learning to operate the WebApp is easy for me.

Attitude toward using technology
A1: Using the WebApp is a bad/good idea.
AF1: The WebApp makes work more interesting.
AF2: Working with the WebApp is fun.
Affect1: I like working with the WebApp.

Social influence
SN1: People who influence my behavior think that I should use the WebApp.
SN2: People who are important to me think that I should use the WebApp.
SF2: The senior management of this business has been helpful in the use of the WebApp.
SF4: In general, the organization has supported the use of the WebApp.

Facilitating conditions
PBC2: I have the resources necessary to use the WebApp.
PBC3: I have the knowledge necessary to use the WebApp.
PBC5: The WebApp is/is not compatible with other WebApps I use.
FC3: A specific person (or group) is available for assistance with WebApp difficulties.

I could complete a job or task using the WebApp…
SE1: If there was no one around to tell me what to do as I go.
SE4: If I could call someone for help if I got stuck.
SE6: If I had a lot of time to complete the job for which the WebApp was provided.
SE7: If I had just the built-in help facility for assistance.

ANX1: I feel apprehensive about using the WebApp.
ANX2: It scares me to think that I could lose a lot of information using the WebApp by hitting the wrong key.
ANX3: I hesitate to use the WebApp for fear of making mistakes I cannot correct.
ANX4: The WebApp is somewhat intimidating to me.

Behavioral intention to use the WebApp
BI1: I intend to use the WebApp in the next <n> months.
BI2: I predict I would use the WebApp in the next <n> months.
BI3: I plan to use the WebApp in the next <n> months.

As each WebApp increment is introduced, a questionnaire containing the questions posed above could be provided to a representative set of end-users. Where appropriate, the questions could be customized to suit the particular WebApp being developed. Once the answers are statistically analyzed, the results can provide the WebE team with an indication of user-centric perceptions of design (and construction) quality.