Professional Documents
Culture Documents
Dwnload Full Software Engineering A Practitioners Approach 7th Edition Pressman Solutions Manual PDF
Dwnload Full Software Engineering A Practitioners Approach 7th Edition Pressman Solutions Manual PDF
https://testbankfan.com/download/software-engineering-a-practitioners-approach-7th-
edition-pressman-solutions-manual/
1. Introduction
This document describes the design of the SafeHome system. Many parts of the
SafeHome design, and the process used to develop it, are covered as a running example
in Roger Pressman’s book “Software Engineering: A Practitioner’s Approach, 6th
Edition” © McGraw-Hill, 2004. We will refer to the book simply as SEPA.
The purpose of this document is to assist those who are reading SEPA and wish to
see a more detailed design document describing SafeHome. It can, for example, be used
by faculty who wish to explore the ideas in SafeHome more deeply with their students or
by students who would like to study a more detailed example of the system architectural
model.
Accompanying this document is a file containing a UML model that can be loaded
into the ArgoUML, an open source modeling tool. The version used to develop the model
is ArgoUML 0.16, which is based on UML 1.31. ArgoUML also exports XMI, a format
for interchange of UML models among tools, so an XMI version of the model is also
provided. ArgoUML is available at argouml.tigris.org and runs on any platform that has a
Java implementation. We chose ArgoUML simply because it is easy for anyone to obtain
– it is not as complete and as bug-free as certain commercial tools, but is good enough for
our purposes (and we have found that no tool behaves exactly the way we would like).
A software model can be produced at many different levels of abstraction. The model
presented here is at an intermediate level: It includes diagrams relating the important
hardware units, classes, and states.
The model presented does not correspond completely with the version of SafeHome
described in SEPA. SEPA describes snapshots of a design in progress, whereas this
document represents a subsequent and more complete iteration of SafeHome. We have,
for example, added details that were not discussed in SEPA, but are necessary to explain
how the system as a whole works.
In accordance with modern software engineering practice, the design presented here
should be considered an iteration, and not the ‘final release’. We invite critique and
suggestions for improvement.
1
See appendix 1 for a discussion of the version of UML used.
SEPA describes much of the background of the SafeHome product line; we suggest you
read the relevant sections of the book before proceeding. We will, however, quickly set
the scene:
The SafeHome company has developed an innovative hardware box that implements
wireless Internet (802.11) connectivity in a very small form factor (the size of a
matchbook). The idea is to use this technology to develop and market a comprehensive
home automation product line. This would ultimately provide not only security functions,
but also would enable control over telephone answering machines, lights, heating, air
conditioning, and home entertainment devices. The first generation of the system,
described here, will only focus on home security since that is a market the public readily
understands.
When fully developed the system envisioned by the SafeHome marketing team will
implement hundreds of use cases. As a first step in development, however, we will
identify the use cases that should be available in the first few releases – these will provide
very basic security functionality.
Figure 1 shows that there are there are two main actors (roles played by users of the
system): HouseholdUser and ConfigurationManager. The latter is a sub-actor of the
former since ConfigurationManagers can do everything that HouseholdUsers can.
The Arm System and Disarm System use cases both require the actor to specify an
activation code. The latter is shown as an inclusion use case. The use cases performed by
the Configuration manager require a more sophisticated Log-In use case to be performed.
1.E.6. You may convert to and distribute this work in any binary,
compressed, marked up, nonproprietary or proprietary form,
including any word processing or hypertext form. However, if
you provide access to or distribute copies of a Project
Gutenberg™ work in a format other than “Plain Vanilla ASCII” or
other format used in the official version posted on the official
Project Gutenberg™ website (www.gutenberg.org), you must, at
no additional cost, fee or expense to the user, provide a copy, a
means of exporting a copy, or a means of obtaining a copy upon
request, of the work in its original “Plain Vanilla ASCII” or other
form. Any alternate format must include the full Project
Gutenberg™ License as specified in paragraph 1.E.1.
• You pay a royalty fee of 20% of the gross profits you derive from
the use of Project Gutenberg™ works calculated using the
method you already use to calculate your applicable taxes. The
fee is owed to the owner of the Project Gutenberg™ trademark,
but he has agreed to donate royalties under this paragraph to
the Project Gutenberg Literary Archive Foundation. Royalty
payments must be paid within 60 days following each date on
which you prepare (or are legally required to prepare) your
periodic tax returns. Royalty payments should be clearly marked
as such and sent to the Project Gutenberg Literary Archive
Foundation at the address specified in Section 4, “Information
about donations to the Project Gutenberg Literary Archive
Foundation.”
• You comply with all other terms of this agreement for free
distribution of Project Gutenberg™ works.
1.F.
Most people start at our website which has the main PG search
facility: www.gutenberg.org.