WO1997027557A1

WO1997027557A1 - Process management system and method

Info

Publication number: WO1997027557A1
Application number: PCT/US1997/001208
Authority: WO
Inventors: Jean B. Lehmann; Matthew B. Reid; Jaye D. Hicks; Steven K. Berenbrock; Brad L. Rucker; Scott M. Boettcher
Original assignee: Electronic Data Systems Corporation
Priority date: 1996-01-25
Filing date: 1997-01-24
Publication date: 1997-07-31
Also published as: CA2243830A1; AU1710297A; EP0976073A1; US5737727A; JP2000504131A; AU706198B2

Abstract

A process management system (10) for operating on a computer (102, 104, 106) includes a graphical user interface (14) for graphically representing a process or a portion thereof to a user, a work element for graphically representing a task to be performed in the process, a work product for graphically representing a resultant product of performing a task, an agent for graphically representing an actor responsible for performing a task, and a link for graphically connecting the work element, work product, and agent indicative of inter-relationships therebetween. A knowledge repository (16) is further coupled to the computer for storing valuable information regarding the process.

Description

PROCESS MANAGEMENT SYSTEM AND METHOD

TECHNICAL FIELD OF THE INVENTION

This invention is related in general to the field of computer software programs. More particularly, the invention is related to a process management system and method therefor.

BACKGROUND OF THE INVENTION

When faced with a complex task, careful consideration and planning are often required to analyze the problem and define the efforts and resources needed to successfully complete the task. Process management refers to the "direction, control, and coordination of work performed to develop a product or perform a service"¹. It involves the specification of who, what, and how requirements for completing tasks. Some companies manage their processes by documenting them in voluminous paper documents, which are difficult and cumbersome to revise, reprint, redistribute, and consult.

There are some existing software that attempt to provide an automated and computerized tool to perform process management, including Project Bridge Modeler by Applied Business Technology, Process Engineer by earmonth & Burchett Management Systems, Methodology Administration Platform by Structured Solutions, Hyper Analyst by Bachman, and firstCASE by AGS Management Systems. These existing process management software tools share some common weaknesses, including a non-graphical expression of the modeled process, a restriction on the number of hierarchical levels allowable in the process, a lack of support for iterative processes, and a lack of support for storing process information in a repository for multi-user access.

SUMMARY OF THE INVENTION Accordingly, there is a need for a process management system and method therefor that support textual and graphical expression of multiple levels of process detail, iterative processes and decision processing, and a repository of knowledge. In accordance with the present invention, a process management system and method are provided which eliminates or substantially reduces the disadvantages associated with prior systems.

In one aspect of the invention, a process management system for operating on a computer includes a graphical user interface for graphically presenting a process or a portion thereof to a user, a work element for graphically representing a task to be performed in the process, a work product for graphically representing a resultant product of performing a task, an agent for graphically representing an actor responsible for performing a task, and a link for graphically connecting the work element, work product, and agent indicative of inter-relationships therebetween. A knowledge repository is further coupled to the computer for storing valuable information regarding the process.

In another aspect of the invention, a method for defining and managing a process on a computer includes the steps of graphically representing a task with a work element graphical object, defining properties associated with the work element graphical object, graphically representing a product resulting from performing a task with a work product graphical object, defining properties associated with the work product graphical object, graphically representing an actor with an agent graphical object, defining properties associated with the agent graphical object, and graphically linking the work element, work product, and agent graphical objects to indicate a process flow.

In yet another aspect of the invention, a method for defining and managing a process on a computer includes the steps of graphically displaying a defined process where tasks are graphically represented by a work element graphical object, products resulting from performing a task are graphically represented by a work product graphical object, actors are graphically represented with an agent graphical object, and said graphical objects are linked to indicate a process flow. A work element graphical object may be expanded to drill down to a graphical representation of a sub-process. Properties associated with the work element, work product, and agent graphical objects may also be displayed.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the present invention, reference may be made to the accompanying drawings, m which: FIGURE 1 is a simplified block diagram of a process management system and method constructed according to the teachings of the present invention;

