Originally the first versions of CSRM had examples. However, when the spec was reduced to a profile, the examples were removed. Because of some of the changes, not all examples are viable, so it is proposed we create new examples. Dave Kaslow also requested that the examples be categorized as a simplified and expert use of the profile to aid adoption by students.

Add mention of Educational examples

We have updated and feel that the CSRM is good enough to include, with the specification as educational attachments. We also need to change the text of the specification to mention the availability of MDZIP and XMI versions.

Attached are example versions of the CSRM as ZIP collections in both MDZIP and XMI formats. I will attach a version with the latest version of XMI as part of the release.

The original icons used for stereotypes in the profile were drafts and need to be replaced with better versions. The icons also need to be delivered as SVG.

The document does not currently show these icons, so diagrams need to be updated or an appendix added to the icons.

Icons supplied as educational attachment for use by implementors

Add the following paragraph to section 2, Conformance.

The profile of this version contains icons for most of the stereotypes. These icons are to be considered educational examples that may be replaced with implementation-specific versions. As an aid to implementers, a collection of Scalable Vector Graphic (SVG) files used for the current icons in the profile (currently embedded as encoded SVG) are included as an educational attachment that may be used as a starting point for implementers to create implementation-specific icons.

Constraints should be added to aid in the creating of correct models. For example, an MoE needs to be related to a moeRequirement which in turn is refined by a moeSpecification.

In addition, by categorization and content of warings and error of the constraints, we could add hints for new users of minimal and advanced concepts.

Defer tp RTF 1.2

Need a better set of actual uses of the model to create and test constraints. Defer to 1.2 RTF.

Section 7.6 to be replaced with an official SysML extensions profile. Section 1.6 was a hack that allowed the specification to move forward.

Unfortunately replacing this section with a SysML profile may not be easy because of issues with how vendors have implemented the SysML extensions. It may be simpler to replicate all or part of the extensions.

No change to 7.6 SysML Extensions is required

No change to 7.6 SysML Extensions is required.

The creation of an official version of SysML Extensions seems unwise as all the vendors and lots of users would be affected. The current profile described in this section is adequate for our purposes.

Note: We already voted on this, but having to recreate it because the result was lost.

David Kaslow requested that derived properties be added to allow reporting.

For example, a user of the profile should be able to add to a table a column that matches the Validated By or Validates concepts (and others) similar to how tables can display Verified By and Verifies.

Issue resolved in CSRM-14

CSRM-2 was re-opened to change the priority (I did not realize this could be modified), CSRM-14 essentially duplicates the issue and was already resolved. Best thing to do is to close this issue as a duplicate of CSRM-14.

Constraints should be added to aid in the creating of correct models. For example, an MoE needs to be related to a moeRequirement which in turn is refined by a moeSpecification.

In addition, by categorization and content of warings and error of the constraints, we could add hints for new users of minimal and advanced concepts.

Defer adding constraints to RTF

This is rather complex and our team does not have the resources to address. It is also better to address the constraints as people begin to use the profile and as RTF possibly expands the standard.

Note: We already voted on this in Ballot #1, but the result was lost.

Dave Kaslow proposes the following changes to stereotypes:

From: CubeSatRequirement to: SatelliteRequirement
From: CubeSatSubsystemRequirement to: SatelliteSubsystemRequirement
From: CubeSatComponentRequirement to: SatelliteComponentRequirement
From: CubeSatUseCase to: SatelliteUseCase
From: CubeSatSubsystemUseCase to: SatelliteSubsystemUseCase

Document attached was where the issue was raised.

Issue created by mistake

This issue related to a proposal and this was mistakingly created against the FTF. Closing with no change required.

Originally the first versions of CSRM had examples. However, when the spec was reduced to a profile, the examples were removed. Because of some of the changes, not all examples are viable, so it is proposed we create new examples. Dave Kaslow also requested that the examples be categorized as a simplified and expert use of the profile to aid adoption by students.

Defer to RTF

The profile is fairly straight forward with much of the vocabulary in MBSE and space domains. Deferring issue to RTF to reconsider for a later version.

The original icons used for stereotypes in the profile were drafts and need to be replaced with better versions. The icons also need to be delivered as SVG.

The document does not currently show these icons, so diagrams need to be updated or an appendix added to the icons.

Defer to RTF

Punting this issue to the next release.