27th Annual INCOSE International Symposium (IS 2017) Jul 17-20, 2017, Adelaide, Australia

Graph-Based Digital Blueprint for Model Based Engineering of Complex Systems

ManasBajaj1,PhD

ChiefSystemsOfficerIntercax

JonathanBackhausStaffSystemsEngineer

Rotary&MissionSystemsLockheedMartinCorporation

TimWalden,LMFellowChiefEngineer

EnterpriseOperationsLockheedMartinCorporation

ManojWaikar

SeniorApplicationsEngineer,Intercax

DirkZwemer

President,Intercax

ChrisSchreiber

SpaceSystemsCompanyLockheedMartinCorporation

GhassanIssaSystemsEngineeringAsc.SpaceSystemsCompany

LockheedMartinCorporation

Intercax

755thStreetNW,Suite312,Atlanta,GA30308,USA

www.intercax.com

LockheedMartinCorporateEngineering,

Technology&Operations,USAwww.lockheedmartin.com

Copyright©2017byIntercaxLLC.PublishedandusedbyINCOSEwithpermission.

Abstract Complex,cyber-physicalsystemsmustbefoundedonadigitalblueprintthatprovidesthemostaccuraterepresentationofthesystembyfederatinginformationfromengineeringmodelsacrossmultipleenterpriserepositories.Thisblueprintwouldserveasthedigitalsurrogateofthesystemandevolveasthephysicalsystemmaturesacrossitslifecycle,fromconceptionanddesigntoproductionandoperations.Thispaperpresentsagraph-basedapproachforrealizingthedigitalblueprint,whichwerefertoastheTotalSystemModel.Thepaperisdividedintofourparts.Part1providesanintroductiontousecasesformodel-basedsystemsengineering.Part2introducesgraphconceptsfortheTotalSystemModel.Part3providesademonstrationofthegraph-basedapproachusingSyndeiasoftwareasarepresentativeapplication.Part4providesasummaryofthispaper,andPart5laysoutpotentialdirectionsforfuturework.

Part 1: Model Based Systems Engineering (MBSE) Thecomplexityinmodernsystemsisgrowingatanunprecedentedpace.Thiscomplexityarisesfromarangeoffactorssuchasincreasingnumberandtypesofsystemcomponents,increasingtypesofinterfacesandinteractionsbetweensystemcomponents,availabilityof

1 Correspondingauthor:Dr.ManasBajaj(email:manas.bajaj@intercax.com)

2

productfunctionalityoutsidetheproductboundaries,andincreasinginteractionswiththeoperatingenvironment(system-of-systems,internet-of-things).Mostmechanicalandelectricalhardware-dominatedsystemshaveincreasinglybecomecyber-physicalinnature.Thiscomplexitychallengestheorganizationsdevelopingmodernsystemsthatmustnowbeequippedwithadvancedsoftwareandhardwaretoolstosupportthesystemthroughitslifecycle—design,manufacturing,operations,andmaintenance—andmustalsorespondtorapidlyevolvingmarketforcesandcompetitionfornewandimprovedsystems.

ThegoalofModel-BasedSystemsEngineeringistocreateandmanageasingleunifiedmodelofthesystemthatcanrepresentallofitsvariedaspects,suchasrequirements,structure,andbehavior,asshowninFigure1.Thesystemmodelisconceptualizedasagraphofinformationthatcanbeviewedfromorprojectedontodifferentperspectives.Thetransitionfromdocument-basedsystemsengineering(DBSE)toMBSEissimilartothetransitionfrom2Dmechanicaldrawingsto3DCADandtheabilitytoautomaticallyderive2Dviewsfroma3DCADmodel.

TheOMGSystemsModelingLanguage(OMGSysML)hasemergedasanopen,international,andindustrystandardforrepresentingthesystemarchitecture.However,mostofthedetailedengineeringisperformedinavarietyofmodelingandsimulationtools,asshowninFigure2.Thedigitalblueprintofasystem,referredtoastheTotalSystemModel(TSM)hereafter,canbeconceptualizedasthesystemarchitecturemodel(asaSysMLmodel)connectedtoavarietyofdomain-specificmodelsviafine-graineddigitalconnections,asshowninFigure2.Enterprisesdevelopingcomplexsystemsuseavarietyofconfigurationmanagementsystems,suchasproductlifecyclemanagement(PLM)systemsforversioningandmanagingtheengineering/manufacturingbills-of-materials,andapplicationlifecyclemanagement(ALM)systemsforversioningandmanagingsoftwarecode,builds,andrelatedartifacts.TheTSMincludesmodelsmanagedindifferentrepositoriesandinter-modelconnectionsbetweenelementsoftheseversionedmodels.Thisapproachprovidesorganizationstheflexibilitytousethebest-in-classtoolsforeachdisciplineandconnectthemtoothermodelsinthefederation.Theconception,development,andmanagementoftheTSMisafundamentalshiftunderwayinorganizationsdevelopingcomplexsystems.

