Back

Back ... ... ... ... ... ... ... ... ... ... ... On Stream ... ... ... ... ... ... ... ... ... ... ... Forward

OntologyStream Inc.

Task D cannot be done before Task B.

This fact is often the bottom line. Without a proper ordering of the workflow, then the productivity of the enterprise is harmed.

Social problems with achieving good workflow:

S.1.1: Requires a leader who understands all detail

S.1.3: Description often must be redone as perceptions and activities change

S.2: Team membership must understand, agree to, and fulfill scheduled tasks on time

S.21: Must understand other’s needs

S.2.2: Ego and ownership must to accommodated

S.3: Overall process should be viewable by every team member

Complexity issues:

C.1: Viewpoint is derived from individual perception of the over all process – and these perceptions are not grounded in the same experiences.

C.2: Each viewpoint may have serious inadequacies when the workflow hits the pragmatic axis of real world constraints.

Issues related to a Process Model for IDEF or Topic Map or similar knowledge representational schema.

R.1: Task A (see figure) may have a topic map representation depicting an XML information structure relevant to Task A.

R.1.1: The notion of a process model could refer to the process in which the topic map representation comes into being

R.1.1.1: This could be simply formal as a means to do what?

R.1.1.1.1: automatically merge topic maps? – give example

R.1.1.1.2: have a data manipulation language for query, and updates? – need example.

R.1.1.2: This could involve issues of cause

R.1.1.2.1: Why was topic represented in this topic map this way?

R.1.1.2.2: What are the knowledge claims specific to the topic structure, and how might these claims be verified or judged?

R.1.2: The process model might be used in workflow.

R.2: Suppose Task B has a topic map representation. How does this representation hold the workflow dependencies that are part of the workflow?