FIGURE 2A to 21 are exemplary process notations of components and connecting links; FIGURE 3 is a diagram showing a ma^or component, work element, and its minor components;

FIGURE 4 is a diagram showing a major component, work product, and its minor components;

FIGURE 5 is a diagram showing a ma]or component, agent, and its minor components;

FIGURE 6 is an exemplary dialog window prompting for process information;

FIGURE 7 is an exemplary dialog window prompting for work element information; FIGURE 8 is an exemplary dialog window prompting for work product information;

FIGURE 9 is an exemplary dialog prompting for process input/output information;

FIGURE 10 is an exemplary dialog window prompting for responsibility information;

FIGURE 11 is an exemplary graphical screen showing a bug correction process;

FIGURE 12 is an exemplary graphical screen showing a bug correction subprocess; FIGURE 13 is an exemplary graphical screen showing an agent dialog window;

FIGURE 14 is an exemplary graphical screen showing a work product dialog window; and

FIGURE 15 is a simplified diagram showing a computer network connecting computers for accessing the process management system of the present invention and data files stored m a common shared memory. DETAILED DESCRIPTION OF THE INVENTION

The preferred embodiment (s) of the present invention is (are) illustrated in FIGURES 1-15, like reference numerals being used to refer to like and corresponding parts of the various drawings.

Referring to FIGURE 1, a process management system constructed according to the teachings of the present invention is shown indicated generally at 10. Process management system 10 uses a number of major components 12, including work element, work product, agent, and several connectivities, to represent or express a process. The process is presented to user(s) graphically through a graphical user interface (GUI) 14. A knowledge repository 16 is coupled to process management system 10 for storing knowledge acquired in formulating past processes, such as templates of existing processes. In one embodiment of the present invention, process management system 10 is developed using object-oriented software development technology. Process management system 10 may be written in the C++ programming language, and commercially available GUI class libraries Tools.h++ from Rogue Wave and/or StarView from Star Division may be used.

FIGURES 2A through 21 show the exemplary notations used to represent the various components of a process. FIGURE 2A shows a work element represented by a rectangle, which is a task that is to be performed. FIGURE 2B is a rectangle with a shadow, which represents a summary work element that has more process details and may be expanded to view those details. The process of expanding a component to view additional details is also called "drill down". In FIGURE 2C, a rectangle with dash lines is a conditional work element, representing a task that is to be performed if a condition is met. FIGURE 2D is a work product, represented by a circle as shown or an ellipse. A work product is the result of performing a task or work element. FIGURE 2E is an agent, represented by a hexagon, which is the person, machinery, automation, or software that is responsible for the task.

The major components: work element, work product, and agent of the process are connected by links shown in FIGURES 2F through 21. A line in FIGURE 2F is a responsibility connection, a line with an arrow thereon in FIGURE 2G denotes input or output, and a dashed line with an arrow in FIGURE 2H is a conditional input/output. FIGURE 21 shows a connection used to represent iteration. Each of the major components, work element, work product, and agent, can be linked to many minor components or properties or traits, which further describe the methodology or process. FIGURE 3 shows the exemplary minor components of a work element 20: standard 21, technique 22, training 23, reference 24, and policy 25. Standard 21 may specify the standard by which the work element is measured, such as the Capability Maturity Model (CMM) established by Software Engineering Institute (SEI) . Technique 22 may specify the techniques that can be used to perform the task described in the work element, such as brains orming, modeling, prototyping, simulation, technical review, etc. Training 23 may set forth the training available to help perform the task in work element 20. Reference 24 may include a bibliography of articles, books, and technical magazines that are associated with the performance of work element 20. Policy 25 may specify the governmental or company policies related to the performance of work element 20.

