PRODUCTS
What
is OPM?
Object-Process Methodology (OPM) is a comprehensive approach to
conceptual modeling for system development, evolution, and lifecycle
support. OPM incorporates the static-structural and
dynamic-procedural aspects of a system into a single unifying model.
OPM features a clear, compact, and concise set of symbols that form
a language for expressing the system's building blocks and how they
relate to each other both structurally and dynamically.
OPM represents the two things that are inherent in a system: its
objects and its processes. Objects are what a system or product is,
and they may have states. Processes express what a system does—how
it transforms the objects, where transformation means generation of
new objects, consumption of existing objects, or change of their
state. The OPM model shows the structural relation and procedural
links between the system's building blocks at any needed level of
detail. The single model provides for clear and expressive animated
simulation of the OPM model, which greatly facilitates design-level
debugging.
OPM has another fundamental advantage: it represents the system
simultaneously in both graphics and a (subset of) natural language.
The two representations are completely interchangeable and convey
the same information in cognitively complementary modes. The
advantage in this approach lies in appreciating the human limitation
to the understanding of complexity. As systems become more complex,
the primary barrier to success is the ability of the human systems
engineers, architects, analysts, and designers to understand the
inherent complexity of the interrelationships. By representing the
system in both textual and graphical form, the power of "both sides
of the brain"—the visual interpreter and the language interpreter—is
engaged.
For additional information please contact
consulting@opcat.com
What is OPCAT?
|
Key Benefits
“I have used many methodologies over my
career. Most of them are based around the object-oriented and
structured design paradigms. I found out about OPM quite by
accident about a year ago. I've been using it ever since. I have
used it to model both hardware and software systems, as well as
for business process modeling. It is an excellent methodology
and I recommend it for anyone developing any kind of system.
One of the nice things about OPM is that it is easy: I was able
to get a team "up-and-running" with the methodology in less than
an hour of teaching them some basic concepts (try doing that
with UML). Another feature is that you can use this for any type
of project; you are not locked into a structured or
object-oriented mindset like structured analysis or UML. OPM can
handle both types of concepts with ease.”
What readers think about OPM?
|
