Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Object-Oriented Proposal and Process Design Methodology Utilizing CASE Tools

IP.com Disclosure Number: IPCOM000112033D
Original Publication Date: 1994-Apr-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 4 page(s) / 201K

Publishing Venue

IBM

Related People

Morgan, JG: AUTHOR [+2]

Abstract

This disclosure outlines a methodology which will enable multi-disciplined organizations to diagram and analyze their business processes and information and to correlate them to the contractual customer requirements. This disclosure also recommends methods in which these business processes may be cut and pasted in order to develop process "what if" scenarios.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 30% of the total text.

Object-Oriented Proposal and Process Design Methodology Utilizing
CASE Tools

      This disclosure outlines a methodology which will enable
multi-disciplined organizations to diagram and analyze their business
processes and information and to correlate them to the contractual
customer requirements.  This disclosure also recommends methods in
which these business processes may be cut and pasted in order to
develop process "what if" scenarios.

      Currently, organizational processes are developed using a
non-CASE tool like text-based (Word Processors) or a graphically
based (Lotus Freelance) tool and then filed in notebooks.  In order
to perform normal process maintenance and updates, the notebook-type
system files must be mechanically reviewed in order to determine the
effect the changes have on the organization.  This Process Of Process
Improvement (POPI) could take months because change analysis is done
by hand by going through all notebooks and determining what the
effects may be.

      When new requirements or a Request For Proposal (RFP) is
requested, the organization must again develop their inputs based on
these notebooks.  This has been an acceptable method in the past
because most contracts require the use of all the processes that the
organization was chartered for; however, in today's environment, it
is not always the case that RFPs will require the entire use of all
the organizational processes and therefore the organization will have
to pick and choose processes from the notebook.  This pick-and-choose
process in a non-CASE tool environment could result in data and
processes to be misused unless labor intensive care is taken.  This
is because the information in these notebooks does not lend itself
well to analysis and the ability to automatically browse through the
processes and to pick and choose what is needed and what may be left
out.  Also, when process research is required to build customer
requirement matrices, the information must be hand-selected and
reentered into a spreadsheet and then analyzed for compliance.  This,
too, is very time consuming and prone to errors.

      In order to solve these problems, new technologies must be
employed that effectively integrate processes, data, and the
requirements that govern their use.  Also, the technology must allow
for rapid information analysis as well as support cut and paste so
that new process flows may be developed and analyzed before they are
actually tried in real use.  The new technology is the use of CASE
tools in a novel fashion, not to develop software as originally
intended, but to develop, maintain, and experiment with
organizational processes and data.

      To demonstrate the effectiveness of using CASE tools for
process development, a pilot process model was developed using the
Excelerator (Intersolve Corporation) CASE tool to diagram the
Software Quality Assurance (SQA) Processes and their requirements.
The intent of the model...