Enterprise Standards:Decomposition & Composition Reference Content - Revision history

90.185.212.37 at 12:22, 1 September 2015

2015-09-01T12:22:27Z

Admin at 14:50, 10 August 2015

2015-08-10T14:50:41Z

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

2015-07-13T09:11:41Z

Created page with "Category:Enterprise Engineering Standards"

New page

[[Category:Enterprise Engineering Standards]]

@@ Line 1: / Line 1: @@
 {{DISPLAYTITLE:Decomposition & Composition Reference Content}}
 The Decomposition & Composition Reference Content consist of the following:
 #[[#|Business Competency Decomposition & Composition]]
 #[[#|Process Decomposition & Composition]]
@@ Line 20: / Line 16: @@
 Decomposition is the process by which the objects are broken down into simpler forms of objects. For example, an application is decomposed into one or more application component(s), while an application component is decomposed into one or more application module(s) and an application module is decomposed into one or more application function(s).
 The application function can, however, be decomposed into multiple application tasks and furthermore an application function defines (a part of) an application service flow. The application service can then be decomposed into application tasks. This simple application decomposition example shows the relevance of decomposing the wanted modelling objects the right way. However, once an object is decomposed it needs to be connected to the right areas. For example, a business normally needs within their application the use of one or more application services, which consist of application tasks and application functions.
 The business sets the purpose for the application and sets the requirements to which the application has to adhere to. An application has an appointed owner of the business and rules are set up to govern the application. Any application task, service or function may be subject to measurement. Application tasks, services or functions are sometimes required to be compliant. Several business competencies use applications to facilitate the automation of one or more of the activities or steps in their processes.
 The application flow determines the flow of an application’s tasks, services and functions. One or more business roles call or deliver input to the application’s tasks, services, and functions. Within the tasks, services and functions of application’s business, information and/or data objects are being used.
 Application tasks, services and functions use, modify, delete and/or produce data. Usually the application will be delivered through a channel and application tasks, services and functions may interact via different media. Application tasks, services and functions are hosted by platforms and the execution of the application service is enabled by infrastructure.
-<br/>
+[[File:LEAD-Decomposition-Composition-Method-Application-Level-1-01.png|frame|center|900px|link=http://lead.orpheus-dev.com/images/d/db/LEAD-Decomposition-Composition-Method-Application-Level-1.pdf|Example of a LEADing Practice Decomposition & Composition Reference Content applied to an Application.]]
-−
-−
-[[File:LEAD-Decomposition-Composition-Method-Application-Level-1-01.png|frame|center|840px|link=http://lead.orpheus-dev.com/images/d/db/LEAD-Decomposition-Composition-Method-Application-Level-1.pdf|Example of a LEADing Practice Decomposition & Composition Reference Content applied to an Application.]]
-−
-[[Category:Enterprise Engineering Standards]]

← Older revision		Revision as of 14:50, 10 August 2015
Line 1:		Line 1:
		+	{{DISPLAYTITLE:Decomposition & Composition Reference Content}}
		+
		+	<br/>
		+
		+	The Decomposition & Composition Reference Content consist of the following:
		+
		+
		+	#[[#\|Business Competency Decomposition & Composition]]
		+	#[[#\|Process Decomposition & Composition]]
		+	#[[#\|Value Decomposition & Composition]]
		+	#[[#\|Service Decomposition & Composition]]
		+	#[[#\|Cloud Decomposition & Composition]]
		+	#[[#\|Information Decomposition & Composition]]
		+	#[[#\|Application Decomposition & Composition]]
		+	#[[#\|Data Decomposition & Composition]]
		+	#[[#\|Platform Decomposition & Composition]]
		+	#[[#\|Infrastructure Decomposition & Composition]]
		+
		+	=== Decomposition & Composition ===
		+
		+	Decomposition is the process by which the objects are broken down into simpler forms of objects. For example, an application is decomposed into one or more application component(s), while an application component is decomposed into one or more application module(s) and an application module is decomposed into one or more application function(s).
		+
		+	<br/>
		+
		+	The application function can, however, be decomposed into multiple application tasks and furthermore an application function defines (a part of) an application service flow. The application service can then be decomposed into application tasks. This simple application decomposition example shows the relevance of decomposing the wanted modelling objects the right way. However, once an object is decomposed it needs to be connected to the right areas. For example, a business normally needs within their application the use of one or more application services, which consist of application tasks and application functions.
		+
		+	<br/>
		+
		+	The business sets the purpose for the application and sets the requirements to which the application has to adhere to. An application has an appointed owner of the business and rules are set up to govern the application. Any application task, service or function may be subject to measurement. Application tasks, services or functions are sometimes required to be compliant. Several business competencies use applications to facilitate the automation of one or more of the activities or steps in their processes.
		+
		+	<br/>
		+
		+	The application flow determines the flow of an application’s tasks, services and functions. One or more business roles call or deliver input to the application’s tasks, services, and functions. Within the tasks, services and functions of application’s business, information and/or data objects are being used.
		+
		+	<br/>
		+
		+	Application tasks, services and functions use, modify, delete and/or produce data. Usually the application will be delivered through a channel and application tasks, services and functions may interact via different media. Application tasks, services and functions are hosted by platforms and the execution of the application service is enabled by infrastructure.
		+
		+	<br/>
		+
		+
		+	[[File:LEAD-Decomposition-Composition-Method-Application-Level-1-01.png\|frame\|center\|840px\|link=http://lead.orpheus-dev.com/images/d/db/LEAD-Decomposition-Composition-Method-Application-Level-1.pdf\|Example of a LEADing Practice Decomposition & Composition Reference Content applied to an Application.]]
		+
	[[Category:Enterprise Engineering Standards]]		[[Category:Enterprise Engineering Standards]]