1 / 15

Implementation Diagrams

Implementation Diagrams. Implementation Diagrams. Both are structural diagrams Component Diagrams : set of components and their relationships Illustrate static implementation view Component maps to one or more classes, interfaces, or collaborations Deployment Diagrams :

cchao
Download Presentation

Implementation Diagrams

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Implementation Diagrams CSE870: UML Component Diagrams

  2. Implementation Diagrams • Both are structural diagrams • Component Diagrams: • set of components and their relationships • Illustrate static implementation view • Component maps to one or more classes, interfaces, or collaborations • Deployment Diagrams: • Set of nodes and their relationships • Illustrate static deployment view of architecture • Node typically encloses one or more components CSE870: UML Component Diagrams

  3. Package Package Name • General purpose mechanism for organizing elements into groups • Can group classes or components. CSE870: UML Component Diagrams

  4. Component Diagram Example.java • Classes • Interfaces • Dependency, generalization, association, and realization relationships Special kind of class diagram focusing on system’s components. CSE870: UML Component Diagrams

  5. Component Diagram Find.exe executable find.html page Index.html Comp2.dll Comp1.dll library CSE870: UML Component Diagrams

  6. Common Uses: • Model source code: • model configuration mgmt • Model executable releases • Release is relatively complete and consistent set of artifacts delivered to user • Release focuses on parts necessary to deliver running system • Component Diagram visualizes, specifies, and documents the decisions about the physical parts that define the software. CSE870: UML Component Diagrams

  7. Common Uses: (cont’d) • Model Physical databases: • database is concrete realization of schema • schemas offer an API to persistent information • model of physical dbases represents storage of that information in tables of a relational dbase or pages of an OO dbase. • Component Diagram can represent this kind of physical database • Model Adaptable systems: • can model static aspects of adaptable systems • can model dynamic aspects (in conjunction with behavioral models) CSE870: UML Component Diagrams

  8. Modeling Source Code • (Forward/Reverse Eng): identify set of source code files of interest • model as components stereotyped as files • Larger systems: use packages to show groups of source code files • Model compilation dependencies among files CSE870: UML Component Diagrams

  9. Modeling Source Code Example Signal.h Signal.h Signal.h {version=3.5} {version=4.0} {version=4.1} • 5 source code files • signal.h (header) • used by 2 other files (signal.cpp, interp.cpp) • interp.cpp has compilation dependency to header file (irq.h) • device.cpp compilation dependency to interp.cpp Signal.cpp <<parent>> <<parent>> Interp.cpp Irq.h Device.cpp CSE870: UML Component Diagrams

  10. Deployment Diagrams CSE870: UML Component Diagrams

  11. Deployment Diagram • Shows the configuration of: • run time processing nodes and • the components that live on them • Graphically: collection of vertices and arcs CSE870: UML Component Diagrams

  12. Contents • Deployment diagrams contain: • Nodes • Dependency and association relationships • may also contain components, each of which must live on some node. CSE870: UML Component Diagrams

  13. A Deployment Diagram <<processor>> <<processor>> <<processor>> <<processor>> <<processor>> <<processor>> server server server Caching server Caching server primary server node Modem bank Internet connection <<network>> local network CSE870: UML Component Diagrams

  14. Modeling Client-Server Architecture • Identify nodes that represent system’s client and server processors • Highlight those devices that are essential to the behavior • E.g.: special devices (credit card readers, badge readers, special display devices) • Use stereotyping to visually distinguish CSE870: UML Component Diagrams

  15. Client-Server System Deploys Deploys Http.exe rting.exe dbadmin.exe tktmstr.exe logexc.exe • Human resource system • 2 pkgs: client, server • Client: 2 nodes • console and kiosk • stereotyped, distinguishable • Server: 2 nodes • caching server and server • Multiplicities are used client console kiosk server 4..* 2..* <<processor>> <<processor>> Caching server server CSE870: UML Component Diagrams

More Related