Model-Based System Integration (MBSI)An Instructional Approach

Dr. Paul MontgomeryAssociate Professor of Systems EngineeringNaval Postgraduate School

May 15, 2012

1

Perspectives CalibrationPerspectives Calibration

Developmental SEDevelopmental SE SI – Different perspective from SEsSI – Different perspective from SEs DoD – Developing complex systemsDoD – Developing complex systems Academia – SE professorAcademia – SE professor MBSE – Evolving and maturingMBSE – Evolving and maturing MBSI – An idea (MBSE from SI’s MBSI – An idea (MBSE from SI’s

perspective)perspective)

2

BLUF

Integration• Integration begins at design

Modeling• Don’t try to integrate the system until you

successfully integrate the system model Instruction

• Integration must be experienced, not merely studied

3

Essential Concepts of I&QEssential Concepts of I&Q11

Integration = ensuring the system comes Integration = ensuring the system comes togethertogether• Interfaces Interfaces (connectivity and flow)(connectivity and flow)

• Interactions Interactions (also interoperability)(also interoperability)

Qualification = ensuring the system is Qualification = ensuring the system is acceptable to the customer acceptable to the customer (aka ‘acceptance’)(aka ‘acceptance’)

• Building the system correctly Building the system correctly (aka ‘verification’)(aka ‘verification’)

• Building the correct system Building the correct system (aka ‘validation’)(aka ‘validation’)

11 I&Q = Integration and Qualification I&Q = Integration and Qualification

4

What’s the Problem? Many system developments fail at integration & qualification (I&Q) … and fail badly Added cost, schedule, and needed redesign 1

• Hershey Foods Corp. PROJECT: IBM-led installation and integration of SAP, Manugistics Group Inc. and Siebel Systems Inc. software…Hershey sales fell 12% in the quarter after the system went live — down $150.5 million compared with the year before

• Norfolk Southern Corp. PROJECT: Systems integration with merger target Consolidated Rail Corp…Norfolk Southern lost more than $113 million in business during its 1998/1999 railroad merger with Conrail. Custom logistics software wasn’t tested properly and a dispatcher mistakenly fed bogus test data into the system

• Tri Valley Growers PROJECT: Oracle Corp. ERP and application integration…Tri Valley bought at least $6 million worth of ERP software and services from Oracle in 1996. None of the software worked as promised; some of it couldn’t even be installed on Tri Valley’s DEC Alpha hardware, the co-op claimed in a $20 million lawsuit filed in February.

From: “Top 10 Corporate Information Technology Failures”5

Where are we (DoD) Going?- DoD and SoS/LSI (Gansler)

SoS acquisition and engineering is the norm in DoD

SoS design, integration and qualification (I&Q) is highly complex

DoD engineering workforce not well aligned to LSI responsibilities

6

• Government oversight of LSI has been complicated with contractual ambiguities

• Delineation of “inherently governmental functions” for LSI needs more clarity

• Private LSIs have inherent conflicts of interests without specific controls

• SoS integration requires a strong, centralized LSI

If SE is Well Defined, Why is I&Q a Challenge? What’s wrong with this picture?

Inte

grat

ion

& Qua

lific

atio

n

Inte

grat

ion

& Qua

lific

atio

n

Inte

grat

ion

& Qua

lific

atio

n

Inte

grat

ion

& Qua

lific

atio

n

Definition &

Decom

position

Definition &

Decom

position

Definition &

Decom

position

Definition &

Decom

position

ID NeedsID Needs

Define Define ConceptConcept

Preliminary Preliminary DesignDesign

Detailed Detailed DesignDesign

Component Component I&TI&T

System I&TSystem I&T

Production Production / Mfg/ Mfg

Deployment Deployment O&MO&M

Verification & Verification & ValidationValidation

Verification & Verification & ValidationValidation

Component Component BuildBuild

7

Integration begins at designMBSI

8

What is a System Model?

9

CORE CORE ModelModelCORE CORE ModelModel

Functional Decomposition (Hierarchy)

Functional Decomposition (Hierarchy)

Functional Flow Model (FFBD)

Functional Flow Model (FFBD)

Interface Diagram (N2)Interface Diagram (N2)

Generic Physical Block Diagram

Generic Physical Block Diagram

Behavior Diagram (Sequence)

Behavior Diagram (Sequence)

Functional Process Model (IDEF0)

Functional Process Model (IDEF0)

MBSI – The SI’s MBSE Perspective

Design Environment

Design Environment

Qualification EnvironmentQualification Environment

Modeling EnvironmentModeling Environment

Integration EnvironmentIntegration

Environment

MBSE? MBSI?

10

SE Activities Should Produce System Definition/Model

Functional Model

Functional Model

Operational Model

Operational Model

Interface Model

Interface Model

Physical Model

