Enterprise Standards:Process Architecture Reference Content - Revision history

Admin at 19:16, 28 October 2015

2015-10-28T19:16:09Z

Admin at 11:34, 2 September 2015

2015-09-02T11:34:51Z

Admin at 08:26, 2 September 2015

2015-09-02T08:26:45Z

Admin at 08:26, 2 September 2015

2015-09-02T08:26:33Z

Admin at 08:25, 2 September 2015

2015-09-02T08:25:36Z

Admin at 08:24, 2 September 2015

2015-09-02T08:24:47Z

Admin at 13:49, 1 September 2015

2015-09-01T13:49:40Z

Admin at 13:29, 1 September 2015

2015-09-01T13:29:01Z

Admin at 13:14, 1 September 2015

2015-09-01T13:14:12Z

Admin at 13:12, 1 September 2015

2015-09-01T13:12:04Z

@@ Line 28: / Line 28: @@
 ##an associated cost. Often used as an alternative term for task.
-'''Process (P) Templates & Artifacts'''
+'''Process (P) Artefacts'''
-The Process Reference Content has 3 types of templates and artifacts in terms of both process 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.
+The Process Reference Content has 3 types of artefacts in terms of both process 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.
-Fully integrated and standardized process modelling and architecture templates enables the subject matter experts/practitioners to work and model with the process meta objects throughout all the architectural layers (business, application and technology). This is also one of the greatest strengths of the LEADing Practice Enterprise Standards. Not only are the process objects governed by its connection modelling rules, but how and where the templates interlink and share common objects is defined and standardized.
+Fully integrated and standardized process modelling and architecture artefacts enables the subject matter experts/practitioners to work and model with the process meta objects throughout all the architectural layers (business, application and technology). This is also one of the greatest strengths of the LEADing Practice Enterprise Standards. Not only are the process objects governed by its connection modelling rules, but how and where the artefacts interlink and share common objects is defined and standardized.
-'''The Process (P) Map Template'''
+'''The Process (P) Map Artefact'''
 The Process (P) Map provides an overview of the key processes of the organization and their main aspects. The following aspects are described per process:
