UML with VS 2010 Part 7: Sketching Interactions with Sequence Diagrams

Play UML with VS 2010 Part 7: Sketching Interactions with Sequence Diagrams
Sign in to queue


In this screencast, Clint Edmonson provides an introduction to UML sequence diagrams and how use cases can be used to drive them.



Download this episode

The Discussion

  • User profile image

    Thank you for choosing MVC as your example Big Smile


    PS. When you alt+tab... how did you get the task switcher to show the big preview?

  • User profile image

    It's a third party tool called Vista Switcher:

  • User profile image

    Hi Saumitra,

    • It's not that I haven't used the same actors. My example simply stopped short of creating designs that involve them all. But you are correct - as iterations progress and designs are created, more of the actors from the analysis will show up in the design model. If these two diverge, it's likely that the use cases are not driving design and implementation during your iterations. Having said that, unless you're following a "model as documentation" strategy, maintaining tight synchronization should not be a primary worry. If you are, I recommend integrating design steps/states into your work items pipeline. Also, using two different modeling projects is NOT the only way to do modeling. It's simply the way I was brought up. I've met teams that use a single modeling project and avoid any worry about design divergence and teams that use separate modeling projects for their layers and/or subsystems.
    • All diagrams and almost every model element can be associated with a work item via a right-click menu. This would let you use work items to link all the artifacts for a feature with full traceability.
  • User profile image
    George Perry

    Your UML with VS 2010 videos series have been extremely helpful, thanks.
    I'm working on an Application Architecture,layerdiagram for a project that also includes a User actor (webclient) and an Administrator actor (WindForm application) similar to the example you used in the videos. However I would like to fully include the administrator as part of my solution because many of his Business and data Access layer components are the same. The question is, I'm not sure how to represent this in my Application layer diagram. In your example you simply connected the administrator (outside of the grey webserver layer) directly to the database layer. In my case, I was thinking off connecting the pink administrator layer to a blue administrator presentation layer, and connect this into the business layer of the webserver. Would this be considered bad practice?

  • User profile image

    @George Perry: I recommend repesenting the admin user interface as a separate UI layer and giving it the same dependencies on BL and data layers, if that's how you intend to code it.

Add Your 2 Cents