Physical Model

Behavioral Model

Behavioral Model

System Definition (“Model”)

11

System Model Underpins I&Q ActivitiesSystem Model Underpins I&Q Activities

12

Don’t try to integrate the system until you integrate the model

System Modeling

13

Progressive IntegrationProgressive Integration

14

Different teams in diverse locations

Integration and Qualification Considerations from Integration and Qualification Considerations from Functional AnalysisFunctional Analysis

15

Complex flows/connectivity

may indicate complex interactions

and bears special attention for

integration and qualification focus

(or possible redesign)

Integration and Qualification Considerations from Integration and Qualification Considerations from Behavior AnalysisBehavior Analysis

16

High behavioral interaction activity

bears special attention for

integration and qualification focus

(or possible redesign)

Integration and Qualification Considerations from NIntegration and Qualification Considerations from N22 AnalysisAnalysis

17

Function Function 11

Function Function 11

Function Function 22

Function Function 22

Function Function 44

Function Function 44

Function Function 55

Function Function 55

Large number of interface content

(complex interactions) can warrant special integration and

qualification focus (or possible

redesign)Function Function

33Function Function

33

Integration must be experienced, not merely taught

I&Q Instructional Methods

18

System ModelSystem Model

System model is essential for project success

Popular Approaches to Teaching I&Q

SE FundamentalsSE Fundamentals SE IntegrationSE Integration Test and EvalTest and Eval

ConceptConceptDesignDesign

BuildBuildIntegrateIntegrate

QualifyQualify

Pro

cess

Ap

pro

ach

“To

ys”

Ap

pro

ach

En

d-t

o-E

nd

Ap

pro

ach

Shortfalls:Non-tangible experienceHard to develop I&Q instinctsDisjointed learning experience

Shortfalls:Cannot design componentsInterfaces are fixedInterface design may be hidden

Shortfalls:Not enough timeNot enough student skillsSet up for failure

19

A ProjectMBSI Instructional Example

20

Overview of Class ProjectOverview of Class ProjectSOH Submarine Detection using Fire ScoutSOH Submarine Detection using Fire Scout(STRAIT SCOUT)(STRAIT SCOUT)

21

Customer Problem StatementCustomer Problem Statement

ProblemProblemIn the Persian Gulf, we do not have a In the Persian Gulf, we do not have a

reliable system to detect submarines reliable system to detect submarines that egress and ingress through the that egress and ingress through the SOH by hiding in tanker wakes.SOH by hiding in tanker wakes.

Research QuestionsResearch QuestionsCan a combination of BAMS and one Can a combination of BAMS and one

FireScout be used to provide a high PFireScout be used to provide a high Pdd

of the submarine behavior above?of the submarine behavior above?What is shipping traffic density vs. PWhat is shipping traffic density vs. Pdd

performance of such a system?performance of such a system?What are some FireScout search What are some FireScout search

strategies for such a system strategies for such a system deployment?deployment?

22

Primary System Assets

BAMS - Persistent surveillance over AOR with surface search Radar

Fire Scout•Speed = 0 – 90kts

FireScout Sensor = LIDAR (Light Detection and Ranging)•Scanning•Sub – inch resolution

23

Top-Level STRAIT SCOUT Architecture ConceptTop-Level STRAIT SCOUT Architecture Concept

24

SensorSensorSensorSensorRed TeamRed TeamRed TeamRed Team

FireScoutFireScoutFireScoutFireScout

C2C2C2C2

Test Parameters (Parameters, Scenarios, Test Parameters (Parameters, Scenarios, Results)Results)Test Parameters (Parameters, Scenarios, Test Parameters (Parameters, Scenarios, Results)Results)

11

66

55

44

77

1 – Ships and sub position data2 – N/A3 – Surface track data4 – Sensor data5 – Flight path commands6 - Position data 7 – Environment parameters8 – Test results

66

88 88

BAMSBAMSBAMSBAMS

11

33

Team Roles & Responsibilities LSI

• Primary stakeholder negotiations• Top-level architecture• Taxonomy and structure

– External systems interfaces– Intra-subsystem interfaces– Functional naming conventions

• Conop• Integration and qualification strategy

– Integration strategy– Acceptance goals, objectives, and agreements

• Leadership Subsystem teams

• Subsystem derived requirements• Subsystem Design

– Functional, interfaces, and generic physical

• Subsystem integration and qualification Instructor = Primary customer/stakeholder25

SE DesignSE Design

Define the problemDefine the problem Develop functional architectureDevelop functional architecture Develop physical architectureDevelop physical architecture Develop operational architectureDevelop operational architecture Develop interface architectureDevelop interface architecture Define integration, test, V&V strategyDefine integration, test, V&V strategy

26

Simulation Concept

27

time = t

time = tn