@@ Line 49: / Line 49: @@
 [[File:LEAD-Frameworks-Table-Process-Map-01.png|frame|center|900px|link=http://{{SERVERNAME}}/images/0/0f/LEAD-Frameworks-Table-Process-Map.pdf|Process Architecture Reference Content - Process Map]]
-'''The Process (P) Matrix Template'''
+'''The Process (P) Matrix Artefact'''
 The Proces (P) Matrix provides an overview of the key processes of the organization and their main relationships with other objects:
@@ Line 61: / Line 61: @@
 [[File:LEAD-Frameworks-Table-Process-Matrix-01.png|frame|center|900px|link=http://{{SERVERNAME}}/images/e/e2/LEAD-Frameworks-Table-Process-Matrix.pdf|Process Architecture Reference Content - Process Matrix]]
-The Process maps, matrices and models are therefore used in the decomposition and composition work within and throughout the different layers. Each specific Process 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 Process maps, matrices and models are therefore used in the decomposition and composition work within and throughout the different layers. Each specific Process 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.
 A Process (P) Model can illustrate a plethora of different steps and activites depending on the context in which it is designed for and used within. The attached example of a Process (P) Model is based on BPMN 2.0, yet also showing the design and modelling opportunities for processes using the LEADing Practice X-BPMN (eXtended Business Process Modelling Notations) modelling principles:
@@ Line 67: / Line 67: @@
 [[File:LEAD-Cross-Enterprise-Standards-Process-Reference-Content-Business-Process-Diagram-WITH-LEGEND-01.png|frame|center|900px|link=http://{{SERVERNAME}}/images/8/86/LEAD-Cross-Enterprise-Standards-Process-Reference-Content-Business-Process-Diagram-WITH-LEGEND.pdf|Process Architecture Reference Content - Business Process Model]]
-'''Using the Process (P) Templates & Artifacts'''
+'''Using the Process (P) Artefacts'''
 Once the key processes of the organization have been specified, they are then linked to, associated with and conntected to the other objects. This association enables the expert/practitioner to tie them to the areas where the key processes have a connection and/or influence. A list of meta objects the key processes relate to are:
@@ Line 104: / Line 104: @@
 *Data Compliance (incl. Security) (S)
-'''Roles involved with the Process (P) Templates and meta objects:'''
+'''Roles involved with the Process (P) Artefacts and meta objects:'''
 {|class="wikitable" style="border: none;width:100%;border:0px; color:white;"
@@ Line 177: / Line 177: @@
 (S) = Secondary object/role
-'''Stakeholders involved with the Process (P) Templates and meta objects:'''
+'''Stakeholders involved with the Process (P) Artefacts and meta objects:'''
 *Top Management: CEO/President

← Older revision		Revision as of 11:34, 2 September 2015
Line 1:		Line 1:
−	[[Category:~~Process~~ Architecture ~~Reference Content~~]]	+	[[Category:Enterprise Architecture Standards]]
	{{DISPLAYTITLE:Process Architecture Reference Content}}		{{DISPLAYTITLE:Process Architecture Reference Content}}

← Older revision		Revision as of 08:26, 2 September 2015
Line 1:		Line 1:
−	[[Category~~:Enterprise Standards~~:Process Architecture Reference Content]]	+	[[Category:Process Architecture Reference Content]]
	{{DISPLAYTITLE:Process Architecture Reference Content}}		{{DISPLAYTITLE:Process Architecture Reference Content}}

← Older revision		Revision as of 08:26, 2 September 2015
Line 1:		Line 1:
−	[[Category:Process Architecture Reference Content]]	+	[[Category:Enterprise Standards:Process Architecture Reference Content]]
	{{DISPLAYTITLE:Process Architecture Reference Content}}		{{DISPLAYTITLE:Process Architecture Reference Content}}

← Older revision		Revision as of 08:25, 2 September 2015
Line 1:		Line 1:
−	[[Category:~~Enterprise Standards~~]]	+	[[Category:Process Architecture Reference Content]]
	{{DISPLAYTITLE:Process Architecture Reference Content}}		{{DISPLAYTITLE:Process Architecture Reference Content}}

← Older revision		Revision as of 08:24, 2 September 2015
Line 1:		Line 1:
		+	[[Category:Enterprise Standards]]
	{{DISPLAYTITLE:Process Architecture Reference Content}}		{{DISPLAYTITLE:Process Architecture Reference Content}}

@@ Line 106: / Line 106: @@
 {|class="wikitable" style="border: none;width:100%;border:0px; color:white;"
-|style="border: none;background-color:#1497d5;width: 30%;text-align:left;" |
+|class="thead" style="border: none;background-color:#1497d5;width: 30%;text-align:left;" |
 '''ENTERPRISE MODELLERS'''
-|style="border: none;background-color:#1497d5;width: 30%;text-align:left;color:white;" |
+|class="thead" style="border: none;background-color:#1497d5;width: 30%;text-align:left;color:white;" |
 '''ENTERPRISE ENGINEERS'''
-|style="border: none;background-color:#1497d5;width: 30%;text-align:left;color:white;" |
+|class="thead" style="border: none;background-color:#1497d5;width: 30%;text-align:left;color:white;" |
 '''ENTERPRISE ARCHITECTS'''
 |-

@@ Line 105: / Line 105: @@
 '''Roles involved with the Process (P) Templates and meta objects:'''
-{|class="no-border" style="border: none !important;width:100%;border:0px; color:white;" |
+{|class="wikitable" style="border: none;width:100%;border:0px; color:white;"
-|style="background-color:#1497d5;width: 30%;text-align:left;" |
+|style="border: none;background-color:#1497d5;width: 30%;text-align:left;" |
 '''ENTERPRISE MODELLERS'''
-|style="background-color:#1497d5;width: 30%;text-align:left;color:white;" |
+|style="border: none;background-color:#1497d5;width: 30%;text-align:left;color:white;" |
 '''ENTERPRISE ENGINEERS'''
-|style="background-color:#1497d5;width: 30%;text-align:left;color:white;" |
+|style="border: none;background-color:#1497d5;width: 30%;text-align:left;color:white;" |
 '''ENTERPRISE ARCHITECTS'''
 |-
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Business Analyst (P)
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Value Engineer (S)
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Business Architect (P)
 |-
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Process eXpert (P)
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Technology Engineer (S)
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Solution Architect (S)
 |-
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Value eXpert (P)
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Process Engineer (P)
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Value Architect (P)
 |-
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Information eXpert (S)
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Test Engineer (S)
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Data Architect (S)
 |-
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Service eXpert (S)
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Quality Engineer (S)
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Service Architect (S)
 |-
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Transformation eXpert (S)
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Change Engineer (S)
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Technology Architect (S)
 |-
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Software Engineer (S)
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Process Architect (P)
 |-
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Enterprise Architect (S)
 |-
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
-|style="background-color:#ebecec;color:black;" |
+|style="border: none;background-color:#ebecec;color:black;" |
 Information Architect (S)
 |-