I'm thinking about using the UML 2 fragment type in my sequence diagrams because there are portions that are repeated between the use cases/sequence diagrams (4/5). Does anyone know if it's acceptable to create the referenced diagram (the common functionality) in a separate image file? The directions state "Create either a Sequence or Collaboration diagram for each use case provided." but this would mean there would be additional diagrams for the referenced portions (5 use cases, with ultimately ~7 sequence diagram images). Or does the UML 2 specification dictate that the referenced diagram be included (in a framed area) in the diagram that is including it (5 use cases and 5 diagram images)?
Kimo, there is no restriction saying you must provide one sequence diagram per use case. It's all about judgment. I have seen people who have passed SCEA with a few classes and diagrams, and others, more prolix, who have also passed the exam with a lot of classes and diagrams.
Remember that, in any case you have a feeling they will not understand your idea only with diagrams, you can make assumptions.
Kimo Kanaka Kanahele
Joined: Sep 18, 2011
I was just wondering about what the UML 2 specification might say about whether one can separate the diagrams. I have Miles' UML 2.0 (O'Reilly) but it doesn't mention anything that the ref fragment has to be on the same diagram as the one referencing it so I'm just guessing it's ok. I believe there are other restrictions for the ref fragment (like the lifeline(s) in the ref fragment has to be in the diagram referencing it). Perhaps it also depends on how strict the graders are on diagram correctness. I'm using Visual Paradigm which allows ref fragment types.
My assignment was made with MagicDraw, which was used by Sun to create domains and use cases and it also allows a separated sequence as a ref fragment. I don't know how VP deals with ref fragment, but I create ref fragments like a method, I mean, I draw a message coming from the border of left side, made my sequence fragment and, in the ending, I draw a reply message again to the border of left side, working as a result of a method. So, on my caller sequence, the ref fragment acted like a method.