Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: Lanrets on August 25, 2022, 05:15:46 pm
-
Hello :-)
I'm new to EA and I struggle with adding requirement to a sequence diagram.
Is it possible?
-
I don't think so (since they are elements). You can add notes that refer to requirements or probably drag a requirements diagram onto a SD. Needs experiments...
q.
-
Dragging creates class role, which is not a desired solution.
Yes, note is a workaround which I'm currently using, but it's not robust...
-
Model requirements with use case diagrams. Sequence diagrams show how you meet the requirement, not what the requirement is.
I append my sequence diagrams to the requirement use case and use the same name for the use case and the sequence diagram.
-
Basically that's also what I do. However, I think that placing a requirement on any diagram (including SD) should be possible. I have no idea whether there is a limitation per UML spec. (If so, EA would be wrong otherwise in allowing the use of classes as lifelines.)
q.
-
I have no idea whether there is a limitation per UML spec.
UML doesn't even have requirements.
SysML requirements are stereotyped classes.
(If so, EA would be wrong otherwise in allowing the use of classes as lifelines.)
My personal view is that classes as lifelines is wrong according to UML. Unfortunately our users have a strong history of objecting to us removing wrong functionality. Even with that view I can't see a way we can remove that functionality without negatively impacting users.
-
My personal view is that classes as lifelines are wrong according to UML. Unfortunately, our users have a strong history of objecting to us removing wrong functionality. Even with that view, I can't see a way we can remove that functionality without negatively impacting users.
To paraphrase "Animal Farm", All users are unreasonable, but some are more unreasonable than others. If the "wrong" functionality were conditionalised, those of us who agree with you could disable it and not allow classes to be lifelines.
Just a thought,
Paolo
-
Similar to the connector syntax checking this could be one more flag in the option jungle. Per default this should be unchecked when labeled "Allow classes in SDs (likely to break your model when using XMI ex/import)". There is only one hint in the help about that (and I can't remember where). Living with inconsistencies is possible. But it will hurt. And you may eventually suffer death.
q.