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

Secure remote control for conventional and virtual desktops

More from The Register

next story
UNIX greybeards threaten Debian fork over systemd plan
'Veteran Unix Admins' fear desktop emphasis is betraying open source
Netscape Navigator - the browser that started it all - turns 20
It was 20 years ago today, Marc Andreeesen taught the band to play
Redmond top man Satya Nadella: 'Microsoft LOVES Linux'
Open-source 'love' fairly runneth over at cloud event
Return of the Jedi – Apache reclaims web server crown
.london, .hamburg and .公司 - that's .com in Chinese - storm the web server charts
Chrome 38's new HTML tag support makes fatties FIT and SKINNIER
First browser to protect networks' bandwith using official spec
Admins! Never mind POODLE, there're NEW OpenSSL bugs to splat
Four new patches for open-source crypto libraries
prev story

Whitepapers

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.
Cloud and hybrid-cloud data protection for VMware
Learn how quick and easy it is to configure backups and perform restores for VMware environments.
Three 1TB solid state scorchers up for grabs
Big SSDs can be expensive but think big and think free because you could be the lucky winner of one of three 1TB Samsung SSD 840 EVO drives that we’re giving away worth over £300 apiece.
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.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.