Feeds

Sequence diagramming that's fit for purpose

Illustrate your point

Choosing a cloud hosting partner with confidence

Book extract, part 4 In this, the final part of our series of experts from Use Case Driven Object Modeling with UML: Theory and Practice Matt Stephens and Doug Rosenberg show you how to draw lean, purposeful sequence diagrams that are driven from the use cases and preliminary design.

As before, this chapter opens with the following "you are here" diagram of the ICONIX Process, showing in red the area about to be covered.

Iconix Process sequence diagram

Mapping sequence and behavior

All the steps in the process so far have been preparing the use cases for the detailed design activity. By this time, your use case text should be complete, correct, detailed, and explicit. In short, your use cases should be in a state where you can create a detailed design from them.

If you figure that preliminary design is all about object discovery, then detailed design is, by contrast, about behavior allocation - that is, allocating the software functions you've identified into the set of classes you discovered during preliminary design.

When you draw sequence diagrams, you're taking another sweep through the preliminary design, adding in detail. You use sequence diagrams to drive the detailed design. We advocate drawing your sequence diagrams in a minimal style.

Here is our final 10-point checklist for successful sequence diagramming. As with all our lists, pay attention because there will be questions:

Top 10 sequence diagramming guidelines

10. Clean up the static model before proceeding to the next step

9. "Prefactor" your design on sequence diagrams before coding

8. Review your class diagrams frequently while you're assigning operations to classes, to make sure all the operations are on the appropriate classes

7. Assign operations to classes while drawing messages. Most visual modeling tools support this capability

6. Don't spend too much time worrying about focus of control

5. Make sure your use case text maps to the messages being passed on the sequence diagram. Try to line up the text and message arrows.

4. Use the sequence diagram to show how the behavior of the use case is accomplished by the objects

3. Start your sequence diagram from the boundary classes, entity classes, actors, and use case text that result from robustness analysis

2. Do a sequence diagram for every use case, with both basic and alternate courses on the same diagram

1. Understand why you're drawing a sequence diagram, to get the most out of it

Providing a secure and efficient Helpdesk

More from The Register

next story
Preview redux: Microsoft ships new Windows 10 build with 7,000 changes
Latest bleeding-edge bits borrow Action Center from Windows Phone
Google opens Inbox – email for people too thick to handle email
Print this article out and give it to someone tech-y if you get stuck
Microsoft promises Windows 10 will mean two-factor auth for all
Sneak peek at security features Redmond's baking into new OS
UNIX greybeards threaten Debian fork over systemd plan
'Veteran Unix Admins' fear desktop emphasis is betraying open source
Entity Framework goes 'code first' as Microsoft pulls visual design tool
Visual Studio database diagramming's out the window
Google+ goes TITSUP. But WHO knew? How long? Anyone ... Hello ...
Wobbly Gmail, Contacts, Calendar on the other hand ...
DEATH by PowerPoint: Microsoft warns of 0-day attack hidden in slides
Might put out patch in update, might chuck it out sooner
prev story

Whitepapers

Choosing cloud Backup services
Demystify how you can address your data protection needs in your small- to medium-sized business and select the best online backup service to meet your needs.
Forging a new future with identity relationship management
Learn about ForgeRock's next generation IRM platform and how it is designed to empower CEOS's and enterprises to engage with consumers.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.
Storage capacity and performance optimization at Mizuno USA
Mizuno USA turn to Tegile storage technology to solve both their SAN and backup issues.