Figure1:GoalofMBSEistodevelopandmaintaina

singleunifiedsystemarchitecture

3

TheTSMfederationevolvesovertimeaseachofitsconstituentmodelsevolveinamulti-disciplinaryandcollaborativeenvironment.AsshowninFigure3,snapshotsoftheTSMcanbetakenatdifferentstagesinthesystemlifecycleandsharedwithstakeholdersorarchivedforfuturequeries.

Figure3:TotalSystemModelevolvesasthesystemdefinitionmaturesacrossitslifecycle

Timeline

T1 T2(BaselineB1)

T3 T4(BaselineB2)

Figure2:TotalSystemModelasthedigitalblueprintofasystem(snapshotintime)

v35

B.20

Rev7

2012-07-12,1000hUSET

B1

C2

v3latest

ConnectionsbasedonReference,DataMap,FunctionWrap,ModelTransform,andCompositepatterns

4

Foranycomplexsystem,theTotalSystemModelprovidesabackbonefortraceability,systemanalyses,impactassessment,andwhat-iftradestudiesacrossthedisciplines.TheTotalSystemModelmayhavedifferenttopologies.ThetopologyshowninFigure2isasingle-hub-and-spokesystemwiththesystemarchitecturemodelinSysMLasthehubcoordinatingandconnectedwithotherdisciplines.Thismaynotbetheonlytopology.Forexample,thereareinter-modelrelationshipsbetweenthemodelsinvariousdisciplines,thataretoodetailedtobetrackedatthesystemarchitecturelevel.Considerthecaseofmodel-basedconnectionsbetweenaCADmodelandaFEA(finiteelementanalysis)orCFD(computationfluiddynamics)model,orconsiderthecaseofconnectingsoftwarerequirementstocode(managedinGitorSubversion)andrelatedticketsinanissuetrackingsystem(suchasJIRA).Anotheralternatetopologyisamulti-hub-and-spokesystemwherewemayhavedifferenthubscoordinatingdisciplinesatdifferentorsamephasesofasystem’slifecycle.Forexample,aSysMLmodelmaybeahubforsystemsengineeringrelatedactivities,connectedwithaPLMhubforcoordinatingmechanical/electricaldesignandmanufacturingactivitiesandanALMhubforcoordinatingsoftwareactivities.Atopologywithouthub(s)isalsoapossibilitybutwithoutanarchitecturemodelinplace,disciplinesstartworkingassiloswithad-hocinformationflows.

Part 2: Graph-based Approach for the Total System Model Inthissection,wediscusshowagraph-basedapproachhelpsusunifyandentertainthediversityofmodelsanddiscplinesinvolvedintheTotalSystemModel.Informationmodelsaregraphs–Fundamentally,informationmodelsofaproductorasystemarecomposedofentitiesandrelationshipsbetweenthoseentities.Thisnetworkofentitiesandrelationshipsisamathematicalgraphdatastructure.Theentitiesaretheverticesinthegraphandtherelationshipsaretheedgesinthegraph.Forexample,aSysMLmodelofasystemisagraphwhererequirements,blocks,activities,andotherelementsaretheverticesinthegraph,andassociations,dependencies,andotherrelationshipsaretheedgesbetweentheverticesinthegraph.Similarly,thebill-of-materialsinformationinaPLMsystemisagraph.Partshavepartversions,andeachpartversionusesotherpartversions.Asimulationmodel,suchasaSimulinkorModelicamodel,isalsofundamentallyagraph.Graphsprovideacommonformalismforrepresentinginformationmodels.TotalSystemModel(TSM)isagraphofgraphs–TheTSMisagraphofmodels,whereeachparticipatingmodelisitselfagraph.TheverticesintheTSMgraphareelementsintheparticipatingdomainmodels,suchasrequirements(orrequirementrevisions)inarequirementsdatabase,parts(orpartversions)inaPLMsystem,orblocksinaSysMLmodel.TheedgesintheTSMgrapharerelationshipsbetweenelementsacrossmodelsorwithinamodel.Intra-ModelandInter-ModelConnection(Edges)–TheTSMgraphincludestwomaintypesofedges,asshowninFigure4below.TheInter-ModelConnectionsaretheedgesbetweenmodelelementsindifferentmodelsorrepositories,suchasaconnectionbetweenarequirementinDOORS-NGtoarequirementorblockintheSysMLmodel.TheseareillustratedinFigure4usingdashedredlinesbetweenthecirclesrepresentingmodelsor

