Issue 6353: Deployment a dependency? (uml2-rtf) Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov) Nature: Revision Severity: Significant Summary: If Artifact and Node are classifiers, why is deployment a dependency? Then runtime artifacts cannot be deployed to runtime nodes. Resolution: Disposition: Deferred to UML 2.4 RTF Revised Text: Actions taken: October 20, 2003: received issue Discussion: Run-time artifacts can be deployed to runtime models, but the type consistency is not formally guaranteed (that is, if Artifact A is deployed to Node B, then instances of A are deployed to instances of B, but there is no ‘instantiation’ of the deployment relationship). In order to formalize the instantiation aspect, Deployment would need to be modeled as a subtype of Association. This solution has been touched on in the submission process as a simplification and tightening of the model but requires some time to work out and bed down, as it would be a non-trivial change. Hence, it would be best tackled in an RTF process. Note (if this solution direction is accepted) that the notation would need to be changed to not use a dependency, but rather an association (possibly with keyword <<deploy>>). End of Annotations:===== me: SysML Company: SysML Partners mailFrom: conrad.bock@nist.gov Nature: Revision Severity: Significant Subject: Deployment a dependency? If Artifact and Node are classifiers, why is deployment a dependency? OMG Issue No: 6353 Title: Deployment a dependency? Source: NIST (Mr. Conrad Bock, conrad.bock@nist.gov) Summary: If Artifact and Node are classifiers, why is deployment a dependency? Then runtime artifacts cannot be deployed to runtime nodes. Discussion: Run-time artifacts can be deployed to runtime models, but the type consistency is not formally guaranteed (that is, if Artifact A is deployed to Node B, then instances of A are deployed to instances of B, but there is no .instantiation. of the deployment relationship). In order to formalize the instantiation aspect, Deployment would need to be modeled as a subtype of Association. This solution has been touched on in the submission process as a simplification and tightening of the model but requires some time to work out and bed down, as it would be a non-trivial change. Hence, it would be best tackled in an RTF process. Note (if this solution direction is accepted) that the notation would need to be changed to not use a dependency, but rather an association (possibly with keyword <>). Disposition: Defer Then runtime artifacts cannot be deployed to runtime nodes