1 / 11

Complex Systems Engineering Strategies

Complex Systems Engineering Strategies. Bob Marcus robert.marcus@sri.com. Complex Systems Properties. Emergent - Macroscopic dynamics and variables occur in the system, which is not easily predictable from local dynamics

lacey-bridges
Download Presentation

Complex Systems Engineering Strategies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Complex Systems Engineering Strategies Bob Marcus robert.marcus@sri.com

  2. Complex Systems Properties • Emergent - Macroscopic dynamics and variables occur in the system, which isnot easily predictable from local dynamics • Multiscale Interactive - The macroscopic and component-level behavior interact in a measurable way • Non-equilibrium – Large changes in the behavior of the system are possible under small perturbations • Metastable - Long-lived non-equilibrium states can arise and be maintained in interaction with the environment • Evolutionary Adaption- The system exhibits altered behavior in response to environmental changes • Self Organizing - Coordinated behavior can take place among components without centralized guidance

  3. Behavior Structures in Complex Systems • Component = Basic element of functionality in the system. Intrinsic behavior under environment influences. • Collaboration = Interactions without macroscopic coordinators. Behavior influenced by peer-to-peer interactions. • Coordination = Interaction possibly managed by coordinators to support group goals. Behavior influenced by group dynamics. • Control = Interactions directed hierarchically to foster global goals. Behavior constrained by controller. • All of these structures can be present in a system of systems and can be mixed and combined recursively

  4. Aspects and Examples of Behavior

  5. Behavior Structures are Recursive Controller Components Coordinators Controllers Coordination Coordinators Controllers Components Collaboration Components Coordinators Controllers

  6. Complex Systems Engineering Strategies • Top down - Traditional systems engineering, Pre-defined coordination and interactions • Bottom up – Self-organizing, Emergent collaboration and coordination from interactions. • Matchmaking – Coordination is based on matching and combining existing components to meet requirements • Middle Out – Coordination combines existing components and collaborations but also drives new requirements, collaborations and components Note: Alternate strategies can be used in different stages of engineering

  7. Top Down Design (Control-based) USERS User Requirements and Derived Requirements Set of Requirements Capability specifications (with priorities) Requirements Analysis Capability description Set of Services Needed Existing, Enhanced, Composite and possible new services and/or systems

  8. Bottom Up Design (Collaboration-based) USERS User Interfaces Capabilities available Capability specifications and possible new capabilities Advertising Capability description (with cost of implementation) and possible new capabilities Set of Services Available Existing, Enhanced, Composite and possible new services and/or systems

  9. Matchmaking ( SOA Orchestration) USERS User Requirements and Derived Requirements Set of Requirements Capability specifications (with priorities) Matchmaking Capability description (with cost of implementation) Set of Services Existing, Enhanced, Composite and possible new services and/or systems

  10. Middle Out Design (Coordination-based) USERS User Requirements and Derived Requirements Set of Requirements New capabilities available Capability specifications (with priorities) and possible new capabilities Mediating Capability description (with cost of implementation) and possible new capabilities Set of Services New capabilities needed Existing, Enhanced, Composite and possible new services and/or systems

  11. Trial Run NECC ST&T Marketplace Needs consolidated, prioritized and binned Needs sent to Bob Marcus Clarify need JMPO, FDCE groups solicited for ST&T needs Match needs with offerings Consumers Producers Gain producers interest Needs Mike Hebert (JPMO) (1) (2) Contractors JPMO (3) Bob Marcus (NCOIC) (3) Vendors (4) FDCE (8) (7) Open Source Libraries Ensure Industry Day(s) meet needs and ensure participation (7) Offerings (6) (5) Standards Bodies Scrub list of offerings and do final offering selections, finalize schedules for Industry Day(s) Develop list of offerings – use Industry Days as delivery mechanism (9)

More Related