5

repositories.TheIntra-ModelConnectionsaretheedges/relationshipsbetweenelementsinthesamemodel,suchasasatisfyrelationshipfromaSysMLblocktoaSysMLrequirement,oratracelinkbetweenaTeamcenterpartrevisiontoarequirementrevision,oralinkbetweentwoissuesortasksinJIRA.SincetheTSMisafederation,itonlyownstheinter-modelrelationshipsbetweentheparticipatingmodelsinthefederation.Theintra-modelrelationshipsareownedbytheparticipatingmodelsbutareaccessibleondemandtotheTSM,suchaswhentraversingtheTSMgraphforimpactanalyses.

Figure4:Bothinter-modelandintra-modelconnections(edges)existintheTSM

PatternsandServicesonEdges–Theinter-modelandintra-modelconnections(edges)intheTSMgraphareofdifferenttypes.Forinter-modelconnections,wehaveidentifiedfourfundamentaltypesasbelowbasedontheservicestheycanprovide.Connectionpattern PurposeReferenceConnection Thistypeofconnectioncanbeusedtotracktheversions

oftherelatedmodelelements.DataMapConnection Thistypeofconnectioncanbeusedtomapandtrackthe

valuesofattributesofmodelelements,inadditiontotheversionsofmodelelements.

FunctionWrapConnection Thistypeofconnectioncanbeusedtowrapexecutablemodels(e.g.Java,Python,Simulink,orModelica),sendinputs,executethemodel,andgetoutputs.

ModelTransformConnection Thistypeofconnectioncanbeusedtomapandtrackthestructureofmodelelements,inadditiontoattributesandversionsoftheconnectedmodelelements.

AstheTSMgraphforasystemiswovenusingdifferenttypesofedges(asabove),onecanperformmodelcomparisonsandsynchronizationsacrossthecompletespectrumofmodel-basedconnections.

6

CollaborativeandautomateddevelopmentoftheTSMGraph–Asthesystemdevelop,onemustconsiderhowtheTSMgraphisbuilt.Though,wecanconnectmodelelementsacrossmultipledisciplinesmanually,itisnotscalableandiserror-prone.Theapproachwehavetakenisthatthespecificparts(sub-graphs)oftheTSMgraphareautomaticallygeneratedaswemoveinformationacrossthedisciplines.Forexample,whenSysMLblockstructure(architecture)isusedtogenerateasimulationmodel,suchasinSimulinkorModelica,thentheinter-modelconnectionsareautomaticallycreatedbetweentheSysMLblocksandthenewlygeneratedsimulationmodelelements.Theinter-modelconnectionsthenprovideconduitsformodelcomparisons,dataflows,transformations,comparisons,andsynchronizationonanongoingbasis.So,theTSMgraphiswovenaspartoftheengineeringworkflow.Additionally,weenvisiontheuseofmachinelearningtechniquestodetectpatternsinconnecteddataorinferencedatathatshouldbeconnectedintheTSMgraph.ModelsTransformationsasGraphTransformations–Sinceweconceptualizeinformationmodelsasgraphs,modeltransformationssuchasSysMLblocktosimulationmodelorPLMpartstructure,orviceversa,canbegroundedingraphtransformations.QueriesasGraphPatternMatching–OneofthekeyfacetsofbuildingaTotalSystemModelgraphistobeabletoperformqueriestosearchformodelelements,relationships,andpatterns.Conceptualizingtheconnectedsetofmodelsasagraphmakesitpossibletoleveragegraphpatternmatchingandgraphenginesasafundamentalcapabilitytoformulateandexecutequeries.Examplesincludesearchingforanyrequirementinarequirementsmanagementsystemthathasnotbeenallocatedtoastructuralorafunctionalelementinthesystemarchitecturemodel(inSysML),orsearchingforallallocationrelationshipsbetweenhardwareandsoftwaresystems.ThefundamentaladvantageofgraphpatternmatchingisthatoneneedstoonlydeclarethepatternintermsofthenodesandrelationshipsandthenagraphenginecouldexecuteandsearchtheTSMgraphforallinstancesofthepattern.Thisavoidstheburdenofwritinganewsoftwarecode(methodorfunction)foreachnewquery.ImpactAnalysesasGraphTraversals–Beyondqueries,graphsprovideasolidfoundationforimpactanalysesacrosstheengineeringmodelspace.TwoexamplesareshowninFigure4.Givenachangeinarequirementinarequirementsmanagementsystem,theTSMgraphwithintra-modelandinter-modelconnectionscanbeusedtoassesstheimpactofthechangeacrossthemodelspace,includingiftherequirementchangewillaffecthardwarepartsorCADdesignsinaPLMsystem.Alternatively,thesamegraphcanbeusedbyamechanicalengineerworkingonthehardwaredesigntotracetheupstreamrequirementsorsystemfunctionsdefinedinthearchitecturemodelthatmaygetaffectedifthegivenpartfailsduringoperation.

