CA2243830A1 - Process management system and method - Google Patents
Process management system and method Download PDFInfo
- Publication number
- CA2243830A1 CA2243830A1 CA002243830A CA2243830A CA2243830A1 CA 2243830 A1 CA2243830 A1 CA 2243830A1 CA 002243830 A CA002243830 A CA 002243830A CA 2243830 A CA2243830 A CA 2243830A CA 2243830 A1 CA2243830 A1 CA 2243830A1
- Authority
- CA
- Canada
- Prior art keywords
- work
- graphically
- graphical object
- work element
- agent
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06311—Scheduling, planning or task assignment for a person or group
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
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
WO 97/215S7 ~CT~US97~1208 PROCESS MANA~EMENT SYSTEM AND METHOD
I~r~ OF T~ INV~TION
This inventlon 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.
RZ~C~KGROU~D OF T~J~ lNV~ lON
When ~aced with a complex task, care~ul consideration and pl~nn;ng are often required to analyze the problem and de~ine the efforts and resources needed to successfully complete the task. Process management re~ers to the "direction, control, and coordination o~ wor~ performed to develop a product or perform a service"l. It invol~es the specification of who, what, and how requirements for completing tasks. Some ~omr~nies manage their processes by documenting them in ~oluminous 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 Learmonth & Burchett Management Systems, Methodology ~mi n i .ccration Platform by Structured Solutions, Hyper Analyst by Bachman, and firstCASE by AGS Management Systems. These existing , W O 97/275~7 PCT~US97/01208 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 iterati~e processes, and a lack of support for storing process information in a repositOry for multi-user access.
!5UMM~Y OF T~ l~v~lION
Accordingly, there is a need for a process management system and method therefor that support textual and graphical expression o~ multiple levels of process detail, iterative processes and decision processing, and a repository of knowledge.
In accordance with the present invention, a proces~
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 re~ponsible for performing a task, and a link for graphically connecting ~he 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 in~ention, a method for defining and managing a process on a computer includes the steps o~ graphically representing a task with a work element graphical object, defining properties associated with the work element graphical object, graphically representing a product resulting ~rom performing a task with a work product graphical object, defining properties WO 97/2755'7 PCT,/lJS97~01208 aSsociated with the work product graphical ob3ect, graphically representing an actor with an agent graphical object, de~ining properties associated with the agent graphical object, and graphically linking the work element, work product, and agent graphical obiects to indicate a process ~low.
In yet another aspect of the invention, a method for de~ining and managing a process on a computer includes the steps o~ 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 ~low. A work element graphical object may be ~r~n~e~ 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.
W O 97t27557 PCTrUS97/01208 BRIFF D~.SCRIPTION OF TH~ ~RAWINGS
For a better understanding o~ the present invention, reference may be made to the accompanying drawings, in which:
FIGURE l is a simplified block diagram of a process management system and method constructed according to the t~hlngs of the present invention;
FIGURE 2A to 2I are exemplary process notations of components and connecting links;
FIGURE 3 ls a diagram showing a major 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 major component, agent, and its minor components;
FIGURE 6 is an exemplary dialog window prompting for process information;
FIGU~E 7 is an exemplary dialog window prompting for work element in~ormation;
FIGURE 8 is an exemplary dialog window prompting for work product information;
FIGURE 9 is an exemplary dialog prompting ~or process input/output information;
FIGURE 10 is an exemplary dialog window prompting for responsibility information;
FIGURE ll 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 F~GURE 15 is a simplified diagram showing a computer network connecting computers ~or accessing the process management system o~ the present invention and data files stored in a common shared memory.
WO 97127557 PCT~US97~01208 ~TAIT,~n D~.~CRIPTION OF T~ IN~r~TION
The preferred embodlment(s) of the present invention is (are) illustrated in FIGURES 1-15, like reference numerals being used to re~er to like and corresponding parts o~ the various drawings.
Referring to FIGURE 1, a process management system constructed according to the teachings o~ the present invention is shown indica~ed generally at lO. Process management system 10 uses a number of major components 12, including work element, work product, agent, and several connecti~ities, 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 lO ~or storing knowledge acquired in ~ormulating past processes, such as templates of existing processes. In one embodiment o~ the present invention, process management system 10 is developed using object-oriented so~tware de~elopment technology. Process management system 10 may be written in the C++ programming language, and commercially available GUI c}ass libraries Tools.hl~ ~rom Rogue Wave and/or StarView from Star Division may be used.
FIGURES 2A through 2I 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 ~Xp~n~e~
to view those details. The process o~ expanding a component to view additional details is also called "drill downl'. In FIGURE 2C, a rectangle with dash lines is a conditional work element, representing a task that is to be per~ormed 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 per~orming a task or work element. FIGURE 2E is an agent, represented by a hexagon, W O 97~275~7 PCTrUS97/01208 .
which is the person, machinery, automation, or software that is responsible ~or the task.
The major components: work element, work product, and agent of the process are connected by links shown in S FIGURES 2F through 2I. 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 2I 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 ~urther describe the methodology or process. FIGURE 3 shows the exemplary minor components of a work element 20: st~ rd 21, technique 22, training 23, re~erence 24, and policy 25. Standard 21 may specify the st~n~l~rd by which the work element i8 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 brainstorming, m~l ;ng, 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 go~prnm~ntal or company policies related to the performance of work element 20.
FIGURE 4 shows the exemplary minor components related to a work product 30. S~:~nt~i9rd 31 may describe the standard used to measure the quality of work product 31.
Techni~ue 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, 8~m~n~~, or materials available or required to train ~or producing work product , W O 97/27557 PCT~US97/01208 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 m~k; ns 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 lS agent 50. Traini.ng 51 sets forth the tr~'n;ng 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 tr~; n; ng may include progr~mm;ng logic, object oriented progr~mm~ng principles, and C++ pl~y,~, ; n~ 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, st~n~rd 54 may describe the standards by which agent 50 is compared and measured.
It is important to ~mph~cize that although specific ~ymbols 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 o~ the process, its owner, audience, purpose, and further c~escriptions may be specified. The owner of a process is ~he entity that owns the definition of the item.
Accordingly, a process may be built ~rom pieces of other W O 97/27557 PCTrUS97/01208 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 alph~nl~meric:
PROCESS
ATT~UBUTE REQ TYPE
N~me Long title of the process Y A/N
Short N~lme Short title of ~e process Y A/N
Lev~l Level in the M. ~ ~ A~ (e.g. Y A~N
F ~ .JIL~ Method, or Process) St~tu~ T ' of the degree of ~ , ' of the proress Y A./N
~ L Name of the <,.~, that owns the ~-~fniti~tn of the Y A/N
process Purpo~e List of .. L; ~ ,~ for using this process Y A~N
r_ . O~_.vi.... ./~ of ~eprocess A/N
A- ~ n~ ;.. " of the tsrgeted audien~ e for this process A/N
Conte~t Brief ~.i~hU.I of how this process fits i~ ' A/N
with other related material 2 0 Cont~ct Where to go for ~,.L~ I in~ - A/N
Benef~t~ List of benefits of this process to company and to the A/N
customer Scope Brief ~;t~ iull of the scope of the pro ess A/N
Ver~ionlRelen~e T~ . of ~e '~FF' ' '- version and release A/N
Note that a Help button, i~ clicked on, provides context-sensitive on-line help suppQrt ~o the user.
FIGURE 7 shows an exemplary dialog window for entering in~ormation on a work element, including name, short name, 3Q whether the work element is re~uired or conditional, and additional textual informarion such as: purposes, W O 97/27557 PCT~US97~0~208 conditions, guidelines, procedure, description, etc.
Dialog windows for entering attributes or associated minor components, such ~s references, training, and techniques 2re further reachable by clicking on respective push buttons. The ~ollowing table summarizes the exemplary i.nformation used to describe a wor~ element. The IF
SUMMARY column indicates whether the attribute is specified, can be rolled up from lower detailed level attri~utes, or can be derived WORUKF~.FMF.~T
A11K1~U1~ DESCRIPlION REQ TYPE rF SUM~LURY
N~me Long titlc of the work element Y A/N Spccify Short N~me Short titlc of the work element A/N Specify Level (N~) Whether the work element is summary or detail Derived Dcrjve ~leaf) ~r- ,~ Type Whethcr the work dement ~ its A/N Specify t?) childrcn by f~mction or flow (for summuy dements only) ~li~ List of . '~ ' di~scs for the work A/N Specify ekment IPu~e List of ol.;.,~ .,J~.. . for thc work element Y A/N Specify/Roll Up ID~.-A ' Short~ . 'd ' oftheworkelementAIN Specify k ~ ' ~ List of guidelines for ~ the work AJN Spccify elemcnt Criffcel Succe~ List of items thnt must be prcscnt for successful A/N Specify/Roll li~ctor _ , ' of the work element Up 1~ List of steps rcquired for ~ the work A/N N/A
elemcnt; dcscribcs the "how-to" or "step-by-step" ~ h 'i (SEr) (for detail elemcnts only) 2 5 S~ ' ~ List of specif c standnrds . ' (e.g. SEI A/N Spccify C' ' ' . ' to ensurc CMM Level 2) . C.l/ Whether the work elcment is required or Binuy Roll Up W O 97/27557 PCT~US97/01208 Al~RIBUTE DESCR~PTION REQ TYPE IF
SUMMARY
Condiffon List of conditions under which the work element A/N N/A
should be completed (for ~ clements only) l~ntry Criteris C~ ' that must bc met before the work Derived Derive ('.') element csn oc stsrted (inputs in the proper status7 agents trsined. task d satisfied7 etc.) Exlt Criterin ~?) C~ ' expccted upon ~ of tne Dcrived Derjve work element (outputs compietcd in the proper status, proccdure c~lmpl~ agents' r ' fulfilled, t~sk satisficd, etc.) U~ Attributcs tnst can bc ~ssigned oy the process A/N Speci~y ~ttributes (NY) author tnat are process spccific (one to throe available) FIGURE 8 is an exemplary window for requesting in~ormation on a work product. The table below summarizes the in~ormation used to descri~e a work product.
WORKPRODUCT
AT~BUTE DESCR~ON REQ TYP~ ~
SUMMARY
Nune Long title of thc work product YA/N Spcci~y Short Na~ne Short titlc of the work product A/N Specify Level (NY) Whcther the work product is summa~y or det~il Dcrivcd Derivc (Ic8f) Type The catcgory of work product (e.g. decision, A/N Specify/ Roll condjtjon, documont, individusl. etc.) Up DeL. ~ Whcther work product csn bc delivercd to the Bin~ Spccify/Roll 2 0 d 'h_. ' ~ eustomer Up Inter~ai/ Indication of whether this work product is Binsry Specify/ Roll E~ter~ai intcrnRlly pro~uccd or extcrnallv supplied Up ~ A~RIBUTE DESCRIPTION REQ TYPI: IF
SUMMARY
Aiins List of ~ .t.. ll_l/local aliases for the work A/N Specify product Purpose List of ol,j.,~ i,c~ for the work product Y A/N Specify/Roll and the data ~ ' by the work product Up D~_., Short c, .~ of the work product A/N Specify Guidoiine List of format and content guidelines for the A/N Spcify work product Content List of the data contnined in the work product A/N N/A
with n brief I ~ . of esch e- ~ ~is List of specifie standnrds ~c ' (e g. SEI A/N Specify C~ ~ ' ' " ~ to ensure CMM Level 2) U~. ~ I ' Attributes that can be nssigned by the process A/N Speeif~
attrlbut~ ~ author that ~re process specific (one to three av~iinbie) The in~ormation used to describe an agent i5 sum~arized in the table below.
ATl'RIBUTE DESCRIPTIONREQ 'IYPE IF
SUMMARY
N~ne Long title of the n8erlt;r s role (e.g. Y A/N Specify project manager, data base ' etc.~
Short N~ne Short titlc of thc agent; ncceptable ' ~ ~ A/N Specify Level a~ Whether the ngent is surnmnry or detail (ieaf) DeriYed DaiYC
2 0 Ai~bs List of c Qe ' niiases for the agentA/N Spccify D._ . Short ~ ' ' of the ngent A/~ Spccify List of I . ' 1,, sicilis and behaviors expected A/N Specify or beneficiai for ~ ~ e in this role U~ ' Attributes thnt can be Assigned by the process A/N Specify attributes (NY~ nuthor thst are process specific (one to three aYailable) W O 97/27557 PCTrUS97/01208 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 o~ a work element. The inpu~/output information is shown in the tables below.
~PUT
Al'rRIBUTE DESCRIPTION REQ lYPE
StYtus Degree of , ' Y A/N
Re4uired/ Whether the work product is required as nn mput under all Y Biml~y C~ - ~ conditions Condition List of conditions under which the input should be expccted A/N
(for; ' ' work products oniv) OUTPUT
A~ ; DESCRIPTION REQTYPE
Stntu~. Degreeof_ . ' Y A/N
r-.~.. l/ Whether the work protuct i5 required ns n output under dl Y Binsry co~ditions Condiffon List of conditions under which the output should be A/N
completed (for. " ' 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 FIGU~E 10:
RESPOr CrP7~.1Ty A~ SU Ih DESt ~lt IlON REQ TYPE
Type The r '~ n~ u~ the sgent hns fot tne work AIN
delnent Sl~ill Lelrel The tcgree of skill in this , ' ' ~ tne n8ent will require A/N
(e.g. novice, i: ' expert~
WO 97127!iS7 PCT/US97~01208 Minor components associated wi~h 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 in~ormation associated with each minor component is shown in the tables below.
TOOL
ATIRIBUTE DESCRIPTION REQ TYPE
Name Titlc of the tool Y A/N
Type C ' ' type of tool (c.g. ~ 1. word proceaa-or. A/N
etc.) D~ ., Shortu.. ~; . ', ~ ofthctool Y A/N
r Execution I . for launching the tool Y
l!; I
TEC~HNIQUE
ATI~BUTE DESCRlPqlON REQ TYPE
Nune Title of the tcchniquc Y AIN
2 0 Type C -- ' ' type of tochnique ~e.g. modeling, p: AIN
ctc.) D~.-. Shorto. ~.. ~ '' ofthetechnique Y A/N
F. ' F~ ohl~ fu'c' ~-~ i for launching the Y
1 - ~ a~ociated tool 2 ~ 'l'EMrLATE
ATIRIBUTE DESCRIPllON REQ TYPE
N~ne Title of the template Y A/N
F ~ ~ Brief~~ .. tomakethetcmplateclcarnnd A~N
. . .
~-- r ~ and cxecution h.a~L for Y
I~r~ OF T~ INV~TION
This inventlon 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.
RZ~C~KGROU~D OF T~J~ lNV~ lON
When ~aced with a complex task, care~ul consideration and pl~nn;ng are often required to analyze the problem and de~ine the efforts and resources needed to successfully complete the task. Process management re~ers to the "direction, control, and coordination o~ wor~ performed to develop a product or perform a service"l. It invol~es the specification of who, what, and how requirements for completing tasks. Some ~omr~nies manage their processes by documenting them in ~oluminous 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 Learmonth & Burchett Management Systems, Methodology ~mi n i .ccration Platform by Structured Solutions, Hyper Analyst by Bachman, and firstCASE by AGS Management Systems. These existing , W O 97/275~7 PCT~US97/01208 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 iterati~e processes, and a lack of support for storing process information in a repositOry for multi-user access.
!5UMM~Y OF T~ l~v~lION
Accordingly, there is a need for a process management system and method therefor that support textual and graphical expression o~ multiple levels of process detail, iterative processes and decision processing, and a repository of knowledge.
In accordance with the present invention, a proces~
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 re~ponsible for performing a task, and a link for graphically connecting ~he 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 in~ention, a method for defining and managing a process on a computer includes the steps o~ graphically representing a task with a work element graphical object, defining properties associated with the work element graphical object, graphically representing a product resulting ~rom performing a task with a work product graphical object, defining properties WO 97/2755'7 PCT,/lJS97~01208 aSsociated with the work product graphical ob3ect, graphically representing an actor with an agent graphical object, de~ining properties associated with the agent graphical object, and graphically linking the work element, work product, and agent graphical obiects to indicate a process ~low.
In yet another aspect of the invention, a method for de~ining and managing a process on a computer includes the steps o~ 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 ~low. A work element graphical object may be ~r~n~e~ 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.
W O 97t27557 PCTrUS97/01208 BRIFF D~.SCRIPTION OF TH~ ~RAWINGS
For a better understanding o~ the present invention, reference may be made to the accompanying drawings, in which:
FIGURE l is a simplified block diagram of a process management system and method constructed according to the t~hlngs of the present invention;
FIGURE 2A to 2I are exemplary process notations of components and connecting links;
FIGURE 3 ls a diagram showing a major 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 major component, agent, and its minor components;
FIGURE 6 is an exemplary dialog window prompting for process information;
FIGU~E 7 is an exemplary dialog window prompting for work element in~ormation;
FIGURE 8 is an exemplary dialog window prompting for work product information;
FIGURE 9 is an exemplary dialog prompting ~or process input/output information;
FIGURE 10 is an exemplary dialog window prompting for responsibility information;
FIGURE ll 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 F~GURE 15 is a simplified diagram showing a computer network connecting computers ~or accessing the process management system o~ the present invention and data files stored in a common shared memory.
WO 97127557 PCT~US97~01208 ~TAIT,~n D~.~CRIPTION OF T~ IN~r~TION
The preferred embodlment(s) of the present invention is (are) illustrated in FIGURES 1-15, like reference numerals being used to re~er to like and corresponding parts o~ the various drawings.
Referring to FIGURE 1, a process management system constructed according to the teachings o~ the present invention is shown indica~ed generally at lO. Process management system 10 uses a number of major components 12, including work element, work product, agent, and several connecti~ities, 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 lO ~or storing knowledge acquired in ~ormulating past processes, such as templates of existing processes. In one embodiment o~ the present invention, process management system 10 is developed using object-oriented so~tware de~elopment technology. Process management system 10 may be written in the C++ programming language, and commercially available GUI c}ass libraries Tools.hl~ ~rom Rogue Wave and/or StarView from Star Division may be used.
FIGURES 2A through 2I 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 ~Xp~n~e~
to view those details. The process o~ expanding a component to view additional details is also called "drill downl'. In FIGURE 2C, a rectangle with dash lines is a conditional work element, representing a task that is to be per~ormed 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 per~orming a task or work element. FIGURE 2E is an agent, represented by a hexagon, W O 97~275~7 PCTrUS97/01208 .
which is the person, machinery, automation, or software that is responsible ~or the task.
The major components: work element, work product, and agent of the process are connected by links shown in S FIGURES 2F through 2I. 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 2I 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 ~urther describe the methodology or process. FIGURE 3 shows the exemplary minor components of a work element 20: st~ rd 21, technique 22, training 23, re~erence 24, and policy 25. Standard 21 may specify the st~n~l~rd by which the work element i8 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 brainstorming, m~l ;ng, 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 go~prnm~ntal or company policies related to the performance of work element 20.
FIGURE 4 shows the exemplary minor components related to a work product 30. S~:~nt~i9rd 31 may describe the standard used to measure the quality of work product 31.
Techni~ue 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, 8~m~n~~, or materials available or required to train ~or producing work product , W O 97/27557 PCT~US97/01208 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 m~k; ns 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 lS agent 50. Traini.ng 51 sets forth the tr~'n;ng 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 tr~; n; ng may include progr~mm;ng logic, object oriented progr~mm~ng principles, and C++ pl~y,~, ; n~ 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, st~n~rd 54 may describe the standards by which agent 50 is compared and measured.
It is important to ~mph~cize that although specific ~ymbols 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 o~ the process, its owner, audience, purpose, and further c~escriptions may be specified. The owner of a process is ~he entity that owns the definition of the item.
Accordingly, a process may be built ~rom pieces of other W O 97/27557 PCTrUS97/01208 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 alph~nl~meric:
PROCESS
ATT~UBUTE REQ TYPE
N~me Long title of the process Y A/N
Short N~lme Short title of ~e process Y A/N
Lev~l Level in the M. ~ ~ A~ (e.g. Y A~N
F ~ .JIL~ Method, or Process) St~tu~ T ' of the degree of ~ , ' of the proress Y A./N
~ L Name of the <,.~, that owns the ~-~fniti~tn of the Y A/N
process Purpo~e List of .. L; ~ ,~ for using this process Y A~N
r_ . O~_.vi.... ./~ of ~eprocess A/N
A- ~ n~ ;.. " of the tsrgeted audien~ e for this process A/N
Conte~t Brief ~.i~hU.I of how this process fits i~ ' A/N
with other related material 2 0 Cont~ct Where to go for ~,.L~ I in~ - A/N
Benef~t~ List of benefits of this process to company and to the A/N
customer Scope Brief ~;t~ iull of the scope of the pro ess A/N
Ver~ionlRelen~e T~ . of ~e '~FF' ' '- version and release A/N
Note that a Help button, i~ clicked on, provides context-sensitive on-line help suppQrt ~o the user.
FIGURE 7 shows an exemplary dialog window for entering in~ormation on a work element, including name, short name, 3Q whether the work element is re~uired or conditional, and additional textual informarion such as: purposes, W O 97/27557 PCT~US97~0~208 conditions, guidelines, procedure, description, etc.
Dialog windows for entering attributes or associated minor components, such ~s references, training, and techniques 2re further reachable by clicking on respective push buttons. The ~ollowing table summarizes the exemplary i.nformation used to describe a wor~ element. The IF
SUMMARY column indicates whether the attribute is specified, can be rolled up from lower detailed level attri~utes, or can be derived WORUKF~.FMF.~T
A11K1~U1~ DESCRIPlION REQ TYPE rF SUM~LURY
N~me Long titlc of the work element Y A/N Spccify Short N~me Short titlc of the work element A/N Specify Level (N~) Whether the work element is summary or detail Derived Dcrjve ~leaf) ~r- ,~ Type Whethcr the work dement ~ its A/N Specify t?) childrcn by f~mction or flow (for summuy dements only) ~li~ List of . '~ ' di~scs for the work A/N Specify ekment IPu~e List of ol.;.,~ .,J~.. . for thc work element Y A/N Specify/Roll Up ID~.-A ' Short~ . 'd ' oftheworkelementAIN Specify k ~ ' ~ List of guidelines for ~ the work AJN Spccify elemcnt Criffcel Succe~ List of items thnt must be prcscnt for successful A/N Specify/Roll li~ctor _ , ' of the work element Up 1~ List of steps rcquired for ~ the work A/N N/A
elemcnt; dcscribcs the "how-to" or "step-by-step" ~ h 'i (SEr) (for detail elemcnts only) 2 5 S~ ' ~ List of specif c standnrds . ' (e.g. SEI A/N Spccify C' ' ' . ' to ensurc CMM Level 2) . C.l/ Whether the work elcment is required or Binuy Roll Up W O 97/27557 PCT~US97/01208 Al~RIBUTE DESCR~PTION REQ TYPE IF
SUMMARY
Condiffon List of conditions under which the work element A/N N/A
should be completed (for ~ clements only) l~ntry Criteris C~ ' that must bc met before the work Derived Derive ('.') element csn oc stsrted (inputs in the proper status7 agents trsined. task d satisfied7 etc.) Exlt Criterin ~?) C~ ' expccted upon ~ of tne Dcrived Derjve work element (outputs compietcd in the proper status, proccdure c~lmpl~ agents' r ' fulfilled, t~sk satisficd, etc.) U~ Attributcs tnst can bc ~ssigned oy the process A/N Speci~y ~ttributes (NY) author tnat are process spccific (one to throe available) FIGURE 8 is an exemplary window for requesting in~ormation on a work product. The table below summarizes the in~ormation used to descri~e a work product.
WORKPRODUCT
AT~BUTE DESCR~ON REQ TYP~ ~
SUMMARY
Nune Long title of thc work product YA/N Spcci~y Short Na~ne Short titlc of the work product A/N Specify Level (NY) Whcther the work product is summa~y or det~il Dcrivcd Derivc (Ic8f) Type The catcgory of work product (e.g. decision, A/N Specify/ Roll condjtjon, documont, individusl. etc.) Up DeL. ~ Whcther work product csn bc delivercd to the Bin~ Spccify/Roll 2 0 d 'h_. ' ~ eustomer Up Inter~ai/ Indication of whether this work product is Binsry Specify/ Roll E~ter~ai intcrnRlly pro~uccd or extcrnallv supplied Up ~ A~RIBUTE DESCRIPTION REQ TYPI: IF
SUMMARY
Aiins List of ~ .t.. ll_l/local aliases for the work A/N Specify product Purpose List of ol,j.,~ i,c~ for the work product Y A/N Specify/Roll and the data ~ ' by the work product Up D~_., Short c, .~ of the work product A/N Specify Guidoiine List of format and content guidelines for the A/N Spcify work product Content List of the data contnined in the work product A/N N/A
with n brief I ~ . of esch e- ~ ~is List of specifie standnrds ~c ' (e g. SEI A/N Specify C~ ~ ' ' " ~ to ensure CMM Level 2) U~. ~ I ' Attributes that can be nssigned by the process A/N Speeif~
attrlbut~ ~ author that ~re process specific (one to three av~iinbie) The in~ormation used to describe an agent i5 sum~arized in the table below.
ATl'RIBUTE DESCRIPTIONREQ 'IYPE IF
SUMMARY
N~ne Long title of the n8erlt;r s role (e.g. Y A/N Specify project manager, data base ' etc.~
Short N~ne Short titlc of thc agent; ncceptable ' ~ ~ A/N Specify Level a~ Whether the ngent is surnmnry or detail (ieaf) DeriYed DaiYC
2 0 Ai~bs List of c Qe ' niiases for the agentA/N Spccify D._ . Short ~ ' ' of the ngent A/~ Spccify List of I . ' 1,, sicilis and behaviors expected A/N Specify or beneficiai for ~ ~ e in this role U~ ' Attributes thnt can be Assigned by the process A/N Specify attributes (NY~ nuthor thst are process specific (one to three aYailable) W O 97/27557 PCTrUS97/01208 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 o~ a work element. The inpu~/output information is shown in the tables below.
~PUT
Al'rRIBUTE DESCRIPTION REQ lYPE
StYtus Degree of , ' Y A/N
Re4uired/ Whether the work product is required as nn mput under all Y Biml~y C~ - ~ conditions Condition List of conditions under which the input should be expccted A/N
(for; ' ' work products oniv) OUTPUT
A~ ; DESCRIPTION REQTYPE
Stntu~. Degreeof_ . ' Y A/N
r-.~.. l/ Whether the work protuct i5 required ns n output under dl Y Binsry co~ditions Condiffon List of conditions under which the output should be A/N
completed (for. " ' 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 FIGU~E 10:
RESPOr CrP7~.1Ty A~ SU Ih DESt ~lt IlON REQ TYPE
Type The r '~ n~ u~ the sgent hns fot tne work AIN
delnent Sl~ill Lelrel The tcgree of skill in this , ' ' ~ tne n8ent will require A/N
(e.g. novice, i: ' expert~
WO 97127!iS7 PCT/US97~01208 Minor components associated wi~h 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 in~ormation associated with each minor component is shown in the tables below.
TOOL
ATIRIBUTE DESCRIPTION REQ TYPE
Name Titlc of the tool Y A/N
Type C ' ' type of tool (c.g. ~ 1. word proceaa-or. A/N
etc.) D~ ., Shortu.. ~; . ', ~ ofthctool Y A/N
r Execution I . for launching the tool Y
l!; I
TEC~HNIQUE
ATI~BUTE DESCRlPqlON REQ TYPE
Nune Title of the tcchniquc Y AIN
2 0 Type C -- ' ' type of tochnique ~e.g. modeling, p: AIN
ctc.) D~.-. Shorto. ~.. ~ '' ofthetechnique Y A/N
F. ' F~ ohl~ fu'c' ~-~ i for launching the Y
1 - ~ a~ociated tool 2 ~ 'l'EMrLATE
ATIRIBUTE DESCRIPllON REQ TYPE
N~ne Title of the template Y A/N
F ~ ~ Brief~~ .. tomakethetcmplateclcarnnd A~N
. . .
~-- r ~ and cxecution h.a~L for Y
3 0 ~ - Iaunching tho aasociated tool W O 97/275S7 PCTrUS97/01208 EXAMPLE
ATI'R~UTE DESCRIPTIONREQ TYPE
N me Nnmeofthe example Y A/N
F, ' ' Brief ~ to make the example clear and A/N
R- - Fvrr~ r~ 't;.-~.tu.~,andexecution i~al~r~liOnS for Y
1 ~ ~ Iaunching the associated tool REFERENCE
A'ITR~UTE DESCRIPTION~EQ TYPE
N-me Short identifier of the reference item A/N
. . ' Due to the vanous pieces ~md formats of ' ' ~ ~ , ' entries A/N
the follo-,ving represents ~ for the content of an entry I'i ~ ~ N me of the book, periodical. or A/N
other ~ ' ~
Volume or version Volume or tate of periotical. or A/N
version of the book/ tocument Source Body, . ~ or puolisher A/N
which provided or published the mnterial }5 Article Titleofthearticleorsection A/N
r fr~nr~rrl Author Author~s) of the book, article. or A/N
other r ~ ~ ' Content BriefA _ ~ r~ orkeyworts A/N
for the content of the material r .. r- ~ ~ f ~ rdi! ' ~r nnd execution ~ ~ for ~ ~ launching the assoeiated tool TRAIN~G
ATTR~U'rE DESCRIPIION REQ 'IYPE
Name Title or name of the training course of material Y A/N
Purpose List of learning objectives for the training course or material A/N
a s D SL~ n~ r of the content of the course or material AAN
WO 97~2755'7 PCT~US97/01208 ATTRUBUTE DESCRIPTION REQ TYPE
Provider Company or ~" ~5.. ~l;un that provides the training courso or Y A./N
material Cont~ct Directions for ordering, .,.. ull.. ~,.. l, or requesUng more AIN
sbout the eourse or materiai .- ,r F~.. t~ fl~ tu~ snd execuuon i~Duu~,huos for ' ~ iaunching the associateci tool POLICY
ATT~UBUTE DESCRlPllON REQ TYP~
N~me Short .l ;~ - of the policy, policy provides the law or Y A/N
. ~ ' that govem, guide, or constrain operations (SEI) Tgpe Funetionai grouping A/N
o~ . Policystatement Y A/N
F F.. . - ~ 'd ~ and execution ;~ hu~,hur~.~ for Y
iaunehing the ~ssociated tool STANDARD
AITRIBUTE DE~SCRIPTION REQ lYPE
N me Short d - - ;I,1:. .- ~ of the standard; standard provides the Y A/N
~, ' ' or . criteria for finai or interim products or process (SEI) Type Funetionsi grouping A/N
~' Standard staternent Y A/N
~ r - , y and execu~on i for Y
2 0 1 launehing 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 le~t o~
the process window, which displays a graphical , W O 97/275S7 PCT~US97/01208 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 wlndow. Those entries with a square icon appearing to the left of the tex~ indicates that these elements are expandable and the user may drill down to a lower level. These expandable elements, for example "~ix 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 o~ another proce~s window that can be reached by drilling down or double clicking on the work element.
In this m~nn~r, complex processes may be organized into multiple levels of a~straction to facilitate the presentation and underst~n~ing thereof.
A customized tool bar is further provided to permit the user to select operations such as open file, close ~ile, 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 ad3usted 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 ~ask, ~ix the bug 65, is W O 9712755'1 PCT~US97mlZ~8 also recorded and documented in a bug report 66. The link between fix the bug ~5 and test the fix 66 ls iterative, because the ~irst ~ew attempts at ~ixing the bug may not succeed. The software (PS Applica~ion) 67 is the work product of testing the fix, if successful. If the bug fix is success~ul, the task close 68 is per~ormed. Becau~e work element close 68 is shown wi~h a shadow, more process details exist and the work element may be ~p~n~ed to drill down to the next level of details, as shown in FIGURE 12.
~he 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 o~ 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 proce~s that have the same name and short names are the same entity.
l'herefore, all bug reports and all agents in the bug correction proces~ are the same re~pective entities.
Referring to FIGURES 13 and 14, dialog windows cLi playing details of the developer agent and the bug report work product are shown overlaid on top o~ the process graphical representation. Any agent, work product, ~nd work element de ined in the process may be clicked on 2S and details thereof may be displayed in like m~nn~r, FIGURE 15 illustrates the distributed m~nner in which the instant sys~em 10 may operate. Process management ~y~tem 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 ~e stored on a comm~n database 108, which may also be linked by computer network 110. Operating in this m~nner, members of an englneering team may independently access and consult a process the team is working on.
System 10 ~urther provides an export capability which produces files in several formats compatible with different CA 02243830 l998-07-2l W O 97/27557 PCT~US97/01208 ~ 18 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 ~or project management.
Constructed in this manner, a process may be defined on process management system lO easily and e~ficiently. Existing processes may also be easily revised and modified. System lQ 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 o~ ef~orts. Through the use o~ system lO, company processes may be easily standardized with common terms and definitions.
Furthermore, the number of levels of process details is unlimi~ed in system lO, 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 ~or graphically representing a task to be per~ormed in the process, that work element being expandable into an unlimited number o~ 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 ~or performing a task, a link for graphically connecting the work WO 97/2755'7 PCT~US97/01208 . 19 element, work product, and agent indicative o~ inter-relationships therebetween, and a knowledge repository coupled to the computer for storing valuable information regarding the process. This project - S management system may ~urther comprise a plurality of properties being associated wlth the work element.
These properties associated with the work element may include a standard trait ~or associating any industry or organizational standard with the per~ormance of the ~0 work element, a technique trait ~or associating any techni~ue applicable to performing the work element, a training trait for a~sociating any training and educational class with the per~ormance of the work element, a policy trait for associating any governmental, industrial, and organizational policy with the performance o~ 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 ~or 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 ~or 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 o~ these traits, such as the tool trait, the example trait, and the template trait may ~urther 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 ~or 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 inter~ace of the process management system may further display a plurality of windows containing graphical representations of the proces~.
Furthermore, the process management system may 1~ 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 ~or 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 re~ulting 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 ob~ect, 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 o~ defining propertie~
asRociated with the work element graphical object, defining a standard trait for associating any industry or organizational standard with the performance of the W O 9712755'7 PCTAUS97/01208 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 - 5 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 ~or 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, de~ining a technique trait for associating any technique applicable to making the work product graphical object, de~ining a training trait ~or 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 trai~ for associating exemplary completed work products with the work product graphical object, defining a reference trait for associating any reference material wi~h the work product graphical object, and/or de~ining a policy trait for a~sociating any governmental, indu~trial, 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 _ W O 97/27557 P~l/U~7/01208 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 S 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 lS 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 per~ormance 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 ~or associating any training and educational class with a performance of 3~ the work element graphical object, displaying a policy trait for associating any governmental, industrial, and , CA 02243830 l998-07-2l WO 97~275~ PCT~US97/01208 organizational policy with the performance of the work element graphical object, and/or displaying a reference ~ trait ~or 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, di~playing a training trait for associatin~ 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 W O 97/275S7 PCT~US97/01208 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.
S 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.
ATI'R~UTE DESCRIPTIONREQ TYPE
N me Nnmeofthe example Y A/N
F, ' ' Brief ~ to make the example clear and A/N
R- - Fvrr~ r~ 't;.-~.tu.~,andexecution i~al~r~liOnS for Y
1 ~ ~ Iaunching the associated tool REFERENCE
A'ITR~UTE DESCRIPTION~EQ TYPE
N-me Short identifier of the reference item A/N
. . ' Due to the vanous pieces ~md formats of ' ' ~ ~ , ' entries A/N
the follo-,ving represents ~ for the content of an entry I'i ~ ~ N me of the book, periodical. or A/N
other ~ ' ~
Volume or version Volume or tate of periotical. or A/N
version of the book/ tocument Source Body, . ~ or puolisher A/N
which provided or published the mnterial }5 Article Titleofthearticleorsection A/N
r fr~nr~rrl Author Author~s) of the book, article. or A/N
other r ~ ~ ' Content BriefA _ ~ r~ orkeyworts A/N
for the content of the material r .. r- ~ ~ f ~ rdi! ' ~r nnd execution ~ ~ for ~ ~ launching the assoeiated tool TRAIN~G
ATTR~U'rE DESCRIPIION REQ 'IYPE
Name Title or name of the training course of material Y A/N
Purpose List of learning objectives for the training course or material A/N
a s D SL~ n~ r of the content of the course or material AAN
WO 97~2755'7 PCT~US97/01208 ATTRUBUTE DESCRIPTION REQ TYPE
Provider Company or ~" ~5.. ~l;un that provides the training courso or Y A./N
material Cont~ct Directions for ordering, .,.. ull.. ~,.. l, or requesUng more AIN
sbout the eourse or materiai .- ,r F~.. t~ fl~ tu~ snd execuuon i~Duu~,huos for ' ~ iaunching the associateci tool POLICY
ATT~UBUTE DESCRlPllON REQ TYP~
N~me Short .l ;~ - of the policy, policy provides the law or Y A/N
. ~ ' that govem, guide, or constrain operations (SEI) Tgpe Funetionai grouping A/N
o~ . Policystatement Y A/N
F F.. . - ~ 'd ~ and execution ;~ hu~,hur~.~ for Y
iaunehing the ~ssociated tool STANDARD
AITRIBUTE DE~SCRIPTION REQ lYPE
N me Short d - - ;I,1:. .- ~ of the standard; standard provides the Y A/N
~, ' ' or . criteria for finai or interim products or process (SEI) Type Funetionsi grouping A/N
~' Standard staternent Y A/N
~ r - , y and execu~on i for Y
2 0 1 launehing 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 le~t o~
the process window, which displays a graphical , W O 97/275S7 PCT~US97/01208 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 wlndow. Those entries with a square icon appearing to the left of the tex~ indicates that these elements are expandable and the user may drill down to a lower level. These expandable elements, for example "~ix 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 o~ another proce~s window that can be reached by drilling down or double clicking on the work element.
In this m~nn~r, complex processes may be organized into multiple levels of a~straction to facilitate the presentation and underst~n~ing thereof.
A customized tool bar is further provided to permit the user to select operations such as open file, close ~ile, 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 ad3usted 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 ~ask, ~ix the bug 65, is W O 9712755'1 PCT~US97mlZ~8 also recorded and documented in a bug report 66. The link between fix the bug ~5 and test the fix 66 ls iterative, because the ~irst ~ew attempts at ~ixing the bug may not succeed. The software (PS Applica~ion) 67 is the work product of testing the fix, if successful. If the bug fix is success~ul, the task close 68 is per~ormed. Becau~e work element close 68 is shown wi~h a shadow, more process details exist and the work element may be ~p~n~ed to drill down to the next level of details, as shown in FIGURE 12.
~he 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 o~ 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 proce~s that have the same name and short names are the same entity.
l'herefore, all bug reports and all agents in the bug correction proces~ are the same re~pective entities.
Referring to FIGURES 13 and 14, dialog windows cLi playing details of the developer agent and the bug report work product are shown overlaid on top o~ the process graphical representation. Any agent, work product, ~nd work element de ined in the process may be clicked on 2S and details thereof may be displayed in like m~nn~r, FIGURE 15 illustrates the distributed m~nner in which the instant sys~em 10 may operate. Process management ~y~tem 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 ~e stored on a comm~n database 108, which may also be linked by computer network 110. Operating in this m~nner, members of an englneering team may independently access and consult a process the team is working on.
System 10 ~urther provides an export capability which produces files in several formats compatible with different CA 02243830 l998-07-2l W O 97/27557 PCT~US97/01208 ~ 18 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 ~or project management.
Constructed in this manner, a process may be defined on process management system lO easily and e~ficiently. Existing processes may also be easily revised and modified. System lQ 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 o~ ef~orts. Through the use o~ system lO, company processes may be easily standardized with common terms and definitions.
Furthermore, the number of levels of process details is unlimi~ed in system lO, 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 ~or graphically representing a task to be per~ormed in the process, that work element being expandable into an unlimited number o~ 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 ~or performing a task, a link for graphically connecting the work WO 97/2755'7 PCT~US97/01208 . 19 element, work product, and agent indicative o~ inter-relationships therebetween, and a knowledge repository coupled to the computer for storing valuable information regarding the process. This project - S management system may ~urther comprise a plurality of properties being associated wlth the work element.
These properties associated with the work element may include a standard trait ~or associating any industry or organizational standard with the per~ormance of the ~0 work element, a technique trait ~or associating any techni~ue applicable to performing the work element, a training trait for a~sociating any training and educational class with the per~ormance of the work element, a policy trait for associating any governmental, industrial, and organizational policy with the performance o~ 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 ~or 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 ~or 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 o~ these traits, such as the tool trait, the example trait, and the template trait may ~urther 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 ~or 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 inter~ace of the process management system may further display a plurality of windows containing graphical representations of the proces~.
Furthermore, the process management system may 1~ 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 ~or 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 re~ulting 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 ob~ect, 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 o~ defining propertie~
asRociated with the work element graphical object, defining a standard trait for associating any industry or organizational standard with the performance of the W O 9712755'7 PCTAUS97/01208 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 - 5 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 ~or 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, de~ining a technique trait for associating any technique applicable to making the work product graphical object, de~ining a training trait ~or 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 trai~ for associating exemplary completed work products with the work product graphical object, defining a reference trait for associating any reference material wi~h the work product graphical object, and/or de~ining a policy trait for a~sociating any governmental, indu~trial, 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 _ W O 97/27557 P~l/U~7/01208 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 S 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 lS 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 per~ormance 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 ~or associating any training and educational class with a performance of 3~ the work element graphical object, displaying a policy trait for associating any governmental, industrial, and , CA 02243830 l998-07-2l WO 97~275~ PCT~US97/01208 organizational policy with the performance of the work element graphical object, and/or displaying a reference ~ trait ~or 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, di~playing a training trait for associatin~ 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 W O 97/275S7 PCT~US97/01208 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.
S 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 (19)
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.
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.
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.
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.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/591,920 US5737727A (en) | 1996-01-25 | 1996-01-25 | Process management system and method |
US08/591,920 | 1996-01-25 |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2243830A1 true CA2243830A1 (en) | 1997-07-31 |
Family
ID=24368507
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002243830A Abandoned CA2243830A1 (en) | 1996-01-25 | 1997-01-24 | Process management system and method |
Country Status (6)
Country | Link |
---|---|
US (1) | US5737727A (en) |
EP (1) | EP0976073A1 (en) |
JP (1) | JP2000504131A (en) |
AU (1) | AU706198B2 (en) |
CA (1) | CA2243830A1 (en) |
WO (1) | WO1997027557A1 (en) |
Families Citing this family (99)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0770967A3 (en) * | 1995-10-26 | 1998-12-30 | Koninklijke Philips Electronics N.V. | Decision support system for the management of an agile supply chain |
JPH10105623A (en) * | 1996-09-27 | 1998-04-24 | Hitachi Ltd | Hierarchical work flow management method and work flow document circulation method |
GB9623954D0 (en) * | 1996-11-15 | 1997-01-08 | Xerox Corp | Systems and methods providing flexible representations of work |
US6104802A (en) | 1997-02-10 | 2000-08-15 | Genesys Telecommunications Laboratories, Inc. | In-band signaling for routing |
US7031442B1 (en) | 1997-02-10 | 2006-04-18 | Genesys Telecommunications Laboratories, Inc. | Methods and apparatus for personal routing in computer-simulated telephony |
US6480600B1 (en) | 1997-02-10 | 2002-11-12 | Genesys Telecommunications Laboratories, Inc. | Call and data correspondence in a call-in center employing virtual restructuring for computer telephony integrated functionality |
US7085775B2 (en) * | 1997-04-09 | 2006-08-01 | Sidewinder Holdings Ltd. | Database method and system for conducting integrated dispatching |
CA2228574A1 (en) * | 1997-06-05 | 1999-08-02 | Attention Control Systems, Inc. | An automatic planning and cueing system and method |
US7546346B2 (en) * | 1997-07-28 | 2009-06-09 | Juniper Networks, Inc. | Workflow systems and methods for project management and information management |
JPH1172499A (en) * | 1997-08-29 | 1999-03-16 | Shimadzu Corp | System controller for analyser |
US6711611B2 (en) | 1998-09-11 | 2004-03-23 | Genesis Telecommunications Laboratories, Inc. | Method and apparatus for data-linking a mobile knowledge worker to home communication-center infrastructure |
US6985943B2 (en) | 1998-09-11 | 2006-01-10 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus for extended management of state and interaction of a remote knowledge worker from a contact center |
US6051029A (en) * | 1997-10-31 | 2000-04-18 | Entelos, Inc. | Method of generating a display for a dynamic simulation model utilizing node and link representations |
USRE46528E1 (en) | 1997-11-14 | 2017-08-29 | Genesys Telecommunications Laboratories, Inc. | Implementation of call-center outbound dialing capability at a telephony network level |
US6078739A (en) * | 1997-11-25 | 2000-06-20 | Entelos, Inc. | Method of managing objects and parameter values associated with the objects within a simulation model |
US6069629A (en) * | 1997-11-25 | 2000-05-30 | Entelos, Inc. | Method of providing access to object parameters within a simulation model |
US6026402A (en) * | 1998-01-07 | 2000-02-15 | Hewlett-Packard Company | Process restriction within file system hierarchies |
US7907598B2 (en) | 1998-02-17 | 2011-03-15 | Genesys Telecommunication Laboratories, Inc. | Method for implementing and executing communication center routing strategies represented in extensible markup language |
US6332154B2 (en) | 1998-09-11 | 2001-12-18 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus for providing media-independent self-help modules within a multimedia communication-center customer interface |
CA2336785A1 (en) | 1998-07-02 | 2000-01-13 | Kepner-Tregoe, Inc. | Method and apparatus for problem solving, decision making, storing, analyzing, retrieving enterprisewide knowledge and conclusive data |
US6873961B1 (en) * | 1998-09-09 | 2005-03-29 | The United States Of America As Represented By The Secretary Of The Navy | Method and apparatus for identifying and tracking project trends |
USRE46153E1 (en) | 1998-09-11 | 2016-09-20 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus enabling voice-based management of state and interaction of a remote knowledge worker in a contact center environment |
US6249768B1 (en) * | 1998-10-29 | 2001-06-19 | International Business Machines Corporation | Strategic capability networks |
US8095581B2 (en) * | 1999-02-05 | 2012-01-10 | Gregory A Stobbs | Computer-implemented patent portfolio analysis method and apparatus |
US6415979B1 (en) | 1999-03-08 | 2002-07-09 | Snc-Lavalin Environment Inc. | Method and apparatus for identifying and recording values associated with plant equipment inspection used in managing fugitive emissions |
WO2000063793A2 (en) * | 1999-04-16 | 2000-10-26 | Entelos, Inc. | Method and apparatus for conducting linked simulation operations utilizing a computer-based system model |
JP2001014389A (en) * | 1999-06-25 | 2001-01-19 | Hitachi Ltd | Workflow server and client terminal |
US6397202B1 (en) * | 1999-07-01 | 2002-05-28 | The United States Of America As Represented By The Secretary Of The Navy | System and method for monitoring risk in a system development program |
US7437304B2 (en) * | 1999-11-22 | 2008-10-14 | International Business Machines Corporation | System and method for project preparing a procurement and accounts payable system |
US6738746B1 (en) | 1999-11-22 | 2004-05-18 | International Business Machines Corporation | System and method for ongoing supporting a procurement and accounts payable system |
US6687677B1 (en) | 1999-11-22 | 2004-02-03 | International Business Machines Corporation | System and method for deploying a procurement and accounts payable system |
US6684191B1 (en) * | 1999-11-22 | 2004-01-27 | International Business Machines Corporation | System and method for assessing a procurement and accounts payable system |
US6714915B1 (en) | 1999-11-22 | 2004-03-30 | International Business Machines Corporation | System and method for project designing and developing a procurement and accounts payable system |
AU1799301A (en) * | 1999-11-23 | 2001-06-04 | Andersen Consulting Llp | Decision management in a merger and acquisition environment and method thereof |
US6671693B1 (en) | 1999-11-23 | 2003-12-30 | Accenture Llp | System for effectively collecting and disseminating data |
US6671692B1 (en) | 1999-11-23 | 2003-12-30 | Accenture Llp | System for facilitating the navigation of data |
US8606588B1 (en) | 1999-11-23 | 2013-12-10 | Accenture Global Services Limited | Merger and acquisition knowledgebase |
US6571235B1 (en) | 1999-11-23 | 2003-05-27 | Accenture Llp | System for providing an interface for accessing data in a discussion database |
US7929978B2 (en) | 1999-12-01 | 2011-04-19 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus for providing enhanced communication capability for mobile devices on a virtual private network |
US7117260B2 (en) | 2000-01-27 | 2006-10-03 | American Express Travel Related Services Company, Inc. | Content management application for an interactive environment |
US7788631B2 (en) * | 2000-02-24 | 2010-08-31 | General Dynamics Advanced Information Systems, Inc. | Process automation system |
US6578004B1 (en) * | 2000-04-27 | 2003-06-10 | Prosight, Ltd. | Method and apparatus for facilitating management of information technology investment |
US7401131B2 (en) * | 2000-05-22 | 2008-07-15 | Verizon Business Global Llc | Method and system for implementing improved containers in a global ecosystem of interrelated services |
US6922685B2 (en) | 2000-05-22 | 2005-07-26 | Mci, Inc. | Method and system for managing partitioned data resources |
US20020005866A1 (en) * | 2000-07-14 | 2002-01-17 | Space-Wise Technologies, Inc. | Method and system for creation of a spatially referenced multimedia relational database that can be transmitted among users or published to internet |
US7246074B1 (en) * | 2000-10-13 | 2007-07-17 | International Business Machines Corporation | System and method for identifying skills and tools needed to support a process utilizing pre-defined templates |
US6750882B1 (en) * | 2000-10-31 | 2004-06-15 | Verizon Laboratories, Inc. | Automated association of operations with objects in a graphical window |
US7222329B2 (en) * | 2000-11-29 | 2007-05-22 | International Business Machines Corporation | Business systems management: realizing end-to-end enterprise systems management solution |
US6862585B2 (en) * | 2000-12-19 | 2005-03-01 | The Procter & Gamble Company | System and method for managing product development |
US20020082895A1 (en) * | 2000-12-22 | 2002-06-27 | Budka Phyllis R. | Method, apparatus and article for project management |
US20030061081A1 (en) * | 2000-12-26 | 2003-03-27 | Appareon | System, method and article of manufacture for collaborative supply chain modules of a supply chain system |
US6681197B2 (en) | 2001-01-05 | 2004-01-20 | The Quaker Oats Company | Automated data collection reporting and analysis system for industrial production |
US20080250020A1 (en) * | 2001-01-20 | 2008-10-09 | Pointcross, Inc | Ontological representation of knowledge |
US20080255918A1 (en) * | 2001-01-20 | 2008-10-16 | Pointcross, Inc. | Ontological representation of knowledge |
US6801818B2 (en) | 2001-03-14 | 2004-10-05 | The Procter & Gamble Company | Distributed product development |
US7406430B2 (en) * | 2001-03-30 | 2008-07-29 | International Business Machines Corporation | Method and system for assessing information technology service delivery |
US6643600B2 (en) | 2001-04-26 | 2003-11-04 | General Electric Company | Method and system for assessing adjustment factors in testing or monitoring process |
US20040015821A1 (en) * | 2001-05-01 | 2004-01-22 | Tonbu, Inc. | System and method for interactive collaborative process management and project management |
US20040204974A1 (en) * | 2001-05-10 | 2004-10-14 | Prinable Robert J. | Method of and system for gathering organisational information |
GB2376094A (en) * | 2001-05-30 | 2002-12-04 | Ibm | Flexible navigation of a workflow graph in a data processing system |
US20020198926A1 (en) * | 2001-06-25 | 2002-12-26 | Panter Gene L. | Program management system and method |
US7289966B2 (en) * | 2001-08-14 | 2007-10-30 | Norman Ken Ouchi | Method and system for adapting the execution of a workflow route |
US6978441B2 (en) * | 2001-10-03 | 2005-12-20 | Sun Microsystems, Inc. | Rating apparatus and method for evaluating bugs |
US20030083923A1 (en) * | 2001-10-29 | 2003-05-01 | Diego Guicciardi | Collaboration-enabled enterprise |
US7281221B2 (en) * | 2001-12-05 | 2007-10-09 | Siemens Building Technologies, Inc. | Work cell problem identification and notification system |
US7386797B1 (en) * | 2002-05-22 | 2008-06-10 | Oracle Corporation | Framework to model and execute business processes within a collaborative environment |
US7370072B2 (en) * | 2002-07-08 | 2008-05-06 | Electronic Evidence Discovery, Inc. | System and method for collecting electronic evidence data |
US7475107B2 (en) * | 2002-07-08 | 2009-01-06 | Electronic Evidence Discovery, Inc. | System and method for managing distributed computer processes |
WO2004053624A2 (en) | 2002-10-17 | 2004-06-24 | The Knowledge It Corporation | Virtual knowledge management system |
US6732648B1 (en) * | 2003-05-05 | 2004-05-11 | Day International Inc. | Printing blanket sleeve having sound dampening feature |
US20040243461A1 (en) * | 2003-05-16 | 2004-12-02 | Riggle Mark Spencer | Integration of causal models, business process models and dimensional reports for enhancing problem solving |
US7426736B2 (en) * | 2003-05-22 | 2008-09-16 | International Business Machines Corporation | Business systems management solution for end-to-end event management using business system operational constraints |
JP2005148933A (en) * | 2003-11-12 | 2005-06-09 | Nec Corp | Project management system and method |
US7904833B2 (en) * | 2003-12-08 | 2011-03-08 | International Business Machines Corporation | Electronic commerce GUI for displaying trading partners |
US20050209901A1 (en) * | 2004-03-18 | 2005-09-22 | Scott Miller | System and method for engineering project tracking |
US7729936B2 (en) * | 2004-05-20 | 2010-06-01 | Taiwan Semiconductor Manufacturing Co., Ltd. | System and method for lot priority adjustment |
US20050278687A1 (en) * | 2004-05-28 | 2005-12-15 | Suresh Madhavan | System and method for facilitating computer software features requested by end users |
US20060036990A1 (en) * | 2004-08-16 | 2006-02-16 | Lockheed Martin Corporation | Tool comprising systems engineering environment for meeting task requirements |
US7590942B2 (en) * | 2004-09-16 | 2009-09-15 | Novatech Llc | System, method and computer program product for documenting and managing execution of procedures in a graphical interface environment |
US20060229921A1 (en) * | 2005-04-08 | 2006-10-12 | Mr. Patrick Colbeck | Business Control System |
US20070016456A1 (en) * | 2005-07-12 | 2007-01-18 | International Business Machines Corporation | System, method and program product for reporting status of contract performance or a process |
US8620713B2 (en) * | 2005-07-15 | 2013-12-31 | Sap Ag | Mechanism to control delegation and revocation of tasks in workflow system |
US9008075B2 (en) | 2005-12-22 | 2015-04-14 | Genesys Telecommunications Laboratories, Inc. | System and methods for improving interaction routing performance |
US8396736B2 (en) * | 2006-04-21 | 2013-03-12 | Process Assets, Llc | Systems and methods for providing documentation having succinct communication with scalability |
US20090048896A1 (en) * | 2007-08-14 | 2009-02-19 | Vignesh Anandan | Work management using integrated project and workflow methodology |
EP2037359A1 (en) * | 2007-09-14 | 2009-03-18 | Siemens Aktiengesellschaft | A method and a system for generating project-related requirements |
US20090144194A1 (en) * | 2007-11-30 | 2009-06-04 | Mark Dickelman | Computer automated systems, devices and methods for data processing of accounting records |
US20090182770A1 (en) * | 2008-01-11 | 2009-07-16 | Pointcross, Inc. | Personalization of contextually relevant computer content |
US20090254546A1 (en) * | 2008-04-03 | 2009-10-08 | Pointcross, Inc. | Personalized screening of contextually relevant content |
US20100121740A1 (en) * | 2008-11-13 | 2010-05-13 | Oracle International Corporation | Data driven orchestration of business processes |
US8589877B2 (en) | 2009-10-07 | 2013-11-19 | International Business Machines Corporation | Modeling and linking documents for packaged software application configuration |
US8234570B2 (en) * | 2009-10-26 | 2012-07-31 | International Business Machines Corporation | Harvesting assets for packaged software application configuration |
US20110167070A1 (en) * | 2010-01-06 | 2011-07-07 | International Business Machines Corporation | Reusing assets for packaged software application configuration |
US8645854B2 (en) * | 2010-01-19 | 2014-02-04 | Verizon Patent And Licensing Inc. | Provisioning workflow management methods and systems |
US8417798B2 (en) | 2010-05-11 | 2013-04-09 | International Business Machines Corporation | Deploying artifacts for packaged software application in cloud computing environment |
US8612931B2 (en) | 2010-07-14 | 2013-12-17 | International Business Machines Corporation | Interactive blueprinting for packaged applications |
US8463816B2 (en) * | 2011-06-27 | 2013-06-11 | Siemens Aktiengesellschaft | Method of administering a knowledge repository |
US9542660B2 (en) | 2012-11-02 | 2017-01-10 | Mitchell International, Inc. | Work process collaboration management |
US10331437B2 (en) * | 2017-07-05 | 2019-06-25 | International Business Machines Corporation | Providing customized and targeted performance improvement recommendations for software development teams |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US538698A (en) * | 1895-05-07 | Car-coupling | ||
US5572436A (en) * | 1990-04-06 | 1996-11-05 | Lsi Logic Corporation | Method and system for creating and validating low level description of electronic design |
US5557531A (en) * | 1990-04-06 | 1996-09-17 | Lsi Logic Corporation | Method and system for creating and validating low level structural description of electronic design from higher level, behavior-oriented description, including estimating power dissipation of physical implementation |
US5598344A (en) * | 1990-04-06 | 1997-01-28 | Lsi Logic Corporation | Method and system for creating, validating, and scaling structural description of electronic device |
US5212771A (en) * | 1990-04-27 | 1993-05-18 | Bachman Information Systems, Inc. | System for establishing concurrent high level and low level processes in a diagram window through process explosion and implosion subsystems |
US5301301A (en) * | 1991-01-30 | 1994-04-05 | National Instruments Corporation | Polymorphic dataflow block diagram system and method for programming a computer |
JPH06187384A (en) * | 1991-02-26 | 1994-07-08 | Texas Instr Inc <Ti> | Designing method and designing-support system |
US5572430A (en) * | 1991-07-03 | 1996-11-05 | Hitachi, Ltd. | Method and apparatus for cooperated design |
JPH05324295A (en) * | 1991-09-12 | 1993-12-07 | Fujitsu Ltd | Design supporting device for software |
FR2684779B1 (en) * | 1991-12-06 | 1996-12-13 | Bull Sa | METHOD AND TOOL FOR CONCEPTUAL MODELING OF EXPERTISE ON A COMPUTER SYSTEM. |
US5310349A (en) * | 1992-04-30 | 1994-05-10 | Jostens Learning Corporation | Instructional management system |
FR2692055B1 (en) * | 1992-06-09 | 1996-10-25 | Bull Sa | DEVICE FOR DESIGNING INFORMATION CONTROL NETWORKS FOR MODELING ALL PROCESSES. |
US5664126A (en) * | 1992-07-24 | 1997-09-02 | Kabushiki Kaisha Toshiba | Human interface system for communicating networked users |
US5450540A (en) * | 1992-12-16 | 1995-09-12 | Apple Computer, Inc. | Graphical interface for interacting constrained actors |
US5630069A (en) * | 1993-01-15 | 1997-05-13 | Action Technologies, Inc. | Method and apparatus for creating workflow maps of business processes |
JP3201156B2 (en) * | 1993-08-30 | 2001-08-20 | トヨタ自動車株式会社 | Method and apparatus for assisting design |
US5552995A (en) * | 1993-11-24 | 1996-09-03 | The Trustees Of The Stevens Institute Of Technology | Concurrent engineering design tool and method |
US5657460A (en) * | 1995-04-11 | 1997-08-12 | Data View, Inc. | System and method for storing and displaying data |
-
1996
- 1996-01-25 US US08/591,920 patent/US5737727A/en not_active Expired - Lifetime
-
1997
- 1997-01-24 WO PCT/US1997/001208 patent/WO1997027557A1/en not_active Application Discontinuation
- 1997-01-24 AU AU17102/97A patent/AU706198B2/en not_active Ceased
- 1997-01-24 EP EP97903113A patent/EP0976073A1/en not_active Ceased
- 1997-01-24 CA CA002243830A patent/CA2243830A1/en not_active Abandoned
- 1997-01-24 JP JP9527048A patent/JP2000504131A/en active Pending
Also Published As
Publication number | Publication date |
---|---|
WO1997027557A1 (en) | 1997-07-31 |
AU1710297A (en) | 1997-08-20 |
EP0976073A1 (en) | 2000-02-02 |
US5737727A (en) | 1998-04-07 |
JP2000504131A (en) | 2000-04-04 |
AU706198B2 (en) | 1999-06-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2243830A1 (en) | Process management system and method | |
Davis | Business process modelling with ARIS: a practical guide | |
Ellis | Workflow technology | |
Ossher et al. | Flexible modeling tools for pre-requirements analysis: conceptual architecture and research challenges | |
Brown | HCI and requirements engineering-exploring human-computer interaction and software engineering methodologies for the creation of interactive software | |
Kuhn | Selecting and effectively using a computer aided software engineering tool | |
Ominsky et al. | User-centered design at IBM consulting | |
van de Weerd | Advancing in software product management: An incremental method engineering approach | |
Vega et al. | Towards a unified catalogue of non-technical quality attributes to support COTS-based systems lifecycle activities | |
Huertas et al. | Using model-based testing to reduce test automation technical debt: an industrial experience report | |
Zarour et al. | A framework to compare software process assessment methods dedicated to small and very small organizations | |
Kobayashi et al. | Workflow business template for application processes in administration department | |
Crozier et al. | Critical analysis of tools for computer-aided software engineering | |
Gross et al. | Problem dimensions in design of CSCW systems | |
Wamelink et al. | Workflow management in construction: opportunities for the future | |
Noack | Extending the software development process with a toolkit of UML-centred techniques | |
Clark | Analysis and comparison of various requirements management tools for use in the shipbuilding industry | |
Action | for 2003 | |
Callaghan et al. | Financial information systems: Teaching REA semantics within an information engineering framework | |
White et al. | Project Aurora: dawn of a new way | |
Preese et al. | The PLATO® courseware development environment | |
Sun et al. | Integrated Design System to Support Partnering Practice in the Water Industry | |
Aalto | Challenges in applying objects to large systems | |
Ett et al. | Evaluating the effectiveness of Process Weaver as a process management tool: a case study | |
Castela et al. | A Supporting Tool For Business Process Modeling |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
FZDE | Dead |