Page tree
Skip to end of metadata
Go to start of metadata

On this Page:
Besides defining behavior and structure in activity respectively class diagrams, we need also architectural models. These models describe all components required to build a service. Architectural information is modeled in the Component Diagram.
Component Diagrams define the types of all used entities like components, classes, interfaces, and artifacts. Furthermore, these diagrams also describe the configuration of deployment artifacts manifesting the logical components.

  • Added in Builder 6.0

As of Builder version 6.0, you don't need to draw a deployment diagram anymore to specify the architecture of a service. As a matter of fact, the old component and deployment diagrams are deprecated to use. However, if you have old services you need to modify, you don't need to refactor the component diagram: the old component and deployment diagrams continue to be supported. The documentation of these diagrams is available throughout the Reference Guide in separate chapters (e.g. Basic Architectural Modeling with E2E Builder 5.1).

We distinguish between components defined by the modeler and implemented as E2E services and components accessed and used by the E2E Bridge. The first category is called E2E Bridge components. Their stereotypes have the prefix E2E, such as <<E2ESOAPService>>. The latter category is named backend components. The notion backend derives from the logical location of these components. In front of the service we have the service client, then we have the E2E service itself (sometimes called frontend service), and in the back of this service we find the utilized services – i.e. the backend services. The term frontend is also used to explain the building blocks of the Runtime in section xUML Runtime Architecture.
Besides frontend and backend components, it is also possible to configure Proxy components. These components are instances of an Apache reverse proxy shielding SOAP and HTTP services. However, proxy concepts are no basic architectural concepts but are described in Advanced Behavioral Modeling - Security Model - Proxy.

While the following chapters describe the overall concepts of component and deployment diagrams, the details about E2E services and adapters accessing backend components are found in the Add-ons chapter. Examples of frontend and backend components are:

Typically, these diagrams are created using the E2E Components Wizard. To learn more about this wizard please refer to the E2E Bridge Builder User's Guide.

Basic Architectural Modeling with E2E Builder 5.1

  • Deprecated since Builder 6.0
 Click here to read an overview of basic architectural modeling with E2E Builder releases before 6.0 ...

Besides defining behavior and structure in activity respectively class diagrams, we need also architectural models . These models describe all components required to build a service. There are two diagrams used to model architectural information:

  • Component Diagrams define the types of all used entities like components, classes, interfaces, and artifacts. Furthermore, these diagrams also describe the configuration of deployment artifacts manifesting the logical components.
  • Deployment Diagrams show the actual physical deployment of the artifacts defined in the component diagrams.

We distinguish between components defined by the modeler and implemented as E2E services and components accessed and used by the E2E Bridge. The first category is called E2E Bridge components. Their stereotypes have the prefix E2E, such as <<E2ESOAPService>>. The latter category is named backend components. The notion backend derives from the logical location of these components. In front of the service we have the service client, then we have the E2E service itself (sometimes called frontend service), and in the back of this service we find the utilized services – i.e. the backend services. The term frontend is also used to explain the building blocks of the Runtime in section xUML Runtime Architecture.
Besides frontend and backend components, it is also possible to configure Proxy components. These components are instances of an Apache reverse proxy shielding SOAP and HTTP services. However, proxy concepts are no basic architectural concepts but are described in Advanced Behavioral Modeling - Security Model - Proxy.

While the following chapters describe the overall concepts of component and deployment diagrams, the details about E2E services and adapters accessing backend components are found in the Add-ons chapter. Examples of frontend and backend components are:

Typically, these diagrams are created using the E2E Component- and Deployment Wizard. To learn more about these wizards please refer to the Builder User Guide.

  • No labels