FIGURE 4 shows the exemplary minor components related to a work product 30. Standard 31 may describe the standard used to measure the quality of work product 31. Technique 32 may describe the techniques that can be used- to produce work product 30, such as joint iterative rapid development, financial cost models, function-level risk assessment, or precedence diagraming. Training 33 may describe the training class, seminar, or materials available or required to train for producing work product 30. Tool 34 sets forth the tool(s) needed to produce or make work product 30. Template 35 provides a shell or pattern that can be used as a guide for the development of work product 30 to speed up the process. Representative examples of work product 30 or completed templates may be provided as examples 36 of work product 30. If a tool or template is associated with an application, such as WordPerfect, Word, and Lotus 1-2-3, for example, system 10 automatically launches the application. Reference 37 is a bibliography that may provide additional information regarding making work product 30. Policy 38 sets forth any policy or policies encompassing the act of producing work product 30.

Four exemplary minor components are shown related to agent 50. Training 51 sets forth the training available for the agent. For example, if an agent is a project manager, the associated training may include project management development, leadership development, and customer relations. For a software developer, the training may include programming logic, object oriented programming principles, and C++ programming language. Reference 52 may list articles, books, and other information related to agent 50. Policy 53 may list any policy that is related to agent 50. Finally, standard 54 may describe the standards by which agent 50 is compared and measured.

It is important to emphasize that although specific symbols and components have been set forth above, they serve as examples and do not limit the teachings of the present invention to those embodiments explicitly shown. FIGURES 6-10 are simplified exemplary dialog windows used to formulate a methodology or process. Referring to FIGURE 6, an exemplary dialog window prompting for information on the process is shown. The name of the process, its owner, audience, purpose, and further descriptions may be specified. The owner of a process is the entity that owns the definition of the item. Accordingly, a process may be built from pieces of other processes. For example, a systems engineering process may reference start-up activities owned by a project management process. A special link may be used to tie processes together without making a new copy of the existing process. Information used to summarize a process is shown in the following table, some of which may not be shown in FIGURE 6, in which A/N stands for alphanumeric:

PROCESS

ATTRIBUTE REQ TYPE

Name Long title of the process Y A/N

Short Name Short title ofthe process Y A N

Level Level in the Methodology Architecture (e.g Y A N Framework, Method, or Process)

Status Indication ofthe degree of completeness ofthe process Y A/N

Organization Name ofthe organization that owns the definition ofthe Y A/N process

Purpose List of objectives/reasons for usmg this process Y A/N

Description Overview/definition ofthe process A/N

Audience Description ofthe targeted audience for this process A/N

Context Bnef description of how this process fits interreia.es A/N with other related mateπal

Contact Where to go for additional information A/N

Benefits List of benefits of this process to company and to the A/N customer

Scope Brief description of the scope of the process A/N

Version/Release Indication ofthe applicable version and release A/N

Note that a Help button, if clicked on, provides context- sensitive on-line help support to the user.

FIGURE 7 shows an exemplary dialog window for entering information on a work element, including name, short name, whether the work element is required or conditional, and additional textual information such as: purposes, conditions, guidelines, procedure, description, etc. Dialog windows for entering attributes or associated minor components, such as references, training, and techniques are further reachable by clicking on respective push buttons. The following table summarizes the exemplary information used to describe a work element. The IF SUMMARY column indicates whether the attribute is specified, can be rolled up from lower detailed level attributes, or can be derived.

WORKELEMENT

ATTRIBUTE DESCRIPTION REQ TYPE IF SUMMARY

Name Long title ofthe work element Y A N Specify

Short Name Short title ofthe work element A/N Specify

Level (NY) Whether the work element is summary or detail Derived Derive (leaf)

Summary Type Whether the work element summarizes its A N Specify (?) children by function or flow (for summary elements only)

Alias List of customer local aliases for the work A N Specify element

Purpose List of objectives/reasons for the work element Y A N Specify Roll Up

Description Short overview/definition ofthe work clement A/N Specify

Guideline List of guidelines for performing the work A/N Specify element

Critical Success List of items that must be present for successful A/N Specify Roll Factor completion ofthe work element Up

Procedure List of steps required for completing the work A/N N/A element; describes the "how-to" or "step-by- step" instructions (SET) (for detail elements only)

Standards List of specific standards considerations (e.g. SEI A N Specify Consideration considerations to ensure CMM Level 2)

