Chapter 8

■ Design Concepts
Slide Set to accompany
Software Engineering: A Practitioner’s Approach, 7/e
by Roger S. Pressman

Slides copyright © 1996, 2001, 2005, 2009 by Roger S. Pressman

For non-profit educational use only

May be reproduced ONLY for student use at the university level when used in conjunction
with Software Engineering: A Practitioner's Approach, 7/e. Any other reproduction or use is
These slides are designed to
prohibited without the express written permission of the author.

accompany Software
All copyright
use.
Engineering:
information MUST appear if these slides areA
posted on a website for student

Practitioner’s Approach, 7/e (McGraw-

Hill, 2009) Slides copyright 2009 by
Roger Pressman. 1
Design
■ Mitch Kapor, the creator of Lotus 1-2-3,
presented a “software design manifesto” in Dr.
Dobbs Journal. He said:
■ Good software design should exhibit:
■ Firmness: A program should not have any bugs that
inhibit its function.
■ Commodity: A program should be suitable for the
purposes for which it was intended.
■ Delight: The experience of using the program should
These slides are designed to
be pleasurable one.
accompany Software Engineering: A
Practitioner’s Approach, 7/e (McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 2
Analysis Model -> Design Model

These slides are designed to

accompany Software Engineering: A
Practitioner’s Approach, 7/e (McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 3
Design and Quality
■ the design must implement all of the explicit
requirements contained in the analysis model,
and it must accommodate all of the implicit
requirements desired by the customer.
■ the design must be a readable,
understandable guide for those who generate
code and for those who test and
subsequently support the software.
■ the design should provide a complete picture
These slides are designed to
of the software, addressing the data,
accompany Software
functional, andEngineering: A
behavioral domains from an
Practitioner’s Approach,perspective.
implementation 7/e (McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 4
Quality Guidelines
■ A design should exhibit an architecture that (1) has been created using
recognizable architectural styles or patterns, (2) is composed of components
that exhibit good design characteristics and (3) can be implemented in an
evolutionary fashion
■ For smaller systems, design can sometimes be developed linearly.
■ A design should be modular; that is, the software should be logically
partitioned into elements or subsystems
■ A design should contain distinct representations of data, architecture,
interfaces, and components.
■ A design should lead to data structures that are appropriate for the classes to
be implemented and are drawn from recognizable data patterns.
■ A design should lead to components that exhibit independent functional
characteristics.
■ A design should lead to interfaces that reduce the complexity of connections
These slides are designed to
between components and with the external environment.
A design should be derived using a repeatable method that is driven by
accompany
■
Software Engineering: A
information obtained during software requirements analysis.
Practitioner’s
■ Approach, 7/e (McGraw-
A design should be represented using a notation that effectively
communicates its meaning.
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 5
Design
Principles
■ The design process should not suffer from ‘tunnel vision.’
■ The design should be traceable to the analysis model.
■ The design should not reinvent the wheel.
■ The design should “minimize the intellectual distance” [DAV95] between
the software and the problem as it exists in the real world.
■ The design should exhibit uniformity and integration.
■ The design should be structured to accommodate change.
■ The design should be structured to degrade gently, even when aberrant
data, events, or operating conditions are encountered.
■ Design is not coding, coding is not design.
■ The design should be assessed for quality as it is being created, not
after the fact.
These ■ slides
The design are designed
should toto minimize conceptual (semantic) errors.
be reviewed
accompany Software Engineering: A
From Davis [DAV95]
Practitioner’s Approach, 7/e (McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 6
Fundamental
Concepts
■
Abstraction—data, procedure, control
■
Architecture—the overall structure of the software
■ Patterns—”conveys the essence” of a proven design solution
■ Separation of concerns—any complex problem can be more easily
handled if it is subdivided into pieces
■ Modularity—compartmentalization of data and function
■ Hiding—controlled interfaces
■ Functional independence—single-minded function and low coupling
■ Refinement—elaboration of detail for all abstractions
■ Aspects—a mechanism for understanding how global requirements
affect design
■ Refactoring—a reorganization technique that simplifies the design
These
■ slides
OO design are designed to II
concepts—Appendix
accompany
■ Software Engineering:
Design Classes—provide design detail thatAwill enable analysis
classes to be implemented
Practitioner’s Approach, 7/e (McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 7
Data
Abstraction doo
r
manufacture
m
r odel
typ
number
swing
e
insert
direction
lsight
s
type
weigh
number
These slides are designed to o
t pening
mechanism
accompany Software Engineering: A
Practitioner’s Approach, 7/e (McGraw-
implemented as a data
Hill, 2009) Slides copyright 2009 by
structure
Roger Pressman. 8
Procedural
Abstraction ope
n
details of
algorith
enter
m

These slides are designed to

accompany Softwareimplemented
Engineering: with aA
"knowledge" of
Practitioner’s Approach,
object7/e
the that(McGraw-
is associated with
enter
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 9
Architecture
“The overall structure of the software and the ways in
which that structure provides conceptual integrity for a
system.” [SHA95a]
Structural properties. This aspect of the architectural design
representation defines the components of a system (e.g., modules,
objects, filters) and the manner in which those components are packaged
and interact with one another. For example, objects are packaged to
encapsulate both data and the processing that manipulates the data and
interact via the invocation of methods
Extra-functional properties. The architectural design description
should address how the design architecture achieves requirements for
performance, capacity, reliability, security, adaptability, and other system
These slides are designed to
characteristics.
accompany
Families ofSoftware Engineering:
related systems. The architecturalAdesign should draw
upon repeatable patterns that are commonly encountered in the design
Practitioner’s
of families ofApproach,
similar systems.7/e (McGraw-
In essence, the design should have the
Hill, 2009)
ability toSlides copyright
reuse architectural 2009
building by
blocks.
Roger Pressman. 10
Patterns
Design Pattern Template
Pattern name —describes the essence of the pattern in a short but expressive
name
Intent —describes the pattern and what it does
Also-known-as —lists any synonyms for the pattern
Motivation —provides an example of the problem
Applicability —notes specific design situations in which the pattern is applicable
Structure —describes the classes that are required to implement the pattern
Participants —describes the responsibilities of the classes that are required to
implement the pattern
Collaborations —describes how the participants collaborate to carry out their
responsibilities
Consequences —describes the “design forces” that affect the pattern and the
These slides are designed to
potential trade-offs that must be considered when the pattern is implemented

accompany Software Engineering: A

Related patterns —cross-references related design patterns

Practitioner’s Approach, 7/e (McGraw-

Hill, 2009) Slides copyright 2009 by
Roger Pressman. 11
Separation of Concerns
■ Any complex problem can be more easily
handled if it is subdivided into pieces that can
each be solved and/or optimized
independently
■ A concern is a feature or behavior that is
specified as part of the requirements model for
the software
These By separating
■ slides concerns
are designed to into smaller, and
therefore
accompany moreEngineering:
Software manageable pieces,
A a problem
takes less
Practitioner’s effort and
Approach, 7/etime to solve.
(McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 12
Modularity
■ "modularity is the single attribute of software that
allows a program to be intellectually manageable"
[Mye78].
■ Monolithic software (i.e., a large program composed of
a single module) cannot be easily grasped by a software
engineer.
■ The number of control paths, span of reference, number of
variables, and overall complexity would make
understanding close to impossible.
■ In almost all instances, you should break the design into
These slides are designed to
many modules, hoping to make understanding easier
accompany
and asSoftware Engineering:
a consequence, reduce the A
cost required to build
Practitioner’s Approach, 7/e (McGraw-
the software.
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 13
Modularity: Trade-
offs What
modules
is the "right" number of
for a specific software
design? module development
cost
cost
of
software
module
integration
cost

These slides are designed to

accompany Software Engineering: A
Practitioner’s Approach, 7/e (McGraw-
number of modules
Hill, 2009)optimal
Slides
of
number
copyright 2009 by
Roger Pressman.
modules 14
Information Hiding
modul •
e controlle algorithm
dinterfac • data
e structure
• details of external
interface
• resource allocation
policy
clients "secret
"
These slides are designed to
accompany Software Engineering: A
Practitioner’s Approach, 7/e (McGraw-
a specific design decision
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 15
Why Information Hiding?
■ reduces the likelihood of “side effects”
■ limits the global impact of local design
decisions
■ emphasizes communication through
controlled interfaces
■ discourages the use of global data
■ leads to encapsulation—an attribute of
high quality
These slides design to
are designed
■ results
accompany in higher
Software quality software
Engineering: A
Practitioner’s Approach, 7/e (McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 16
Stepwise
Refinement
ope
n

walk to
reach
door; for
knob;
open repeat until door
door; turn
opens knob
walk if knob doesn't turn,
clockwise;
close
through; thentake key
door. out;find correct
These slides are designed to key;insert in
endi
lock;
accompany Software Engineering:
pull/push
f A
door
move out of
Practitioner’s Approach, 7/eend (McGraw-
way;
Hill, 2009) Slides copyright repeat
2009 by
Roger Pressman. 17
Sizing Modules: Two Views

These slides are designed to

accompany Software Engineering: A
Practitioner’s Approach, 7/e (McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 18
Functional Independence
■ Functional independence is achieved by developing
modules with "single-minded" function and an
"aversion" to excessive interaction with other modules.
■ Cohesion is an indication of the relative functional
strength of a module.
■ A cohesive module performs a single task, requiring little
interaction with other components in other parts of a
program. Stated simply, a cohesive module should
(ideally) do just one thing.
■ Coupling is an indication of the relative interdependence
among modules.
These slides are designed to
■ Coupling depends on the interface complexity between
accompany Software
modules, Engineering:
the point at which entryAor reference is made to a
module, and what data pass across the interface.
Practitioner’s Approach, 7/e (McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 19
Aspects
■ Consider two requirements, A and B.
Requirement A crosscuts requirement B “if a
software decomposition [refinement] has been
chosen in which B cannot be satisfied without
taking A into account. [Ros04]
■ An aspect is a representation of a cross-cutting
concern.

These slides are designed to

accompany Software Engineering: A
Practitioner’s Approach, 7/e (McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 20
Aspects—An Example
Consider two requirements for the SafeHomeAssured.com WebApp.
■
Requirement A is described via the use-case Access camera
surveillance via the Internet. A design refinement would focus on
those modules that would enable a registered user to access video
from cameras placed throughout a space. Requirement B is a generic
security requirement that states that a registered user must be validated
prior to using SafeHomeAssured.com. This requirement is applicable
for all functions that are available to registered SafeHome users. As
design refinement occurs, A* is a design representation for
requirement A and B* is a design representation for requirement B.
Therefore, A* and B* are representations of concerns, and B* cross-cuts
A*.
■ An aspect is a representation of a cross-cutting concern. Therefore, the
design representation, B*, of the requirement, a registered user must be
These slides aretodesigned
validated prior to
using SafeHomeAssured.com, is an aspect of the
accompany
SafeHome Software
WebApp. Engineering: A

Practitioner’s Approach, 7/e (McGraw-

Hill, 2009) Slides copyright 2009 by
Roger Pressman. 21
Refactoring
■ Fowler [FOW99] defines refactoring in the following manner:
■ "Refactoring is the process of changing a software system in
such a way that it does not alter the external behavior of the
code [design] yet improves its internal structure.”
■ When software is refactored, the existing design is examined
for
■ redundancy
■ unused design elements
■ inefficient or unnecessary algorithms
■ poorly constructed or inappropriate data structures
■ or any other design failure that can be corrected to yield a
better design.
These slides are designed to
accompany Software Engineering: A
Practitioner’s Approach, 7/e (McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 22
OO Design Concepts
■ Design classes
■ Entity classes
■ Boundary classes
■ Controller classes
■ Inheritance—all responsibilities of a superclass is
immediately inherited by all subclasses
■ Messages—stimulate some behavior to occur in the
receiving object
■ Polymorphism—a characteristic that greatly reduces the
effort required to extend the design
These slides are designed to
accompany Software Engineering: A
Practitioner’s Approach, 7/e (McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 23
Design Classes
■ Analysis classes are refined during design to become entity
classes
■ Boundary classes are developed during design to create the
interface (e.g., interactive screen or printed reports) that the user
sees and interacts with as the software is used.
■ Boundary classes are designed with the responsibility of managing
the way entity objects are represented to users.
■ Controller classes are designed to manage
the creation or update of entity objects;
■
■ the instantiation of boundary objects as they obtain information
from entity objects;
■ complex communication between sets of objects;
These slides
■
are designed
validation to
of data communicated between objects or between the
accompany user and the application.
Software Engineering: A
Practitioner’s Approach, 7/e (McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 24
The Design Model

These slides are designed to

accompany Software Engineering: A
Practitioner’s Approach, 7/e (McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 25
Design Model Elements
■ Data elements
■ Data model --> data structures
■ Data model --> database architecture
■ Architectural elements
■ Application domain
■ Analysis classes, their relationships, collaborations and behaviors are
transformed into design realizations
■ Patterns and “styles” (Chapters 9 and 12)
■ Interface elements
■ the user interface (UI)
■ external interfaces to other systems, devices, networks or other
producers or consumers of information
■ internal interfaces between various design components.
These■ slides areelements
Component designed to
Deployment elements
accompany
■
Software Engineering: A
Practitioner’s Approach, 7/e (McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 26
Architectural Elements
■ The architectural model [Sha96] is derived
from three sources:
■ information about the application domain for the
software to be built;
■ specific requirements model elements such as data
flow diagrams or analysis classes, their relationships
and collaborations for the problem at hand, and
■ the availability of architectural patterns (Chapter 12)
and styles (Chapter 9).
These slides are designed to
accompany Software Engineering: A
Practitioner’s Approach, 7/e (McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 27
Interface Elements

These slides are designed to

accompany Software Engineering: A
Practitioner’s Approach, 7/e (McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 28
Component
Elements

These slides are designed to

accompany Software Engineering: A
Practitioner’s Approach, 7/e (McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 29
Deployment Elements

These slides are designed to

accompany Software Engineering: A
Practitioner’s Approach, 7/e (McGraw-
Hill, 2009) Slides copyright 2009 by
Roger Pressman. 30