R R R Implementation Diagrams CSE870: UML Component Diagrams

R R R Implementation Diagrams CSE870: UML Component Diagrams

R R R 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

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

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

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

R R R 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

R R R 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

R R R 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

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

R R R Deployment Diagrams CSE870: UML Component Diagrams

R R R 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

R R R 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

R R A Deployment Diagram R Internet node connection Modem bank processor processor Caching server Caching server network local network processor primary server processor server processor server CSE870: UML Component Diagrams processor server

R R R 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

R R R Client-Server System 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 Caching server Deploys Http.exe rting.exe CSE870: UML Component Diagrams processor server Deploys dbadmin.exe tktmstr.exe logexc.exe