LEAD Reference Content:Layered Enterprise Architecture Reference Content - Revision history

Admin at 10:08, 14 January 2019

2019-01-14T10:08:58Z

Admin: Created page with "{{DISPLAYTITLE: Layered Enterprise Architecture Reference Content}} = Layered Enterprise Architecture Reference Content =
The main principle behind the Layered En..."

2019-01-14T10:06:52Z

Created page with "{{DISPLAYTITLE: Layered Enterprise Architecture Reference Content}} = Layered Enterprise Architecture Reference Content = <blockquote> The main principle behind the Layered En..."

New page

{{DISPLAYTITLE: Layered Enterprise Architecture Reference Content}}
= Layered Enterprise Architecture Reference Content =
<blockquote>
The main principle behind the Layered Enterprise Architecture Development (LEAD) concept, and what makes it differ from other traditional Enterprise Architecture frameworks, is the fact that it does not only work in domains, but across layers (business, application and technology) within multiple domains through using the decomposition and composition method to integrate effortlessly across the different layers when interlinking the different modelling principles.
</blockquote>

The LEAD layered method is built upon the concept of interlinking the objects that are within and work across the layers. While the layers and their specific objects may/will have different modelling principles, they do still have correlations, relationships and/or connections with other layers and these need to be related/connected in the right way:
*The Business Layer describes the objects within the Business layer (e.g. Business Goals, Business Requirements and the Business Competencies that are linked to Business Processes, Business Services and Business Workflow).
*The Application Layer describes the deliverables within the Application, Data and Information Architecture. The maps, matrices and models depicts how Data Goals, Data Flow & Services, Data Requirements and Data Components are linked to Application Goals, Information Flow & Services, Application Requirements and Application Flow & Components.
*The Technology Layer describes the deliverables within the platform and infrastructure areas. The maps, matrices and models depicts how Platform Goals, Platform Flow & Services, Platform Requirements and Platform Components are linked to Infrastructure Goals, Infrastructure Flow & Services, Infrastructure Requirements and Infrastructure Components.

As shown in the example to the right, each layer’s Service Objects are defined by the specific layer's requirements, the capability of the object, the resources, tasks and information. The functions that a layer provides can be seen as the layer’s services since a layer provides a set of functions and tasks and thereby services to its upper layer.

[[File:LEAD-Service-Oriented-Architecture-Reference-Content-Layered-Service-Architecture-01.png|thumb|caption|center|800px|LEAD Service-Oriented Architecture Reference Content - Layered Service Architecture]]

In turn, the upper layer uses the lower layer’s services (functionality and tasks) to achieve its own functions (services). The “n’th layer (+1 and/or – 1) can therefore be seen as a service requester or provider since it either provides a service (gives input) or uses the services provided by its lower layer (receives output).

== Example of a Blueprinting & Implementation model using Layered Enterprise Architecture ==

The Layered Enterprise Architecture Reference Content consist of the following:
#[[#business-layer|Business Layer]]
#[[#application-layer|Application Layer]]
#[[#technology-layer|Technology Layer]]

===Business Layer===

The Business Layer describes the deliverables within the Business layer e.g the Business Goals and Business Competencies are linked to Business Requirements and Business Processes.

[[File:LEAD-Blueprinting-Decomposition-Composition-Approach-Layered-Architecture-Roadmap-Business-Layer-01.png|frame|center|900px|link=Media:LEAD-Blueprinting-Decomposition-Composition-Approach-Layered-Architecture-Roadmap-Business-Layer.pdf|An example of a LEADing Practice Blueprinting & Implementation model using the Layered Architecture Reference Content (Business Layer)]]

The LEAD concept is built upon the concept of the interlinked layers and objects. While the business layer objects may have different modelling principles, they do however still have correlations, relationships and/or connections with each other and that these need to be, as described below, connected in the right way:
*Business competencies create and work with business objects to execute the defined goals.
*Business goals define the reason and purpose of the business object.
*Rules are set in place to govern the business, information and data objects (the different rules are, however, defined differently for the different objects and areas).
*When business competencies deliver business services, they have activities (business processes) which interact with the business objects as well.
*Business competencies/functions and processes have business roles.
*Business roles work with both business objects as well as information objects.
*Business objects may contain information objects.

===Application Layer===

The Application Layer describes the deliverables within the application, date and Information Architecture. The maps, matrices and models depicts how Data Goals, Data Flow & Service, Data Requirements and Data Components are linked to Application Goals, Information Flow & Service, Application Requirements and Application Flow & Component.