Part 3: Demonstration of the Graph-based Approach using Syndeia Syndeiaisasoftwareplatformforintegratedmodel-basedengineering(MBE/MBSE).Inthissection,SyndeiaisusedasarepresentativesoftwareapplicationtodemonstratetheconceptsrelatedtoTSM,especiallythegraph-basedaspectswhicharethethemeofthispaper.

7

SyndeiaenablesengineeringteamstocollaborativelydevelopandmanagetheTotalSystemModel(TSM)graphofacomplexsystem(orproject)bycombiningthesystemarchitecturemodel(inSysML)withmodelsinavarietyofenterpriserepositoriesandtools,suchasPLM(e.g.Teamcenter,Windchill),CAD(e.g.NX,Creo),ALM(e.g.GitHub),ProjectManagement(e.g.JIRA),RequirementsManagement(e.g.DOORS-NG),Simulations(e.g.MathematicaandMATLAB/Simulink),Databases(e.g.MySQL),andotherdatasources(e.g.Excel),asillustratedinFigure5.Syndeialeveragesindustrystandards,suchasREST,JSON,STEP,andOSLCandnativetoolAPIstoconnectto,query,updateandsearchmodelsinenterpriserepositories.Syndeiaservesasa“CM-of-CMsystems”(whereCMimpliesconfigurationmanagement)bymanagingtheconfigurationoftheentirefederationofmodels,whilethemodelsindividuallyaremanagedindifferentCMsystems,suchasPLM,ALM,ERP(EnterpriseResourcePlanningsystems),anddatabases.

Figure5:Syndeiaisasoftwareplatformforcreating,managing,querying,analyzing,and

visualizingtheconnectedgraphofmodelsforacomplexsystem.

Part 3.1: Generating the TSM graph AsshowinFigure6,SyndeiaprovidesaDashboardinterfacetoviewalltherepositoriesandmodelingenvironmentsontheRHSanddraganddropelementsfromSysMLarchitecturemodeltorepositories,orviceversa,withagivenconnectiontype(Reference,DataMap,ModelTransform,FunctionWrap).Dependingupontheselectedconnectiontype,thedraganddropoperationscancreateconnections(e.g.forReferenceconnections)orgenerate/transformmodelsinadditiontocreatingconnections.ThismakesitpossibletobuildtheTSMgraphinanautomatedmanneraspartoftheengineeringworkflow.

8

Figure6:Simpledraganddropinterfacetoconnect,map,transformmodelsandgenerate

theinter-modelconnections(edges)oftheTSMgraph

Part 3.2: Visualizing the TSM Graph Theinter-modelconnections(edges)createdareshowninatabularformatinFigure7.TheexampleshowsmodeltransformconnectionsbetweenblocksinaSysMLmodelandtheconnectedpartversionsinTeamcenterPLMsystem.

Figure7:Inter-modelconnectionsintheTSMgraphshownasatable.

Syndeiaalsogeneratesacirclechorddiagramforinteractivevisualizationofalltheinter-modelconnectionsintheTSMgraph.TheexampleshowninFigure8showselementsfrommodelsinSysML,TeamcenterPLM,GitHub,JIRA,andSimulinkparticipatingintheTSMgraphforanUnmannedAerialVehiclesystem.

Switch reposDrag-n-Drop

Drag-n-Dropgeneratesmodels&createsconnections

9

Figure8:Inter-modelconnectionsintheTSMgraphshownasacirclechorddiagram

