Enterprise Standards:Service-Oriented Architecture Reference Content - Revision history

Admin at 18:45, 28 October 2015

2015-10-28T18:45:10Z

90.185.212.37 at 13:30, 2 September 2015

2015-09-02T13:30:52Z

Admin at 13:24, 2 September 2015

2015-09-02T13:24:28Z

Admin at 13:14, 2 September 2015

2015-09-02T13:14:39Z

Admin at 13:14, 2 September 2015

2015-09-02T13:14:14Z

Show changes

87.121.100.91: Created page with "Category:Enterprise Architecture Standards"

2015-07-13T09:11:41Z

Created page with "Category:Enterprise Architecture Standards"

New page

[[Category:Enterprise Architecture Standards]]

@@ Line 3: / Line 3: @@
 '''Description of the Service-Oriented Architecture Reference Content'''
-The Service-Oriented Architecture Reference Content and the Service (Se) Templates provide an overview of the key (business) services of an enterprise and their specific (decomposed) service aspects. The purpose of the Service (Se) Templates is to provide a centralized and official overview of the key (business) services of an enterprise with their specification and their relations as described above.
+The Service-Oriented Architecture Reference Content and the Service (Se) Artefacts provide an overview of the key (business) services of an enterprise and their specific (decomposed) service aspects. The purpose of the Service (Se) Artefacts is to provide a centralized and official overview of the key (business) services of an enterprise with their specification and their relations as described above.
 A service delivers or supports business capabilities, has an explicitly defined interface, and is explicitly governed. Services are defined for both the business layer (purpose and goal (i.e. value), competency, service and process), information systems (application layer including data) as well as for technology (platform and infrastructure layer).
-'''Service (Se) Templates & Artifacts'''
+'''Service (Se) Artefacts'''
-The Service-Oriented Architecture Reference Content has 3 types of templates and artifacts in terms of both Service (Se) maps, matrices and models that capture the meta objects which are instrumental, and an essential part of the enterprise modelling, enterprise engineering and enterprise architecture. Each of these are based on a specific view, with particular stakeholder concern to enable value identification, creation, and realization.
+The Service-Oriented Architecture Reference Content has 3 types of artefacts in terms of both Service (Se) maps, matrices and models that capture the meta objects which are instrumental, and an essential part of the enterprise modelling, enterprise engineering and enterprise architecture. Each of these are based on a specific view, with particular stakeholder concern to enable value identification, creation, and realization.
-Fully integrated and standardized service modelling and architecture templates enables the subject matter experts/practitioners to work and model with the service meta objects throughout all the architectural layers (business, application and technology) and this is one of the greatest strengths of the LEADing Practice Enterprise Standards. Not only are the service objects governed by its connection modelling rules, but how and where the templates interlink and share common objects is also defined and standardized.
+Fully integrated and standardized service modelling and architecture artefacts enables the subject matter experts/practitioners to work and model with the service meta objects throughout all the architectural layers (business, application and technology) and this is one of the greatest strengths of the LEADing Practice Enterprise Standards. Not only are the service objects governed by its connection modelling rules, but how and where the artefacts interlink and share common objects is also defined and standardized.
-'''The Service (Se) Map Template'''
+'''The Service (Se) Map Artefact'''
 The Service (Se) Map shows the key (business) services of the enterprise and their decomposed service aspects. The Service (Se) Map consist of content in the listed format:
@@ Line 34: / Line 34: @@
 The purpose of the Service (Se) Map is to identify and decompose a list of all the services within the enterprise. This list helps to understand the breadth of functionality provided by the services. It will also provide a centralized and official overview of the key services in the enterprise including all service-related aspects.
-'''The Service (Se) Matrix Template'''
+'''The Service (Se) Matrix Artefact'''
 The Service (Se) Matrix provides an overview of the key (business) services of the enterprise and its purpose is to relate these services to other meta objects that share a relationship with the key (business) services of the enterprise. The Service (Se) Matrix consist of content in the listed format:
