© 2010 ibm corporation integrating multi-domain environment, relationship hub – a foak project...

© 2010 IBM Corporation

Integrating Multi-domain Environment , Relationship Hub – a FOAK Project

Zvi Lando , IAI (Israel Aerospace Industries )

Nir Mashkif , Haifa Research Lab


IBM ResearchA&D FOAK Project

Agenda

Systems Engineering in Israel Aerospace Industries (IAI)

IBM Research and IAI project collaboration: Relationship Hub (RH)

Demonstration

3-SARAHUnclassifiedThis document contains proprietary information of Israel Aerospace Industries Ltd. and may not be reproduced, copied, disclosed or utilized in any way in whole or in part, without the prior written consent of Israel Aerospace

Industries Ltd

Integrated NPI: Hierarchical System ViewIntegrated NPI: Hierarchical System View

Subs 1 Subs 2 Subs 3

System

Mod 1.1

Mod 1.2

Mod 2.1

Mod 2.2

Mod 2.3

Mod 3.1

Mod 3.2

System Engineer

System Engineer

System Engineer

System Engineer

System Engineer

System Engineer

System Engineer

System Engineer

System Engineer

System Engineer

System Engineer

SW Comp

HW Comp

Mech Comp

SW Comp

HW Comp

Mech Comp


Industries Ltd

Integrated NPI: Inter-Discipline ViewIntegrated NPI: Inter-Discipline View

System Engineer

System Engineer

System Engineer

System Engineer

System Engineer

System Engineer

System Engineer

System Engineer

System Engineer

System Engineer

Systems Engineering Process

Software Engineering Process

Electronics Engineering Process

Mechanical Engineering Process

Inter-Node Process Alignment & Data ContinuityInter-Node, Inter-Discipline, Process Alignment & Data ContinuityIntra-Node, Inter-Discipline, Process Alignment & Data Continuity


Industries Ltd

Integrated NPI: ExampleIntegrated NPI: Example

SARAH

Search And Rescue Automated Helicopter

Air VehicleControl Station Mission Planning Station

Portable Video Terminal

Air Frame Avionics Payload

Payload Control

(Software)

Payload Equipment

(Electronics)

Payload Structure

(Mechanics)

Req

uiremen

ts

Structural Constraints

Cross-Discipline Constraints


Industries Ltd

Business ObjectivesBusiness ObjectivesReduce Time Reduce Cost Improve Quality

Integrated Development Environment


Industries Ltd

Integrated Development EnvironmentIntegrated Development Environment

Data Continuity Process Alignment

Tool Connectivity


Industries Ltd

Quality Center

(HP)

DOORS (IBM)

Example: Requirements Engineering & Test DesignExample: Requirements Engineering & Test Design

8

System Requirements

Process Alignment

Requirements Engineering Process

Test Design Process

Notification of System Requirements availability

for test design

Data Continuity

Specialized Connector

Data duplication

Manual or no notification of

availability

System Requirements

Derivation

Test Design


Industries Ltd

Data Continuity ChallengesData Continuity Challenges

9

Doors

SA ,RPE

TCUE

/NX

MantraRhapsody

Other:SAP - ERP

Mantor Harness

HP Quality Center

9

Mentor, SAP…

Challenge 1: Avoid building & maintaining

multiple specialized inter-tool connectors

Challenge 2: Avoid inter-tool data

duplication

Challenge 3: Extend to additional tools



10

Agenda


IBM Research and IAI project collaboration: PLM Relationship Hub (RH)

Demonstration



11 11

No peer to peer integration

Product data exists in different systems

Traceability

Impact analysis

Data Duplication

DataContinuity

Relationship Hub

Doors

SA

TC

/NX

PDM Rhapsody

RPE

HP Quality Center

The Relationship Hub -The Solution Approach



12

P2P tools/Systems environment

tools/Systems with Relationship Hub

“TO BE” Environment



13

