Component diagrams and deployment diagrams in UML9 diagrams

Component diagrams and deployment diagrams are used to describe the physical and physical operation of a system. The component is the basic unit, which encapsulates the reusable module in the system as an alternative physical unit, which is called a component. A component is a package unit in a system or subsystem that provides one or more interfaces and is a reusable part of the system's upper layer, including software code (source code, binary code, and executable file) or a corresponding component, such as a script or command-line file.

As a physical implementation unit of a system-well-defined interface, a component can rely on only the interface supported by the component without directly relying on other components, and can avoid the direct dependency between the system and other components by using the interface.

A component instance is used to represent the implementation of physical units that exist at run time and to locate in instance nodes, with code features and identity features: The code feature of a component is that it contains and encapsulates the classes that implement system functions, the implementation code of other elements, and some instance objects that make up the system; the identity of a component is the identity and state That is used to locate the physical object on which it is located.

A component diagram is a diagram used to represent the relationship between a component, a class, or an interface and a component in a system. Where the relationship between the component and the component is dependent, the defined class or interface behaves as a dependency or implementation relationship with the class. The component diagram shows the interface relationship between the interfaces of the components of the system, forming a larger design unit of the system, providing the designer with a natural form of a system solution model, and allowing an architecture design after the system is complete to verify that the necessary functions of the system are implemented by which components, Ensure that the final system is accepted.

The component diagram can also present the early design of the target system, which is connected by the different teams of the system development, which facilitates the communication between different development groups. and decide the task allocation and requirements analysis, and the system administrator can get a complete understanding of the progress of the system through the early view of component diagrams running on the logical components of their systems.

The deployment diagram depicts a static view of the hardware nodes at the time of the system runtime, where the software artifacts running on those nodes will be physically run and how they will communicate with each other. Contains two basic elements: a connection between a node and a node.

In rational rose, there are two types of nodes, namely processors and devices. A processor is a node, such as a server, workstation, that has the ability to compute and execute a variety of software. The aspect that describes the processor should include the scheduling and process of the processor. Scheduling refers to the processing of the processor in its process for a certain purpose to achieve a common use of resources for the time allocation, sometimes need to specify the scheduling of the processor, so that processing to achieve optimal or better results.

Preemptive preemptive, high-priority processes can preempt low-priority processes

Nonpreemptive no priority, process has no priority, and the current process executes the next process after completion

Cyclic cycle scheduling, process loop control, each process has a certain time, over the specified time, to the next process

Executive using some sort of computational algorithm to control schedule scheduling

Manual user to perform process scheduling manually

The main program in a component diagram, or an active object in a collaboration diagram, is a process. A processor can contain a number of processes that can be executed using a specific scheduling method.

A device is a node that does not have the ability to handle itself. In general, some services are provided externally through their interfaces,

such as printers, scanners.

The connection is used to represent a hardware connection between two nodes, which can be connected directly to the cable, or it can be a satellite or other indirect connection

And the connections are both bidirectional. One or more communication protocols are supported in the connection, and each protocol can use a

is described by the constructed type of the connection.

HTTP Hypertext Transfer Protocol

JDBC Java database Connection, a set of Java APIs written for database access

ODBC Open database connection, a set of Microsoft Database Access application programming interface

RMI Remote communication protocol, a Java Remote Call communication protocol

RPC Remote Procedure Call communication protocol

Synchronous synchronization connection, the sender must wait for feedback from the receiving party before sending the message

Asynchronous asynchronous connection, send sends no need to wait for feedback from the receiving party to send the message again

Web Service communication through the SOAP and UDDI Web service protocol  

The developer and deployer of the system can make good use of the deployment diagram to understand the physical operation of the system, and to model the complex physical operations, such as distributed systems.

Component and deployment diagrams in the UML9 diagram