1 / 34

Visualizing SISO Smackdown Scenario with OPM and HLA

Visualizing SISO Smackdown Scenario with OPM and HLA. Israel Institute of Technology – Technion, 2012. 2. Technology: Object Process Methodology (OPM) Modeling for Development of HLA Simulations. Products:. • Model Generated BOM/HLA Products Procedure

yazid
Download Presentation

Visualizing SISO Smackdown Scenario with OPM and HLA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Visualizing SISO Smackdown Scenario with OPM and HLA Israel Institute of Technology – Technion, 2012

  2. 2 Technology:Object Process Methodology (OPM) Modeling for Development of HLA Simulations Products: • • Model Generated BOM/HLA Products Procedure • • Model Based Simulation Scenario Development Applicability: Sim of Lunar Exploration Architectures

  3. 3 OPM-BOM Translation

  4. 4 Introduction • The BOM generation analysis focused on two variations of object models: • Object Process Methodology (OPM) and • Base Object Model (BOM) • The aim is to develop and implement rules of mapping from OPM to BOM. • The staff: • Mr. David Howes, former NASA engineer (USA). • Prof. Dov Dori, supervisor of the project. • Mr. Sergey N. Bolshchikov, graduate student of Information Systems • Mr. Noam Shmueli, graduate student of Information Systems • Mrs. Michal Ezion, student of Information Systems • Mrs. Hadar Bibi, student of Information Systems

  5. 5 Short OPM description • The OPM model consists of a set of: • Object Process Diagram (OPD set) and a corresponding • Object Process Language (OPL text). • The OPL sentence generated in response to the model. • The root diagram is the most abstract level called: • System Diagram (SD) • The OPDs in the OPD set are hierarchical by construction via recursively zooming into process(es) of interest. • Each is a refinement of its ancestor.

  6. 6 Example OPM SD0: Meal preparing

  7. 7 SD1: Meal preparing in zoomed

  8. 8 OPM components • OPM Entities • The bricks: Things and States • Object: a thing that exist or might exist. • Process: a thing that happens to an object and transforms it. • OPM Links • Structural Link: • specifies a static, time-independent, long-lasting aspect of the system. • Connect two objects or two processes. • Procedural Link – Enabling or Transforming Link: • specifies a procedural, behavioral, time-dependent, or dynamic • aspect of the system. • Connect an object and a process.

  9. 9 OPM- Entities

  10. 10 OPM- Structural Links

  11. 11 OPM-Procedural Transforming Links

  12. 12 OPM-Procedural Enabling Links

  13. 13 OPM- Procedural Control Links

  14. 14 To develop and implement a correct mapping mechanism between OPM and BOM for High-Level Architecture utilizing. Goal • We focus on four tables related to Conceptual Model Definition: • 1. Pattern of Interplay • provides a mechanism for identifying sequences of pattern actions. • 2. State Machine • provides a mechanism for identifying the behavior states expected to be exhibited by one or more conceptual entities. • 3. Entity Type • provides a mechanism for describing the types of conceptual entities used to represent senders and receivers. • 4. Event Type • provides a mechanism for describing the types of conceptual events.

  15. 15 Description • The work was performed in four Steps: • Learn OPM: • We took two courses on OPM: Specification and Analysis of Information Systems and Methodologies in Information Systems Development. • Learn BOM: • We studied the BOM template specification, Prepared by SISO Base Object Model Product Development Group. • Develop the mapping rules: • We analyzed the OPM diagram bottom up– from the leaves to the tree root. We matched the OPM components and OPM rules to those in the BOM, by analyzing parallels between OPM entities and links and the four BOM’s tables. • Implementation Logic: • We transformed OPM XML representation to data structure of graph in Python code. • We applied the rules on the graph representation and supply the BOM tables, again in Python code. • We transformed the BOM tables into BOM XML representation.

  16. 16 Agent/ instrument link Sub Process name of leaf Process name of leaf Result link OPM-BOM Translation Example A process is a thing that transforms an object. Anagent link is a procedural link that connects a process with an human enabler of that process but is not (significantly) affected by it. An instrument link is a procedural link that needed for the process to happen, but it is not transformed by the occurrence of this process. A result link is a transformation link that connects a process with an object that yield it.

  17. 17 Consumption/ Effect link State associated with condition/ event link Object associated with condition /event Link Invocation link A consumption link is a transformation link that connects a process with an object and consume it. An effect link isa bidirectional arrow, between the affecting (state-changing) process and the affected object—the object whose state has changed as a result of the process occurrence. An invocation link is a direct link between an invoking process and an invoked one, where the object created by the former process triggers and is immediately consumed by the latter. An event link is a procedural link from a triggering object or object state to the triggered process. A condition link is akin to an "if…then" command: If a condition link originates from the state, the semantics is "do if.” A condition link is akin to an "if…then" command: If the object is at the state from which the condition link originates, then execution of the target process

  18. 18 Mapping Table - Pattern of Interplay

  19. 19 Pattern of Interplay • Notes: • We do not produce variants. Possible to do with process inheritance. • We do not produce exceptions since OPM defines time exceptions that are not BOM exceptions. • Exception: • If the sub process is connected to an attribute, then this is not a sender. • Solution: we navigate to the object that exhibits the attribute and make it a sender.

  20. 20 Process with Result Link Object State Object State Object Name An object is a thing that exists or might exist A state is a possible situation or position at which an object can be or a value it can assume for some positive amount of time. A result link is a transformation link that connects a process with an object that yield it.

  21. 21 Mapping Table – State Machine Note: Exit Condition consists of Exit Action and Next State. Assume that changing of object state is done by only one process. In other words, changing from state 1 to state 2 is done by process A, changing from state 2 to state 3 is done by process B and so on.

  22. 22 Object attributes (Exhibition / Aggregation) Object states Object Exhibition-Characterization, which denotes the relation between an exhibitor—a thing exhibiting a one or more features (attributes and/or operations) and the things that characterize the exhibitor. Aggregation-Participation, which denotes the relation between a whole and its parts.

  23. 23 Mapping Table - Entity Type

  24. 24 Process Name of leaf Consumption Event Link Instrument Event Link Agent Link Result Link Effect Link Instrument Link An instrument event link is a combination of an instrument link and event link. Being an event link, it triggers a process. Being an instrument link, it leaves the triggering object unchanged. A consumption event link is a combination of an event link and a consumption link. Being an event link, it triggers a process Being a consumptionlink, it indicates the (conditional) consumption of the triggering object

  25. 25 Mapping Table - Event Type

  26. 26 BOM Generation Analysis Summary and Future Work • The initial work of translating Object-Process Methodology into Base Object Model for High-Level Architecture translates OPM Diagram into 4 main BOM tables – Pattern of Interplay, State Machine, Entity Type, and Event Type – with certain limitations. • The future work includes reducing translation limitations; translating OPM into more BOM tables; support of BOM federation.

  27. 27 OPM Scenario Model

  28. 28 28 Rationale for Model Based Sim Scenario Development • A conceptual “architecture” for a sim is usually power point based, leaving a concept details gap before more detailed studies commence • A model based sim concept definition builds a basis for following studies upon a conceptual model of the goals of the simulation with its objects and their behavior • The model is developed top - down with increasing levels of detail, providing a structured, orderly development • Two models are developed: • Design model - no HLA details • Implementation model - with real time and HLA details

  29. 29 OPM Model Based Scenario Development Features • The model provides a top-down description of the scenario’s structure and behavior • The model includes real-time representations • Necessary conditions for an activity are explicit • The model can also provide an HLA oriented representation of the simulation as opposed to just a system only representation • Element processes in the OPM model corresponds to element software modules • OPM has one model diagram type with dual cognitive representation

  30. 30 OPM System (Context) Diagram

  31. 31 Lunar Mining and Transporting In-zoom OPM symbology provided in the appendix

  32. An Example HLA Implementation in an OPM Model • This is a model fragment for a cargo transfer from the Lunar Transfer Vehicle to the Lunar Shuttle • The raising of an interaction for the transfer is represented • The TV Docked Interacting process changes the vehicle states and triggers the interaction

  33. Model Equivalent Text This textual representation of the cargo transfer model provides cognitive based crosscheck on developing the model TV Docked Interaction triggers LS Cargo Transferring Action.Sim Transfer Vehicle is a Transfer Vehicle.Sim Transfer Vehicle can be undocked, Docked, hasCargo, or noCargo.Sim Transfer Vehicle exhibits TV Cargo Weight.TV Cargo Weight can be xxxx or 0.Sim Transfer Vehicle triggers TV Docked Interacting when it enters Docked.Sim Lunar Shuttle is a Lunar Shuttle.Sim Lunar Shuttle can be undocked, docked, noCargo, or hasCargo.Sim Lunar Shuttle exhibits LS Cargo Weight.LS Cargo Weight can be 0 or xxxxx.Sim Lunar Shuttle triggers TV Docked Interacting when it enters docked.TV Docked Interacting requires DockedSim Transfer Vehicle and dockedSim Lunar Shuttle.TV Docked Interacting changes Sim Lunar Shuttle from noCargo to hasCargo, Sim Lunar Shuttle from noCargo to docked, Sim Lunar Shuttle from undocked to hasCargo, Sim Lunar Shuttle from undocked to docked, Sim Transfer Vehicle from hasCargo to noCargo, Sim Transfer Vehicle from hasCargo to Docked, Sim Transfer Vehicle from undocked to noCargo, and Sim Transfer Vehicle from undocked to Docked.TV Docked Interacting yields TV Docked Interaction.LS Cargo Transferring Action requires TV Docked Interaction.LS Cargo Transferring Action changes LS Cargo Weight from 0 to xxxxx and TV Cargo Weight from xxxx to 0.

  34. 32 32 Scenario Products Developed • Detailed outline of a scenario for a Lunar mining mission • Used for developing consensus on mission activities • OPM scenario design model down to first level of interplay among mission elements • Developed to identify element modes, commands, and states which would support element interactions • Protocol communication model for Lunar orbiting communications satellite • Sub-model to develop agreement on a communications protocol

More Related