ABPSC 3.4b1 NO IDEA Avatar
  1. OMG Issue

ABPSC — Tables have conflicting / missing mappings

  • Key: ABPSC-76
  • Status: open  
  • Source: us.navy.mil ( Mr. Matthew LaPorte)
  • Summary:

    1) Duration constraint in table 20 says it maps to constraint definition but later says it is not mapped yet.

    2) Time constraint in table 20 maps to constraint definition but table 21 says otherwise

    3) 7.7.6.2.1 says Abstraction relationship is mapped to a sysml v2 dependency but the table 9 (7.7.6.1) says it is mapped to AllocationDefinition and SatisfyRequirementUsage.

    4) 7.7.6.1 Comment in the table 9 is mapped to a v2 package but in 7.7.6.2.2 is mapped to v2 comment.

    5) Constraint in table 9 should ALSO be mapped to a AssertContstraintUsage per 7.7.6.2.5

    6) 7.7.4.2.27 - ParameterSet does have a mapping but the table 5 (7.7.4.1) indicates that it doesn't have a mapping.

    7)7.7.4.1 - Instance Specification in table 5 is mapped to a connection usage. The actual mapping should be part usage. Linked instance specification should be mapped to connection usage. Should Add table row for Link Instance Specification

  • Reported: ABPSC 3.3 — Fri, 6 Dec 2024 17:22 GMT
  • Updated: Fri, 6 Dec 2024 22:19 GMT