Required/ Whether the work element is required or Binary Roll Up Conditional conditional ATTRIBUTE DESCRIPTION REQ TYPE IF SUMMARY

Condition List of conditions under which the work element A N N/A should be completed (for conditional elements only)

Entry Criteria Conditions that must be met before the work Dcnved Denve

(?) element can be started (inputs in the proper status, agents trained, task dependencies satisfied, etc.)

Exit Criteria (?) Conditions expected upon completion o the Derived Denve work element (outputs completed in the proper status, procedure completed, agents' responsibilities fulfilled, task dependencies sausfied, etc.)

User-defined Attributes that can be assigned by the process A N Specify attributes (NY) author that are process specific (one to three available)

FIGURE 8 is an exemplary window for requesting information on a work product. The table below summarizes the information used to describe a work product.

WORKPRODUCT

ATTRIBUTE DESCRIPTION REQ TYPE IF SUMMARY

Name Long title ofthe work product Y A N Specify

Short Name Short title of the work product A/N Specify

Level (NY) Whether the work product is summary or detail Derived Denve (leaf)

Type The category of work product (e.g. decision, A/N Specify/ Roll condition, document, individual, etc.) Up

Delrverable/Non- Whether work product can be delivered to the Binary Specify Roll deliverable customer Up

Internal/ Indication of whether this work product is Binary Specify/ Roll External internally produced or externally supplied Up ATTRIBUTE DESCRIPTION REQ TYPE DF SUMMARY

Alias List of customer/ local aliases for the work A N Specify product

Purpose List of objectives/reasons for the work product Y A/N Specify/Roll and the data represented bv the work product Up

Description Short overview/definition o the work product A N Specify

Guideline List of format and content guidelines for the A/N Specify work product

Content List ofthe data contained in the work product A N N/A with a brief descπpuon of each

Standards List of specific standards considerations (e g. SEI AM Specify Consideration considerations to ensure C M Level 2)

User-defined Attributes that can be assigned by the process AJN Specify attributes (NY) author that are process specific (one to three available)

The information used to describe an agent is summarized in the table below.

AGENT

ATTRIBUTE DESCRIPTION REQ TYPE IT- SUMMARY

Name Long title ofthe agent; participant's role (e.g. Y AM Specify project manager, data base administrator, etc.)

Short Name Short title ofthe agent; acceptable abbreviaUon AM Specify

Level (NY) Whether the agent is summary or detail (leaf) Derived Denve

Alias List of customer/local aliases for the agent A/N Specify

Description Short overview/definition of the agent A N Specify

Competency List of knowledge, skills and behaviors expected A N Specify or beneficial for performing in this role

User-defined Attributes that can be assigned by the process AM Specify attributes (NY) author that are process specific (one to three available) Input/output is a link that connects work products and work elements. A work product is an input to a work element, and a work product can also be an output of a work element. The input/output information is shown in the tables below.

INPUT

ATTRIBUTE DESCRIPTION REQ TYPE

Status Degree of completeness Y A N

Required Whether the work product is required as an input under all Y Binarv Conditional conditions

Condition List of conditions under which the input should be expected A N (for conditional work products only)

OUTPUT

ATTRIBUTE DESCRIPTION REQ TYPE

Status Degree of completeness Y AM

Required Whether the work product is required as an output under all Y Binary Conditional conditions

Condition List of conditions under which the output should be A/N completed (for conditional work products only)

The link between an agent and a work element is the responsibility connectivity. The information used to describe responsibility is listed in the table below and shown in an exemplary dialog screen in FIGURE 10 :

RESPONSIBILITY

ATTRIBUTE DESCRIPTION REQ TYPE

Type The responstbility/authonty the agent has for the work A/N element

SldU Level The degree of skill in this responsibility the agent will require A N (e.g. novice, intermediate, expert) Minor components associated with responsibility, including training, tools, and techniques, may also be specified. When these minor components are selected, appropriate dialog windows pop up to receive information entered by the user/author in a similar manner, using some of the same graphical tools shown. The information associated with each minor component is shown in the tables below.

TOOL

ATTRIBUTE DESCRIPTION REQ TYPE

Name Title ofthe tool Y A/N

Type Generalized type of tool (e.g. spreadsheet, word processor, AM etc.)

Description Short overview/definition ofthe tool Y A/N

Execution Execution requirements for launching the tool Y Information

TECHNIQUE

ATTRIBUTE DESCWPΠON REQ TYPE

Name Title ofthe technique Y AM

Type Generalized type of technique (e.g. modeling, prioritization, AM etc.)

Description Short ove ew/definition/abstract ofthe technique Y AM

Execution Executable file/directory instructions for launching the Y Information associated tool

TEMPLATE

ATTRIBUTE DESCRIPTION REQ TYPE

Name Title ofthe template Y A N

Explanation Brief description to make the template clear and A/N understandable

Execution Executable file/directory and execution instructions for Y Information launching the associated tool EXAMPLE

ATTRIBUTE DESCRIPTION REQ TYPE

Name Name of the example Y A/N

Explanation Brief description to make the example clear and A N understandable

Execution Executable file directory and execuuon instructions for Y Information launching the associated tool

REFERENCE

ATTRIBUTE DESCRIPTION REQ TYPE

Name Short identifier ofthe reference item AM

Description Due to the vanous pieces and formats of bibliographic entries A N the following represents suggesuons for the content of an entry

PublicaUon Name ofthe book, periodical, or AM other publication

Volume or version Volume or date of periodical, or AM version o the book/ document

Source Body, organization, or publisher A/N which provided or published the matenal

Article Titte ofthe article or section A N referenced

Author Authors) ofthe book, article, or A/N other publication