Figure9showsanalternativevisualizationoftheTSMgraph.Givenaspecificmodelelement,suchasaSysMLblockorTeamcenterpartversionorDOORS-NGrequirements,onecanexplorealltheconnectedmodelelements,onedegreeofseparationatatime.Thecolorededgesinthegrapharetheintra-modelconnections.Inthisexample,allcolorededgesareinorangecolorandrepresentrelationshipsintheSysMLmodel,suchasdependencies,associations,andcontainments.Theblack-coloredrelationshipsaretheinter-modelrelationships,connectingmodelelementsbetweendifferentmodelsandtools.

Figure9:Exploringintra-andinter-modelconnectionsintheTSMgraph

GitHub

SysML

JIRA

Teamcenter

Simulink

GitHubSysML JIRA Teamcenter Simulink

GitHubfolder

Teamcenterrequirement

10

Part 3.3: Querying the TSM Graph Inthissection,wewillillustrateexamplesofgraph-basedqueriesontheTotalSystemModel.Wepresentthesequeriesin2parts.InPart3.3.1,wepresentgraphqueriesonthesystemarchitecturemodelinSysML,andinPart3.3.2,wepresentgraphqueriesontheTotalSystemModelgraphwhichincludestheSysMLmodelandtheinter-modelconnectionstoelementsinrequirements,PLM,ALM,databases,andotherrepositories.

Part 3.3.1: Graph queries on the system architecture (SysML-based) part of the Total System Model graph

Figure10illustratesanexamplearchitecturemodelofanUnmannedAerialVehicle(UAV)systeminSysML(Rhapsody).Themodelcontainsrequirements,blockstructure,usecases,andinteractions,statemachine,andactivitybaseddefinitionsofUAVbehaviors.

Figure10:ExampleSysMLmodelofaUAVwithstructural,functional,andrequirement

elements.

Figure11illustratesagraphstructuregeneratedinNeo4jgraphdatabasefromtheSysML-basedarchitecturemodelusingSyndeia.

11

Figure11:UAVarchitecturemodelasagraphinNeo4jgraphdatabase,

generatedbySyndeia

Givenagraphstructure,wecannowrunqueriesonthearchitecturemodelusinggraphpatterns.Someexamplequeriesandresultingsub-graphsareillustratedbelow.ThequeriesareformulatedusingtheCypherquerylanguageforNeo4jandareshowninthetoppartofthefigures,e.g.match(p:Package)returnpfetchestheSysMLpackagestructure.1. Query–GetallpackagesintheSysML-basedarchitecturemodel

Figure12:Querytogetallpackagesinthemodel

CypherQueryVertextypes/labelsintheresultingsub-graphEdgetypes/labels intheresultingsub-graph

12

2. Query–Getallincomingandoutgoingrelationships(edges)fortheUAVrequirementspecification

Figure13:Querytogetallrelationshipsforagivenrequirementspecification

3. Query–Getvaluepropertiesofblocks

Figure14:Querytogetallvaluepropertiesofblocks

13

4. Query–GetallrelationshipsfortheUAVblock

Figure15:QuerytogetallrelationshipsfortheUAVblock

5. Query–Getallrequriementsthatarenotconnectedtoanything(akadangling

requirements).Nonewerefound.

Figure16:Querytogetalldanglingrequirements

14

6. Query–GetallbehaviorsoftheUAVsystem

Figure17:QuerytogetallbehaviormodelsassociatedwiththeUAVblock

Part 3.3.2: Graph queries on the complete Total System Model graph 7. Query–GetthecompleteTotalSystemModelgraph,includingtheSysMLmodeland

inter-modelconnections.Notethetypesofverticesandedgesreturned.

Figure18:GetallnodesandedgesintheTSMgraph

15

8. Query–GetallconnectionsbetweenSysMLandDOORS-NGrequirements.Intheresultingsub-graph,therednodesareSysMLrequirementandgreynodesarerequirementsorrequirementcollectionsinDOORS-NG.

Figure19:GetallSysML–DOORS-NGrelations

9. Query–Getallinter-modelconnectionsintheTSMgraphthatareoftype

“REFERENCE_CONNECTION”.

Theresultinggraph(Figure20)showsreferenceconnectionsbetweenSysMLblocksandJIRAissues,SysMLblocksandGitHubfiles,andSysMLblocksandSimulinkmodels.

16

Figure20:GetallreferenceconnectionsintheTSMgraph

10. Query–GetallconnectionstoMySQLtablesandrows.TheresultinggraphshowsSysML

blocks(yellowvertices)—radar,video_camera,thermal_camera—connectedtoMySQLtableswiththesamenames(redvertices),andspecializationofthoseblocksconnectedtorowsinMySQLtables(greenvertices).

