CSE 70 UML Overview Classes

CSE 70: Unified Modeling Language Class Diagrams Design Patterns Strategy
Ingolf Krueger
Department of Computer Science & Engineering University of California, San Diego La Jolla, CA 92093-0114, USA
California Institute for Telecommunications and Information Technologies La Jolla, CA 92093-0405, USA
Learning Goals for Today
Ingolf Krueger, 2010
CSE
Learning Goals
Know the use of the Unified Modeling Language (UML) for requirements capture and design.
Be able to draw and understand basic UML class diagrams.
Know and be able to apply the Strategy Pattern
CSE
Unified Modeling Language (UML)
source: http://commons.wikimedia.org/wiki/File:UML_Diagrams.jpg Ingolf Krueger, 2010 CSE 4
UML
A visual language for specifying, constructing, and documenting system artifacts. Provides different language elements (diagrams/text) to model systems from various viewpoints
Structure Behavior
OMG standard since 1997, now at version UML 2.2 Especially useful for modeling/documenting objectoriented systems: requirements, architecture, design
but not limited to that
Ingolf Krueger, 2010 CSE 5
Basics Covered in CSE 70
Behavior
State Machine Use case
Structure
Class
Object Component Composite Structure Deployment
Interaction Overview
Sequence Activity
Communication
Package
CSE 6
UML Class Diagrams
CSE
Example: ChatServer Class in Java

ChatServer.java !
public class ChatServer extends BaseChatServer {! ... ! private String[] clients; ! private int client_index;! ... ! public void sign_on(String client_id) {! clients[client_index++] = client_id;! }! ...! }!!
CSE

ChatServer.java !
inheritance relationship
public class ChatServer extends BaseChatServer {! ... ! private String[] clients; ! private int client_index;! ... ! public void sign_on(String client_id) {! clients[client_index++] = client_id;! }! ...! }!!
CSE

ChatServer.java !
public class ChatServer extends BaseChatServer {! ... ! private String[] clients; ! fields private int client_index;! ... ! public void sign_on(String client_id) {! clients[client_index++] = client_id;! }! ...! }!!
CSE
10

ChatServer.java !
public class ChatServer extends BaseChatServer {! ... ! private String[] clients; ! private int client_index;! methods ... ! public void sign_on(String client_id) {! clients[client_index++] = client_id;! }! ...! }!!
CSE
11
UML Class Diagrams: Basics Attributes/ Fields Superclass
Subclass Inheritance (extends) Operations/ Methods
CSE
12
UML Class Diagrams: Compare to Java Code

public class ChatServer ! extends BaseChatServer {! ... ! private String[] clients; ! private int client_index;! ... ! public void ! sign_on(String client_id) {! clients[client_index++] = ! client_id;! }! ...! }!!
Class Diagrams: Inheritance

public class ChatServer ! extends BaseChatServer {! ... ! private String[] clients; ! private int client_index;! ... ! public void ! sign_on(String client_id) {! clients[client_index++] =! client_id;! }! ...! }!!
Class Diagrams: Attributes/Fields

Class Diagrams: Methods

Class Diagrams: Basics
read: ChatServer is-a BaseChatServer
CSE
17
Classes and Interfaces
CSE
18
Class Diagrams: Interfaces & Classes

public interface IDispatchTarget { !public void close();! }! ! public interface IController extends IDispatchTarget {! !public void ! parseCommand(String cmd);! }! ! public class Client ! implements IController {! ! }!!



