Smith’s Aerospace © P. Bailey & K. Vander Linden, 2005 Architecture: Component and Deployment Diagrams Patrick Bailey Keith Vander Linden Calvin College

Smith’s Aerospace © P. Bailey & K. Vander Linden, Architecture ● Every system has an architecture ● Forms the basis for – Common understanding among stakeholders – High level and detailed design – Assignment of resources

Smith’s Aerospace © P. Bailey & K. Vander Linden, Architecture Software Architecture Technical Architecture Enterprise

Smith’s Aerospace © P. Bailey & K. Vander Linden, Software Architecture The architecture of a software-intensive system is the structure or structures of the system, which comprise software elements, the externally visible properties of those elements, and the relationships among them.

Smith’s Aerospace © P. Bailey & K. Vander Linden, Component and Deployment A component is a code module. Component diagrams are physical analogs of class diagram. Deployment diagrams show the physical configurations of software and hardware.

Smith’s Aerospace © P. Bailey & K. Vander Linden, Component in Rhapsody A component is a physical subsystem in the form of a library or executable program or other software components such as scripts, command files, documents, or databases. Its role is important in the modeling of large systems that comprise several libraries and executables. For example, the Rhapsody application itself is made up of many components, including the graphic editors, browser, code generator, and animator, all provided in the form of a library.

Smith’s Aerospace © P. Bailey & K. Vander Linden, Components: Key Points ● A component is a logical, replaceable part of a system that conforms to and provides the realization of a set of interfaces. ● Good components define crisp abstractions with well-defined interfaces. ● Interfaces allow you to build the implementation of a component using smaller components.

Smith’s Aerospace © P. Bailey & K. Vander Linden, Terms ● Interface – collection of operations that specify a service that is provided or requested. ● Component – replaceable part of the system ● Port – a specific window into an encapsulated component accepting messages to and from the component conforming to specified interfaces. ● Internal structure – internal implementation of component ● Part – specification of a role that composes part of the implementation of a component. ● Connector – is a communication relationship between two parts or ports within the context of a component.

Smith’s Aerospace © P. Bailey & K. Vander Linden, Interface Anatomy ( component required interface provided interface dependency name_A name_b Ref:The Unified Modeling Language User Guide (2 nd Ed),Booche et el

Smith’s Aerospace © P. Bailey & K. Vander Linden, To see the details... name_A name_b > ImpObject req_read() Realization usage Ref:The Unified Modeling Language User Guide (2 nd Ed),Booche et el

Smith’s Aerospace © P. Bailey & K. Vander Linden, The port... Ticket Seller bidirectional port Booking Load Attractions ) Required Interface Credit Cards attractions charging port port nameinterface name normal sales priority sales Ticket Sales component declaration Ref:The Unified Modeling Language User Guide (2 nd Ed),Booche et el

Smith’s Aerospace © P. Bailey & K. Vander Linden, Port vs Interface ● A port is instantiated. It exists. ● An interface is a definition – a standard.

Smith’s Aerospace © P. Bailey & K. Vander Linden, Hierarchy & Connectors Catalog Sales inventory :OrderHandlinginventory ( :FindItems :ShipItemsdirect connector delegation connector :OrderEntry :Fullfillment charging:Credit :OrderHandoff Ref:The Unified Modeling Language User Guide (2 nd Ed),Booche et el

Smith’s Aerospace © P. Bailey & K. Vander Linden, Ref:

Smith’s Aerospace © P. Bailey & K. Vander Linden, One aspect of a component that is not included in a component diagram is how to create the configurations that are part of a component. Configurations specify how the component should be built, such as the target environment, initialization needed, and checks to perform on the model before code is generated. On the other hand, it can provide you a road map to configuration management. A note …

Smith’s Aerospace © P. Bailey & K. Vander Linden,

Smith’s Aerospace © P. Bailey & K. Vander Linden, Deployment diagrams show the configuration of run-time processing elements and the software component instances that reside on them. Use deployment diagrams to specify the run-time physical architecture of a system. Deployment diagrams are graphs of nodes connected by communication associations. Component instances are assigned to run on specific nodes during program execution. Relation lines represent communication paths between nodes. Deployment in Rhapsody

Smith’s Aerospace © P. Bailey & K. Vander Linden, Nodes represent devices or other resources that store and process instances during run time. For example, a node can represent a type of CPU. A node can be owned only by a package—nodes cannot be nested inside other nodes. Nodes can contain component instances.

Smith’s Aerospace © P. Bailey & K. Vander Linden, Connection The connection is a solid line between nodes to represent the “physical” connection between the nodes.

Smith’s Aerospace © P. Bailey & K. Vander Linden, Execution Environment This is a specialized node which can execute artifacts such as components. Unix Server 1 > transaction persistence Explicit services

Smith’s Aerospace © P. Bailey & K. Vander Linden, Component instances represent executable processes, objects, or libraries that run or reside on processing resources (nodes) during program execution. They are represented by the UML component symbol: a box with two small rectangles on the left side. A component instance is an instance of a component type. Unlike components, there is no special naming convention for component instances. Drawing a component instance inside a node indicates that the component instance lives or runs on that node during run time.

Smith’s Aerospace © P. Bailey & K. Vander Linden, Component Instance Example and Dependency A dependency represents a requirement by one component instance of information or services provided by another. Dependencies can also be drawn between nodes. You can add a dependency using the Dependency tool or the browser. >

Smith’s Aerospace © P. Bailey & K. Vander Linden, Case Study

Smith’s Aerospace © P. Bailey & K. Vander Linden,

Smith’s Aerospace © P. Bailey & K. Vander Linden,