Upload
others
View
17
Download
0
Embed Size (px)
Citation preview
Software DesignThe Dynamic Model
Design Sequence Diagrams and Communication DiagramsInstructor: Dr. Hany H. AmmarDept. of Computer Science and Electrical Engineering, WVU
Ouline
UML Development – Overview The Requirements, Analysis, and Design
Models Static and Dynamic Design Examples
UML Development - Overview
PROGRAM
ACTORS
ANALYSISSpecify Domain Objects
Detailed DESIGN
IMPLEMENTATION
DATA
DICTIONARY
TimeUSE CASES
ANALYSISCLASS DIAGRAM(S)
IMPLEMENTATIONActivity DIAGRAMS
SEQUENCEDIAGRAMS
OPERATION CONTRACTS
StateChart DIAGRAMs
DEPLOYMENT DIAGRAMSUBSYSTEM CLASS/OR COMPONENT
DIAGRAMS
Architectural DesignIncludeDesign Objects
ObjectDesign
SCENARIOS
REQUIREMENTSELICITATION
DESIGN DIAGRAMS
IMPLEMENTATIONCHOICES
DESIGN SEQUENCE DIAG.OR COLLABORATION DIAG
The Requirements, Analysis, and Design Models
Static AnalysisDynamic Analysis
Functional/ NonfunctionalRequirements
Use Case Diagrams/Sequence Diagrams(the system level)
- Analysis Class Diagrams- State Diagrams/Refined Sequence Diagrams (The object level)
Requirements ElicitationProcess
The AnalysisProcess
Static ArchitecturalDesign
Dynamic Design
The DesignProcess
• Design Class Diagrams andComponents Diagrams• Design Sequence Diagrams• Comm. or Collab. Diagrams
Static and Dynamic Design The Static design class diagram model is
developed iteratively using the dynamic model represented in design sequence diagrams or collaboration (also called communication) diagrams
Design sequence diagrams show detailed interactions between objects of classes in different subsystems
They are defined based on analysis (system) sequence diagrams developed for a given Use-Case scenario defined in the analysis (or the requirements) model
Static and Dynamic Design
The development of Design Class Diagrams is completed by defining operations and classes to support the interactions represented in the dynamic model.
Operations of classes in the design class diagram are defined using the dynamic interactions in the dynamic model sequence diagrams
New classes might be needed in the design class diagram to support the interactions of objects in the sequence diagrams (e.g., Interface classes, proxy classes, scheduler classes etc.)
Class Operations
The behavior of a class is represented by its operations Operations may be found by examining interaction
diagramsregistration
formregistration
manager
3: add course(joe, math 01)
RegistrationManager
addCourse(Student,Course)
Design Sequence Diagrams (UML2)Specify operations and states on the timelinesDetailed Parameters list can be specified during detailed design
Digital Sound Recorder:A Complete Example
Digital Sound Recorder:A Complete Example, Use Case Diag.
The Sound RecorderAnalysis Level Class Diagram
Digital Sound Recorder:A Complete Example: Architecture
The Static model,DesignClass Diagram:DesigningThe Subsystems,
Digital Sound Recorder:A Complete Example:
Design Class Diag:Class OperationsAre defined UsingDesign Sequence diagrams
Digital Sound Recorder:A Complete Example
Digital Sound Recorder:A Complete Example: The Dynamic modelDSD shows the interactions between objects in different subsysts
Design Sequence Diagram
Digital Sound Recorder:A Complete Example
Digital Sound Recorder:A Complete Example
• A Scheduler subsystem is added to provide interrupt Handling for timer interrupts to alert observers for synchronous tasks • Uses the observer design pattern (to be discussed later)
Digital Sound Recorder:A Complete Example: The Dynamic model
Interactions are shown using a UML collaboration diagram. Timer interrupt update scenario
Notice anEventProxyClass is addedFor posting Events.Uses the ProxyDesgin pattern
Digital Sound Recorder:A Complete Example: The Dynamic model
Setting the alarm clock scenario: the controller object of type SettingTimeUserMode is setting the AlarmClock object which is shown by the ClockView object
Model-View-Controller Architecture Style
• The Controller manipulates the data Model• The View retrieves data from the model and
displays needed information
Model-View-Controller Architecture StyleDynamic Interactions
Digital Sound Recorder:A Complete Example: The Dynamic model
The Banking System Example: Consolidated Collaboration (Communication) Diagramscombines static and dynamic information
Obtained by combiningMultiple scenarios ofInteractions
(Context Subsystem diag.)Labeled interactionsbetween subsystems
Labels Interactions between objects in a subsystem
Example: Consolidated Collaboration Diagram of the Elevator Control System
Peer-to-Peer Architecture Style
Peer-to-Peer Architecture StyleThe Gnutella Example
• Pure Peer-to-PeerArchitecture• A sends query for a data resource to neighbors B and H, they pass it on until the peer havingthe resource is found or until a certain threshold of hopsis reached
Peer-to-Peer Architecture StyleThe Skype Example
• A mixed client-Server and Pee-to-Peer• Skype Peers get promoted to a supernodestatus based on their network connectivityAnd machine performance• Supernodes perform the Communication and routingof massages to establish a call• When a user logs in to the serverhe is connected to a supernode• If a peer becomes a supernodehe unknowingly bears the cost of routinga potentially large number of calls.