Figure21:GetallconnectionstoMySQLtablesandrowsintheTSMgraph

17

11. Query–GetallconnectionsbetweenSysMLblocksinthearchitecturemodelandWindchillparts.

Figure22:GetallconnectionstoWindchillpartsintheTSMgraph

18

12. Query–TracebetweentheUAVblockintheSysMLmodelandtheElectricalSystempart(versionA.1)inWindchill.Theresultingsub-graphindicatesthattheUAVsystemusesthePlatformsub-systemwhichusesanElectricalsub-systemthatisconnectedtotheElectricalSystempartversionA.1inWindchill.

Figure23:TracerelationshipsbetweenUAVblockandaWindchillpartintheTSMgraph

13. Query–TracebetweenaDOORS-NGrequirementcollectionandWindchillpart.The

resultingsub-graphindicatesthattheDOORS-NGrequirementcollection(greyvertex)isconnectedtotheWindchillpart(redvertex)viaaSysMLrequirement(pinkvertex)andSysMLblock(yellowvertex).

Figure24:GettraceabilitybetweenDOORS-NGrequirements/requirementcollections

andWindchillpartswithin3degreesofseparation

19

Part 3.4: Maintaing consistency across the TSM Graph Syndeialeveragestheinter-modelconnectionsintheTSMgraphtoprovideservicesformodelcomparisonsandbi-directionalsynchronization.AsshowinFigure25,adifferencetablecanbegeneratedacrossaspectrumofinter-modelconnectionstoindicateelementsthatareoutofsync.FortheexampleshowninFigure25,newtrackingsensorshavebeenaddedtotheUnmannedAerialVehiclesystemarchitecturemodel(inSysML)butarenotpartofthePLMbill-of-materialinTeamcenter.Thisishighlightedinredinthedifferencetable.

Figure25:CompareandsynchronizeconnectedmodelelementsintheTSMgraph

Part 4: Summary Inthispaper,wehaveintroducedtheconceptofaTotalSystemModelasthedigitalblueprintofasystem,federatingversionedmodelsandmodel-elementsfrommultipleenterpriserepositoriesandsoftwaretools,suchasPLM,CAD/CAE,ALM,requirements,database,andsoftwareconfigurationmanagementsystems.Thisapproachprovidesthebenefittousebest-in-classtoolsandrepositoriesformodelingdifferentaspectsofthesystem(suchasstructure,behavior,requirements,simulation)andbringsthemtogetherbyusingacommonarchitecture(suchasinSysML)andfederatingthemodelsandmodelelements.WehaveabstractedtheTotalSystemModelasagraphstructurewherethenodesarethemodels(ormodelelements)indifferenttoolsandtheedgesaretherelationshipsbetweenthemodels(ormodelelements).Then,wehavepresentedconcreteusecasesofcreating,visualizing,querying,andmaintainingconsistencyintheTotalSystemModelgraph,usingarepresentativesoftwareapplicationSyndeia.Averybroadsetofqueryexamples(graphpatternmatching)havebeenpresentedtoillustratethevalueofabstractingtheTotalSystemModelasagraph.

Part 5: Future Work Weenvisionthefollowingpotentialdirectionsforfuturework.

1. DevelopalibraryofgraphpatternstorepresentfrequentlyaskedquestionsandbasicmodelverificationrulesthatcanbeexecutedontheTotalSystemModel,such

20

asdetectingallrequirementsthatarenotsatisfiedbyastructureorfunctionelement,ordon’thaveatestcase.

2. Createmechanismstodevelopverificationandvalidationplansthatcanexecuteonthegraphtocontinuouslycheckfortheconsistencyofthesystemmodel.Thismayincludeverifyingthephysicsoftheproblemorcontinuousverificationofrequirements.

3. Developanapproachtomodelthehistoryofthegraphasitevolvesacrossthesystemlifecycleandplayouttheevolutionofasystemrequirement,partorfunctionacrossthelifecycle.

4. Formulateapproachestogeneratesub-graphsoftheTotalSystemModelthatcanbesharedoutsidetheboundaryoftheorganizationtoenablemodel-basedsystemintegrationwithoutcompromisinginformationsecurityandintellectualproperty.

5. Enrichrelationships(edges)inthegraphwithparametrizedmathematicalexpressionstoperformmathematicalanalyses,suchasfromsimplemassroll-upstosystemtradestudiesandassessingthequantitativeimpactofchanges.

