UML with VS 2010 Part 7: Sketching Interactions with Sequence Diagrams (Channel 9)

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

Posted: Jul 28, 2010 at 12:04 PM

By: Clint Edmonson

(4)

13,609 Views

5 Comments

14 minutes, 14 seconds

Download

Right click “Save as…”

High Quality WMV (PC, Xbox, MCE)
MP4 (iPod, Zune HD)
Mid Quality WMV (Lo-band, Mobile)

format
< > embed
+ queue

Sign In first to access your queue.
Close

Sorry, video was not added to the queue, an error occurred. Please Contact Us and let us know.
Close

Embed code for this video

Copy the code above to embed our video on your website/blog.

Video format

Auto
Use our suggested format for this video.
Smooth Streaming
Adaptive bitrate streaming - little buffering but lower video quality at times of low bandwidth.
Progressive
Traditional buffered video format.
HTML5
For browsers that support h264 MP4 or WebM video playback such as:
IE9+, Chrome 5+, or Safari 4+.

Note: These selections will fall back to the next best format depending upon browser capability.

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

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.

Follow the Discussion

Subscribe to these comments

samov

Aug 12, 2010 at 6:41 AM quote reply

Thank you for choosing MVC as your example

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

Aug 13, 2010 at 8:51 AM quote reply

It's a third party tool called Vista Switcher: http://www.ntwind.com/software/vistaswitcher.html
clinted Clint Edmonson
Sep 02, 2010 at 7:47 AM quote reply
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.
George Perry

Jan 20, 2011 at 2:17 AM quote reply

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?
clinted Clint Edmonson

Jan 25, 2011 at 1:34 PM quote reply

@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.

Remove this comment

Remove this thread

Comments Closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.