LEAD Reference Content:The BPM Ontology - Revision history

Admin at 14:07, 12 January 2017

2017-01-12T14:07:21Z

Admin at 14:03, 12 January 2017

2017-01-12T14:03:11Z

Admin at 14:02, 12 January 2017

2017-01-12T14:02:40Z

Admin at 14:00, 12 January 2017

2017-01-12T14:00:40Z

Show changes

Admin at 13:56, 12 January 2017

2017-01-12T13:56:49Z

Admin at 13:56, 12 January 2017

2017-01-12T13:56:01Z

Admin at 13:55, 12 January 2017

2017-01-12T13:55:30Z

Admin at 13:54, 12 January 2017

2017-01-12T13:54:43Z

Admin at 13:53, 12 January 2017

2017-01-12T13:53:53Z

Admin at 13:53, 12 January 2017

2017-01-12T13:53:31Z

@@ Line 119: / Line 119: @@
 | style="background: #f0f0f0;" | Business resource/actor
 | A specific person, system, or organization that initiates or interacts with the defined functions and activities. Actors may be internal or external to an organization.
-| -
+|-
 | style="background: #f0f0f0;" | Business role
 | A part that someone or something has in a particular defined function, activity, or situation. A resource/actor may have a number of roles.
-| -
+|-
 | style="background: #f0f0f0;" | Business function
 | A cluster of tasks creating a specific class of jobs.
-| -
+|-
 | style="background: #f0f0f0;" | Business owner
 | A role performed by an actor with the rights, rules, competencies, and capabilities to take decisions for the part of enterprise for which stewardship responsibilities have been assigned.
-| -
+|-
 | style="background: #f0f0f0;" | Cost
 | An amount that has to be paid or given up to obtain the use or access to something.
-| -
+|-
 | style="background: #f0f0f0;" | Revenue
 | The realized income of an enterprise or part thereof.
-| -
+|-
 | style="background: #f0f0f0;" | Object (business and information)
 | A real-world thing of use by or which exists within the enterprise and information objects reveal only their interface, which consists of a set of clearly defined relations. In the context of the business competency, the relevant objects are only those which relate to the enterprise’s means to act.
-| -
+|-
 | style="background: #f0f0f0;" | Product
 | A result and output generated by the enterprise. It has a combination of tangible and intangible attributes (features, functions, usage).
-| -
+|-
 | style="background: #f0f0f0;" | Contract
 | An agreement between two or more parties that establishes conditions for interaction.
-| -
+|-
 | style="background: #f0f0f0;" | Business rule
 | A statement that defines or constrains some aspect of behavior within the enterprise and always resolves to either true or false.
-| -
+|-
 | style="background: #f0f0f0;" | Business compliance
 | The process or tools for verifying adherence to rules and decisions.
-| -
+|-
 | style="background: #f0f0f0;" | Location
 | A facility, place, or geographic position.
-| -
+|-
 | style="background: #f0f0f0;" | Business channel
 | A means of access or otherwise interacting within an enterprise or between an enterprise and its external partners (customers, vendors, suppliers, etc.).
-| -
+|-
 | style="background: #f0f0f0;" | Business workflow
 | A stream, sequence, course, succession, series, and progression as well as order for the movement of information or material from one enterprise function, enterprise service, or enterprise activity (worksite) to another.
-| -
+|-
 | style="background: #f0f0f0;" | Business service
 | The externally visible (“logical”) deed or effort performed to satisfy a need or to fulfill a demand, meaningful to the environment.
-| -
+|-
 | style="background: #f0f0f0;" | Service flow (including output/input)
 | A set of one or more service input output states, where each service state defines a step in the service flow that, when entered, executes a behavior.
-| -
+|-
 | style="background: #f0f0f0;" | Service measurement (Service Performance Indicator (SPI) and Service Level Agreement (SLA))
 | The basis by which the enterprise evaluates or estimates the nature, quality, ability, or extent of the services. The commitments of a business service are assessed.
-| -
+|-
 | style="background: #f0f0f0;" | Logical application component
 | An encapsulation of application functionality that is independent of a particular implementation.
-| -
+|-
 | style="background: #f0f0f0;" | Physical application component
 | A deployable part of a software product, providing identifiable functions and existing within a specific version of the product.
-| -
+|-
 | style="background: #f0f0f0;" | Application function
 | The specification of a significant aspect of the internal behavior of the application, which acts as a broader description of a set of application features.
-| -
+|-
 | style="background: #f0f0f0;" | Application task
 | The automated behavior of a process activity performed by an application.
-| -
+|-
 | style="background: #f0f0f0;" | Application service
 | An externally visible unit of functionality, provided by one or more components, exposed through well-defined interfaces, and meaningful to the environment.
-| -
+|-
 | style="background: #f0f0f0;" | Application/system flow
 | The specification of the sequence in which two application tasks processes (or an application task and an application event or gateway) are executed, one of which provides an output, which is an input to the other.
-| -
+|-
 | style="background: #f0f0f0;" | System measurement
 | Measures that are defined and implementable within an application.
-| -
+|-
 | style="background: #f0f0f0;" | Application/system report
 | Reports that are defined and implementable or implemented within or by an application.
-| -
+|-
 | style="background: #f0f0f0;" | Application roles
 | A role performed by an actor with the rights, competencies, and capabilities to take decisions about an application, its behavior, and properties.
