You are here

Business Process

public class: Business_Process
Author: Jim Salmons
Project: Phase: 1.0; Status: Proposed; Version: 1.0; Complexity: 1
Dates: Created: 8/5/2006 3:11:40 PM; Modified: 8/6/2006 2:37:26 PM;
Flags: Active: false; IsRoot: false; IsLeaf: false;
Extension Points:
UUID: {EF18B42D-6A06-4970-85DE-43D6201A12CC}
In this metamodel, Business_Processes are relatively lightweight. That is, their role is to know which Actor Roles and initial Activities to instantiate in order to achieve their Goals. This lightweigt nature is what gives this metamodel its characterization an Actor-Role oriented model.

In most Workflow or Business Process Management systems, Process is "King." The Business Process model element is the "prime mover" and "referee" of the model's activity. Such Process-oriented systems can be easily understood and implemented as useful systems. However, they often lack some of the "faithfullness" to how we think about and participate in Real World systems.

For example, we may know that a Sales_Process is at work in a given context. But we more often think of this as a Buyer and Seller (Roles) engaged in a series of Activities (Negotion, Purchase Activities) that result in a Sale (Goal). The Sales_Process may conceptually encapsulate this scenario, but it is the Actors' playing Roles engaged in interactive Activities that realize the process.

So Business_Processes in an Actor-Role system are more like a Matchmaker than a Traffic Cop or Orchestra Conductor. Yes, Business_Processes play a vital role. But this role is not preeminent.

Goto: Custom Properties

See also: Role_Collaboration, Organization, Goal

Appears in: Logical View

Custom Properties