CH 09

Software Engineering: A Practitioners Approach, 6/e
Chapter 9 Design Engineering

copyright 1996, 2001, 2005
R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY for student use at the university level when used in conjunction with Software Engineering: A Practitioner's Approach. Any other reproduction or use is expressly prohibited.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, 2005
Analysis Model -> Design Model
sc e n a r i o - b a se d e l e me nt s
use-cases - text use-case diagrams activity diagrams swim lane diagrams
f l o w- o r i e n t e d e l e me nt s
data flow diagrams control-flow diagrams processing narratives
Co m p o n e n t L e v e l D e sig n
In t e r f a c e D e sig n
Analysis Model
A r c h it e c t u r a l D e sig n
c l a ss- b a se d e l e me nt s
class diagrams analysis packages CR C models collaboration diagrams
be ha v i or a l e l e me nt s
state diagrams sequence diagrams
D a t a / Cla ss D e sig n
Design Model
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 of the software, addressing the data, functional, and behavioral domains from an implementation perspective.
3
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 between components and with the external environment. A design should be derived using a repeatable method that is driven by information obtained during software requirements analysis. A design should be represented using a notation that effectively communicates its meaning.
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. The design should be reviewed to minimize conceptual (semantic) errors.
From Davis [DAV95]
Fundamental Concepts

abstractiondata, procedure, control architecturethe overall structure of the software patternsconveys the essence of a proven design solution modularitycompartmentalization of data and function hidingcontrolled interfaces Functional independencesingle-minded function and low coupling refinementelaboration of detail for all abstractions Refactoringa reorganization technique that simplifies the design
6
Data Abstraction
door
manufacturer model number type swing direction inserts lights type number weight opening mechanism implemented as a data structure
Procedural Abstraction
open
details of enter algorithm
implemented with a "knowledge" of the object that is associated with enter
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 characteristics.
Families of related systems. The architectural design should draw upon repeatable patterns that are commonly encountered in the design of families of similar systems. In essence, the design should have the ability to reuse 9
Patterns
Design Pattern Template
Pattern namedescribes the essence of the pattern in a short but expressive name Intentdescribes the pattern and what it does Also-known-aslists any synonyms for the pattern Motivationprovides an example of the problem Applicabilitynotes specific design situations in which the pattern is applicable Structuredescribes the classes that are required to implement the pattern Participantsdescribes the responsibilities of the classes that are required to implement the pattern Collaborationsdescribes how the participants collaborate to carry out their responsibilities Consequencesdescribes the design forces that affect the pattern and the potential trade-offs that must be considered when the pattern is implemented Related patternscross-references related design patterns
10
Modular Design
easier to build, easier to change, easier to fix ...
11
Modularity: Trade-offs
What is the "right" number of modules for a specific software design?
module development cost
cost of software module integration cost
optimal number of modules
number of modules
12
Information Hiding
module
controlled interface algorithm data structure details of external interface resource allocation policy
clients
"secret"
a specific design decision

13
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 encapsulationan attribute of high quality design results in higher quality software
14
Stepwise Refinement
open
walk to door; reach for knob; open door; walk through; close door. repeat until door opens turn knob clockwise; if knob doesn't turn, then take key out; find correct key; insert in lock; endif pull/push door move out of way; end repeat
15
Functional Independence
COHESION - the degree to which a module performs one and only one function. COUPLING - the degree to which a module is "connected" to other modules in the system.
16
Sizing Modules: Two Views

What's inside?? How big is it??
MODULE
17
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.
18
OO Design Concepts
Design classes

Entity classes Boundary classes Controller classes
Inheritanceall responsibilities of a superclass is immediately inherited by all subclasses Messagesstimulate some behavior to occur in the receiving object Polymorphisma characteristic that greatly reduces the effort required to extend the design
19
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. 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; validation of data communicated between objects or between the user and the application.
Controller classes are designed to manage

20
Inheritance
Design options:

The class can be designed and built from scratch. That is, inheritance is not used. The class hierarchy can be searched to determine if a class higher in the hierarchy (a superclass)contains most of the required attributes and operations. The new class inherits from the superclass and additions may then be added, as required. The class hierarchy can be restructured so that the required attributes and operations can be inherited by the new class. Characteristics of an existing class can be overridden and different versions of attributes or operations are implemented for the new class.
21
Messages
:SenderObject
message (<parameters>) :ReceiverObject
22
Polymorphism
Conventional approach
case of graphtype: if graphtype if graphtype if graphtype if graphtype end case; = linegraph then DrawLineGraph (data); = piechart then DrawPieChart (data); = histogram then DrawHisto (data); = kiviat then DrawKiviat (data);
All of the graphs become subclasses of a general class called graph. Using a concept called overloading [TAY90], each subclass defines an operation called draw. An object can send a draw message to any one of the objects instantiated from any one of the subclasses. The object receiving the message will invoke its own draw operation to create the appropriate graph.
graphtype draw
23
The Design Model

