Modelling your application architecture Options

codeling 1264 - 5397
@2019-04-11 13:41:26

In Visual Studio, a component diagram shows the parts of a design for a software system. A component diagram helps you visualize the high-level structure of the system and the service behavior that those pieces provide and consume through interfaces. To create a UML component diagram, on the Architecture menu, click New UML or Layer Diagram.

The following table describes the elements that you can use on a component diagram, together with their main properties.


Shape Element Description and Main Properties
1 Component A reusable piece of system functionality. A component provides and consumes behavior through interfaces, and can use other components.

You can hide or show the internal parts of a component using the expand/collapse control (9).

A component is a kind of class.

- Is Indirectly Instantiated. If true (default), the component exists only as a design artifact. At run time, only its parts exist.
2 Provided Interface Port Represents a group messages or calls that a component implements and that other components or external systems can use. A port is a property of a component that has an interface as its type.
3 Required Interface Port Represents a group of messages or calls that the component sends to other components or external systems. The component is designed to be coupled to components that provide at least these operations. The port has an interface as its type.
4 Dependency Can be used to indicate that a Required Interface on one component can be satisfied by a Provided Interface on another.

Dependencies can also be used more generally between model elements, to show that the design of one depends on the design of the other.
5 Part An attribute of a component, whose type is a usually another component. A part is used in the internal design of its parent component. Parts are shown graphically, nested within the parent component.

To create a Part of an existing component type, drag the component from UML Model Explorer onto the owner component.

To create a Part of a new type, click the Component tool and then click the owner component.

For example, a component Car has parts engine:CarEngine, backLeft:Wheel, frontRight:Wheel, and so on.

More than one part can have the same type, and different components can have parts of the same type.

- Type. The type of the part, which is defined elsewhere in the model. Typically, the type is another component.
- Multiplicity. Defaults to 1. You can set it to 0..1 to indicate that the part can have the value null, \* to indicate that the part is a collection of instances of the given type, or to any expression that can be evaluated to a range of numbers.
6 Part Assembly A connection between the required interface ports of one part and the provided interface ports of another. The implementation of a part assembly can vary from one component to another. The connected parts must have the same parent component.
7 Delegation Links a port to an interface of one of the component's parts. Indicates that messages sent to the component are dealt with by the part, or that messages sent from the part are sent out from the parent component.
(not shown) Generalization Indicates that one component inherits from another component. Parts and interfaces are inherited.
9 Collapse/Expand control Use this to hide or show a component's internal parts.
(not shown) Comment For additional notes. You can link a comment to any number of elements on the diagram by using the Connector tool.

codeling 1264 - 5397
@2019-04-12 11:52:23

In Visual Studio, you can use a layer diagram to visualize the high-level, logical architecture of your system. A layer diagram organizes the physical artifacts in your system into logical, abstract groups called layers. These layers describe major tasks that the artifacts perform or the major components of your system. Each layer can also contain nested layers that describe more detailed tasks.

Unlike a traditional architecture diagram, throught layer diagram in Visual Studio, you can verify that the actual dependencies in the source code conform to the intended dependencies that you have specified. By making validation part of a regular build on Team Foundation Server, you can ensure that the program code continues to adhere to the system's architecture through future changes.

Users browsing this topic