| |
| en:nar_dokument:struktura_modelovanych_architektur [2021/06/01 15:50] – created Tomáš Šedivec | en:nar_dokument:struktura_modelovanych_architektur [2021/06/01 15:53] (current) – Tomáš Šedivec |
|---|
| The **Architectural Vision** is a layer of aggregated information used to convey basic messages about the understanding of the organization, its current and, more often than not, its target state. The layer does not have to be directly related to the individual cognized sub-elements of the organization. Vision models represent a visualization of selected answers to the strategic questions **Where** and **Why** the organization is going. | The **Architectural Vision** is a layer of aggregated information used to convey basic messages about the understanding of the organization, its current and, more often than not, its target state. The layer does not have to be directly related to the individual cognized sub-elements of the organization. Vision models represent a visualization of selected answers to the strategic questions **Where** and **Why** the organization is going. |
| |
| The second and third layers, along with the vision, represent the enterprise architecture, the **Architecture of Authority** (EA). These layers capture the inventory, visualization and understanding of what all is in the organization and in what relationships. Models of these layers represent answers to the questions **What?** and **What elements make up the organization. In describing the future state, these layers represent information about **What?** and **Why?** the structure of the organization's future system. | The second and third layers, along with the vision, represent the enterprise architecture, the **Architecture of Authority** (EA). These layers capture the inventory, visualization and understanding of what all is in the organization and in what relationships. Models of these layers represent answers to the questions **What?** and What elements make up the organization. In describing the future state, these layers represent information about **What?** and **Why?** the structure of the organization's future system. |
| |
| The **Office Architecture** is the vehicle for a holistic view of the office/enterprise. It represents an enumeration of all types of objects (concepts) that occur in the organization, whether or not they are further modeled in the strategic, segment and capability architectures. This list of object types is the basis for a glossary of concepts associated with architecture, i.e. the structure and behaviour of an organisation. | The **Office Architecture** is the vehicle for a holistic view of the office/enterprise. It represents an enumeration of all types of objects (concepts) that occur in the organization, whether or not they are further modeled in the strategic, segment and capability architectures. This list of object types is the basis for a glossary of concepts associated with architecture, i.e. the structure and behaviour of an organisation. |
| * Communication infrastructure architecture, also known as platform architecture | * Communication infrastructure architecture, also known as platform architecture |
| |
| The vertical domains of the motivational architecture, complement and intersect the horizontal architectures and provide answers to the question **Why is our organization the way it is,** or **Why should it be different than it is? | The vertical domains of the motivational architecture, complement and intersect the horizontal architectures and provide answers to the question **Why is our organization the way it is,** or **Why should it be different than it is?** |
| |
| * Strategy and Direction Architecture, originally called just Motivation Architecture | * Strategy and Direction Architecture, originally called just Motivation Architecture |
| The above structure of models is complemented by the so called modelling models - **metamodels** and for accelerating the implementation of EA, the highly desirable **practical examples:** | The above structure of models is complemented by the so called modelling models - **metamodels** and for accelerating the implementation of EA, the highly desirable **practical examples:** |
| |
| The ** **Metamodel and Glossary of Terms - Definition Models (Model Models)** are provided by this methodology and we anticipate that they will be maintained in each agency's model repository to inform the NAR methodology. However, this assumes that in addition to a binding metamodel, for the national exchange of models, it will be possible to extend the metamodels in each office by so-called specializations, see for example [[nar_document:ramec_content_and_output_architectures|Architecture Content and Output Framework]]. | * **Metamodel and Glossary of Terms - Definition Models (Model Models)** are provided by this methodology and we anticipate that they will be maintained in each agency's model repository to inform the NAR methodology. However, this assumes that in addition to a binding metamodel, for the national exchange of models, it will be possible to extend the metamodels in each office by so-called specializations, see for example [[nar_document:ramec_content_and_output_architectures|Architecture Content and Output Framework]]. |
| * **Generalized examples** - as successful pilot projects progress, more models and diagrams of sufficient quality will be added to serve as examples. These are individual models in nature, but will often be generalised, anonymised, so that the specific authority being modelled is no longer visible. These models are not binding on anyone, but serve to inspire as vehicles of practical experience. Such will be disseminated both centrally from OHA and communally between authorities. | * **Generalized examples** - as successful pilot projects progress, more models and diagrams of sufficient quality will be added to serve as examples. These are individual models in nature, but will often be generalised, anonymised, so that the specific authority being modelled is no longer visible. These models are not binding on anyone, but serve to inspire as vehicles of practical experience. Such will be disseminated both centrally from OHA and communally between authorities. |
| |