Hi how would one careate a sequence diagram for a usecase A that extends another usecase B. Can we just include the related objects of usecase B in sequence diagram of usecase A Thanx
Joined: Oct 27, 2002
Hi, For Readability, I would put the extended use case in a separate diagram and refer to the other diagram with a note. In Rose you can link the other diagram through the note. Communication is the key. If the sequence diagram gets too complex to communicate well than find a better way to communicate your ideas. Also, avoid repeating the same sequence in every diagram.... for example the logon sequence which can be accomplished at different places in systems.
I saw a lot of messages here talking about seperate a big sequence diagram into 2 or more diagrams. And some guys talk about "Notes" to connect the diagrams together. But, I wander how it can be. Say, I have a big sequence diagram. If I divid it into 2 diagram. There would be many "message" line between these 2 diagram. And, how can I put the information in those diagrams?
Joined: Sep 18, 2003
Can somebody explain how we can draw(using rational rose) alternate scanerios in the sequence diagram and how to show change of focus of control from one sequence diagram to another.. Appreciate your response. Thanks,