high
a na ly sis m ode l
class diagr ams analysis packages CRC models collabor at ion diagr ams dat a f low diagr ams cont r ol- f low diagr ams pr ocessing nar r at ives use- cases - t ext use- case diagr ams act ivit y diagr ams sw im lane diagr ams collabor at ion diagr ams st at e diagr ams sequence diagr ams class diagr ams analysis packages CRC models collabor at ion diagr ams dat a f low diagr ams cont r ol- f low diagr ams pr ocessing nar r at ives st at e diagr ams sequence diagr ams
Requirement s: const raint s int eroperabilit y t arget s and conf igurat ion
design class r ealizat ions subsyst ems collabor at ion diagr ams
t echnical int er f ace design Navigat ion design GUI design
component diagr ams design classes act ivit y diagr ams sequence diagr ams
design class r ealizat ions subsyst ems collabor at ion diagr ams component diagr ams design classes act ivit y diagr ams sequence diagr ams
de sign m ode l
r ef inement s t o: r ef inement s t o: design class r ealizat ions subsyst ems collabor at ion diagr ams component diagr ams design classes act ivit y diagr ams sequence diagr ams
low
deployment diagr ams
archit ect ure element s
int erface element s
component -level element s
deployment -level element s

24
process dimension
Design Model Elements
Data elements

Data model --> data structures Data model --> database architecture Application domain Analysis classes, their relationships, collaborations and behaviors are transformed into design realizations Patterns and styles (Chapter 10) the user interface (UI) external interfaces to other systems, devices, networks or other producers or consumers of information internal interfaces between various design components.
Architectural elements

Interface elements

Component elements Deployment elements
25
Interface Elements
MobilePhone WirelessPDA
Cont rolPanel
LCDdisplay LEDindicat ors keyPadCharact erist ics speaker wirelessInt erf ace readKeySt roke() decodeKey () displaySt at us() light LEDs() sendCont rolMsg()
Key Pad
< < int erfac e> > Key Pad
readKeyst roke() decodeKey()
Figure 9 .6 UML int erfac e represent at ion for Co n t r o lPa n e l
26
Component Elements
SensorManagement
Sensor
27
Deployment Elements
Cont rol Panel
Security
CPI serv er
homeownerAccess
Personal comput er
externalAccess
Security
Surveillance
homeManagement
communication
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 6/e and are provided Figure 9 .8 deploy m ent diagram for SafeHom e with permission by R.S. Pressman & Associates, Inc., copyright UML 1996, 2001, 2005
28
Design Patterns
The best designers in any field have an uncanny ability to see patterns that characterize a problem and corresponding patterns that can be combined to create a solution A description of a design pattern may also consider a set of design forces.
Design forces describe non-functional requirements (e.g., ease of maintainability, portability) associated the software for which the pattern is to be applied.
The pattern characteristics (classes, responsibilities, and collaborations) indicate the attributes of the design that may be adjusted to enable the pattern to accommodate a variety of problems.
29
Frameworks
A framework is not an architectural pattern, but rather a skeleton with a collection of plug points (also called hooks and slots) that enable it to be adapted to a specific problem domain. Gamma et al note that:

Design patterns are more abstract than frameworks. Design patterns are smaller architectural elements than frameworks Design patterns are less specialized than frameworks
30

CH 09

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

CH 09

Enviado por

Direitos autorais:

Formatos disponíveis

Software Engineering: A Practitioners Approach, 6/e

Chapter 9 Design Engineering

Analysis Model -> Design Model

Design and Quality

For smaller systems, design can sometimes be developed linearly.

implemented with a "knowledge" of the object that is associated with enter

optimal number of modules

a specific design decision

Why Information Hiding?

Sizing Modules: Two Views

Fowler [FOW99] defines refactoring in the following manner:

When software is refactored, the existing design is examined for

Entity classes Boundary classes Controller classes

Controller classes are designed to manage

message (<parameters>) :ReceiverObject

The Design Model

t echnical int er f ace design Navigat ion design GUI design

deployment diagr ams

archit ect ure element s

int erface element s

component -level element s

deployment -level element s

Design Model Elements

Component elements Deployment elements

< < int erfac e> > Key Pad

readKeyst roke() decodeKey()

Figure 9 .6 UML int erfac e represent at ion for Co n t r o lPa n e l

Você também pode gostar