TC/NX

Relationship Hub: Support Systems Engineering Method

Cross tool models/artifacts integrated view

Cross tool models/artifacts bidirectional relations

Cross tool search and query

Impact analysis

Inter Connectivity rules checking via constraint satisfaction technology

Cross tool reports and documents generation

Cross domain baselining

PDM

TC/Mantra

DOORS

SA

Reports/ RPE

Wiring/ messaging

Rhapsody

Clearcase/RTC

Capabilities of the Relationship Hub



14

The Relationship Hub Architecture

SOA/OSLC bridge

Jazz Team ServerData Model CData Model BData Model A

REST APIs

REST APIs

SE: System Architect , Rhapsody

RH Adapter RH Adapter

Req: Doors

Testing: HP QC

SW: Rhapsody ,RSA

RH Adapter

ALM / PLM

- CAM

Build on

Mechanical Eng: Team Center

PDM tool:

RH Adapter RH Adapter

Manufacturing

/ERP

RH Adapter

RH Web UI

RH UI Extensions in

ALM/PLM Tools

Apps:Impact analysisInter Connectivity Rule Checking – By CSP solverDocument Generation – By RPEBi directional Inter Link Creation and mgt

Relationship HubRelationship Hub

WPS



15

Cross Tool Models/Artifacts Integrated View

Impact Analysis

IRC – Interconnectivity Rule Checking

Automatic Document Generation

The Relationship Hub Applications



16

TC/NX

Relationship Hub

DOORSSA

Integrated view of data models from heterogeneous engineering tools

Stores only indexing data including intra-relationships

Capture client methodology for enriching the data

Enable query the data according to the client methodology

Cross tool relations among model elements from different tools/disciplines

Common Web UI for create and manage Inter Relations

Inter Inter LinksLinks

Intra Intra LinksLinks

Cross Tool Models/Artifacts Integrated View



17

TC/NX

Relationship Hub

DOORSSA

The ability to identify all related elements that could potentially be impacted by a change in an Elements

Perform smart search across RH elements and relations according to predefine types:

Upstream impact analysis

Downstream impact analysis

Customize – reflects the customer’s analysis definitions

Uses advance visualization

Modify the results , navigation, aggregations ,comments

Present and aggregate the result according to the customer reference model (e.g. system /Sub systems)

Impact Analysis



18

Impact analysis – Systems decomposition viewImpact analysis – Systems decomposition view

Structural view is not enough and not reflect the real systems structureIAI’s preferred to arrange the results according to their system and sub

system structure The RH system enables flexible way to define additional custom views.

(e.g. Functional view)

Systems/Sub System

Elements

Impact Analysis – Reference Model



19

Design Process Methodology

Extendable to a model which satisfies rules ?yes no

Violations and

Contradictions

Implicit links Forbidden links Allowed links

RH

Existing items and links

Rules on links structure

CSP solver

-NP Complete

-Declerative

Interconnectivity Rules Checking (IRC)



20

Requirements coverage by tests

–A test covers a requirement–Requirement must be associated to a single model

element (or is defined non-functional)–A test is derived from a single function –If a test covers a requirement, it must be derived from

the function which is linked to the same requirement

Example

test function

requirementcover

derive

associated



21

Documents Generation in Heterogeneous EnvironmentGenerates composite document with diverse data sources whose

relationships are managed by Relationship Hub.System ArchitectSystems Modeling

DOORSRequirement Management

Rational Publishing EngineDocument Generation

DOORS Requirement

SA Diagram

SA Definition

Relationship Hub(2) Create links

(4) Send composite view ,Generate Document

Compose comprehensive

view

Maintain relationship model

Relationship Model

Siemens TCU

HP QC

(3) Send data for creating views

(1) Publish data for creating links



22

Agenda


IBM Research and IAI project collaboration: Relationship Hub (RH)

Demonstration



Demonstration



Integrated NPI: Example

