Status: open Implementation work Blocked
Source: Eclectica Systems Ltd ( Nic Plum)
In Table 4.2 UML::Artifact is defined as excluded.
In previous versions there was a paragraph Figure A.4 - 'SysML provides the capability to represent a document using the UML 2 standard stereotype «document» applied to the artifact model element. '
This, whilst contradicting the exclusion of Artifact from SysML did at least define how artifacts/documents were to be represented. Now there is absolutely nothing other than we can't use Artifact.
How are we supposed to represent a document? As there are few to no specialisation hierarchies in the specification it's almost impossible to see the thinking and, say, where / how deployedDocument fits into a taxonomy.
I'm trying to create a SysML profile and I need to represent a Document, Standard, Contract etc - all artifacts in the UML sense but no idea what I should now be using in a SysML profile.
Reported: SysML 1.7b1 — Sat, 24 Jun 2023 11:11 GMT
Updated: Fri, 14 Jul 2023 19:56 GMT