@@ Line 55: / Line 55: @@
 [[File:LEAD-Frameworks-Table-Service-Matrix-01.png|frame|center|900px|link=http://{{SERVERNAME}}/images/6/66/LEAD-Frameworks-Table-Service-Matrix.pdf|Service-Oriented Architecture Reference Content - Service Matrix]]
-The Service maps, matrices and models are therefore used in the decomposition and composition work within and throughout the different layers. Each specific Service template shows which objects are within which template, thereby specifying if it is a map, a matrix or a model. It furthermore shows where the object of one template can be reused in another template.
+The Service maps, matrices and models are therefore used in the decomposition and composition work within and throughout the different layers. Each specific Service artefact shows which objects are within which artefact, thereby specifying if it is a map, a matrix or a model. It furthermore shows where the object of one artefact can be reused in another artefact.
-'''Using the Service (Se) Templates & Artifacts'''
+'''Using the Service (Se) Artefacts'''
 Once the key (business) services of the enterprise have been specified, they are then linked to, associated with and connected to the other objects. This association enables the expert/practitioner to tie them to the areas where the key (business) services have a connection and/or influence. A list of meta objects the key (business) services relate to are:
@@ Line 102: / Line 102: @@
 *Infrastructure Service (P)
-'''Roles involved with the Service (Se) Templates and meta objects:'''
+'''Roles involved with the Service (Se) Artefacts and meta objects:'''
 {|class="wikitable" style="border: none;width:100%;border:0px; color:white;"
@@ Line 150: / Line 150: @@
 (S) = Secondary object/role
-'''Stakeholders involved with the Service (Se) Templates and meta objects:'''
+'''Stakeholders involved with the Service (Se) Artefacts and meta objects:'''
 *Top Management: CEO/President

@@ Line 1: / Line 1: @@
 {{DISPLAYTITLE:Service-Oriented Architecture Reference Content}}
 '''Description of the Service-Oriented Architecture Reference Content'''
 The Service-Oriented Architecture Reference Content and the Service (Se) Templates provide an overview of the key (business) services of an enterprise and their specific (decomposed) service aspects. The purpose of the Service (Se) Templates is to provide a centralized and official overview of the key (business) services of an enterprise with their specification and their relations as described above.
 A service delivers or supports business capabilities, has an explicitly defined interface, and is explicitly governed. Services are defined for both the business layer (purpose and goal (i.e. value), competency, service and process), information systems (application layer including data) as well as for technology (platform and infrastructure layer).
 '''Service (Se) Templates & Artifacts'''
 The Service-Oriented Architecture Reference Content has 3 types of templates and artifacts in terms of both Service (Se) maps, matrices and models that capture the meta objects which are instrumental, and an essential part of the enterprise modelling, enterprise engineering and enterprise architecture. Each of these are based on a specific view, with particular stakeholder concern to enable value identification, creation, and realization.
 Fully integrated and standardized service modelling and architecture templates enables the subject matter experts/practitioners to work and model with the service meta objects throughout all the architectural layers (business, application and technology) and this is one of the greatest strengths of the LEADing Practice Enterprise Standards. Not only are the service objects governed by its connection modelling rules, but how and where the templates interlink and share common objects is also defined and standardized.
 '''The Service (Se) Map Template'''
 The Service (Se) Map shows the key (business) services of the enterprise and their decomposed service aspects. The Service (Se) Map consist of content in the listed format:
 *What specification: Service Area
 *What specification: Service Group
@@ Line 38: / Line 29: @@
 *Who/Whose specification: Manager Involved
 *Who/Whose specification: Service/Process/Application Roles Involved
 [[File:LEAD-Frameworks-Table-Service-Map-01.png|frame|center|900px|link=http://{{SERVERNAME}}/images/8/86/LEAD-Frameworks-Table-Service-Map.pdf|Service-Oriented Architecture Reference Content - Service Map]]
 The purpose of the Service (Se) Map is to identify and decompose a list of all the services within the enterprise. This list helps to understand the breadth of functionality provided by the services. It will also provide a centralized and official overview of the key services in the enterprise including all service-related aspects.
 '''The Service (Se) Matrix Template'''
 The Service (Se) Matrix provides an overview of the key (business) services of the enterprise and its purpose is to relate these services to other meta objects that share a relationship with the key (business) services of the enterprise. The Service (Se) Matrix consist of content in the listed format:
 *Which specification e.g. internal and external forces and drivers
 *Why in terms of strategy e.g. strategic business objectives and critical success factors (objectives)
@@ Line 67: / Line 52: @@
 *Whom/whose specification e.g. process owner
 *What/which specification e.g. application, data service, platform service and infrastructure service
 [[File:LEAD-Frameworks-Table-Service-Matrix-01.png|frame|center|900px|link=http://{{SERVERNAME}}/images/6/66/LEAD-Frameworks-Table-Service-Matrix.pdf|Service-Oriented Architecture Reference Content - Service Matrix]]
 The Service maps, matrices and models are therefore used in the decomposition and composition work within and throughout the different layers. Each specific Service template shows which objects are within which template, thereby specifying if it is a map, a matrix or a model. It furthermore shows where the object of one template can be reused in another template.
 '''Using the Service (Se) Templates & Artifacts'''
 Once the key (business) services of the enterprise have been specified, they are then linked to, associated with and connected to the other objects. This association enables the expert/practitioner to tie them to the areas where the key (business) services have a connection and/or influence. A list of meta objects the key (business) services relate to are:
 *Driver & Forces (external/internal) (S)
 *Strategy (Strategic Business Objective) (P)
@@ Line 122: / Line 101: @@
 *Platform Service (P)
 *Infrastructure Service (P)
 '''Roles involved with the Service (Se) Templates and meta objects:'''
 {|class="wikitable" style="border: none;width:100%;border:0px; color:white;"
@@ Line 169: / Line 146: @@
 |-
 |}
 (P) = Primary object/role
 (S) = Secondary object/role
 '''Stakeholders involved with the Service (Se) Templates and meta objects:'''
 *Top Management: CEO/President
@@ Line 183: / Line 157: @@
 *Lower Management: Team/Group Leader
 *Operational: User (Senior, Medior, Junior)
 (*): Chief Executive Officer, Chief Channel Officer, Chief Financial Officer, Chief Information Officer, Chief Risk & Security Officer, Chief HR Office, Chief Marketing & Sales Officer, Chief R&D Officer, Chief Procurement Officer, Chief Strategy Officer, Chief Buss. Dev. Officer, Chief Technology Officer, Chief Environment & Health Officer.
 '''The Service-Oriented Architecture Reference Content Poster'''
 We have put together a poster containing many different Service Models touching many important aspects of key (business) services of an enterprise.
 [[File:POSTER-LEAD-Service-Reference-Framework-01.png|frame|center|900px|link=http://{{SERVERNAME}}/images/2/20/POSTER-LEAD-Service-Reference-Framework.pdf|Service-Oriented Architecture Reference Content Poster]]

@@ Line 135: / Line 135: @@
 '''ENTERPRISE ARCHITECTS'''
 |-
-|style="border: none;background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |Business Analyst (P)
-Business Analyst (P)
+|style="border: none;background-color:#ebecec;color:black;" |Value Engineer (S)
-|style="border: none;background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |Business Architect (P)
 Value Engineer (S)
 |style="border: none;background-color:#ebecec;color:black;" |
 Business Architect (P)
 |-
-|style="border: none;background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |Value eXpert (P)
-Value eXpert (P)
+|style="border: none;background-color:#ebecec;color:black;" |Process Engineer (S)
-|style="border: none;background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |Value Architect (P)
 Process Engineer (S)
 |style="border: none;background-color:#ebecec;color:black;" |
 Value Architect (P)
 |-
-|style="border: none;background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |Process eXpert (S)
 Process eXpert (S)
 |style="border: none;background-color:#ebecec;color:black;" |
 Software Engineer (P)
-|style="border: none;background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |Enterprise Architect (S)
 Enterprise Architect (S)
 |-
-|style="border: none;background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |Transformation eXpert (S)
-Transformation eXpert (S)
+|style="border: none;background-color:#ebecec;color:black;" |Technology Engineer (S)
-|style="border: none;background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |Solution Architect (S)
 Technology Engineer (S)
 |style="border: none;background-color:#ebecec;color:black;" |
 Solution Architect (S)
 |-
-|style="border: none;background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |Information eXpert (S)
 Information eXpert (S)
 |style="border: none;background-color:#ebecec;color:black;" |
-|style="border: none;background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |Service Architect (P)
 Service Architect (P)
 |-
-|style="border: none;background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |Service eXpert (P)
 Service eXpert (P)
 |style="border: none;background-color:#ebecec;color:black;" |
-|style="border: none;background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |Information Architect (S)
 Information Architect (S)
 |-
 |style="border: none;background-color:#ebecec;color:black;" |
@@ Line 181: / Line 166: @@
 |style="border: none;background-color:#ebecec;color:black;" |
-|style="border: none;background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |Technology Architect (S)
 Technology Architect (S)
 |-
 |}

@@ Line 1: / Line 1: @@
 [[Category:Enterprise Architecture Standards]]
+{{DISPLAYTITLE:Service-Oriented Architecture Reference Content}}
 '''Description of the Service-Oriented Architecture Reference Content'''