5 comments about Object-Process Methodology.

1. I have been fascinated by the simplicity and usefulness of the
   Object-Process Methodology paradigm and approach expressed in the book. As a
   researcher in Science Education I have been grappling with how to represent
   complex, technology-enhanced educational systems that involve humans,
   processes and educational artifacts. OPM and the OPCAT software enclosed
   were very instrumental in enabling me to model and represent the "big
   picture" of educational systems I developed. With OPM I was then able to
   gradually refine portions of the system to any desired level of detail.
   The applicability of OPM to IT-intensive educational systems is a testimony
   to the generic nature of the methodology and to the fact that it is useful
   in so many domains. The combination of a single simple graphical model that
   generates natural language on the fly is really unique and valuable. I
   wholeheartedly recommend the book to anyone interested in modeling complex
   systems, be they of technological, economical, or social nature. The method
   is straightforward, easy to learn even for non IT-professionals, and most
   rewarding in terms of the quality and clarity of the resulting graphical and
   textual model.



2. 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.



3. 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.




4. 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.




5. 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.
   
   Finally, this methodology is fast. It is just easier and more intuitive to model in an OPM fashion. I've also found that others can comprehend the OPM models better than other methodologies too.
   
   I used to be a UML advocate until I found OPM. I have found concepts that are difficult to model in UML are quite easy to model in OPM. It is just more flexible.
   
   The book is really good by the way. It is very complete and gives plenty of good exammples. I congratulate Dov Dori and his team for providing something that all engineering disciplines can use to design their systems.

No comments about Automotive Paints and Coatings.

1 comments about Statistical Methods for Six Sigma: In R&D and Manufacturing.

1. I WAS LOOKING FOR A BOOK TO USE AS A MFG/DESIGN ENG FOR QUICK REFERENCE TO COMMONLY USED METHODS, GAGE R&RS, POPULATION COMPARISONS, STATISTICAL SIGNIFICANTS, THIS BOOK DOES IT. VERY CONCISE AND WELL THOUGHT OUT.

1 comments about Hydraulics for Firefighting.

1. I needed this text for a course I'm taking to complete my degree in Fire Science Management. Aside from one minor formula discrepancy, the information is thorough and extensive. Not only are formulas provided, they are simplified as much as possible for ease in calculation. Formulas are provided for anything and everything you'd ever want or need to calculate concerning hydraulics for firefighting. It is a great text and will become a handy reference.

No comments about Drug-Induced Mitochondrial Dysfunction.

No comments about 2006 Significant Changes to the International Residential Code.

2 comments about Rf Power Amplifiers.

1. I am a student of the university of technology. This book helped me to understant design RF power amplifiers. It contains many practical examples in each chapter so you can try if you realy understant actual topic. After I've read a half of this book I was able to build a realy function class A amplifier.
   Using a simulation program (like PSpice) is also very helpful.
   I thing this is a good book for students with basic scope of transitor and RF circuity.



2. Excellent book with detailed treatment of the various amplifier classes `other than A & AB' with extensive tips for tuning & stability/prevention of oscillations, detailed survey & discussion of the various input & output matching transformers, baluns & resonant circuits. Excellent references (many from industry app notes & amateur radio - demonstrating the practical bent of the book) & bibliographies at the end of each chapter are almost worth the price alone. Excellent `pro & con' and `tips' summaries. Grebennikov more analytical and not as much detail in differentiating between the various classes, esp. the pitfalls & difficulties/limiting factors. A sort of updated & expanded Kraus/Bostian/Raab!

No comments about Computer Confluence IT Edition.

1 comments about Practical Process Research & Development.

1. If you ever wonder how to run your reaction on a three tons scale, this is one of the books to go for. On the top it is also real fun to read.

No comments about Advanced Batteries: Materials Science Aspects.