SARAH

Search And Rescue Automated Helicopter

Air VehicleControl Station Mission Planning Station

Portable Video Terminal

Air Frame Avionics Payload

Payload Control

(Software)

Payload Equipment

(Electronics)

Payload Structure

(Mechanics)

Req

uiremen

ts

Structural Constraints

Cross-Discipline Constraints



25

System System (SARAH)(SARAH)

SubsysteSubsystem (AV)m (AV)

Module Module (PYLD)(PYLD)

End End Component Component (PYLD (PYLD Strct)Strct)

End End Component Component TestsTests

Module Module TestsTests

Subsystem Subsystem Tests Tests

Systems Systems TestsTests

Inte

grat

ion

Inte

grat

ion

Inte

grat

ion

Req’ Verification

Requirement Verification



Allocation

Allocation

Allocation

Integrated Systems Engineering Environment1. Derive System Requirements



26

System Architect

DOORS

Merged Stakeho

lder Reqs

System Reqs

Trace

Associate

Analysis

M_ActivitiesC1

Cn

CN

P

Q

R

S

P

MP

Q

R

S

P

M_ModesOM1

OMm

OMm

M_Modes

Problem Terms Solution Terms

Challenge:• Associate

requirements in DOORS with model elements in SA without having to copy model elements from SA into DOORS

Deriving system requirements



27

Relationship Hub UI for Creating Links

2. Select a start element using the dialog box

3. Press Create to create a link

4. Select an end element of the link using the dialog box

5. A link between the start and end elements is create

DOORS element

SA element

DOORS-SA link

1. Press Locate Element to specify a start

element of the link to be created 1. Create Link within Doors



28

Cross Tool Documents Generation Using RPE

DOORS Relationship Hub System Architect

Modified SSS Template

RPE

Generated SSS

Generates

REST APIDOORS DXL REST API

Generates an SSS [System Specification] with the new integration architecture

SA Diagram

DOORS Requirement

SA Definition



29

Generated Document“System Requirement Coverage”

From QCFrom DOORS

System requirements from DOORS and associated QC tests are arranged in a tabular form.

Their relationships are defined in the Relationship Hub.



Snapshot of a RPE Generated Document

Data from TC

Data from DOORS



31

System System (SARAH)(SARAH)

SubsysteSubsystem (AV)m (AV)

Module Module (PYLD)(PYLD)

End End Component Component (PYLD (PYLD Strct)Strct)

End End Component Component TestsTests

Module Module TestsTests

Subsystem Subsystem Tests Tests

Systems Systems TestsTests

Inte

grat

ion

Inte

grat

ion

Inte

grat

ion

Req’ Verification




Allocation

Allocation

Allocation

Use case: Integrated Systems Engineering Environment7. Change Impact Analysis



32

Stake Holder requirement Adjustable Camera changes

“Camera elevation shall be adjustable from pointing straight down to 15 degrees above the horizon”

“Camera elevation shall be adjustable from pointing straight down to 17 degrees above the horizon”

What are the elements impacted as a result of this change?

Change in Stake Holder requirement



33

Trigger the Impact analysis from with in the tools setTrigger the Impact analysis from with in the tools setImpact Analysis UI [1/6]



34

Structural viewStructural viewImpact Analysis UI [2/6]



35

System ViewSystem ViewImpact Analysis UI [3/6]



36

System view – Expand SARAHSystem view – Expand SARAHImpact Analysis UI [4/6]



37

System view – Expand Air VehicleSystem view – Expand Air VehicleImpact Analysis UI [5/6]



38

System view – Expand PayloadSystem view – Expand PayloadImpact Analysis UI [6/6]



39

© 2010 ibm corporation integrating multi-domain environment, relationship hub – a foak project...

Documents

sarah unclassified

system mod

data continuity challenges

haifa research lab slide

integrated view cross

iai project collaboration

tcnx relationship hub

solution approach slide