-| -
+|-
 | style="background: #f0f0f0;" | Application rule
 | A business rule implemented within and able to be executed by an application.
-| -
+|-
 | style="background: #f0f0f0;" | Data object
 | A logical cluster of all sets of related data representing an object view of a business object.
-| -
+|-
 | style="background: #f0f0f0;" | Data table
 | A physical specification of the means of arranging data in rows and columns while being stored in physically persistence structures.
-| -
+|-
 | style="background: #f0f0f0;" | Data flow
 | The specification of the sequence in which data moves from one state to another.
-| -
+|-
 | style="background: #f0f0f0;" | Data owner
 | A role performed by an actor with the rights, competencies, and capabilities to take decisions about the aspects of data for which stewardship responsibilities have been assigned.
-| -
+|-
 | style="background: #f0f0f0;" | Data rule
 | Criteria used in the process of determining or verifying values of data or generalizing certain features of data.
-| -
+|-
 | style="background: #f0f0f0;" | Platform device
 | A set of platform components configured to act as a modular part of a platform.

← Older revision		Revision as of 14:03, 12 January 2017
Line 12:		Line 12:

	Meta-objects create, describe, or equip objects. A meta-object defines an object’s type, relation attributes, functions, control structures, etc. Object groups serve to group objects with a common purpose, goal, aim, target, objective, and sets. In the BPM ontology, object groups collect meta-objects related to a subdomain. Object meta-models are precise definitions of meta-objects, the semantics of the relationships they are involved in, and the rules that apply to them. BPM ontology terms are assembled into two groups: composition and decomposition (meta-objects). The decomposition meta-objects are presented in Table 1 and allow modelers to structure processes.		Meta-objects create, describe, or equip objects. A meta-object defines an object’s type, relation attributes, functions, control structures, etc. Object groups serve to group objects with a common purpose, goal, aim, target, objective, and sets. In the BPM ontology, object groups collect meta-objects related to a subdomain. Object meta-models are precise definitions of meta-objects, the semantics of the relationships they are involved in, and the rules that apply to them. BPM ontology terms are assembled into two groups: composition and decomposition (meta-objects). The decomposition meta-objects are presented in Table 1 and allow modelers to structure processes.
		+

	{\| class="wikitable" style="text-align: left; width: 100%;"		{\| class="wikitable" style="text-align: left; width: 100%;"

← Older revision		Revision as of 14:02, 12 January 2017
Line 218:		Line 218:
	Table 2: Process composition meta-objects.		Table 2: Process composition meta-objects.

		+
		+	'''Document''': [[Media:The BPM Ontology.pdf\|Download the BPM Ontology document]]

	[[Category: Business Ontology]]		[[Category: Business Ontology]]

@@ Line 18: / Line 18: @@
 | style="width: 80%; background: #1f992d; color: #ffffff;" | '''Description'''
 |-
-| style="background: #e6e6e6;" | Process area (categorization)
+| style="background: #f0f0f0;" | Process area (categorization)
 | The highest level of an abstract categorization of processes.
 |-
-| Process group (categorization)
+| style="background: #f0f0f0;" | Process group (categorization)
 | A categorization and collection of processes into common groups.
 |-
-| Business process
+| style="background: #f0f0f0;" | Business process
 | A set of structured activities or tasks with logical behaviors that produce a specific service or product.
 |-
-| Process step
+| style="background: #f0f0f0;" | Process step
 | A conceptual set of behaviors bound by the scope of a process that, each time it is executed, leads to a single change of inputs (form or state) into a single specified output. Each process step is a unit of work normally performed within the constraints of a set of rules by one or more actors in a role, which are engaged in changing the state of one or more resources or enterprise objects to create a single desired output.
 |-
-| Process activity
+| style="background: #f0f0f0;" | Process activity
 | A part of the actual physical work system that specifies how to complete the change in the form or state of an input, oversee, or even achieve the completion of an interaction with others actors and which results in the making of a complex decision based on knowledge, judgment, experience, and instinct.
 |-

@@ Line 18: / Line 18: @@
 | style="width: 80%; background: #1f992d; color: #ffffff;" | '''Description'''
 |-
-| style="background: #f5f5f5;" | Process area (categorization)
+| style="background: #e6e6e6;" | Process area (categorization)
 | The highest level of an abstract categorization of processes.
 |-

@@ Line 15: / Line 15: @@
 {| class="wikitable" style="text-align: left; width: 100%;"
 |-
-| style="width: 20%; background: #1f992d; text-color: #ffffff;" | '''Process Object'''
+| style="width: 20%; background: #1f992d; color: #ffffff;" | '''Process Object'''
-| style="width: 80%; background: #1f992d; text-color: #ffffff;" | '''Description'''
+| style="width: 80%; background: #1f992d; color: #ffffff;" | '''Description'''
 |-
 | Process area (categorization)

@@ Line 15: / Line 15: @@
 {| class="wikitable" style="text-align: left; width: 100%;"
 |-
-| style="width: 20%; background: #c8c8c8;" | '''Process Object'''
+| style="width: 20%; background: #1f992d; text-color: #000;" | '''Process Object'''
-| style="width: 80%; background: #c8c8c8;" | '''Description'''
+| style="width: 80%; background: #1f992d; text-color: #000;" | '''Description'''
 |-
 | Process area (categorization)