References • Bajaj,M.,Cole,B.,Zwemer,D."ArchitecturetoGeometryIntegratingSystemModelswith

MechanicalDesign".AIAASpace2016Conference,LongBeach,CA,USA,Sep13-16,2016-https://goo.gl/6CZIcw

• Bajaj,M.,Zwemer,D.,Yntema,R.,Phung,A.,Kumar,A.,Dwivedi,A.,Waikar,M."MBSE++FoundationsforExtendedModel-BasedSystemsEngineeringAcrossSystemLifecycle".26thAnnualINCOSEInternationalSymposium(IS2016)Edinburgh,Scotland,UK,July18-21,2016-https://goo.gl/qpFaOT

• Bajaj,M.,Zwemer,D.,Peak,R.,Phung,A.,Scott,A.andWilson,M.(2011).SatellitestoSupplyChains,EnergytoFinance—SLIMforModel-BasedSystemsEngineering,Part1:MotivationandConceptofSLIM.21stAnnualINCOSEInternationalSymposium,Denver,CO,June20-23,2011-http://goo.gl/ga5kG

• Bajaj,M.,Zwemer,D.,Peak,R.,Phung,A.,Scott,A.andWilson,M.(2011).SatellitestoSupplyChains,EnergytoFinance—SLIMforModel-BasedSystemsEngineering,Part2:ApplicationsofSLIM.21stAnnualINCOSEInternationalSymposium,Denver,CO,June20-23,2011-http://goo.gl/C1awN

• CATIA(DassaultSystèmes)-http://www.3ds.com/products-services/catia,asaccessedonMar30,2016

• Creo(PTC)-http://www.ptc.com/cad/creo,asaccessedonMar30,2016• Dropbox-https://www.dropbox.com/,asaccessedonMar30,2016• Egnyte-https://www.egnyte.com,asaccessedonMar30,2016• EnterpriseArchitect(SparxSystems)-http://www.sparxsystems.com/products/ea/,asaccessed

onMar30,2016• Enovia(DassaultSystèmes)-http://www.3ds.com/products-services/enovia,asaccessedonMar

30,2016• Fisher,A.,Nolan,M.,Friedenthal,S.,Loeffler,M.,Sampson,M.,Bajaj,M.,VanZandt,L.,Hovey,K.,

