Product Lifecycle Engineering with ObjectProcess Methodology January 2005

Product Lifecycle Engineering with Object-Process Methodology January 2005 Dov Dori Technion, Israel; MIT, USA www. Object. Process. org

What is Object-Process Methodology? A comprehensive paradigm for l l l modeling, engineering, and lifecycle support of complex, multi-disciplinary systems

Why Object-Process Methodology? l Systems are becoming more Complex l Interdisciplinary l l This calls for a generic universal modeling approach for Modeling l Engineering l Lifecycle support l

: Two major OPM features l Unification of: l function, l Structure, and l behavior in a single model l Bi-modal expression of the model via l intuitive yet formal graphics, and l equivalent natural language

OPM Evolution l Covers function, structure and behavior of systems that involve: l l l l l hardware, software, regulations, humans Based on theory & experiments Twelve years under development Taught at leading academic institutions Industrial users Under commercialization

Resources: OPM book Dov Dori, Object-Process Methodology - A Holistic Systems Paradigm, Springer Verlag, Berlin, Heidelberg, New York, 2002 (ISBN 3 -540 -65471 -2; Foreword by Edward Crawley. Hard cover, 453 pages, with CD-ROM).

Resources: OPM Website

OPM Bi-modal Representation A single diagramming tool: Object-Process Diagram (OPD) A corresponding subset of language: Object. Process Language (OPL)

Objects and Processes • Objects and processes are two types of • • • equally important things (entities) required to describe a system in a single, unifying model At any point in time, each object is at some state Object states are transformed through the occurrence of a process Complexity is controlled through recursive and selective scaling (zooming) of objects and/or processes to any desired level of details

The OPM Ontology: OPM Elements are Entities and Links l Entity types: l l Object: A thing that exists for some time State: A situation at which an object can be Process: A thing that transforms an object Link types: l l Structural link: A link denoting a persistent relation between objects Procedural link: A link between a process and the object it transforms or a state of that object

OPM’s Building Blocks are Things: Objects and Processes Object Process

States are situations of objects

A process changes an object state

A process generates a new object

Combining Behavior with Structure

Object Essence l Can be informatical (default) or physical Object-Process Diagram (OPD) Object-Process Language (OPL) sentence(s)

Object Affiliation l Can be systemic (the default) or environmental

Thing / Attribute Object Symbol Description / OPL sentence A thing (entity) that has the potential of stable, unconditional physical or mental existence. Object Name is an object. Process A thing representing a pattern of transformation that objects undergo. Processing is a process. Essence An attribute that determines whether the thing (object or process) is physical (shaded) or informational. Processing is physical. Affiliation An attribute that determines whether the thing is environmental (external to the system, dashed contour) or systemic. Processing is environmental.

Top-level view (System Diagram, SD) of the Product Lifecycle Engineering system

Top-level view (System Diagram, SD) of the Product Lifecycle Engineering system Object-Process Diagram (OPD) OPD hierarchy view Object-Process Language (OPL) paragraph

Product Lifecycle Engineering system: OPL paragraph Product is physical. Product can be approved, distributed, used, pre-tested, rejected, stored, sold, or retired. pre-tested is initial. retired is final. Product is made of Raw Material. Product benefits User. Manufacturer is physical. Manufacturer makes & supports Product. Environment is environmental and physical. Environment consists of User, Market Demand, Raw Material, Technology, and Competition. User is environmental and physical. Market Demand is environmental. Raw Material is environmental and physical. Technology is environmental. Competition is environmental. Product Lifecycle Engineering is physical. Product Lifecycle Engineering requires Environment. Product Lifecycle Engineering affects Product, User, and Manufacturer.

OPM Elements: Entities and Links l Entity types: l l Object: A thing that exists for some time State: A situation at which an object can be Process: A thing that transforms an object Link types: l l Structural link: A link denoting a persistent relation between objects Procedural link: A link between a process and the object it transforms or a state of that object

Complexity Management l l The ability to trade off clarity and completeness: l Clarity is the ability to clearly present and see the system’s structure and behavior l Completeness is the extent to which all the details of the system are specified These two model attributes necessarily contradict each other

Complexity Management in OPM Three refinement/abstraction mechanisms: l In-zooming/out-zooming l Unfolding/folding l State expression/state suppression

Zooming into the Product Lifecycle Engineering process All procedural link types are seen

Processes transform objects l Three transformation options: Change an object state l Create (generate) a new object l Consume (destroy) an existing object l

Zooming into Design

Zooming into Manufacturing

Zooming into Assembly & Testing

Enabling Links l Link objects that enable the process but are not transformed by it l Agent link Links a human or a group of humans that trigger the process or participate in it l Instrument link Links a non-human object that the process requires in order for it to occur or execute

Zooming into Commerce

Structural Links l Fundamental Structural Links Aggregation-participation l Exhibition-characterization l Generalization-specialization l Classification-instantiation l l General tagged structural links

Zooming into End-Of-Life

Zooming into Making (within Manufacturing)

Zooming into Software Module Developing (within Making)

Unfolding of Initial Shaping (within Making)

Summary l OPM supports product and syste lifecycle engineering as it is suitable for: Requirements elicitation and analysis l System architecting and detailed design l Collaboration among various stakeholders l Simulation for testing and verification l Code and database generation l UML diagram generation Automatic documentation l

Example: The carbon cycle Object-Process Diagram (OPD) Object-Process Language (OPL) paragraph

Carbon cycle: The OPL script Object-Process Language (OPL) paragraph