sztipanovits panel slides.ppt

18
 Institute for Software Integrated Systems Vanderbilt University MODEL-INTEGRATED DESIGN IN SOFTWARE, SYSTEMS AND CONTROL ENGINEERING  Janos Sztipanovits ISIS, Vanderbilt University SERC Workshop October 5, !""

Upload: hegxx

Post on 01-Nov-2015

219 views

Category:

Documents


0 download

TRANSCRIPT

  • doTransition (fsm as FSM, s as State, t as Transition) = require s.active step exitState (s) step if t.outputEvent null then emitEvent (fsm, t.outputEvent) step activateState (fsm, t.dst)

    Mathematical and physical foundationsDomain-Specific EnvironmentsModel-Based Design ToolsDomain Specific Design Automation Environments:AutomotiveAvionicsSensorsTools:ModelingAnalysis VerificationSynthesisKey Idea: Use models in domain-specific design flows and ensure that final design models are rich enough to enable production ofartifacts with sufficiently predictable properties. Impact: significant productivity increase in design technologyChallenges:CostBenefit only narrow domains Island of Automation

  • doTransition (fsm as FSM, s as State, t as Transition) = require s.active step exitState (s) step if t.outputEvent null then emitEvent (fsm, t.outputEvent) step activateState (fsm, t.dst)

    Semantic Foundation Component LibrariesDomain-Specific EnvironmentsMetaprogrammable Tools, Environments Metaprogrammable Design ToolsMetaprogrammableTool Infrastructure Model Building Model Transf. Model Mgmt. Tool Integration Explicit Semantic FoundationStructuralBehavioralKey Idea: Ensure reuse of high-value tools in domain-specific design flows by introducing a metaprogrammable tool infrastructure. VU-ISIS implementation: Model Integrated Computing (MIC) tool suite (http://repo.isis.vanderbilt.edu/downloads/)BackplaneDomain Specific Design Automation Environments:AutomotiveAvionicsSensorsSemantic

  • Components span:Multiple physicsMultiple domainsMultiple toolsBatteryVMSISGServos/LinkagesEngineTransmissionUse Case 1: Cyber Physical SystemsDARPA AVM Program

  • CPS Design Flow RequiresModel IntegrationModelingArchitecture DesignIntegrated Multi-physics/Cyber DesignDetailed DesignExplorationModelingV&VSimulationModelingAnalysisRapid explorationExploration with integrated optimization and V&VDeep analysisPhysics-based Structure/CAD/Mfg SW Domain Specific Modeling LanguagesArchitecture ModelingDesign Space + Constraint ModelingLow-Res Component Modeling Architecture ModelingDesign Space + Constraint ModelingDynamics Modeling (ODE)Computational Behavior ModelingCAD/Thermal ModelingManufacturing ModelingArchitecture ModelingDynamics, RT Software, CAD, Thermal, Detailed Domain Modeling (FEM)

  • Physical components are involved in multiple physical interactions (multi-physics)

    Source of resilience: explicit modeling of multi-physics interactions.Electrical DomainMechanical DomainHydraulic DomainThermal DomainHeterogeneity of PhysicsTheories, Dynamics, ToolsTheories, Dynamics, ToolsTheories, Dynamics, ToolsTheories, Dynamics, ToolsModel Integration Challenge: Physics

  • Source of resilience: systems science principles for decoupling across design layers (such as passive dynamics to decouple stability from implementation induced time-varying delays Heterogeneity of AbstractionsPlant DynamicsModelsController ModelsDynamics: Properties: stability, safety, performance Abstractions: continuous time, functions, signals, flows,Physical designSystem Architecture ModelsResourceManagementModels

    System/Platform DesignSystems : Properties: timing, power, security, fault tolerance Abstractions: discrete-time, delays, resources, scheduling,Model Integration Challenge: Implementation Layers

  • Model Integration LanguagePro-ECATIATools and Frameworks Assets / IP / Designer ExpertiseSL/SFSem. IFCADSem. IFTDSem. IFModel Integration Language (MIL)abstractionImpact: Open Language Engineering Environment Adaptability of Process/Design Flow Accommodate New Tools/Frameworks , Accommodate New LanguagesThermalDesktopSEER-MFGHierarchical Ported Models /Interconnects Structured Design SpacesMeta-model Composition OperatorsSemanticBackplaneMIL SL/SFMIL SEERMIL CADabstractionabstractionMIL Pro-E

  • Use Case 2: C2 Wind TunnelUnmanned Sensor PlatformsIssues to be studied experimentally: Distributed Command and Control Synchronization and coordination Distributed dynamic decision making Network effects Information Sharing Shared situation awareness Common Operation Picture (COP) Network effects

    Advanced Cooperative Control Cooperative search algorithmsAFOSR PRET Program

  • Heterogeneous Simulation Integration

    Organization/CoordinationController/Vehicle Dynamics3-D Environment (Sensors)SL/SFHow can we integrate the models?How can we integrate the simulated heterogeneous system components?How can we integrate the simulation engines?CPN

  • Model Integration Architecture in C2WTCPN

  • Simulation Integration Architecture in C2WTSimulation Data Distribution/Communication Middleware Simulation Integration Platform (HLA) Distributed Simulation PlatformInstrumentation LayerDEVSFederate.OmNet++FederateCPNFederate.OGREFederateSimulinkFederate

    ControllerModels

    NetworkModels

    Org.Models

    FusionModelsModel Integration LayerComponentModelsInstrumentation LayerExperimentSpecification& ConfigurationRun-timeModels

    Env.Modelshttps://wiki.isis.vanderbilt.edu/OpenC2WT

  • Example: Simulink model integration (Vehicle dynamics)

  • Experiments: Impact of Cyber AttacksNetwork attack:A sub-network with hundreds of zombie nodes attacks a critical router on the main network.Flood attack on udp, tcp or ping Full networkZombie subnet

  • SummaryQuestions: What are challenging systems application domains? Heterogeneous SoS domains (like CPS and C2). How does practice diverge from theory, and how do we connect? Precise compositionality is hard to achieve in heterogeneous systems, still, we need predictability. Need systems science principles for simplifying interactions and dependences (decoupling).Where are relevant technologies to be found? In cross-disciplinary interactions. E.g. scalability in embedded software verification may require tradeoffs in systems dynamics.What would be the most critical tools and products? Component-based and model-based design approaches and tools are and will be increasingly essential.

  • Example: Architecture Modeling ArchitectureModelingSublanguage/ CapabilityFormalism, Language Constructs, ExamplesUsageHierarchical Module InterconnectComponentsInterfacesInterconnectsParametersPropertiesSystems ArchitectExplore Design Space Derive Candidate DesignsDesign Space ModelingSystems ArchitectDefine Design Space Define ConstraintHierarchically Layered Parametric AlternativesAlternatives/OptionsParametersConstraints

  • ComputationalDynamicsModelingPhysical Dynamics ModelingDomain Engineersdesign controllerSystem EngineersProcessor allocatePlatform EffectsComponent Engineer - model dynamics with Hybrid Bond GraphsSystem Engineers- Compose system dynamicsDataflow + Stateflow + TT ScheduleInteraction with Physical ComponentsCyber ComponentsProcessing ComponentsHybrid Bond GraphsEfforts, Flows,Sources, Capacitance, Inductance,Resistance,TransformersGyrators, SensorActuatorSoftware AssemblyProcessor TopologyAllocationExample: Dynamics Modeling

  • *Solid Modeling (CAD / Geometry)Manufacturing ModelingComponent EngineerDefines Structural Interface System Engineer- Defines Architecture

    Component EngineerDefines Part CostDefines Structural Interface, FastenerStructural InterfacesDefined with Peer Roles:AxisPointSurfaceCAD LinksComponent Manuf. CostMakeMaterialFab ProcComplxityShape/WtOTS: Cost/unitStructural InterfacesFastener Types, Num# Standard Structural Interfaces (ex: SAE #1)Example: Physical Structure and Manufacturing Modeling

    **********10/8/08Barksdale AFBC2WT Demonstration********