3.2.1.
ArgoUML shall be a correct implementation of the UML 1.4 model.
REQ5 REVa
Rationale:
The vision of ArgoUML is to provide a tool that helps people
work with an UML model.
The UML model might later on be used in some other tool.
If the implementation is not correct then ArgoUML will not be
compatible with that other tool or the user will be confused.
There might be a lot of tough decisions when it comes to
if it is ArgoUML or some other tool that deviates from the UML 1.4
but there shall never be any doubt that the intention of ArgoUML
is to implement UML correctly.
Stakeholder:
User of ArgoUML
3.2.2.
ArgoUML shall implement everything in the UML 1.4 model.
REQ6 REVa
Rationale:
The ambition is to implement all of UML.
This means that no matter how you use UML ArgoUML will always be
a working tool.
Stakeholder:
User of ArgoUML
3.2.3.
About enforcement of well-formedness rules from the UML standard.
REQ15 REVa
WFR = Well-Formedness Rule. This matter was discussed in
the dev list, in the thread following
"http://argouml.tigris.org/servlets/ReadMsg?list=dev&msgNo=20622".
1. Critics shall warn for any WFR violations
(a critic for every WFR would be ideal).
2. Generally, ArgoUML shall not enforce WFRs, except in certain cases.
3. In such cases (where we enforce a WFR) we shall
a. document this case, and
b. be consistent about it.
4. Even if a WFR is enforced, ArgoUML shall still be able
to deal with a model that breaks it.
Rationale:
since we can load a XMI that breaks the WFR.
Stakeholder:
User of ArgoUML