Content Brief description or key words A/N for the content o the mateπal

Execution Executable filedirectory and execution instructions for Information launching the associated tool

TRAINING

ATTRIBUTE DESCRIPTION REQ TYPE

Name Title or name ofthe training course of mateπal Y A N

Purpose List of learning objectives for the training course or material AM

Description Summarv/synopsis ofthe content o the course or mateπal AM ATTRIBUTE DESCRIPTION REQ TYPE

Provider Company or organization that provides the training course or Y A/N mateπal

Contact Directions for ordenng, enrollment, or requesung more AN information about the course or mateπal

Execution Executable file/directory and execution instructions for Information launching the associated tool

POLICY

ATTRIBUTE DESCRIPTION REQ TYPE

Name Short descπption ofthe policy, policy provides the law or Y AM regulations that govern, guide, or constrain operations (SEI)

Type Funcuonai grouping A/N

Statement Policy statement Y AM

Execution Executable file/directory and execution instructions for Y Information launching the associated tool

STANDARD

ATTRIBUTE DESCRIPTION REQ TYPE

Name Short dcscπpϋon ofthe standard; standard provides the Y AM operational definitions or acceptance cπteπa for final or interim products or process (SEI)

Type Functional grouping AM

Statement Standard statement Y AM

Execution Executable file/directory and execution lnstrucuons for Y Information launching the associated tool

It must be noted that the exemplary screens shown in FIGURES 6-10 are illustrative only, and that windows tools and manipulations such as push buttons, pull-down menus, tool bars, status lines, scroll bars, etc. as known in the art may be incorporated and/or substituted therein.

FIGURE 11 is an exemplary screen showing a bug correction process. A hierarchies window is to the left of the process window, which displays a graphical representation of the process. The hierarchies window currently shows the work element hierarchy, but may be changed to show agent or work product hierarchies of the process by clicking on the appropriate buttons immediately above the window. Those entries with a square icon appearing to the left of the text indicates that these elements are expandable and the user may drill down to a lower level. These expandable elements, for example "fix the bug" and "close", are shown in the graphical window with a shadow.

The process window contains the graphical depiction of a process or a portion of a process. Process windows contain agents, work elements, work products, and any connections therebetween. Every image in a process window is a selectable object that has properties associated therewith. Summary work elements shown as a work element with a shadow represent the existence of additional details in the form of another process window that can be reached by drilling down or double clicking on the work element. In this manner, complex processes may be organized into multiple levels of abstraction to facilitate the presentation and understanding thereof.

