impove archimate sections

mauvaisetroupe · Oct 1, 2023 · bbadb2c · bbadb2c
1 parent 5f150c4
commit bbadb2c
Show file tree

Hide file tree

Showing 6 changed files with 30 additions and 20 deletions.
diff --git a/content/en/ea-design-it/metamodel/metamodel-application.md b/content/en/ea-design-it/metamodel/metamodel-application.md
@@ -35,11 +35,10 @@ In the above web banking example, from DEV & IT-OPS teams perspective, web banki
 Application and Application Components can be mapped to **Application Component**
 An application is composed of Application Component. This is usually modeled with an **Application Structure Viewpoint**
 
-<span style="background-color: blue; color: white; font-weight: bold">Archimate 3.1</span> There is no definition of Application
-
-<span style="background-color: blue; color: white; font-weight: bold">Archimate 3.1</span> An application component represents an encapsulation of application functionality aligned to implementation structure, which is modular and replaceable.
-
-<span style="background-color: blue; color: white; font-weight: bold">Archimate 3.1</span> An application component is defined as a modular, deployable, and replaceable part of a software system that encapsulates its behavior and data and exposes these through a set of interfaces.
+> <span style="background-color: blue; color: white; font-weight: bold">Archimate 3.1</span> 
+> - There is no definition of Application
+> - An application component represents an encapsulation of application functionality aligned to implementation structure, which is modular and replaceable.
+> - An application component is defined as a modular, deployable, and replaceable part of a software system that encapsulates its behavior and data and exposes these through a set of interfaces.
 
 
 ![landscape archimate](../jpg/applications.jpg)