[[File:LEAD-Blueprinting-Decomposition-Composition-Approach-Layered-Architecture-Roadmap-Application-Layer-01.png|frame|center|900px|link=Media:LEAD-Blueprinting-Decomposition-Composition-Approach-Layered-Architecture-Roadmap-Application-Layer.pdf|An example of a LEADing Practice Blueprinting & Implementation model using the Layered Architecture Reference Content (Application Layer)]]

Also the Application layer objects have different modelling principles, however, they do still have correlations, relationships and/or connections with each other and that these need to be, as described below, connected in the right way. Applications can automate one or more processes (business processes), which interact with the business objects, information objects and data objects:
*An application is decomposed into one or more application component(s).
*Application components hosts data objects.
*Data objects are called upon and used and thereby processed within information objects.
*An application component is decomposed into one or more application module(s).
*An application module is decomposed into one or more application function(s).
*An application function defines (a part of) an application service flow (which supports the business service flow).
*An application service is related to one or more application function(s).
*Application functions work through information objects with business objects.
*An application function is decomposed in multiple application tasks.
*Also application service can be decomposed in application tasks.
*Application tasks create, read, update and delete data and therefore work with data objects.
*The application task triggers one or more application features.
*An application feature is related to one or more application function(s) and thereby application features work with information objects.
*Application tasks work through the application functions with the information objects and thereby the real-world business objects.
*Application users have roles that use the application functionality that call upon information objects.
*In an application, the information objects called upon by a user are processed data objects.
*All objects use both media and channels.
*Business roles interact with both manual and automated processes and deliver both manual (business) and automated (IT) services.

===Technology Layer===

The Technology Layer describes the deliverables within the platform and infrastructure areas. The maps, matrices and models depicts how Platform Goals, Platform Flow & Service, Platform Requirements and Platform Components are linked to Infrastructure Goal, Infrastructure Flow & Service, Infrastructure Requirements and Infrastructure Component.

[[File:LEAD-Blueprinting-Decomposition-Composition-Approach-Layered-Architecture-Roadmap-Technology-Layer-01.png|frame|center|900px|link=Media:LEAD-Blueprinting-Decomposition-Composition-Approach-Layered-Architecture-Roadmap-Technology-Layer.pdf|An example of a LEADing Practice Blueprinting & Implementation model using the Layered Architecture Reference Content (Technology Layer)]]

Also the Technology Layer objects have different modelling principles, however, they do still have correlations, relationships and/or connections with each other and that these need to be, as described below, connected in the right way. Below is an technology layer example working across the layers:
*A platform is used to enable an application on several hierarchical levels: platform component enables application component, platform service enables application service and platform service element enables application task.
*The application components and modules reside on infrastructure components. Infrastructure services support the platform, data and application services.
*The business service in the business layer is automated by the application service, data service (application layer) , platform service and infrastructure service (technology layer).

<blockquote>
Each layer (business, application and technology) has many different models and modelling principles appropriate for handling the different tasks, and these principles have more correlations, relationships and connections than what currently exists in most other Enterprise Architecture standards.
</blockquote>

The above-mentioned associations and correlations, the different modelling principles have not only one, but multiple interaction points. In order to identify and capture all of these objects and their relations correctly within the LEAD way of working and modelling, it is necessary to decompose the different entities and objects within the area they are connected with (e.g. competency, function, process, service, role, flow, application, media, channel, etc.).

Below are more examples of the Layered Enterprise Architecture Reference Content used in different models:
{|class="wikitable" style="width:100%;border:0px;" |
|class="thead" style="background-color:rgb(195, 217, 255);width: 100%;text-align:left;" |
'''Layered Enterprise Architecture Reference Content'''
|-
|[[Media:LEAD-Enterprise-Meta-Object-Taxonomy-Notations-Descriptions-01.png|Enterprise Meta Object Taxonomy & Notations]]
|-
|[[Media:LEAD-Layered-Enterprise-Architecture-Reference-Content-Enterprise-Architecture-01.png|Layered Enterprise Architecture]]
|-
|[[Media:LEAD-Layered-Enterprise-Architecture-Reference-Content-Enterprise-Architecture-with-Modelling-Principles-01.png|Layered Enterprise Architecture with Modelling Principles]]
|-
|[[Media:LEAD-Layered-Enterprise-Architecture-Reference-Content-Layer-Structure-01.png|Layer Structure]]
|-
|[[Media:LEAD-Layered-Enterprise-Architecture-Reference-Content-Layer-Structure-Extended-01.png|Layer Structure [Extended]]]
|-
|[[Media:LEAD-Layered-Enterprise-Architecture-Reference-Content-Layer-Structure-Extended-01.png|Layer Structure [Extended]]]
|-
|[[Media:LEAD-Layered-Enterprise-Architecture-Reference-Content-Layered-Architecture-Concept-Service-01.png|Layered Architecture Concept [Service-Oriented]]]
|-
|[[Media:LEAD-Layered-Enterprise-Architecture-Reference-Content-Layered-Enterprise-Architecture-Development-01.png|Layered Enterprise Architecture Development]]
|-
|[[Media:LEAD-Layered-Enterprise-Architecture-Reference-Content-LEAD-Architecture-Partitions-01.png|LEAD Architecture Partitions]]
|-
|[[Media:LEAD-Layered-Enterprise-Architecture-Reference-Content-LEAD-Cube-01.png|The LEAD Cube]]
|-
|[[Media:LEAD-Layered-Enterprise-Architecture-Reference-Content-The-Structural-Way-Through-The-Layers-Simple-01.png|The LEAD Structural Way Through Layers [Simple]]]
|-
|[[Media:LEAD-Layered-Enterprise-Architecture-Reference-Content-The-Structural-Way-Through-The-Layers-Views-01.png|The LEAD Structural Way Through Layers [Views]]]
|}

