Business Process Reengineering - Chart Key

From RiskWiki

(Difference between revisions)
Jump to: navigation, search
m
m
Line 2: Line 2:
[[IMAGE:BPRChartKeyV4.gif]]
[[IMAGE:BPRChartKeyV4.gif]]
 +
Line 9: Line 10:
* All symbols are recursive - meaning that they can include nested members of the same type as the parent, a constrained subset of the child objects or, in some cases, unrestrained subsets.
* All symbols are recursive - meaning that they can include nested members of the same type as the parent, a constrained subset of the child objects or, in some cases, unrestrained subsets.
-
* All symbols are either objects or lines (arrows).
+
* All symbols are either events, objects or connectors ( lines or arrows).
-
* All objects are connected by lines or by being recursively embedded in a parent object - which then becomes a container for that object.
+
* All objects and/or events are connected by lines called connectors, or by being recursively embedded in a parent object - which then becomes a container for that object.
* Data flows through the connecting lines into the objects where it is stored, and/or transformed and/or distributed. Data is ethereal and moves from one place to another transforming and being transformed by the vesels in which it is store. A document, for example, is therefore considered to be a data store - not the data itself. A manufactured item, is also a data store, containing the end result of multiple processes each transforming the storage vessel. This is the key concept that enables this process charting method to transcend both service and manufacturing process modelling domains.
* Data flows through the connecting lines into the objects where it is stored, and/or transformed and/or distributed. Data is ethereal and moves from one place to another transforming and being transformed by the vesels in which it is store. A document, for example, is therefore considered to be a data store - not the data itself. A manufactured item, is also a data store, containing the end result of multiple processes each transforming the storage vessel. This is the key concept that enables this process charting method to transcend both service and manufacturing process modelling domains.
* The arrows connecting objects are dataflows - refering to the movement of information, not explicitly the media on which the information is stored at the time.
* The arrows connecting objects are dataflows - refering to the movement of information, not explicitly the media on which the information is stored at the time.
Line 18: Line 19:
** selector bars
** selector bars
** optional (conditional) flags
** optional (conditional) flags
 +
** Authorisation Signature and/or
 +
** Global Type flags (like E for error flows).
* Objects are sciptable
* Objects are sciptable
-
 
+
* All objects (and ideally, but not mandated - connectors) have unique identifiers.
-
 
+
* All objects can be containers and as such may be "drilled through" to their content
 +
* Events impose a block on some or all functions of the connected object untill the event fires.
 +
* All processes are assumed to operate concurrently when data is present on their incoming connectors, or an event fires, unless also constrained by other events blocking the object's funcctions. Events may thus operate as a clock, or trigger and as a governor or inhibitor.
 +
* The dataflow method is capable of modelling both excitatory networks and inhibitory process networks.

Revision as of 15:51, 17 January 2011

Chart Symbols and Their Meanings

IMAGE:BPRChartKeyV4.gif


Discussion

The key chart includes a number of features that are perhaps a little unusual:

  • All symbols are recursive - meaning that they can include nested members of the same type as the parent, a constrained subset of the child objects or, in some cases, unrestrained subsets.
  • All symbols are either events, objects or connectors ( lines or arrows).
  • All objects and/or events are connected by lines called connectors, or by being recursively embedded in a parent object - which then becomes a container for that object.
  • Data flows through the connecting lines into the objects where it is stored, and/or transformed and/or distributed. Data is ethereal and moves from one place to another transforming and being transformed by the vesels in which it is store. A document, for example, is therefore considered to be a data store - not the data itself. A manufactured item, is also a data store, containing the end result of multiple processes each transforming the storage vessel. This is the key concept that enables this process charting method to transcend both service and manufacturing process modelling domains.
  • The arrows connecting objects are dataflows - refering to the movement of information, not explicitly the media on which the information is stored at the time.
  • Connecting Arrows can take a number of annotations, including:
    • identification of the data stream (or data streams)
    • a filter condition for access
    • selector bars
    • optional (conditional) flags
    • Authorisation Signature and/or
    • Global Type flags (like E for error flows).
  • Objects are sciptable
  • All objects (and ideally, but not mandated - connectors) have unique identifiers.
  • All objects can be containers and as such may be "drilled through" to their content
  • Events impose a block on some or all functions of the connected object untill the event fires.
  • All processes are assumed to operate concurrently when data is present on their incoming connectors, or an event fires, unless also constrained by other events blocking the object's funcctions. Events may thus operate as a clock, or trigger and as a governor or inhibitor.
  • The dataflow method is capable of modelling both excitatory networks and inhibitory process networks.



BackLinks




CopyRight Bishop Phillips Consulting Pty Ltd 1997-2012 ( Business Process Reengineering - Chart Key )
Personal tools