A customized tool bar is further provided to permit the user to select operations such as open file, close file, save file, print, and to further select icons for the work element, work product, agent, and links therebetween to build or modify the displayed process. The graphical display may be easily manipulated, for example, the size and location of the windows can be adjusted by clicking and dragging on the window or window boundaries, or the windows may be made to be cascaded, overlapped, or tiled.

It may be instructional to walk through the bug correction process to show how a process is represented. A developer 60 is responsible for (link 61) changing the bug status 62 in a piece of software. The work product of changing the bug status is a bug report 63 and a bug tracking database 64. The next task, fix the bug 65, is also recorded and documented in a bug report 66. The link between fix the bug 65 and test the fix 66 is iterative, because the first few attempts at fixing the bug may not succeed. The software (PS Application) 61 is the work product of testing the fix, if successful. If the bug fix is successful, the task close 68 is performed. Because work element close 68 is shown with a shadow, more process details exist and the work element may be expanded to drill down to the next level of details, as shown in FIGURE 12. The close sub-process shown in FIGURE 12 displays three tasks: check in files 71, update library files 72, and close out bug 73. The associated agents and work products of these work elements are shown. It may be seen that all work elements within a process are unique regardless of whether the name and short names are the same. Unlike work elements, agents and work products in a process that have the same name and short names are the same entity. Therefore, all bug reports and all agents in the bug correction process are the same respective entities. Referring to FIGURES 13 and 14, dialog windows displaying details of the developer agent and the bug report work product are shown overlaid on top of the process graphical representation. Any agent, work product, and work element defined in the process may be clicked on and details thereof may be displayed in like manner.

FIGURE 15 illustrates the distributed manner in which the instant system 10 may operate. Process management system 10 may be run on a stand alone personal computer or work station, or on one or more computers 102-106 that are linked together by a computer network 110. Information that can be shared by many users may be stored on a common database 108, which may also be linked by computer network 110. Operating in this manner, members of an engineering team may independently access and consult a process the team is working on.

System 10 further provides an export capability which produces files in several formats compatible with different applications. For example, Common-Separated Values formatted files may be exported to spreadsheet and database applications to generate statistical information on a process. Microsoft Project Exchange formatted files can also be produced and exported to most project management tools for project management.

Constructed in this manner, a process may be defined on process management system 10 easily and efficiently. Existing processes may also be easily revised and modified. System 10 displays the defined process in a graphical manner, which aides in the comprehension and management of the process. Knowledge accumulated from past experiences are also accessible by multiple users for reuse. For example, a company may distribute general processes that can then be customized to fit the special needs of individual organizations within the company. In this manner, existing processes may be reused and tailored to each new process without reinvestment of efforts. Through the use of system 10, company processes may be easily standardized with common terms and definitions. Furthermore, the number of levels of process details is unlimited in system 10, enabling complex processes to be represented in an uncluttered manner. Accordingly, in one aspect of the invention, a process management system for operating on a computer includes a graphical user interface for graphically presenting a process or a portion thereof to a user, a work element for graphically representing a task to be performed in the process, that work element being expandable into an unlimited number of graphically representable sub-process levels, a work product for graphically representing a resultant product of performing a task, an agent for graphically representing an actor responsible for performing a task, a link for graphically connecting the work element, work product, and agent indicative of inter¬ relationships therebetween, and a knowledge repository coupled to the computer for storing valuable information regarding the process. This project management system may further comprise a plurality of properties being associated with the work element. These properties associated with the work element may include a standard trait for associating any industry or organizational standard with the performance of the work element, a technique trait for associating any technique applicable to performing the work element, a training trait for associating any training and educational class with the performance of the work element, a policy trait for associating any governmental, industrial, and organizational policy with the performance of the work element, and/or a reference trait for associating any reference material with the performance of the work element . The process management system according to the present invention may also comprise a plurality of properties being associated with the work product. These properties may include a standard trait for associating any industry or organizational standard with the work product, a technique trait for associating any technique applicable to making the work product, a training trait for associating any training or educational class with making the work product, a tool trait for associating any tool applicable to making the work product, a template trait for associating a shell product that may be used as a starting point of making the work product, an example trait for associating exemplary completed work products with the work product, a reference trait for associating any reference material with the work product and/or a policy trait for associating any governmental, industrial, or organizational policy with the work product. Each of these traits, such as the tool trait, the example trait, and the template trait may further include a launchable application. The process management system may further comprise a plurality of properties being associated with the agent . These properties may include a standard trait for associating any industry or organization standard with the agent, a training trait for associating any training and educational class with the agent, and/or a policy trait for associating any governmental, industrial, or organizational policy with the agent. The graphical user interface of the process management system may further display a plurality of windows containing graphical representations of the process. Furthermore, the process management system may additionally comprise an exporter for exporting a defined process in a predetermined format and/or may further include context-sensitive help.