[[Category: Enterprise Architecture]]

@@ Line 7: / Line 7: @@
 The LEAD layered method is built upon the concept of interlinking the objects that are within and work across the layers. While the layers and their specific objects may/will have different modelling principles, they do still have correlations, relationships and/or connections with other layers and these need to be related/connected in the right way:
 *The <b>Business Layer</b> describes the objects within the Business layer (e.g. Business Goals, Business Requirements and the Business Competencies that are linked to Business Processes, Business Services and Business Workflow).
-*The <b>Application Layer</b> describes the deliverables within the Application, Data and Information Architecture. The maps, matrices and models depicts how Data Goals, Data Flow & Services, Data Requirements and Data Components are linked to Application Goals, Information Flow & Services, Application Requirements and Application Flow & Components.
+*The <b>Information Layer</b> describes the deliverables within the Application, Data and Information Architecture. The maps, matrices and models depicts how Data Goals, Data Flow & Services, Data Requirements and Data Components are linked to Application Goals, Information Flow & Services, Application Requirements and Application Flow & Components.
 *The <b>Technology Layer</b> describes the deliverables within the platform and infrastructure areas. The maps, matrices and models depicts how Platform Goals, Platform Flow & Services, Platform Requirements and Platform Components are linked to Infrastructure Goals, Infrastructure Flow & Services, Infrastructure Requirements and Infrastructure Components.
@@ Line 20: / Line 20: @@
 The Layered Enterprise Architecture Reference Content consist of the following:
 #[[#business-layer|Business Layer]]
-#[[#application-layer|Application Layer]]
+#[[#information-layer|Information Layer]]
 #[[#technology-layer|Technology Layer]]
@@ Line 38: / Line 38: @@
 *Business objects may contain information objects.
-===Application Layer===
+===Information Layer===
-The Application Layer describes the deliverables within the application, date and Information Architecture. The maps, matrices and models depicts how Data Goals, Data Flow & Service, Data Requirements and Data Components are linked to Application Goals, Information Flow & Service, Application Requirements and Application Flow & Component.
+The Information Layer describes the deliverables within the application, date and Information Architecture. The maps, matrices and models depicts how Data Goals, Data Flow & Service, Data Requirements and Data Components are linked to Application Goals, Information Flow & Service, Application Requirements and Application Flow & Component.
 [[File:LEAD-Blueprinting-Decomposition-Composition-Approach-Layered-Architecture-Roadmap-Application-Layer-01.png|frame|center|900px|link=Media:LEAD-Blueprinting-Decomposition-Composition-Approach-Layered-Architecture-Roadmap-Application-Layer.pdf|An example of a LEADing Practice Blueprinting & Implementation model using the Layered Architecture Reference Content (Application Layer)]]
-Also the Application layer objects have different modelling principles, however, they do still have correlations, relationships and/or connections with each other and that these need to be, as described below, connected in the right way. Applications can automate one or more processes (business processes), which interact with the business objects, information objects and data objects:
+Also the Information layer objects have different modelling principles, however, they do still have correlations, relationships and/or connections with each other and that these need to be, as described below, connected in the right way. Applications can automate one or more processes (business processes), which interact with the business objects, information objects and data objects:
 *An application is decomposed into one or more application component(s).
 *Application components hosts data objects.

LEAD Reference Content:Layered Enterprise Architecture Reference Content - Revision history

Admin at 10:08, 14 January 2019

Admin: Created page with "{{DISPLAYTITLE: Layered Enterprise Architecture Reference Content}} = Layered Enterprise Architecture Reference Content = The main principle behind the Layered En..."

Admin: Created page with "{{DISPLAYTITLE: Layered Enterprise Architecture Reference Content}} = Layered Enterprise Architecture Reference Content =
The main principle behind the Layered En..."