Please enable JavaScript.

Coggle requires JavaScript to display documents.

Scalable méthodes for modeling CPS (System boundary definition (:check:…

- - - - Global mission: Req: the sys mission and objectives are determined: The initial req and their relationships to each other
      - Lifecycle: stm: to take into account the constraints of each phase: each phase will be ddetailed in further diagrams
      - Context: bdd: the sys boundary: what is inside the sys. These interactions should be considered in the design phase and specified within the req
      - External interfaces: ibd: supporting the interactions of the boundary has to be defined. All the actors that figure in the context diagram shall also be on the IBD representing the external interfaces
      - User operating modes: stm: the external behavior with regard to the user of the system: detail the usage of the system during its "operating" state of the lifecycle.
      - Services provided by the system: Use case. For each operating mode, each services provided by the system to the end-user is modeled by a use-case. Each use case is linked with the relevant operating mode
      - Functional scenarios: seq: The same actors that are linked to the usecase shall be on the corresponding seq diagram. Internal operations may emerge from this diagram and will be used in the functional model during the white box analysis
      - Requirements specification: req (derive, refine and contain)
      - Requirements traceability: req (refine, allocate and satisfy): to link multi-views bw each other and be consistent with each other: to trace all requirements and ensure consistency of the black box phase. The traceability links: ["refine"=bw req & UC] - ["allocate"=bw req & roles in BDD context] - ["satisfy"=bw req and external ports IBD]
    - - Logical breakdown and allocation : BDD = logical structure. Kind of technology: to ensure consistency with black box analysis, the op identified in seq diagrams can be allocated to relevant components.
      - Requirements traceability: req-from the previous phase component-level req are derived from sys-level req and allocated to the corresponding req. The logical components shall satify these req ["satisfy"=to show the dependency
      - Functional architecture: activity diagram: functional req identified in the black box analysis (use cases & operations identified on seq)
      - Logical architecture: IBD to specify the internal interactions bw the components
      - Parametric diagram: constraints: bridge between sysml and other tools - it offers the possibility to feed back the sys model with sim results
      - Physical allocation: BDD - after having checked with simulation (modelica) allocate physical components to logical components
      - Physical architecture: ibd
  - - - Modeling challenges that arise from the intrinsic heterogeneity, concurrency and sensitivity to timing of CPS
- - - - cps can reason in various dynamic contexts and develop context-dependent stratégies to adapt themselves to the need of specific application scenarios - the three major functionalities: sensing - resoning and actuating - adapt their functionalities to dynamic concepts
        
        The development of multiple context aware systems that can change behaviors in real-time in order to enhance system performance - operate dynamically in changing contexts
        
        the system should enable adaptive or dynamic operation of these systems. Context dépendent-operation can enhance smartness of the system performance which include context-dependent (sensing, reasoning, informing) behaviors can be enhanced by execution of real-time control stratégies developed considering the dynamic changes of the context
        
        The objective of context dépendent reasoning is to generate relevant contents and making décisions for users on what to inform considering both