Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

In the below Sequence diagram, when the user have entered the Username and Password, I have to do the authentication. Now you can see two details valid details and invalid detail in the diagram , which i will return when the user password match and miss-match respectively.

Now My big question is which one i have to draw first, either valid details or invalid detail, how I know which one will come first.

share|improve this question
add comment

2 Answers

up vote 2 down vote accepted

Neither. I would likely put them on different diagrams. The sequence diagram is supposed to represent a single flow of execution through your design, and these are two different flows.

If you are worried now that you have to duplicate the diagram, and it would be more efficient to represent both you would be right - but remember that your UML will not be compiled - it does not need to represent everything your program does.

Ask yourself why you are drawing this. It is a tool to help describe ( or explore ) your design - you only need to diagram the things that you need to explore, and in many cases it is just the complex flows.

share|improve this answer
    
Ya your correct! I thought of adding it as an separate diagram. but now will do that –  Ant's Apr 7 '11 at 15:21
    
I disagree with your single flow of execution statement. IMO a sequence diagram is used to communicate the flow of an operation in your system. There is a reason why Sequence Diagrams have Combined Fragments, which is to show the alternative paths. Why would you want that flow spread out across a bunch of separate diagrams when they can be shown in a single diagram? –  Dunk Apr 7 '11 at 17:03
    
I am no UML expert, and don't doubt that there is notation for it, but in practical terms what value you will get out of it. For simple flows like the one above I can understand the notation - but then again for simple flows like that I would never draw a diagram, it feels like over documentation. For more complex flow, the split would create too many lines and remove the value of the diagram to explain a concept. Even in the simple basic guide ibm.com/developerworks/rational/library/3101.html it looks more complex that I would like. But perhaps it is just the way I would use it? –  Stephen Bailey Apr 7 '11 at 18:54
add comment

IMHO it is similar to which order you handle this in code in an if/else branch. In general I prefer handling the common case first (i.e. the valid details in this case), as this makes the code more readable.

But overall on a sequence diagram it doesn't make much difference - do it the way it feels more natural to you (IMHO drawing branches, loops etc. on a sequence diagram is unnatural and ugly enough any way :-).

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.