In another aspect of the invention, a method for defining and managing a process on a computer includes graphically representing a task with a work element graphical object, defining properties associated with the work element graphical object, graphically representing a product resulting from performing a task with a work product graphical object, defining properties associated with the work product graphical object, graphically representing an actor with an agent graphical object, defining properties associated with the agent graphical object, and graphically linking the work element, work product, and agent graphical objects to indicate a process flow, including graphically representing an iterative link corresponding to an iterative relationship. Such method may further include within the step of defining properties associated with the work element graphical object, defining a standard trait for associating any industry or organizational standard with the performance of the work element graphical object, defining a technique trait for associating any technique applicable to performing the work element graphical object, defining a training trait for associating any training or educational class with the performance of the work element graphical object, defining a policy trait for associating any governmental, industrial, or organizational policy with the performance of the work element graphical object, and/or defining a reference trait for associating any reference material with the performance of the work element graphical object. The method for defining and managing a process on a computer may further include within the step of defining properties associated with the work product graphical object defining a standard trait for associating any industry or organizational standard with the work product graphical object, defining a technique trait for associating any technique applicable to making the work product graphical object, defining a training trait for associating any training and educational class with making the work product graphical object, defining a tool trait for associating any tool applicable to making the work product, defining a template trait for associating a shell product that may be used as a start point of making the work product graphical object, defining an example trait for associating exemplary completed work products with the work product graphical object, defining a reference trait for associating any reference material with the work product graphical object, and/or defining a policy trait for associating any governmental, industrial, or organizational policy with the work product graphical object. These traits, including the template trait, example trait, and tool trait, may further include a step for defining a launchable application. The method for defining and managing a process on a computer may further include within the step of defining properties associated with the agent graphical object defining a standard trait for associating any industry or organization standard with the agent graphical object, defining a training trait for associating any training and education class with the agent graphical object, and/or defining a policy trait for associating any governmental, industrial, or organizational policy with the agent graphical object. Moreover, the method for defining and managing a process on a computer may include a step for providing a plurality of windows containing graphical representations of levels of the process.

In a further aspect of the invention, a method for defining and managing a process on a computer includes graphically displaying a defined process where tasks are graphically represented by a work element graphical object, products resulting from performing a task are graphically represented by a work product graphical object, actors are graphically represented with an agent graphical object, and the graphical objects are linked to indicate a process flow, expanding a work element graphical object to drill down to a graphical representation of a sub-process, and displaying properties associated with the work product, work element, and agent graphical objects. The property displaying step of this method may further include the step of displaying a standard trait associating any industry or organizational standard with a performance of the work element graphical object, displaying a technique trait for associating any technique applicable to performing the work element graphical object, displaying a training trait for associating any training and educational class with a performance of the work element graphical object, displaying a policy trait for associating any governmental, industrial, and organizational policy with the performance of the work element graphical object, and/or displaying a reference trait for associating any reference material with the performance of the work element graphical object. Moreover, the property displaying step of the method for defining and managing a process on the computer may further include a step for displaying a standard trait for associating an industry or organizational standard with the work product graphical object, displaying a technique trait for associating any technique applicable to making the work product graphical object, displaying a training trait for associating any training and educational class with making the work product graphical object, displaying a tool trait for associating any tool applicable to making the work product graphical object, displaying a template trait for associating a shell product that may be used as a starting point of making the work product graphical object, displaying an example trait for associating exemplary completed work products with the work product graphical object, displaying a reference trait for associating any reference material with the work product graphical object, and/or displaying a policy trait for associating any governmental, industrial, or organizational policy with the work product graphical object. The properly displayed step may further include a step of launching an application. Further the property displaying step of the method for defining and managing a process on a computer may further include a step of displaying a standard trait for associating any industry or organizational standard with the agent graphical object, displaying a training trait for associating any training and education class with the agent graphical object, and/or displaying a policy trait for associating any governmental, industrial, or organization policy with the agent graphical object. The method for defining and managing a process on a computer may further comprise the step of exporting a defined process in a predetermined format . Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made therein without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

