Interface Driven Risk Modeling - Technion

Interface

Driven Risk

Modeling Yaniv Mordecai

March 2012

Interface Driven Risk Modeling

1

http://esml.iem.technion.ac.il/

http://www1.technion.ac.il/

What it’s all about…

March 2012


2


Risk Management

Interface Modeling

The Risk Management Process

• Identification

• Assessment

• Mitigation

• Monitoring

March 2012


3

The Modeling Process

Transforming Interface Prospects to Risks

Interface Modeling

System Modeling

March 2012


4

What is an Interface?

• Trivial definition:

– A boundary across which two systems meet and act on or communicate with each other.

• Extended definition: • Anything, across, through, over, or around which two

things meet and act on or communicate with each other.

March 2012


5

Interface Evolution

Divergence

Technological Evolution

Sensual Evolution, Augmented Reality

Multidimensional Interaction

Chaining

Interface Centric Design and Development

March 2012


6

Extended Interface Modeling

• Multiple levels/phases/aspects of interaction.

• Multiple forms of interface realization.

• Dual physical-logical realization.

• Encapsulation and suppression vs. decomposition and unfolding.

• Measurable characteristics and objectives (capacity, size, stability, availability, cost, throughput, criticality, etc.)

March 2012


7

Interfaces in the broadest sense

• The internet

• Language

• Friendship / Human relations

• The atmosphere/ magnetosphere

• Gravity

• Common Sense

• You name it!

March 2012


8

Interface-Risk Modeling

March 2012


9

A B Matter/Data/Energy/Currency

Noise, Opposition

Friction, Errors, Heat

Emergence, Causality, Interaction

Object / Process

Processing

Disturbance

Techniques for Interface Risk

Modeling and Mitigation

• Refinement

• The Missing Pieces

• Cut Across

• Pipe 2 Box

March 2012


10

Refinement

March 2012


11

Sys1 Sys2

Sys1

Sys 1.1

Sys 1.2

Sys2

Sys 2.1

Sys 2.2

Medium ???

The Missing Pieces

March 2012


12

Sys1

Source ???

Sys 1.2

Sys2

Sys 2.1

Receiver ???

Cut Across - 1

March 2012


13

Sys1

User1

Organization1

Sys2

User2

Organization2

Cut Across - 2

March 2012


14

System 3

System 2

System 1

Process 3

Process 2

Process 1

Project3

Project2

Project 1

Pipe 2 Box

March 2012


15

Sys1

Sys 1.2

Sys2

Sys 2.1

Sys1

Sys 1.2

Sys2

Sys 2.1 Sys3 Medium

Sys1

Sys 1.2

Sys2

Sys 2.1

SoS 3 Medium

Sys 3.1 Sys 3.2 Sys 3.3

Summary

• The conceptual similarity of interface modeling and risk modeling.

• A structured approach to risk identification through interface modeling.

• Risk modeling on top of the system model, not separately.

March 2012


16

The Enterprise Systems Modeling

Laboratory

• A unique education and research studio concept.

• Implementation of powerful tools and methodologies.

• Participating in several projects across the world (NASA SMACKDOWN, TALOS, VISIONAIR, ISO, SEBoK)

March 2012


17

• NASA Smackdown Project The SISO Simulation Smackdown is an effort to promote better awareness and understanding of both the importance and the complexity of modern modeling and simulation through hands-on mentoring and participation with modeling and simulation practitioners.

• TALOS autonomous robot project

Develop and field test the innovative concept of a mobile, modular, scalable, autonomous and adaptive system for protecting European borders.

Our contribution to both projects is VIVID OPM – A framework for model-driven simulated animation

Simulated Animation

Projects

Tanas, M.; Holubowicz, W.; Adamczyk, A.; Taberski, G.; "The TALOS project. EU wide robotic border guard system," Methods and Models in Automation and Robotics (MMAR), 2011 16th International Conference on , vol., no., pp.336-340, 22-25 Aug. 2011 URL: http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6031369&isnumber=6031302

http://esml.iem.technion.ac.il/?page_id=690

http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6031369&isnumber=6031302







• ISO Standardization of OPM

• We advocate a model-based systems engineering approach for creating “industry-strength” technical documents

• Technical document authoring is the function of the system – the organization – that delivers the technical document.

• Systems Engineering Body of Knowledge (SEBoK) • The SEBoK is a guide to the body of knowledge, providing references to detailed sources

for additional information.

• The SEBoK is primarily domain independent, with implementation examples providing the domain-specific context.

• The SEBoK is focused on engineered systems: products, services, systems of systems (SoS), and enterprises

International Standards and

Knowledge Generation Projects




http://www.sebokwiki.org/index.php/Main_Page



Thanks!

Yaniv Mordecai 054-9768764

[email protected]

March 2012


20

http://esml.iem.technion.ac.il/

http://www1.technion.ac.il/

Interface Driven Risk Modeling - Technion

Documents

Transcript of Interface Driven Risk Modeling - Technion