{"id":25853,"date":"2021-07-21T16:19:02","date_gmt":"2021-07-21T14:19:02","guid":{"rendered":"https:\/\/cesam.community\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/"},"modified":"2023-01-20T11:42:33","modified_gmt":"2023-01-20T10:42:33","slug":"2-2-the-three-architectural-visions-2-2","status":"publish","type":"post","link":"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/","title":{"rendered":"2.2 The three Architectural Visions (2\/2)"},"content":{"rendered":"<div class=\"wpb-content-wrapper\"><section class=\"vc_row wpb_row vc_row-fluid  vc_custom_1627389518372\"><div class=\"wpb_column vc_column_container vc_col-sm-10 vc_col-md-offset-1 col-xs-mobile-fullwidth\"><div class=\"vc_column-inner \"><div class=\"wpb_wrapper\"><div class=\"vc_row wpb_row vc_inner vc_row-fluid\"><div class=\"wpb_column vc_column_container vc_col-sm-9  col-xs-mobile-fullwidth\"><div class=\"vc_column-inner \"><div class=\"wpb_wrapper\"><h3 id=\"0.1\" class=\"text-medium-gray text-small margin-5px-bottom alt-font text-uppercase heading-style4  heading-1\"  style=\"font-weight: 500;\">2.2.2.3 Constructional Vision<\/h3><div class=\"last-paragraph-no-margin\"><p style=\"text-align: justify;\">The <em>constructional vision<\/em> provides white box models of the system where one describes all concrete hardware, software and \u201chumanware\u201d<sup class=\"modern-footnotes-footnote \" data-mfn=\"1\" data-mfn-post-scope=\"00000000000019b60000000000000000_25853\"><a href=\"javascript:void(0)\"  role=\"button\" aria-pressed=\"false\" aria-describedby=\"mfn-content-00000000000019b60000000000000000_25853-1\">1<\/a><\/sup><span id=\"mfn-content-00000000000019b60000000000000000_25853-1\" role=\"tooltip\" class=\"modern-footnotes-footnote__note\" tabindex=\"0\" data-mfn=\"1\">Remember that men can be part of systems with either strong organizational dimensions such for instance as information<br \/>\nsystems, or when a human stakeholder plays such a key role (e.g. pilot, driver, operator, etc.) that it may be important to include him\/her in the design, considering then an operated system rather that the underlying technical system alone.<\/span> components of a system with their interactions. Its core motivation is to elicit in that way the concrete structure \u2013 that is to say the \u201cHow\u201d \u2013 of the system. It is thus probably the most intuitive part of a systems architecture.<\/p>\n<\/div>[vc_single_image image=\u00a0\u00bb25367&Prime; img_size=\u00a0\u00bb450&#215;206&Prime; alignment=\u00a0\u00bbcenter\u00a0\u00bb]<div class=\"last-paragraph-no-margin\"><p style=\"text-align: center;\"><strong><span style=\"font-size: 10pt;\">Figure 23 \u2013 Constructional vision \u2013 Product Breakdown Structure (PBS) of an electronic toothbrush\u00a0<\/span><\/strong><\/p>\n<\/div><div class=\"last-paragraph-no-margin\"><p style=\"text-align: justify;\">The core notion of the constructional vision is of course the notion of \u201ccomponent of a system\u201d, that refers to a concrete part of the considered system. In other terms, a <em>component<\/em> associated with a given system models a physical, software or even \u201chumanware\u201d resource that belongs to the system. In other word, each atom of a system shall belong to one and only one of its components. A common pattern to denote a component is thus just to use its usual technical or business name.<br \/>\nExactly as in the functional vision, all constructional concepts \u2013 such as configuration, constructional scenarios or constructional objects (see Section 2.4 for more details) \u2013 are again uniquely referring to the system of interest, without involving any external system. All these concepts can be managed at different levels of abstraction \/ grain. Figure 22 shows for instance the <em>Product Breakdown Structure<\/em> (PBS) of an electronic toothbrush, where its components are put in a hierarchy according to the fact that a high level component results from the integration of the lower level components.<br \/>\nNote finally that the term \u201carchitecture\u201d usually only refers to the constructional architecture of a system. One shall thus be aware of the fact that we will use this term in a much broader acceptation through our entire pocket guide, especially when speaking of systems architecture which does refer to the union of all architectural visions for a given system as introduced above.<\/p>\n<\/div><h3 id=\"0.1\" class=\"text-medium-gray text-small margin-5px-bottom alt-font text-uppercase heading-style4  heading-2\"  style=\"font-weight: 500; color: #01af50;\">2.2.3 Relationships between the three Architectural Visions<\/h3><div class=\"last-paragraph-no-margin\"><p style=\"text-align: justify;\">Last but not least, it is also important to point out the network of relationships existing between the three architectural visions, since they are at the heart of the systems architecting process. It is in particular especially important to maintain these relationships during the different design phases, which is difficult due to the \u201chighly iterative &amp; recursive nature\u201d of systems architecting [66].<\/p>\n<\/div>[vc_single_image image=\u00a0\u00bb25369&Prime; img_size=\u00a0\u00bb450&#215;248&Prime; alignment=\u00a0\u00bbcenter\u00a0\u00bb]<div class=\"last-paragraph-no-margin\"><p style=\"text-align: center;\"><strong><span style=\"font-size: 10pt;\">Figure 24 \u2013 Relationships between the three architectural visions\u00a0<\/span><\/strong><\/p>\n<\/div><div class=\"last-paragraph-no-margin\"><p style=\"text-align: justify;\">Figure 24 shows the generic relationships between the architectural visions as explained below.<\/p>\n<p style=\"text-align: justify;\">\u2022 The operational vision connects first with the two other visions due to the fact that missions are naturally implemented by functions, but also components. Another way to make this connection is to observe that all external flows between the different external systems and the system of interest, as provided by the operational vision, must be internally captured or produced (depending the external flows are input or output flows from the internal point of view of the considered system) by functions of the system of interest<sup class=\"modern-footnotes-footnote \" data-mfn=\"2\" data-mfn-post-scope=\"00000000000019b60000000000000000_25853\"><a href=\"javascript:void(0)\"  role=\"button\" aria-pressed=\"false\" aria-describedby=\"mfn-content-00000000000019b60000000000000000_25853-2\">2<\/a><\/sup><span id=\"mfn-content-00000000000019b60000000000000000_25853-2\" role=\"tooltip\" class=\"modern-footnotes-footnote__note\" tabindex=\"0\" data-mfn=\"2\"> In other terms, it is sufficient to continue each external flow, as identified in the operational vision, within the system to get the first functions of the system of interest. Functional analysis will then continue internally the same kind of analysis up to identifying exhaustively all functions, which can be checked by a functional synthesis proving that all identified functions are forming a coherent functional network<\/span>.<\/p>\n<p style=\"text-align: justify;\">\u2022 The functional vision connects back in the same way with the operational vision and forth with the constructional vision due to the fact that each abstract function must be concretely allocated to \/ implemented by some set of constructional components.<\/p>\n<p style=\"text-align: justify;\">\u2022 The constructional vision connects then back to the two other visions according to the implementation and allocation relationships that we just pointed out.<\/p>\n<p style=\"text-align: justify;\">Note in particular that <strong>one should not think<\/strong><sup class=\"modern-footnotes-footnote \" data-mfn=\"3\" data-mfn-post-scope=\"00000000000019b60000000000000000_25853\"><a href=\"javascript:void(0)\"  role=\"button\" aria-pressed=\"false\" aria-describedby=\"mfn-content-00000000000019b60000000000000000_25853-3\">3<\/a><\/sup><span id=\"mfn-content-00000000000019b60000000000000000_25853-3\" role=\"tooltip\" class=\"modern-footnotes-footnote__note\" tabindex=\"0\" data-mfn=\"3\">Which is unfortunately a common mistake \u2026<\/span> that operational artefacts do only allocate to functional artefacts, which on their side do only allocate to constructional artefacts. Such a vision would indeed be dramatically false. Operational, functional and constructional visions shall indeed be analyzed as a circle of three interdependent visions. Figure 25 illustrates this situation.<\/p>\n<\/div>[vc_single_image image=\u00a0\u00bb25371&Prime; img_size=\u00a0\u00bb420&#215;212&Prime; alignment=\u00a0\u00bbcenter\u00a0\u00bb]<div class=\"last-paragraph-no-margin\"><p style=\"text-align: center;\"><strong><span style=\"font-size: 10pt;\">Figure 25 \u2013 Relationships existing between the three architectural visions\u00a0<\/span><\/strong><\/p>\n<\/div><div class=\"last-paragraph-no-margin\"><p style=\"text-align: justify;\">One must first understand that the operational vision is nothing else than a mixed functional and constructional description of the part of the environment of the system of interest which involves this last system. As an immediate consequence, the functional (resp. constructional) dimension of the environment Env(S) of a given system S naturally maps with the functional (resp. constructional) dimension of S. Such a property implies therefore that operational architecture is connected both to functional and constructional architectures of a given system. As a matter of fact, the geometry of a given system\u2019s environment \u2013 which is one of its typical constructional properties \u2013 maps for instance directly with the geometry of the considered system, without any connection with functions<sup class=\"modern-footnotes-footnote \" data-mfn=\"4\" data-mfn-post-scope=\"00000000000019b60000000000000000_25853\"><a href=\"javascript:void(0)\"  role=\"button\" aria-pressed=\"false\" aria-describedby=\"mfn-content-00000000000019b60000000000000000_25853-4\">4<\/a><\/sup><span id=\"mfn-content-00000000000019b60000000000000000_25853-4\" role=\"tooltip\" class=\"modern-footnotes-footnote__note\" tabindex=\"0\" data-mfn=\"4\">The shape of my body typically implies the shape of a chair, without requiring any functional analysis\u2026<\/span>. The same situation also holds for most of the physical properties of the environment.<\/p>\n<p style=\"text-align: justify;\">On the other hand, one must also notice that there may be feedbacks from the constructional vision onto the functional vision and\/or the operational vision and\/or from the functional vision onto the operational vision. The choice of a specific technology at constructional level may indeed typically induce functions that were not directly requested. Deciding to implement a given service through an automated device creates for instance immediately the \u201cTo distribute electricity\u201d function. In the same way, the choice of a specific function at functional level may allow new services that were initially not designed. As another example, just remember that nobody could imagine the creation of an entire new world of new services thanks to the apparently simple Internet functionality<sup class=\"modern-footnotes-footnote \" data-mfn=\"5\" data-mfn-post-scope=\"00000000000019b60000000000000000_25853\"><a href=\"javascript:void(0)\"  role=\"button\" aria-pressed=\"false\" aria-describedby=\"mfn-content-00000000000019b60000000000000000_25853-5\">5<\/a><\/sup><span id=\"mfn-content-00000000000019b60000000000000000_25853-5\" role=\"tooltip\" class=\"modern-footnotes-footnote__note\" tabindex=\"0\" data-mfn=\"5\">Which functionally speaking is nothing else that allowing the exchange between different computers<\/span>!<\/p>\n<\/div><h3 id=\"0.1\" class=\"text-medium-gray text-small margin-5px-bottom alt-font text-uppercase heading-style4  heading-3\"  style=\"font-weight: 500; color: #01af50;\">2.2.4 Organization of a System Model<\/h3><div class=\"last-paragraph-no-margin\"><p style=\"text-align: justify;\">We are now in position to derive the first consequences of the CESAM framework on the structure of a system model. We are indeed now aware of two dimensions of any system, the first one being provided by the three architectural visions used to model a system, the second one being simply given by the abstraction \/ grain level on which a given system may be analyzed. On this last point, we shall just recall that any integrated system can be analyzed on the different levels of its integration hierarchy that is to say at system, sub-system, sub-sub-system, etc. levels.<\/p>\n<\/div>[vc_single_image image=\u00a0\u00bb25373&Prime; img_size=\u00a0\u00bb500&#215;314&Prime; alignment=\u00a0\u00bbcenter\u00a0\u00bb]<div class=\"last-paragraph-no-margin\"><p style=\"text-align: center;\"><strong><span style=\"font-size: 10pt;\">Figure 26 \u2013 Organization of a system model\u00a0<\/span><\/strong><\/p>\n<\/div><div class=\"last-paragraph-no-margin\"><p style=\"text-align: justify;\">Hence any system model can be naturally organized in a matrix way where the different system views are classified according to their architectural vision and the level of analysis within the system integration hierarchy, as depicted in Figure 26. Note that the horizontal relation between these views is allocation or implementation as explained in the previous sub-section, when the vertical relation is refinement when going from a high level view to a lower level view and abstraction when doing the converse. Refinement means here providing more details with respect to a given architectural view, when abstraction stands for a not (too much) destructive idealization<sup class=\"modern-footnotes-footnote \" data-mfn=\"6\" data-mfn-post-scope=\"00000000000019b60000000000000000_25853\"><a href=\"javascript:void(0)\"  role=\"button\" aria-pressed=\"false\" aria-describedby=\"mfn-content-00000000000019b60000000000000000_25853-6\">6<\/a><\/sup><span id=\"mfn-content-00000000000019b60000000000000000_25853-6\" role=\"tooltip\" class=\"modern-footnotes-footnote__note\" tabindex=\"0\" data-mfn=\"6\">An abstraction\/refinement mechanism is formally provided [25] by a pair (\u03b1 , \u03c1\u00a0) of applications between sets of so-called concrete objects and sets of so-called abstract objects, where abstraction application \u03b1 maps each set of concrete objects into a set of abstract objects and refinement application \u03c1\u00a0maps each set of abstract objects into a set of concrete objects. These applications are then called an abstraction\/refinement pair if and only if \u03b1(\u03c1(A)) \u2286 A for each abstract set A (refining an abstract set and then re-abstracting the result cannot enlarge the initial abstraction) and C \u2286 \u03c1(\u03b1(C)) for each concrete set C (abstracting a concrete set and then refining the result cannot reduce the initial concrete scope). <\/span> of a series of views, where one will reason in terms of clusters from a lower level perspective, thus losing the details for getting the big picture on a given architectural topic<sup class=\"modern-footnotes-footnote \" data-mfn=\"7\" data-mfn-post-scope=\"00000000000019b60000000000000000_25853\"><a href=\"javascript:void(0)\"  role=\"button\" aria-pressed=\"false\" aria-describedby=\"mfn-content-00000000000019b60000000000000000_25853-7\">7<\/a><\/sup><span id=\"mfn-content-00000000000019b60000000000000000_25853-7\" role=\"tooltip\" class=\"modern-footnotes-footnote__note\" tabindex=\"0\" data-mfn=\"7\">Abstraction &amp; refinement are core mechanisms for systems architects, especially when creating architectural hierarchies. A quite frequent problem in architecture is indeed the excessive number of objects generated by a step of an architectural analysis. In order to handle them effectively and to achieve their real global understanding, we typically have to cluster and to synthesize them into abstract objects. This abstraction activity can be achieved by partitioning the objects in clusters of \u201csimilar\u201d weakly inter-dependent objects, then clarifying systematically the key characteristics (goal, function, feature, etc.) of each group and naming each group consequently. Such a process will naturally lead to architectural hierarchies such as Mission, Functional or Product Breakdown Structures as introduced in the previous subsections.<\/span>. On one hand, refinement is clearly the right tool when one wants to precisely analyze a problem. On the other hand, abstraction<sup class=\"modern-footnotes-footnote \" data-mfn=\"8\" data-mfn-post-scope=\"00000000000019b60000000000000000_25853\"><a href=\"javascript:void(0)\"  role=\"button\" aria-pressed=\"false\" aria-describedby=\"mfn-content-00000000000019b60000000000000000_25853-8\">8<\/a><\/sup><span id=\"mfn-content-00000000000019b60000000000000000_25853-8\" role=\"tooltip\" class=\"modern-footnotes-footnote__note\" tabindex=\"0\" data-mfn=\"8\">6 As a matter of fact, one observes in practice that abstraction is not at all an easy activity. Most of people are in particular not able to manipulate efficiently this mechanism. The key difficulty is indeed to find the \u201cgood\u201d abstractions of a given problem, that is to say a good balance between too abstract and too detailed views. The key point is here to be able to manipulate coarse grain views, with which one can reason more easily and thus take the good strategic decisions, but that can also be refined in fine grain views. This requires the abstract views to be holistic in order to capture all dimensions of a given problem. What happens unfortunately often in real life is that one creates too simple abstractions to be useful!<\/span> is crucial for being able to define an architectural strategy without being lost in an ocean of details.<\/p>\n<\/div><a  href=\"https:\/\/cesam.community\/2021\/07\/20\/2-3-cesam-systems-architecture-pyramid\/\" target=\"_self\" class=\"btn pofo-button-1 bg-position-center-center  wow none button-style9  btn-link text-extra-dark-gray text-deep-pink-hover  btn-medium   vc_custom_1668509806147\" >NEXT PAGE<i class=\"ti-arrow-right   margin-5px-left no-margin-right\" aria-hidden=\"true\"><\/i><\/a><\/div><\/div><\/div><div class=\"wpb_column vc_column_container vc_col-sm-3  col-xs-mobile-fullwidth\"><div class=\"vc_column-inner \"><div class=\"wpb_wrapper\"><h2 class=\"text-medium-gray text-small margin-5px-bottom alt-font text-uppercase heading-style4  heading-4\"  style=\"font-size: 10px; font-weight: 600; color: #000000;\" data-fontsize=\"10px\">TABLE OF CONTENTS<\/h2>[vc_wp_custommenu nav_menu=\u00a0\u00bb132&Prime;]<h2 class=\"text-medium-gray text-small margin-5px-bottom alt-font text-uppercase heading-style4  heading-5\"  style=\"font-size: 10px; font-weight: 600; color: #000000;\" data-fontsize=\"10px\">REFERENCES<\/h2><div class=\"last-paragraph-no-margin\"><p style=\"text-align: left;\"><span style=\"font-size: 8pt;\">[66] NASA, Systems Engineering Handbook, 2007-edition, NASA\/SP-2007-6105, 2007\u00a0<\/span><\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/section>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>The constructional vision provides white box models of the system where one describes all concrete hardware, software and \u201chumanware\u201d components of a system with their interactions. Its core motivation is to elicit in that way the concrete structure \u2013 that is to say the \u201cHow\u201d \u2013 of the system. It is thus probably the most intuitive part of a systems architecture&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[158],"tags":[157],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v24.2 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>2.2 The three Architectural Visions (2\/2) - Cesam Community<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"2.2 The three Architectural Visions (2\/2) - Cesam Community\" \/>\n<meta property=\"og:description\" content=\"The constructional vision provides white box models of the system where one describes all concrete hardware, software and \u201chumanware\u201d components of a system with their interactions. Its core motivation is to elicit in that way the concrete structure \u2013 that is to say the \u201cHow\u201d \u2013 of the system. It is thus probably the most intuitive part of a systems architecture...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/\" \/>\n<meta property=\"og:site_name\" content=\"Cesam Community\" \/>\n<meta property=\"article:published_time\" content=\"2021-07-21T14:19:02+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-01-20T10:42:33+00:00\" \/>\n<meta name=\"author\" content=\"admin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@cesamcommunity\" \/>\n<meta name=\"twitter:site\" content=\"@cesamcommunity\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"admin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/\"},\"author\":{\"name\":\"admin\",\"@id\":\"https:\/\/cesam.community\/fr\/#\/schema\/person\/1698618e5539e0eadd3578d29281a505\"},\"headline\":\"2.2 The three Architectural Visions (2\/2)\",\"datePublished\":\"2021-07-21T14:19:02+00:00\",\"dateModified\":\"2023-01-20T10:42:33+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/\"},\"wordCount\":2053,\"publisher\":{\"@id\":\"https:\/\/cesam.community\/fr\/#organization\"},\"keywords\":[\"Article\"],\"articleSection\":[\"CESAM Systems Architecting Method\"],\"inLanguage\":\"fr-FR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/\",\"url\":\"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/\",\"name\":\"2.2 The three Architectural Visions (2\/2) - Cesam Community\",\"isPartOf\":{\"@id\":\"https:\/\/cesam.community\/fr\/#website\"},\"datePublished\":\"2021-07-21T14:19:02+00:00\",\"dateModified\":\"2023-01-20T10:42:33+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/cesam.community\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"CESAM Systems Architecting Method\",\"item\":\"https:\/\/cesam.community\/fr\/category\/cesam-systems-architecting-method-en\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"2.2 The three Architectural Visions (2\/2)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/cesam.community\/fr\/#website\",\"url\":\"https:\/\/cesam.community\/fr\/\",\"name\":\"Cesam Community\",\"description\":\"La communaut\u00e9 CESAM\",\"publisher\":{\"@id\":\"https:\/\/cesam.community\/fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/cesam.community\/fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/cesam.community\/fr\/#organization\",\"name\":\"CESAM Community\",\"url\":\"https:\/\/cesam.community\/fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/cesam.community\/fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/cesam.community\/wp-content\/uploads\/2021\/04\/cesam_community_logo_v4.png\",\"contentUrl\":\"https:\/\/cesam.community\/wp-content\/uploads\/2021\/04\/cesam_community_logo_v4.png\",\"width\":7310,\"height\":1018,\"caption\":\"CESAM Community\"},\"image\":{\"@id\":\"https:\/\/cesam.community\/fr\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/x.com\/cesamcommunity\",\"https:\/\/www.linkedin.com\/company\/community-cesam\/about\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/cesam.community\/fr\/#\/schema\/person\/1698618e5539e0eadd3578d29281a505\",\"name\":\"admin\",\"sameAs\":[\"https:\/\/cesam.community\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"2.2 The three Architectural Visions (2\/2) - Cesam Community","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/","og_locale":"fr_FR","og_type":"article","og_title":"2.2 The three Architectural Visions (2\/2) - Cesam Community","og_description":"The constructional vision provides white box models of the system where one describes all concrete hardware, software and \u201chumanware\u201d components of a system with their interactions. Its core motivation is to elicit in that way the concrete structure \u2013 that is to say the \u201cHow\u201d \u2013 of the system. It is thus probably the most intuitive part of a systems architecture...","og_url":"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/","og_site_name":"Cesam Community","article_published_time":"2021-07-21T14:19:02+00:00","article_modified_time":"2023-01-20T10:42:33+00:00","author":"admin","twitter_card":"summary_large_image","twitter_creator":"@cesamcommunity","twitter_site":"@cesamcommunity","twitter_misc":{"\u00c9crit par":"admin","Dur\u00e9e de lecture estim\u00e9e":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/#article","isPartOf":{"@id":"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/"},"author":{"name":"admin","@id":"https:\/\/cesam.community\/fr\/#\/schema\/person\/1698618e5539e0eadd3578d29281a505"},"headline":"2.2 The three Architectural Visions (2\/2)","datePublished":"2021-07-21T14:19:02+00:00","dateModified":"2023-01-20T10:42:33+00:00","mainEntityOfPage":{"@id":"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/"},"wordCount":2053,"publisher":{"@id":"https:\/\/cesam.community\/fr\/#organization"},"keywords":["Article"],"articleSection":["CESAM Systems Architecting Method"],"inLanguage":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/","url":"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/","name":"2.2 The three Architectural Visions (2\/2) - Cesam Community","isPartOf":{"@id":"https:\/\/cesam.community\/fr\/#website"},"datePublished":"2021-07-21T14:19:02+00:00","dateModified":"2023-01-20T10:42:33+00:00","breadcrumb":{"@id":"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/cesam.community\/fr\/2021\/07\/21\/2-2-the-three-architectural-visions-2-2\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/cesam.community\/fr\/"},{"@type":"ListItem","position":2,"name":"CESAM Systems Architecting Method","item":"https:\/\/cesam.community\/fr\/category\/cesam-systems-architecting-method-en\/"},{"@type":"ListItem","position":3,"name":"2.2 The three Architectural Visions (2\/2)"}]},{"@type":"WebSite","@id":"https:\/\/cesam.community\/fr\/#website","url":"https:\/\/cesam.community\/fr\/","name":"Cesam Community","description":"La communaut\u00e9 CESAM","publisher":{"@id":"https:\/\/cesam.community\/fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/cesam.community\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/cesam.community\/fr\/#organization","name":"CESAM Community","url":"https:\/\/cesam.community\/fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/cesam.community\/fr\/#\/schema\/logo\/image\/","url":"https:\/\/cesam.community\/wp-content\/uploads\/2021\/04\/cesam_community_logo_v4.png","contentUrl":"https:\/\/cesam.community\/wp-content\/uploads\/2021\/04\/cesam_community_logo_v4.png","width":7310,"height":1018,"caption":"CESAM Community"},"image":{"@id":"https:\/\/cesam.community\/fr\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/x.com\/cesamcommunity","https:\/\/www.linkedin.com\/company\/community-cesam\/about\/"]},{"@type":"Person","@id":"https:\/\/cesam.community\/fr\/#\/schema\/person\/1698618e5539e0eadd3578d29281a505","name":"admin","sameAs":["https:\/\/cesam.community"]}]}},"_links":{"self":[{"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/posts\/25853"}],"collection":[{"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/comments?post=25853"}],"version-history":[{"count":18,"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/posts\/25853\/revisions"}],"predecessor-version":[{"id":33368,"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/posts\/25853\/revisions\/33368"}],"wp:attachment":[{"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/media?parent=25853"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/categories?post=25853"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cesam.community\/fr\/wp-json\/wp\/v2\/tags?post=25853"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}