|
Object-Process Methodology
 |
Author: Dov Dori
List Price: $49.95
Our Price: Click to see the latest and low price
ISBN: 3540654712
Publisher: Springer Verlag (17 August, 2002)
Edition: Hardcover
Sales Rank: 433,490
Average Customer Rating: 5 out of 5
|
Customer ReviewsRating: 5 out of 5
The way modeling ought to work
OPM is a methodology for modeling systems, technical as well as any other system. In the techical world it compares with UML. OPM is designed with consistant and simple notations, uses simple rules that when combined can be used to model any system (real or informational) to any level of complexity that is desired by the system architect. Also, it integrates object modeling and process modeling in one diagram (although you can still keep them separate if you wanted). UML uses complex rules to model complex systems, something that is very difficult to make happen, therefore it is very difficult to learn and use. OPM uses simple rules and consistant notations to model complex systems. After simple introductions to the methology, we have been able to start using it in our organization. More powerful and far simpler then UML. The way UML should have been done long time ago.
Rating: 5 out of 5
Object-Process Methodology (OPM)
This book describes how Object-Process Methodology (OPM) CASE can be used as a tool for generating complete system intent specifications by graphical object diagrams, precise semantic and syntactic language, and intuitive symbols, definitions and structures. As systems have become more complex, a prevalent problem in systems development has been the number of accruing errors. These errors can cause catastrophic failure in the worst-case in addition to intolerable schedule delays and cost overruns. Introducing errors as well as difficulty finding and successfully correcting them occurs because of the lack of proper analysis and design tools for complex system specifications. OPM has the attributes to mitigate against the possibility of system failure, providing comprehensive visibility for better schedule and cost control in product development. It enhances reuse of system modules, processes and software routines in different contexts, while reducing the chance of errors. OPM automatically generates intent specifications that are readily understood by both customers and product team members and are translatable to machine control subsystems. OPM is a holistic systems paradigm that extends the Object-Oriented (OO) paradigm and overcomes its major shortcomings by integrating system structure and behavior in a single integrated graphic and natural language model. OPM successfully tackles the task of development and lifecycle management of systems, products and projects. OPM is a significant extension of and a major departure from the OO approach. It incorporates the system static-structural and dynamic-procedural aspects into a single, unified model. Presented as a concise visual formalism by a set of Object-Process Diagrams (OPD set), it is automatically translated into a set of Object-Process Language (OPL) script, a subset of natural English. At the basis of the OPM philosophy is the observation that to faithfully and naturally analyze and design systems in any domain, processes, like objects, should be considered as stand-alone "things" (entities) that are not necessarily encapsulated within objects. This detachment and de-coupling of processes from objects emphasizes the duality and complementarity of objects and processes, and opens the door for structure-behavior unification. At any point in time, objects exist with some structure and state. This is the static aspect of the system. Processes affect objects by changing their states. This is the dynamic aspect of the system. System complexity is managed through a number of graphical scaling options: zooming into and out of processes, unfolding and folding objects, and expressing or suppressing object states. These mechanisms provide for selectively detailing a subset of things while still maintaining the high-level context of the details.OPM provides a new framework for specifying design intents and capturing the complexity of hardware and software interaction. Through OPL, it is possible to translate the process into a machine executable code. In addition, OPM can capture the dynamic behavior of the hardware attributes and software states in a single integrated graphical and textual language that is understandable by domain experts who have no programming experience. These traits of OPM ease the development effort for evaluating the system reliability during the design stages. Simulation and testing protocols can be automatically generated though future extensions of OPM to reduce lengthy system verification efforts.
The main benefit of OPM is its ability to identify system objects, processes, and the relationships among them in a structured way. The resulting OPD set becomes an excellent framework for identifying how to implement structural and procedural improvements. The resulting OPL script provides a well-defined set of existing and future specifications for the system. The ability to freely switch from text to graphics and back is of great value to understanding the system as a whole with a single graphic and textual model, without the need to consult various models and carry out mental transformation among these various models.
Based on my personal experience, the following points highlight the benefits OPM can bring to the particular projects described in this paper.
1.OPM is an excellent way to represent daily activities, products, processes and other complex things
2.OPM has allowed representing the complete system with its various aspects in a single model. The model specifies the systems function, structure and behavior aspects without sacrificing clarity.
3.OPM can be used as a common language to exchange design among members of a team.
4.Since OPM design is visual and textual at the same time, it is easy to explain the design.
5.OPL is very easy to generate from OPD
6.OPM will be a good tool for documenting the existing processes and as ISO documentation.
Rating: 5 out of 5
OPM: Finally a universal tool for system architects
There is an eternal debate between system designers
and architects of software, products and large systems:
Is it ever possible to show structure (the arrangement
of objects) and system behavior (over time) in the same
representation? Dov Dori's book shows convincingly that it can
be done. Particularly powerful is the duality between
graphical system representation and natural language.
Also, the CD-ROM with OPCAT software allows one to follow
the examples in the book and apply OPM directly to a project.
The book is clearly written and will appeal to engineers,
computer scientists and software developers. A refreshing
contrast to the traditional way of looking a object-centered
systems architecting. This begs for more ... in terms of
connecting OPM to other tools such as Design Structure Matrices,
but also for representing highly complex systems over >2 levels
of decomposition.
Similar Products
· Information Modeling and Relational Databases: From Conceptual Analysis to Logical Design
· Design Patterns
|