Associations, Aggregation
CSE
23
Example: ChatClient
package simplechat.client;! import simplechat.server.*;! ...! public class ChatClientImp {! !private String name;! private ChatServer server;! public void setName(String name) {! this.name = name! }! ...!
ChatClientImp.java !
Example: ChatClient
!public ChatClientImp(String client_id, ! String server_id) {! ! !try {! ! ! !Registry registry = ! LocateRegistry.getRegistry();! ! ! !server = ! (ChatServer) ! registry.lookup(server_id);! ! ! !! ! ! !server.sign_on(client_id);! ...! ! ! !!
Undirected Association
any number of exactly one
Association (undirected)
CSE
26
role/field name
CSE
27
read: every object of class ChatClientImp has exactly one ChatServer every object of class ChatServer has many ChatClientImps
public class ChatClientImp {! ...! private ChatServer server;! ...! } !

public class ChatClientImp {! ...! private ChatServer server;! ...! } !

public class ChatServer {! ...! private ChatClientImp[] clients;! ...! } !

Frequently Used Multiplicities
Symbol 1 n n..m *
Meaning exactly one exactly n at least n and at most m any number of
CSE
32
Design Patterns: Proven solutions for recurring design problems in specific contexts
Why bother? Lets Design a Chat Server that can Handle Messages
First Design
CSE
35
Customer wants: Server with Message Logging Capability
CSE
36
Second Design: Message Logging Server
CSE
37
Customer also wants: Server with Message Encryption Capability
CSE
38
Third Design: Logging OR Encryption
CSE
39
Customer really wants: Logging Server with Encryption Capability
CSE
40
Fourth Design: Logging with Encryption
CSE
41
Pros and Cons of Fourth Design

Pro:
Customer requirement can be fulfilled
Cons:
Unclear design decomposition strategy:
why should message handling dominate logging? why should logging dominate encryption?
Tight coupling between message handling, logging and encryption capability!

Addition of further capabilities leads to exponential spread of the class hierarchy
What if we want to replace the logging/encryption algorithm at runtime: requires restart of entire server!
CSE
42
Separation of Concerns
Let me try to explain to you, what to my taste is characteristic for all intelligent thinking. It is, that one is willing to study in depth an aspect of one's subject matter in isolation for the sake of its own consistency, all the time knowing that one is occupying oneself only with one of the aspects. [] But nothing is gained on the contrary! by tackling these various aspects simultaneously. It is what I sometimes have called "the separation of concerns", which, even if not perfectly possible, is yet the only available technique for effective ordering of one's thoughts, that I know of.1
1E.
W. Dijkstra: "On the role of scientific thought", in E.W. Dijkstra, Selected Writings on Computing: A Personal Perspective, New York, NY, USA: Springer-Verlag New York, Inc., pp. 6066 Ingolf Krueger, 2010 CSE 43
What are the separate concerns of the Server design? Message Handling, Logging, Encryption
How can we separate them out?
CSE
45
Chat Server Interfaces: MessageHandler
CSE
46
Chat Server Interfaces: Encryptor and Logger
CSE
47
How can we bring them back together?
CSE
48
Chat Server with Composition
CSE
49
Example: Server with Composition

public class Server {!
ChatServer.java !
!private MessageHandler handler;! !private MessageLogger logger;! !private MessageEncryptor encryptor;! public Server() {! handler = null;! logger = null;! encryptor = null;! } ...!

Server.java ! ...! public void setHandler(MessageHandler handler){ ! this.handler = handler;! }!
public void setLogger(MessageLogger logger) {! this.logger = logger;! }! public void setEncryptor(MessageEncryptor en) { ! this.encryptor = en;! }! ...!

Server.java ! ...! public void doHandleMessage(Message msg) {! this.handler.handleMessage(msg);! }!
public void doLogMessage(Message msg) {! this.logger.handleMessage(msg);! }! public void doEncryptMessage(Message msg) {! this.encryptor.handleMessage(msg);! }! }!
Example: RSAFileServer
RSAFileServer.java !
public class RSAFileServer {!
public RSAFileServer() {! super();! setHandler(new BasicHandler());! setLogger(new FileLogger());! setEncryptor(new RSAEncryptor()); } ...! }!
CSE
53
Key OO Design Principles
Develop Against Interfaces rather than Implementations Favor Composition over Inheritance
Separation of Concerns: Variability vs. Stability
Separate what varies from what doesnt. OO Mechanisms:

Encapsulation (Classes/Interfaces) Inheritance Association/Aggregation/Composition
How to do it? Design Patterns to the Rescue

What have you learned today?
CSE
56
Learning Goals
Know the use of the Unified Modeling Language (UML) for requirements capture and design.
Be able to draw and understand basic UML class diagrams.
Know and be able to apply the Strategy Pattern
CSE
57

CSE 70 UML Overview Classes

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

CSE 70 UML Overview Classes

Transféré par

Droits d'auteur :

Formats disponibles

CSE 70: Unified Modeling Language Class Diagrams Design Patterns Strategy

Learning Goals for Today

Ingolf Krueger, 2010

Be able to draw and understand basic UML class diagrams.

Know and be able to apply the Strategy Pattern

Ingolf Krueger, 2010

Unified Modeling Language (UML)

source: http://commons.wikimedia.org/wiki/File:UML_Diagrams.jpg Ingolf Krueger, 2010 CSE 4

Basics Covered in CSE 70

UML Class Diagrams

Ingolf Krueger, 2010

Example: ChatServer Class in Java

Ingolf Krueger, 2010

Example: ChatServer Class in Java

Ingolf Krueger, 2010

Example: ChatServer Class in Java

Ingolf Krueger, 2010

Example: ChatServer Class in Java

Ingolf Krueger, 2010

UML Class Diagrams: Basics Attributes/ Fields Superclass

Subclass Inheritance (extends) Operations/ Methods

Ingolf Krueger, 2010

UML Class Diagrams: Compare to Java Code

Class Diagrams: Inheritance

Class Diagrams: Attributes/Fields

Class Diagrams: Methods

Class Diagrams: Basics

read: ChatServer is-a BaseChatServer

Ingolf Krueger, 2010

Classes and Interfaces

Ingolf Krueger, 2010

Class Diagrams: Interfaces & Classes

Class Diagrams: Interfaces & Classes

Class Diagrams: Interfaces & Classes

Class Diagrams: Interfaces & Classes

Ingolf Krueger, 2010

Ingolf Krueger, 2010

Ingolf Krueger, 2010

public class ChatClientImp {! ...! private ChatServer server;! ...! } !

public class ChatClientImp {! ...! private ChatServer server;! ...! } !

public class ChatServer {! ...! private ChatClientImp[] clients;! ...! } !

Frequently Used Multiplicities

Meaning exactly one exactly n at least n and at most m any number of

Ingolf Krueger, 2010

Ingolf Krueger, 2010

Customer wants: Server with Message Logging Capability

Ingolf Krueger, 2010

Second Design: Message Logging Server

Ingolf Krueger, 2010

Customer also wants: Server with Message Encryption Capability

Ingolf Krueger, 2010

Third Design: Logging OR Encryption

Ingolf Krueger, 2010

Customer really wants: Logging Server with Encryption Capability

Ingolf Krueger, 2010

Fourth Design: Logging with Encryption

Ingolf Krueger, 2010

Pros and Cons of Fourth Design

Tight coupling between message handling, logging and encryption capability!

Ingolf Krueger, 2010

How can we separate them out?

Ingolf Krueger, 2010

Chat Server Interfaces: MessageHandler

Ingolf Krueger, 2010