FireScoutsensor scan field

Tanker track and direction

time

Detection?

Wake (no sub)

Wake (with sub)

VBA

Project I&Q Environment

Excel™

VBA

Excel™

VBA

Excel™

Excel™

Subsystem A

Subsystem B

Subsystem CSystem

LSI Team

Subsystem Teams

Advantages:Readily available “Office” toolsConcept-to-designInterface visibilityTeam integration = subsystem integrationLSI integration = system integration

Disadvantages:VBA is not innate SE skillToo much to do in time allotedIntegration can still be undisciplined

28

MBSI EnvironmentIm

plementation

Physical Modeling

BehavioralModeling

InterfaceModeling Qualification

Modeling

ConopNeeds

MissionConstraints

AssumptionsGoals

Objectives

Cell formulas and VBA Sheets and cells

modeling

Functional Modeling

“Design”“I&Q”

29

Primary Class Project Phases

System design Model integration (CORE1) System development (code) Subsystem & System integration System verification (test) System validation (demonstrate) System acceptance (grade)

1 CORE 8 (University) Service pack 3

30

The si perspectiveMBSI Instructional Example

31

SI Challenge QuestionsSI Challenge Questions

Do you understand your problem and what your subsystem Do you understand your problem and what your subsystem needs to do?needs to do?

Do you understand enough about your subsystem Do you understand enough about your subsystem behaviors to define functions?behaviors to define functions?

How many functions are in your subsystem?How many functions are in your subsystem? Are the functions Are the functions ““modularmodular”” and simple? and simple? How many interactions do you expect?How many interactions do you expect? How many external interfaces do you need to define?How many external interfaces do you need to define? How many internal interfaces do you need to define?How many internal interfaces do you need to define? Have you thought of which functions need to be integrated Have you thought of which functions need to be integrated

first?first? What are the integration and qualification risks that are What are the integration and qualification risks that are

starting to emerge?starting to emerge?

32

Simplified Strait Scout Sequence Diagram?

33

C2C2 FSFSLSILSI RedRed SensorSensor

Setup / Run

Sub detected

Record

Terminate

Locations

Flight Cmds

Fly/ Location

loop

BAMSBAMS

Target Data

Strait Scout Functional Context Systems

34

Control flow is linear?

Control flow is linear?

N2

35

Interface complexity?

Interface complexity?

IDEF

36

Many interfaces?

Many interfaces?

Many interfaces?

Many interfaces?

Sequence

37

Triggers? Responses?

Triggers? Responses?

Student DiscoveriesStudent Discoveries

Early requirements clarification is importantEarly requirements clarification is important Early architecture design imperative (especially Early architecture design imperative (especially

functional and interface)functional and interface) Rushing to development prior to model definition wastes Rushing to development prior to model definition wastes

time and efforttime and effort Early model integration drives out:Early model integration drives out:

Functional gaps and overlapsFunctional gaps and overlaps Interface inconsistencies and discontinuitiesInterface inconsistencies and discontinuities System behavior misunderstandingsSystem behavior misunderstandings Inter and intra-system interface problemsInter and intra-system interface problems

SI involvement in design can reduce risk during I&QSI involvement in design can reduce risk during I&Q Project would have failed without MBSE/MBSI methodsProject would have failed without MBSE/MBSI methods

38

Lessons learnedMBSI – An Instructional Approach

39

Value of MBSI Successful I&Q requires:

• Strong LSI / SI• Detailed system definition (particularly interfaces and functional

interactions)• Early taxonomy and structure definition• Early SI influence with I&Q success perspective• Modeling in order to discipline design efforts• Model integration prior to system integration to reduce I&Q risks• Diverse and integrated SE/SI support system (i.e. tool sets, etc.)

MBSE tools not yet MBSI tools “Teach” I&Q using MBSI applied to experiential project

40

References

Handbook of Systems Engineering and Management, Sage and Rouse (ed.), Wiley and Sons, 1999, Chapter 14

Systems Engineering Guide for Systems of Systems, Ver 1.0, Aug 2008, Director, Systems and Software Engineering, DUSD (Acq and Tech), OSD (AT&L)

The Role of the Lead System Integrator, Gansler, et.al., NPS-AM-09-005, Jan 2009

Top 10 Corporate Information Technology Failures, www.computerworld.com/computerworld/records/images/pdf/44NfailChart.pdf

http://cdn.business2community.com/wp-content/uploads/2012/04/customer-experience-focus.jpg

http://www.fas.org/man/dod-101/sys/ac/f-18-ef-usnhornt.jpg http://www.behavioradvisor.com/sbPuzzled.jpg http://www.blogspot.com/-hSnr-sGBKko/T2_-WfiI8DI/AAAAAAAAD88/

tzcvl7wxgRA/s1600/acellphone.gif

41