diff --git a/content/en/ea-design-it/metamodel/metamodel-data-flow-item.md b/content/en/ea-design-it/metamodel/metamodel-data-flow-item.md
@@ -29,7 +29,8 @@ Data flow (topic /EVT/CUSTOMER) is used by two Data Flow Item (typically Kafka E
 
 # Mapping with Archimate specification
 
-<span style="background-color: blue; color: white; font-weight: bold">Archimate 3.1</span> A Data Flow Item is modeled with a Archimate Data Object.
-There is an aggregation or composition relationship between Dat Flow and Data Flow Items
+> <span style="background-color: blue; color: white; font-weight: bold">Archimate 3.1</span> 
+> - A Data Flow Item is modeled with a Archimate Data Object.
+> - There is an aggregation or composition relationship between Dat Flow and Data Flow Items
 
 ![Data Flow](../jpg/data-flow-item.jpg)
diff --git a/content/en/ea-design-it/metamodel/metamodel-data-flow.md b/content/en/ea-design-it/metamodel/metamodel-data-flow.md
@@ -40,7 +40,9 @@ Interface TRAD.006 is implemented with a DataFlowItem (typically a topic in a st
 
 A Data Flow is modeled with a Archimate **Data Object.**
 
-<span style="background-color: blue; color: white; font-weight: bold">Archimate 3.1</span> A data object represents data structured for automated processing.
+> <span style="background-color: blue; color: white; font-weight: bold">Archimate 3.1</span> 
+>
+> A data object represents data structured for automated processing.
 
 Data Flow could appear on **Application Cooperation Viewpoint** :
 

diff --git a/content/en/ea-design-it/metamodel/metamodel-functional-flow.md b/content/en/ea-design-it/metamodel/metamodel-functional-flow.md
@@ -51,7 +51,9 @@ Functional Flow is mainly thought as a use case described with a **sequence diag
 
 Basically, a Functional Flow is a subset of Landscape, representing a specific usage of a part of the landscape in a specific functional use case.
 
-Like Landscape, a Functional Flow is typically an **Application Cooperation Viewpoint**.
+> <span style="background-color: blue; color: white; font-weight: bold">Archimate 3.1</span> 
+>
+> Like Landscape, a Functional Flow is typically an **Application Cooperation Viewpoint**.
 
 ![landscape archimate](../jpg/functional-flow.jpg)
 

diff --git a/content/en/ea-design-it/metamodel/metamodel-interface.md b/content/en/ea-design-it/metamodel/metamodel-interface.md
@@ -33,7 +33,9 @@ trough two different Interfaces:
 
 # Mapping with Archimate specification
 
-Interface can be mapped to **flow relationship**.
+> <span style="background-color: blue; color: white; font-weight: bold">Archimate 3.1</span> 
+>
+> Interface can be mapped to **flow relationship**.
 
 As explained in [this article](https://bizzdesign.com/blog/practical-archimate-viewpoints-for-the-application-layer/), you could model your flow relationship in different manner:
  1. Adding one flow relationship for each data object. That choice gives the option to add properties like exchange frequency, format and other details, but that choice can also lead to very complex diagrams. 

diff --git a/content/en/ea-design-it/metamodel/metamodel-landscape.md b/content/en/ea-design-it/metamodel/metamodel-landscape.md
@@ -37,31 +37,35 @@ In this example, Landscape in composed of 2 Functional Flows :  **GEN.001** and
 
 An application landscape is typically an **Application Cooperation Viewpoint**.
 
-<span style="background-color: blue; color: white; font-weight: bold">Archimate 3.1</span> **Architecture View** - A representation of a system from the perspective of a related set of concerns. 
+> <span style="background-color: blue; color: white; font-weight: bold">Archimate 3.1</span> 
+> - **Architecture View** - A representation of a system from the perspective of a related set of concerns. 
+> -  **Architecture Viewpoint** - A specification of the conventions for a particular kind of architecture view. 
+> -  The **Application Cooperation Viewpoint** describes the relationships between application components in terms of the information flows between them, or in terms of the services they offer and use. This viewpoint is typically used to create an overview of the application landscape of an organization.
+>
+> In EADesignIt, we use Application Cooperation Viewpoint used the following elements:
+> - Application Components
+> - Flow Relationship 
 
-<span style="background-color: blue; color: white; font-weight: bold">Archimate 3.1</span> **Architecture Viewpoint** - A specification of the conventions for a particular kind of architecture view. 
+![landscape archimate](../jpg/landscape.jpg)
 
-<span style="background-color: blue; color: white; font-weight: bold">Archimate 3.1</span> The **Application Cooperation Viewpoint** describes the relationships between application components in terms of the information flows between them, or in terms of the services they offer and use. This viewpoint is typically used to create an overview of the application landscape of an organization.
+### Static or dynamic ?
 
 This viewpoint can be static or dynamic:
 - In a **static context**, it displays application services and accessed data. 
 - In a **dynamic context**, it models behavioral dependencies using flows. 
 
 > **EADesignIt is used to model the dynamic version of this viewpoint, without the application service concept for simplified diagrams**, useful for illustrating end-to-end data flows across many applications.
 
+For the big picture, this might be good enough to guide the architecture development. As a complementary diagram for more detailed solution design in projects, you might want to use UML sequence diagrams that show in detail the data flows from one application to another (including confirmation messages that are important for solution design but not at a higher architecture level). That's why EADesignIt introduce yhe notion of [Functional Flow](../metamodel-functional-flow/)
+
+### Flow Relationships modeling convention
+
 When dealing with the dynamic application cooperation viewpoint and the use of flow relationships, it's important to establish a convention that dictates the number of flow relationships permissible between applications: 
 - You can choose between adding **one flow relationship for each data object**, which provides details like exchange frequency but may result in cluttered diagrams, 
 - Or opt for **one flow relationship per technology interface**, which offers a clearer big-picture view
 
 > EADesignIT unequivocally embraces the second option by introducing the concept of [Interface](../metamodel-interface/) to denote this singular relationship between two applications, specifically for a given technology.
 
-
-Application Cooperation Viewpoint used the following elements:
- - Application Components
- - Flow Relationship 
-
-![landscape archimate](../jpg/landscape.jpg)
-
 Interesting post with some additional information could be read [here](https://bizzdesign.com/blog/practical-archimate-viewpoints-for-the-application-layer/)
 
 ## What's next ?