Process management system and method5737727Abstract A process management system (10) for operating on a computer (102, 104, 106) includes a graphical user interface (14) for graphically presenting a process or a portion thereof to a user, a work element for graphically representing a task to be performed in the process, a work product for graphically representing a resultant product of performing a task, an agent for graphically representing an actor responsible for performing a task, and a link for graphically connecting the work element, work product, and agent indicative of inter-relationships therebetween. A knowledge repository (16) is further coupled to the computer for storing valuable information regarding the process. Claims What is claimed is: Description TECHNICAL FIELD OF THE INVENTION
______________________________________
PROCESS
ATTRIBUTE DESCRIPTION REQ TYPE
______________________________________
Name Long title of the process
Y A/N
Short Name
Short title of the process
Y A/N
Level Level in the Methodology Architec-
Y A/N
ture (e.g. Framework, Method, or
Process)
Status Indication of the degree of complete-
Y A/N
ness of the process
Organization
Name of the organization that owns
Y A/N
the definition of the process
Purpose List of objectives/reasons for using
Y A/N
this process
Description
Overview/definition of the process
A/N
Audience Description of the targeted audience
A/N
for this process
Context Brief description of how this process
A/N
fits interrelates with other
related material
Contact Where to go for additional informa-
A/N
tion
Benefits List of benefits of this process to
A/N
company and to the customer
Scope Brief description of the scope of the
A/N
process
Version/Release
Indication of the applicable version
A/N
and release
______________________________________
Note that a Help button, if clicked on, provides context-sensitive on-line help support to the user. FIG. 7 shows an exemplary dialog window for entering information on a work element, including name, short name, whether the work element is required or conditional, and additional textual information such as: purposes, conditions, guidelines, procedure, description, etc. Dialog windows for entering attributes or associated minor components, such as references, training, and techniques are further reachable by clicking on respective push buttons. The following table summarizes the exemplary information used to describe a work element. The IF SUMMARY column indicates whether the attribute is specified, can be rolled up from lower detailed level attributes, or can be derived.
__________________________________________________________________________
WORK ELEMENT
ATTRIBUTE
DESCRIPTION REQ
TYPE
IF SUMMARY
__________________________________________________________________________
Name Long title of the work element
Y A/N Specify
Short Name
Short title of the work element
A/N Specify
Level (NY)
Whether the work element is summary or detail (leaf)
Derived
Derive
Summary Type
Whether the work element summarizes its children
A/N Specify
(?) by function or flow (for summary elements only)
Alias List of customer/local aliases for the work element
A/N Specify
Purpose List of objectives/reasons for the work element
Y A/N Specify/Roll Up
Description
Short overview/definition of the work element
A/N Specify
Guideline
List of guidelines for performing the work element
A/N Specify
Critical Success
List of items that must be present for successful
A/N Specify/Roll Up
Factor completion of the work element
Procedure
List of steps required for completing the work
A/N N/A
element; describes the "how-to" or "step-by-step"
instructions (SEI) (for detail elements only)
Standards
List of specific standards considerations (e.g.
A/N Specify
Consideration
considerations to ensure CMM Level 2)
Required/
Whether the work element is required or conditional
Binary
Roll Up
Conditional
Condition
List of conditions under which the work element
A/N N/A
should be completed (for conditional elements only)
Entry Criteria
Conditions that must be met before the work element
Derived
Derive
(?) can be started (inputs in the proper status, agents
trained, task dependencies satisfied, etc.)
Exit Criteria (?)
Conditions expected upon completion of the work
Derived
Derive
element (outputs completed in the proper status;
procedure completed, agents' responsibilities
fulfilled, task dependencies satisfied, etc.)
User-defined
Attributes that can be assigned by the process author
A/N Specify
attributes (NY)
that are process specific (one to three available)
__________________________________________________________________________
FIG. 8 is an exemplary window for requesting information on a work product. The table below summarizes the information used to describe a work product.
__________________________________________________________________________
WORK PRODUCT
ATTRIBUTE
DESCRIPTION REQ
TYPE
IF SUMMARY
__________________________________________________________________________
Name Long title of the work product
Y A/N Specify
Short Name
Short title of the work product
A/N Specify
Level (NY)
Whether the work element is summary or detail (leaf)
Derived
Derive
Type The category of work product (e.g. decision,
A/N Specify/Roll Up
condition, document, individual, etc.)
Deliverable/Non-
Whether work product can be delivered to the
Binary
Specify/Roll Up
deliverable
customer
Internal/
Indication of whether this work product is internally
Binary
Specify/Roll Up
External
produced or externally supplied
Alias List of customer/local aliases for the work product
A/N Specify
Purpose List of objectives/reasons for the work product
Ynd
A/N Specify/Roll Up
the data represented by the work product
Description
Short overview/definition of the work product
A/N Specify
Guideline
List of format and content guidelines for the work
A/N Specify
product
Content List of the data contained in the work product with
A/N N/A
brief description of each
Standards
List of specific standards considerations (e.g.
A/N Specify
Consideration
considerations to ensure CMM Level 2)
User-defined
Attributes that can be assigned by the process author
A/N Specify
attributes (NY)
that are process specific (one to three available)
__________________________________________________________________________
The information used to describe an agent is summarized in the table below.
__________________________________________________________________________
AGENT
ATTRIBUTE
DESCRIPTION REQ
TYPE
IF SUMMARY
__________________________________________________________________________
Name Long title of the agent; participant's role (e.g.
Yroject
A/N Specify
manager, data base administrator, etc.)
Short Name
Short title of the agent; acceptable abbreviation
A/N Specify
Level (NY)
Whether the agent is summary or detail (leaf)
Derived
Derive
Alias List of customer/local aliases for the agent
A/N Specify
Description
Short overview/definition of the agent
A/N Specify
Competency
List of knowledge, skills and behaviors expected
A/N Specify
beneficial for performing in this role
User-defined
Attributes that can be assigned by the process author
A/N Specify
attributes (NY)
that are process specific (one to three available)
__________________________________________________________________________
Input/output is a link that connects work products and work elements. A work product is an input to a work element, and a work product can also be an output of a work element. The input/output information is shown in the tables below.
__________________________________________________________________________
ATTRIBUTE
DESCRIPTION REQ
TYPE
__________________________________________________________________________
INPUT
Status Degree of completeness Y A/N
Required/
Whether the work product is required as an input under
Yll
Binary
Conditional
conditions
Condition
List of conditions under which the input should be
A/Nected
(for conditional work products only)
OUTPUT
Status Degree of completeness Y A/N
Required/
Whether the work product is required as an output under
Yll
Binary
Conditional
conditions
Condition
List of conditions under which the output should be
A/Npleted
(for conditional work products only)
__________________________________________________________________________
The link between an agent and a work element is the responsibility connectivity. The information used to describe responsibility is listed in the table below and shown in an exemplary dialog screen in FIG. 10:
______________________________________
ATTRIBUTE DESCRIPTION REQ TYPE
______________________________________
RESPONSIBILITY
Type The responsibility/authority the
A/N
agent has for the work element
Skill Level
The degree of skill in this respon-
A/N
sibility the agent will require
(e.g. novice, intermediate, expert)
______________________________________
Minor components associated with responsibility, including training, tools, and techniques, may also be specified. When these minor components are selected, appropriate dialog windows pop up to receive information entered by the user/author in a similar manner, using some of the same graphical tools shown. The information associated with each minor component is shown in the tables below.
______________________________________
ATTRIBUTE
DESCRIPTION REQ TYPE
______________________________________
TOOL
Name Title of the tool Y A/N
Type Generalized type of tool A/N
(e.g. spreadsheet, word processor, etc.)
Description
Short overview/definition of the tool
Y A/N
Execution
Execution requirements for
Y
Information
launching the tool
TECHNIQUE
Name Title of the technique
Y A/N
Type Generalized type of technique
A/N
(e.g. modeling, prioritization, etc.)
Description
Short overview/definition/
Y A/N
abstract of the technique
Execution
Executable file/directory instructions for
Y
Information
launching the associated tool
TEMPLATE
Name Title of the template
Y A/N
Explanation
Brief description to make the
A/N
template clear and understandable
Execution
Executable file/directory and execution
Y
Information
instructions for launching the
associated tool
EXAMPLE
Name Name of the example Y A/N
Explanation
Brief description to make the
A/N
example clear and understandable
Execution
Executable file/directory and execution
Y
Information
instructions for launching the
associated tool
REFERENCE
Name Short identifier of the reference item
A/N
Description
Due to the various pieces and formats
A/N
of bibliographic entries the following
represents suggestions for the content
of an entry
Publication
Name of the book, A/N
Volume or
Volume or date of A/N
version periodical, or version
of the book/document
Source Body, organization, or
A/N
publisher which provided
or published the material
Article Title of the article or
A/N
section referenced
Author Author(s) of the book,
A/N
article or other
publication
Content Brief description or key
A/N
words for the content of
the material
Execution
Executable file/directory and execution
Information
instructions for launching the
associated tool
TRAINING
Name Title or name of the training course
Y A/N
of material
Purpose List of learning objectives for the
A/N
training course or material
Description
Summary/synopsis of the content of the
A/N
course or material
Provider Company or organization that provides
Y A/N
the training course or material
Contact Directions for ordering, enrollment,
A/N
or requesting more information about
the course of material
Execution
Executable file/directory and execution
Information
instructions for launching the
associated tool
POLICY
Name Short description of the policy; policy
Y A/N
provides the law or regulations that
govern, guide, or constrain
operations (SEI)
Type Functional grouping A/N
Statement
Policy statement Y A/N
Execution
Executable file/directory and execution
Y
Information
instrutions for launching the
associated tool
STANDARD
Name Short description of the standard;
Y A/N
standard provides the operational
definitions or acceptance criteria for
final or interim products
or process (SEI)
Type Functional grouping A/N
Statement
Standard statement Y A/N
Execution
Executable file/directory and execution
Y
Information
instructions for launching the
associated tool
______________________________________
It must be noted that the exemplary screens shown in FIGS. 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. FIG. 11 is an exemplary screen showing a bug correction process. A hierarchies window is to the left of the process window, which displays a graphical representation of the process. The hierarchies window currently shows the work element hierarchy, but may be changed to show agent or work product hierarchies of the process by clicking on the appropriate buttons immediately above the window. Those entries with a square icon appearing to the left of the text indicates that these elements are expandable and the user may drill down to a lower level. These expandable elements, for example "fix the bug" and "close", are shown in the graphical window with a shadow. The process window contains the graphical depiction of a process or a portion of a process. Process windows contain agents, work elements, work products, and any connections therebetween. Every image in a process window is a selectable object that has properties associated therewith. Summary work elements shown as a work element with a shadow represent the existence of additional details in the form of another process window that can be reached by drilling down or double clicking on the work element. In this manner, complex processes may be organized into multiple levels of abstraction to facilitate the presentation and understanding thereof. A customized tool bar is further provided to permit the user to select operations such as open file, close file, save file, print, and to further select icons for the work element, work product, agent, and links therebetween to build or modify the displayed process. The graphical display may be easily manipulated, for example, the size and location of the windows can be adjusted by clicking and dragging on the window or window boundaries, or the windows may be made to be cascaded, overlapped, or tiled. It may be instructional to walk through the bug correction process to show how a process is represented. A developer 60 is responsible for (link 61) changing the bug status 62 in a piece of software. The work product of changing the bug status is a bug report 63 and a bug tracking database 64. The next task, fix the bug 65, is also recorded and documented in a bug report 66. The link between fix the bug 65 and test the fix 66 is iterative, because the first few attempts at fixing the bug may not succeed. The software (PS Application) 67 is the work product of testing the fix, if successful. If the bug fix is successful, the task close 68 is performed. Because work element close 68 is shown with a shadow, more process details exist and the work element may be expanded to drill down to the next level of details, as shown in FIG. 12. The close sub-process shown in FIG. 12 displays three tasks: check in files 71, update library files 72, and close out bug 73. The associated agents and work products of these work elements are shown. It may be seen that all work elements within a process are unique regardless of whether the name and short names are the same. Unlike work elements, agents and work products in a process that have the same name and short names are the same entity. Therefore, all bug reports and all agents in the bug correction process are the same respective entities. Referring to FIGS. 13 and 14, dialog windows displaying details of the developer agent and the bug report work product are shown overlaid on top of the process graphical representation. Any agent, work product, and work element defined in the process may be clicked on and details thereof may be displayed in like manner. FIG. 15 illustrates the distributed manner in which the instant system 10 may operate. Process management system 10 may be run on a stand alone personal computer or work station, or on one or more computers 102-106 that are linked together by a computer network 110. Information that can be shared by many users may be stored on a common database 108, which may also be linked by computer network 110. Operating in this manner, members of an engineering team may independently access and consult a process the team is working on. System 10 further provides an export capability which produces files in several formats compatible with different applications. For example, Common-Separated Values formatted files may be exported to spreadsheet and database applications to generate statistical information on a process. Microsoft Project Exchange formatted files can also be produced and exported to most project management tools for project management. Constructed in this manner, a process may be defined on process management system 10 easily and efficiently. Existing processes may also be easily revised and modified. System 10 displays the defined process in a graphical manner, which aids in the comprehension and management of the process. Knowledge accumulated from past experiences are also accessible by multiple users for reuse. For example, a company may distribute general processes that can then be customized to fit the special needs of individual organizations within the company. In this manner, existing processes may be reused and tailored to each new process without reinvestment of efforts. Through the use of system 10, company processes may be easily standardized with common terms and definitions. Furthermore, the number of levels of process details is unlimited in system 10, enabling complex processes to be represented in an uncluttered manner. 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.
|
Same subclass Same class Consider this |
||||||||||
