UML component Diagrams (component diagrams)

Directory (?) [-] UML Component Diagram Component Diagram What is the component how to read the component diagram how to draw the Component Diagram Application explanation This chapter summary

http://terryfeng.iteye.com/blog/524353

Overview

The component diagram (Component Diagram) describes the various components of the software and their dependencies. Component diagrams typically contain 3 elements: components (Component), interfaces (Interface), and Dependencies (Dependency). Each component implements some interfaces and uses other interfaces.
UML Component Diagrams (component diagrams) Blog Categories: [Essay classification] [Architecture] UML Enterprise Application Server data structure work

• What is a component

Elements of components and components

• A component is a replaceable physical part of a system that wraps implementations that implement and comply with and provide a set of interfaces

• Specification: For the widget, there must be an abstract description of the service it provides. In layman's sense, each component must provide a specific service

• One or more implementations: A component is a physical concept that must be supported by one or more implementations, and of course these implementations must conform to specifications

• Constrained component standards: each component must conform to a certain component standard when implemented

• Encapsulation method: That is, the packaging standard for component compliance

• Deployment method: When a piece is to be run, first deploy it

Types of artifacts

• Implementation artifacts: Such artifacts are necessary and adequate components of an executable system, such as dynamic-link libraries (DLLs), executables (EXE), and also include COM +, CORBA, and Enterprise-class Java Beans, and dynamic Web pages are part of the implementation artifacts

• Work Product components: This type of component is primarily the product of the development process, including the creation of source code files and data files for the implementation component. These artifacts are not directly involved in the executable system, but are used to produce intermediate work products for the executable system

• Execution Widget: Created as a result of an executing system, such as a COM + object formed by a DLL instantiation

Interface representation of components and components

3 representations that provide and request (use or refer to as dependencies)

• How to read component drawings

Read the basic component diagram

Reading nested widget diagrams

The above picture describes

1. Sales Management Server includes two components, transaction processing procedures and financial interface

2. Financial interface needs financial system support, it can be said that the financial interface relies on the existence of financial system, transaction processing procedures, the use of financial interface, rely on the financial interface, and for the cash register system to provide sales information. • How to draw a widget diagram

Determine the external interface of the subsystem

• The entire "Online hotel reservation subsystem" as a component to consider its external interface. It is obvious that it first needs to provide a user interface, and secondly, it needs to connect with the hotel system and complete the reservation work.

Determining child artifacts and interfaces

• Obviously there is a component to implement the user interface, a component to complete the connection with the hotel system and booking, and there should be a responsible for the user's needs and the hotel's supply to match the "scheduler"

• Component Diagram application Instructions

Modeling the structure of an executable program

• First identify the set of artifacts you want to model

• Consider the different types of components in a set

• Analyze the relationships of each component in this set

Modeling the source code

• Identify the collection of relevant source code files of interest and model them as artifacts;

• For larger systems, use packages for grouping;

• The use of constraints to represent the source code version number, the author and the last modified date and other information;

• Use dependencies to represent the dependencies of compilation between these files

• Summary of this chapter

Firstly, the definition of component and the five elements of component are introduced.

After understanding the basic knowledge of component, this paper illustrates the reading skills of basic component graph and nested component graph, and then expounds the drawing steps of nested component graph.

At the end of this chapter, the Application field of component graph is explained, and the most common two kinds of scenes are illustrated: Executable program structure modeling, source code modeling

Content from: UML Object-oriented design ppt