|
Problem Report 0007 Details
Show help for this page
Click here to view your privileges
This page provides all information on Problem Report 0007 and all reviews you are authorized to see.
Report 0007 Actions
| Problem Report Number |
0007 |
|---|
| Submitter's Classification |
Specification problem |
|---|
| State |
Resolved |
|---|
| Resolution |
Rejected (REJ) |
|---|
| Problem Resolution ID |
REJ.AM.0002 |
|---|
| Raised |
2020-12-26 06:40 |
|---|
| Updated |
2021-01-20 12:39 |
|---|
| Published |
2021-01-20 12:39 |
|---|
| Product Standard |
ArchiMate 3 Tool |
|---|
| Certification Program |
ArchiMate Certified by The Open Group |
|---|
| Specification |
ArchiMate 3 Tools Conformance Requirements |
|---|
| Location in Spec |
version 1.0, February 2017, section 2.1.3 Relationship Support. |
|---|
| Problem Summary |
Approve proposal to mitigate Tool Certification deficiency to connect a
relationship to other relationships |
|---|
| Problem Description
|
Currently it is not possible within our modeling tool to connect relationships
with other relationships as required by the ArchiMate 3 Conformance
Requirements, version 1.0, February 2017, section 2.1.3 Relationship Support.
This deficiency was explicitly communicated in the ArchiMate Tool Certification
Checklist submitted to The Open Group with all other certification documents in
2018 and 2020. The tool nevertheless received the certification at both occasions.
Inspite of this, we would like to address any non-conformance and rectify this
deficiency the following way. We propose to introduce a connector object similar to
a junction to which relationships can be attached, thereby ?simulating? a
relationship being connected to another relationship.
The ArchiMate Model Exchange File Format export of the tool would take care of
converting such constructs into proper relationship-to-relationship entries within
the output file. Analogously the AMEFF import would create such constructs when
encountering relationship-to-relationship entries within the input file.
Please let us know as soon as possible if our proposal would sufficiently mitigate
the deficiency thereby keeping the ArchiMate 3.1 Tool Certificate for the tool. |
|---|
Review Information
| Review Type |
SA Review |
|---|
| Start Date |
2020-12-26 06:40 |
|---|
| Last Updated |
2021-01-19 17:06 |
|---|
| Completed |
2021-01-19 17:06 |
|---|
| Status |
Complete |
|---|
| Review Resolution |
Rejected (REJ) |
|---|
| Review Conclusion |
The ability to draw relationships to relationships is a requirement for conforming tools.
The proposed workaround introduces an element that does not exist in the ArchiMate language, which would cause confusion with the two Junctions and is not in line with the idea behind associations with relationships ? this is intended to relate some element to one single relationship, not two relationships broken up by an connector in the middle. If this alternate approach was intended then the language would have introduced another kind of junction.
With the proposed workaround you can not easily model for example that an object is transferred across a flow, since you will need to model two flows with this new connector in the middle and then interpret that as somehow continuous. Also how would this show up in other views of the same model that do not contain the object associated to the flow? How does it impact the analysis of models and the derivation rules? How do you make sure only allowable relationships between A and B can be ?split? by such a connector?
In summary this proposal is not conforming and issues arise which reinforce the need to reject this proposal as allowable behavior. |
|---|
Problem Reporting System Options:
|
|
|
|
|