Palmer,J.andHart,L.(2014),ModelLifecycleManagementforMBSE.INCOSEInternationalSymposium,24:207–229.doi:10.1002/j.2334-5837.2014.tb03145.x(PDFavailableathttp://goo.gl/ZWywBH)

• FMI-https://www.fmi-standard.org/,asaccessedonMar30,2016• Git-https://git-scm.com,asaccessedonMar30,2016• GitHub-https://github.com/,asaccessedonMar30,2016

21

• GoogleDrive-https://www.google.com/drive/,asaccessedonMar30,2016• ISO10303(STEP)-http://goo.gl/qH7Rdw,asaccessedonMar30,2016• JIRA(Atlassian)-https://www.atlassian.com/software/jira/,accessedonMar30,2016• JSON - http://www.json.org/, accessed on Mar 30, 2016 • MagicDraw(NoMagic)-http://www.nomagic.com/products/magicdraw.html,asaccessed

onMar30,2016• MATLAB/Simulink(MathWorks)-http://in.mathworks.com/products/simulink/,asaccessed

onMar30,2016• Mathematica(WolframResearch)-http://www.wolfram.com/mathematica/,asaccessedonMar

30,2016• Melody(Intercax)-http://intercax.com/products/melody/,asaccessedonMar30,2016• Neo4j(NeoTechnology)-https://neo4j.com/,asaccessedonNov20,2016• NX(Siemens)-http://www.plm.automation.siemens.com/en_us/products/nx/,asaccessed

onMar30,2016• OSLC-http://open-services.net/,asaccessedonMar30,2016• ParaMagic(Intercax)-http://intercax.com/products/paramagic/,asaccessedonMar30,2016• ParaSolver(Intercax)-http://intercax.com/products/parasolver/,asaccessedonMar30,2016• PLCS-https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=plcs,asaccessed

onMar30,2016• PTCIntegrityModeler(formerlyArtisanStudiofromAtego)-http://www.ptc.com/model-based-

systems-engineering/integrity-modeler,asaccessedonMar30,2016• RDF-http://www.w3.org/RDF/,asaccessedonMar30,2016• REST-http://www.w3.org/2001/sw/wiki/REST,asaccessedonMar30,2016• Rhapsody(IBM)-http://goo.gl/qMXwn6,asaccessedonMar30,2016• ReqIF - http://www.omg.org/spec/ReqIF/, as accessed on Mar 30, 2016 • SOAP-http://www.w3.org/TR/soap/,asaccessedonMar30,2016• Solvea(Intercax)-http://intercax.com/products/solvea/,asaccessedonMar30,2016• Subversion(Apache)-https://subversion.apache.org,asaccessedonMar30,2016• Syndeia(Intercax)-http://intercax.com/products/syndeia/,asaccessedonMar30,2016• SystemsModelingLanguage(SysML,OMG)-http://www.omgsysml.org/,asaccessedonMar30,

2016• Teamcenter(SiemensPLM)-http://goo.gl/bv7iEB,asaccessedonMar30,2016• UPDM-http://www.omg.org/spec/UPDM/,asaccessedonMar30,2016• Windchill(PTC)-http://www.ptc.com/product-lifecycle-management/windchill,asaccessed

onMar30,2016• WSDL–http://www.w3.org/TR/wsdl,asaccessedonMar30,2016

Biography ManasBajaj,PhDistheCo-FounderandChiefSystemsOfficersatIntercax.HehasledmultiplegovernmentandcorporatesponsoredR&Dprojectsoverlast15years,includingSBIRPhase1&2awards.Hehasledthedevelopmentofseveralcommercialsoftwareapplications,includingtheSyndeiaapplicationreferencedinthispaper.Dr.BajajearnedhisPhD(2008)andMS(2003)inMechanicalEngineeringfromGeorgiaTech,andBTech(2001)fromIndianInstituteofTechnology(IIT),Kharagpur,India.HehasbeenactivelyinvolvedinthedevelopmentoftheOMGSysMLstandardandtheISOSTEPstandards,andisaContentDeveloperfortheOCSMPcertificationprogram.Dr.Bajajistheauthorofnumerous

22

technicalpapersandarticles.Heisaco-developerofawidelypopularSysMLandMBSEtrainingprogramwithover4000participantssince2008.DirkZwemer,PhDisCo-FounderandPresident/CEOofIntercax,directingbusinessdevelopmentandprovidingstrategicconsultingforcustomersadoptingmodel-basedsystemsengineeringpractices.Heisacertifiedsystemsmodelingprofessional(OCSMPLevel4—ModelBuilderAdvanced).Hehasover30yearsofexperience,andistheauthorofnumerouspatents,technicalpapers,tradejournalarticles,andmarketresearchreports.HereceivedaPhDinChemicalPhysicsfromUCBerkeleyandanMBAfromSantaClaraUniversity.ManojWaikarisaSeniorSoftwareR&DEngineeratIntercaxandisacorecontributortotheSyndeiaplatformforMBE/MBSE.Hehasarichbackgroundinnext-generationweb-basedapplicationsandtechnologies.JonBackhausisaStaffSystemsEngineeratLockheedMartinwithintheRotary&MissionSystemsbusinessarea,supportingtheAdvancedSystemsorganizationDigitalTransformationInitiative.Jonhasabackgroundinsystemsengineeringandappliedmathematics.HeearnedaMaster’sinSystemsEngineeringfromCornellUniversityandaBachelor’sinElectricalEngineeringfromBucknellUniversity.TimWaldenisaLockheedMartinFellowandtheAdvancedSystemsChiefEngineer,withinCorporateEngineering&ProgramOperations.TimhasledthecorporateDigitalTransformationInitiative,bringingtheadvancementsofthe4thIndustrialRevolutiontothediverseLockheedMartinportfolio.Hehas30yearsintheDefenseIndustry,including20yearsinthesatellitegroundsystemdomain.HehasaBachelorofScienceinComputerSciencefromWestVirginiaUniversity.ChrisSchreiberisaSystemsEngineeringManageratLockheedMartinSpaceSystemsCompany,leadingModel-BasedSystemsEngineeringimplementationacrossallSpaceSystemsCompanyprograms,andistheactingSeniorManagerfortheSystemsEngineeringModernizationdepartment.Chrishasabackgroundinsoftwareandsystemsengineeringintheaerospaceanddefenseandmanufacturingindustries.HeearnedhisB.S.inFinanceandEconomicsfromtheUniversityofMontana,andiscompletinghisM.S.inComputerScienceSystemsEngineeringfromtheUniversityofDenver.GhassanIssaisaSystemsEngineeringAssociateattheLockheedMartingSpaceSystemsCompany.