OPCAT: Object-Process CASE Tool

Slides:



Advertisements
Similar presentations
Integration of MBSE and Virtual Engineering for Detailed Design
Advertisements

Visual Model-based Software Development EUD-Net Workshop, Pisa, Italy September 23 rd, 2002 University of Paderborn Gregor Engels, Stefan Sauer University.
Realizing OPM Philosophy in the Context of Full Life- Cycle Support Avi Soffer Technion, Israel Institute of Technology Thesis Advisor: Prof. Dov Dori.
Object-Oriented Analysis and Design
ניתוח מערכות מידע 1 The basic premise of OPM is that objects and processes are two types of equally important classes of things, that together faithfully.
C++ Training Datascope Lawrence D’Antonio Lecture 11 UML.
© Copyright Eliyahu Brutman Programming Techniques Course.
Itntroduction to UML, page 1 Introduction to UML.
Ontologies Reasoning Components Agents Simulations Agent Modeling Language: An Overview Wendell Véras Vinícius Remígio Jacques Robin.
MCA –Software Engineering Kantipur City College. Topics include  Formal Methods Concept  Formal Specification Language Test plan creation Test-case.
Visualizing SISO Smackdown Scenario with OPM and HLA Israel Institute of Technology – Technion, 2012.
UML Class Diagrams: Basic Concepts. Objects –The purpose of class modeling is to describe objects. –An object is a concept, abstraction or thing that.
CASE Tools And Their Effect On Software Quality Peter Geddis – pxg07u.
UML Unified Modeling Language. What is UML? Unified Modeling Language (UML) is a standardized, general-purpose modeling language in the field of software.
Essence Duality Awareness in Information System Interaction with Physical and Cyber Environments Yaniv Mordecai, Technion, Haifa, Israel Prof. Dov Dori,
An Introduction to Software Architecture
Object Process Methodology OPM ד " ר אבי סופר. ניתוח מערכות מידע 2 OPM Basic Concepts Emphasis Equally balancing static (structure) and dynamic (behavior)
Odyssey A Reuse Environment based on Domain Models Prepared By: Mahmud Gabareen Eliad Cohen.
1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.
Lab 04.
1 Introduction to Software Engineering Lecture 1.
Lab 5 CPIT 250 System Analysis and Design.
Ch- 8. Class Diagrams Class diagrams are the most common diagram found in modeling object- oriented systems. Class diagrams are important not only for.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Object-Oriented Parsing and Transformation Kenneth Baclawski Northeastern University Scott A. DeLoach Air Force Institute of Technology Mieczyslaw Kokar.
Class Diagrams. Terms and Concepts A class diagram is a diagram that shows a set of classes, interfaces, and collaborations and their relationships.
McGraw-Hill/Irwin© 2008 The McGraw-Hill Companies, All Rights Reserved Chapter 17 Object-Oriented Design and Modeling Using the UML.
Software Engineering Lecture 10: System Engineering.
Visual Dynamic Model Inspecting with OPM Model- Based Simulation Environment Yevgeny Yaroker, Valeria Perelman, Prof. Dov Dori 18 March 2016.
ניתוח מערכות מידע ומבוא להנדסת תכנה 1 The basic premise of OPM is that objects and processes are two types of equally important classes of things, that.
Model Based Systems Engineering Visualization Steven Corns Missouri University of Science & Technology.
Introduction to UML and Rational Rose UML - Unified Modeling Language Rational Rose 98 - a GUI tool to systematically develop software through the following.
Smith’s Aerospace © P. Bailey & K. Vander Linden, 2006 Classes and Objects Patrick Bailey Keith Vander Linden Calvin College.
Defects of UML Yang Yichuan. For the Presentation Something you know Instead of lots of new stuff. Cases Instead of Concepts. Methodology instead of the.
Modeling with UML – Class Diagrams
OPCATeam OPM-based Collaborative Systems Modeling
CHAPTER
UML Diagrams By Daniel Damaris Novarianto S..
Chapter 1: Introduction to Systems Analysis and Design
SysML 2.0 Requirements for Visualization
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Object-Oriented Analysis and Design
SysML v2 Formalism: Requirements & Benefits
Systems Analysis and Design With UML 2
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Unified Modeling Language
Software Design Mr. Manoj Kumar Kar.
UML Diagrams Jung Woo.
The Process of Object Modeling
Object-Process Methodology (OPM): Language Principles and Vivid OPM: Model-Driven System Visualization at the The Enterprise Systems Modeling Laboratory.
Design your System with Object-Process Methodology – OPM
Complexity Management via OPM Built-In Mechanism: Theory & Practice
UML Class Diagrams: Basic Concepts
DoDAF 2.x Meta Model (DM2) Conceptual Level
Introduction to UML.
Chapter 20 Object-Oriented Analysis and Design
Object-Oriented Knowledge Representation
Software Construction Lecture 2
UML profiles.
An Introduction to Software Architecture
Chapter 9 Architectural Design.
Chapter 1: Introduction to Systems Analysis and Design
Requirements Modeling Framework
Chapter 1: Introduction to Systems Analysis and Design
UML  UML stands for Unified Modeling Language. It is a standard which is mainly used for creating object- oriented, meaningful documentation models for.
Modeling the involvement of Rpb4/7 in the mRNA biogenesis and degradation with Object-Process Methodology Dov Dori and Mordechai Choder Technion - Israel.
UML Design for an Automated Registration System
System Model Acquisition from Requirements Text
Software Architecture & Design
Presentation transcript:

OPCAT: Object-Process CASE Tool ICEIS 2003 Dov Dori Technion, Israel; MIT, USA www.ObjectProcess.org

Why Object-Process Methodology? As the complexity and interdisciplinary nature of systems increases, the need for a universal modeling, engineering, and lifecycle support approach becomes ever more essential. The complexity and software orientation of the current standard language calls for a simpler, formal, generic paradigm for systems development.

What is Object-Process Methodology (OPM)? A comprehensive systems modeling, engineering, and lifecycle support paradigm Two major features: Unification of function, structure and behavior in a single model Bi-modal expression of the model via intuitive yet formal graphics and equivalent natural language

The OPM Ontology: OPM Elements are Entities and Links Entity types: 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: 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 Elements: Entities and Links Entity types: 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: 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

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

Creating a new object: Result link

Consuming an existing object: Consumption link

Changing object state

States can be initial or final

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

Aggregation-participation A structural relation between the whole and its parts

Exhibition-characterization A structural relation between a thing and its features

Generalization-specialization A structural relation between a thing and its specializations (known as the “is-a” relation)

Classification-instantiation A structural relation between a thing and its instances

General tagged structural link A structural relation between two things whose semantics is expressed through its tag Bidirectional tagged structural link Unidirectional tagged structural link

Participation constraints Structural relation can be associated with various quantities

Syntax and Semantics Consistency Checking Trying to make a process part of an object results:

Procedural Links Enabling Links Transforming Links Agent link Instrument link Transforming Links result/consumption/input/output link Effect link

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

Agent Link

Instrument Link

Complexity Management The ability to trade off clarity and completeness: Clarity is the ability to clearly present and see the system’s structure and behavior 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: In-zooming/out-zooming Unfolding/folding State expression/state suppression

In-zooming Exposing the details inside a complex process

In-zooming The sub-processes of the Building process are depicted inside the in-zoomed process ellipse

Simulation by animation

Green objects already exist

Building started

Building in-zoomed

Foundation Constructing in-zoomed

Foundation Constructing in-zoomed

Certificate is being created

Foundations are being created, Holes and Concrete consumed

House ready, Raw Material gone

Summary OPCAT is suitable for Requirements elicitation and analysis System architecting and detailed design Collaboration among various stakeholders Simulation for testing and verification (operational) Code and database generation UML diagram generation (operational) Automatic documentation (operational)

Current OPCAT projects Universal code generator (operational) Groupware capability Automatic diagram layout Visual Semantic Web Pen input Voice input and output Interface to CAD and ERP Module creation and reuse Requirements elicitation and analysis System architecting and detailed design Collaboration among various stakeholders Simulation for testing and verification Code and database generation UML diagram generation Automatic documentation