WHAT IS CLAIMED IS:

1. A process management system for operating on a computer, comprising: a graphical user interface for graphically presenting a process or a portion thereof to a user; a work element for graphically representing a task to be performed in the process, said work element being expandable into an unlimited number of graphically representable sub-process levels; a work product for graphically representing a resultant product of performing a task; an agent for graphically representing an actor responsible for performing a task; a link for graphically connecting said work element, work product, and agent indicative of inter¬ relationships therebetween; and a knowledge repository coupled to said computer for storing valuable information regarding the process.

2. The process management system, as set forth in claim 1, wherein said link includes a responsibility link for connecting an agent with a work element.

3. The process management system, as set forth in claim 1, wherein said link includes an input/output link for connecting a work element with a work product.

4. The process management system, as set forth in claim 3, wherein said input/output link includes a conditional input/output link.

5. The process management system, as set forth in claim 1, wherein said link includes an iteration link indicative of an iterative relationship.

6. The process management system, as set forth in claim 1, further comprising a plurality of properties being associated with said work element.

7. The process management system, as set forth in claim 1, further comprising a plurality of properties being associated with said work product.

8. The process management system, as set forth in claim 1, further comprising a plurality of properties being associated with said agent.

9. The process management system, as set forth in claim 1, further comprising a process link for linking a defined process to another defined process or a portion thereof.

10. A method for defining and managing a process on a computer, comprising the steps of: graphically representing a task with a work element graphical object; defining properties associated with said work element graphical object; graphically representing a product resulting from performing a task with a work product graphical object; defining properties associated with said work product graphical object; graphically representing an actor with an agent graphical object; defining properties associated with said agent graphical object; and graphically linking said work element, work product, and agent graphical objects to indicate a process flow, including graphically representing an iterative link corresponding to an iterative relationship.

11. The method, as set forth in claim 10, further comprising the step of graphically representing said work element being expandable into an unlimited number of graphically representable sub-process levels.

12. The method, as set forth in claim 10, wherein the graphically linking step includes the step of graphically representing a responsibility link for connecting an agent graphical object with a work element graphical object.

13. The method, as set forth in claim 10, wherein the graphically linking step includes the step of graphically representing an input/output link for connecting a work element graphical object with a work product graphical object.

14. The method, as set forth in claim 13, wherein the graphically representing input/output link step includes the step of graphically representing a conditional input/output link.

15. The method, as set forth in claim 10, further comprising the step of providing a plurality of dialog windows for receiving property definitions of said work element, work product, and agent graphical objects.

16. The method, as set forth in claim 10, further comprising the step of exporting a defined process in a predetermined format.

17. The method, as set forth in claim 10, further comprising the step of defining a process link for linking a defined process to another defined process or a portion thereof.

18. The method, as set forth in claim 10, further comprising the step of providing context-sensitive help.

19. A method for defining and managing a process on a computer, comprising the steps of: graphically displaying a defined process where tasks are graphically represented by a work element graphical object, products resulting from performing a task are graphically represented by a work product graphical object, actors are graphically represented with an agent graphical object, and said graphical objects are linked to indicate a process flow; expanding a work element graphical object to drill down to a graphical representation of a sub-process; and displaying properties associated with said work element, work product, and agent graphical objects.