UML IMPLEMENTATION DIAGRAMS Implementation diagrams show the implementation

Uml implementation diagrams implementation diagrams

This preview shows page 37 - 40 out of 47 pages.

UML IMPLEMENTATION DIAGRAMS Implementation diagrams show the implementation phase of systems development, such as the source code structure and the run-time implementation structure. There are 2 types of implementation diagrams: *. Component diagrams – Its Show the stucture of the code itself. *. Deployment Diagrams – Its show the structure of the runtime system. These are relatively simple, high-level diagrams compared with other UML diagrams. Component Diagram : Component diagrams model the physical components (such as source code, executable program, user interface) in a design. These high-level physical components mayor may not be equivalent to the many smaller components you use in the creation of your application. For example, a user interface may contain many other offtheshelf components purchased to put together a graphical user interface. Another way of looking at components is the concept of packages . A package is used to show how you can group together classes, which in essence are smaller scale components. A package usually will be used to group logical components of the application, such as classes, and not necessarily physical components. However, the package could be a first approximation of what eventually will turn into physical grouping. In that case, the package will become a component . A component diagram is a graph of the design's components connected by dependency relationships. A component is represented by the boxed fig shown in Fig 34 Dependency is shown as a dashed arrow. Fig 34: A Component Diagram
Image of page 37
OBJECT ORIENTED ANALYSIS AND DEDIGN UNIT - II 38 Deployment Diagram Deployment diagrams show the configuration of run-time processing elements and the software components, processes, and objects that live in them. Software component instances represent run-time manifestations of code units. In most cases, component diagrams are used in conjunction with deployment diagrams to show how physical modules of code are distributed on various hardware platforms. In many cases, component and deployment diagrams can be combined. A deployment diagram is a graph of nodes connected by communication association. Nodes may contain component instances, which mean that the component lives or runs at that node. Components may contain objects; this indicates that the object is part of the component. Components are connected to other components by dashedarrow dependencies, usually through interfaces, which indicate one component uses the services of another. Each node or processing element in the system is represented by a three- dimensional box. Connections between the nodes (or platforms) themselves are shown by solid lines (see Fig 35). Fig 35. The Basic UML notation for a deployment diagram.
Image of page 38
OBJECT ORIENTED ANALYSIS AND DEDIGN UNIT - II 39 MODEL MANAGEMENT: PACKAGES AND MODEL ORGANIZATION A package is a grouping of model elements. Packages themselves may contain other packages. A package may contain both subordinate packages and ordinary model elements. The entire system can be thought of as a single high-level package with
Image of page 39
Image of page 40

You've reached the end of your free preview.

Want to read all 47 pages?

  • Fall '16
  • Object Oriented

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

Stuck? We have tutors online 24/7 who can help you get unstuck.
A+ icon
Ask Expert Tutors You can ask You can ask You can ask (will expire )
Answers in as fast as 15 minutes