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

Smith’s Aerospace © P. Bailey & K. Vander Linden, Component Diagram You use component diagrams to create new or existing components, specify the files and folders they contain, and define the relations between these elements. These relations include the following: Dependency—A relationship in which the proper functioning of one element requires information provided by another element. In a component diagram, a dependency can exist between any component, file, or folder. Interface—A set of operations that publicly define a behavior or way of handling something so knowledge of the internals is not needed. Component diagrams define interfaces between components only.

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. A note …

Smith’s Aerospace © P. Bailey & K. Vander Linden, Component Diagrams Contain Components Files Folder Dependencies Component Interfaces and Realizations Flows and FlowItems

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

9 Component Diagram Tool Bar

Smith’s Aerospace © P. Bailey & K. Vander Linden, Exercise ● Create a new project ● Create a simple component ● Generate code ● View the created code in a text editor

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, Example Deployment Diagram

Smith’s Aerospace © P. Bailey & K. Vander Linden, Deployment Diagram Icon and Tool Bar

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, 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, 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, Flows and FlowItems provide a mechanism for specifying exchange of information between system elements at a high level of abstraction. This functionality enables you to describe the flow of data and commands within a system at a very early stage, before committing to a specific design. As the system specification evolves, you can refine the abstraction to relate to the concrete implementation. Flows

Smith’s Aerospace © P. Bailey & K. Vander Linden, Like other diagrams, deployment diagrams belong to a package. When you create a deployment diagram in the browser at the project level, Rhapsody assigns the diagram to the default package and displays it in the Deployment Diagrams folder located at the project level. To create a deployment diagram in a particular package, first select the package, then create the new diagram. The nodes and component instances in the deployment diagram belong to the package of that diagram. Speaking of packages