User Tools

Site Tools


sysml-roadmap:structure_behavior_concepts_modeling_core_team_wiki_page

This is an old revision of the document!


Back to the Systems Engineering Concept Model (SECM) Working Group Wiki

Structure/Behavior Concepts Modeling Focus Team

Team

  1. Manas Bajaj - Intercax
  2. Conrad Bock - NIST
  3. Roger Burkhart - John Deere
  4. Hans-Peter deKoning - ESA
  5. Sandy Friedenthal
  6. Chas Gayley
  7. Andrew Mullis - Lockheed Martin
  8. Marc Sarrel - JPL
  9. John Watson

Objectives

Starting Point

Limitations of SysML v1

  1. Lack of integration of how flows are captured in terms of item flows, flow properties, object flows, operation parameters, … (Sandy)
  2. Integration of operations on blocks including how parameters of operations align with flows and triggers on state machines (Marc)
  3. Lack of precision of how property specific types and initial values compartments on usages/ibd’s are defined (Roger)
  4. Limitations of capturing deeply nested properties (and other features) in the model such that a right wheel can be differentiated from a left wheel of a vehicle (Sandy, Hans Peter)
  5. Differences in the way port and part are modeled leading to inability to seamlessly evolve a port to become a part and vice versa (Hans Peter)
  6. Port complexity and associated interface complexity (Roger)
  7. Lack of geometric concepts such as shape and coordinate system and topologies (Sandy, Conrad)
  8. Limitations in ability to over-ride values and type for a particular usage including redefinition at nested levels of inheritance (Roger) and at realization levels (Hans Peter)
  9. Limitations in ability to represent as-defined versus as-realized (Hans Peter).
  10. Inability to easily represent instances with time varying property values and differentiate instances from snapshots at a point in time (Sandy)
    1. Example: thrust versus time for an aircraft with a particular tail number
  11. Ambiguity in the meaning of a property and its value (Conrad)
  12. Need for more engineering friendly terms for initial values, constants (vs read only) (Roger)
  13. Limitations in being able to model logical operations (e.g., and, or, nor, not) on structural relationships such as whole part and specialization (Sandy)
    1. Supports variant modeling and different configurations
  14. Inability to clarify that multiple symbols can represent the same element on the same diagram (e.g., proxy port) (Conrad)
  15. State dependent properties (e.g., stowed vs deployed antenna of a spacecraft, power consumption in different states) (Hans Peter)
  16. Time varying structure/topology such as changing compositions and interconnections (John)
  17. Limited support (concepts and notation) for real-time software architecture modeling concepts for structure and behavior that include the following (Note: Ron Townsend identified this limitation):
    1. Thread
    2. Data Storage
    3. Mutex
    4. Application, Library, or Service Boundary
    5. Other concepts that are behavior oriented such as thread creation, etc.

Driving Requirements

Requirements Analysis

The state of the concept model for Structure is captured in the annotated class diagram below.

Derived Requirements

References

sysml-roadmap/structure_behavior_concepts_modeling_core_team_wiki_page.1486591768.txt.gz · Last modified: 2017-02-08 17:09 by hpdekoning