12/20/2023 0 Comments Design sequence diagram![]() ![]() However, even though the notation supports it, we consider the practice of drawing flowcharts on sequence diagrams to be inadvisable, because it puts emphasis on the wrong part of the problem. UML 2.0 allows you to draw full-blown flowcharts on your sequence diagrams. The following diagram shows the sequence diagram notation (click the diagram for a larger version):ĭON’T TRY TO DRAW FLOWCHARTS ON SEQUENCE DIAGRAMS (FOCUS ON BEHAVIOR ALLOCATION INSTEAD) Just as you drew one robustness diagram per use case, you’ll also draw one sequence diagram per use case. There’s a direct link between each use case, its robustness diagram, and the sequence diagrams. But note that we advocate drawing your sequence diagrams in a minimal, quite specific format (which we describe fully in this chapter). You use sequence diagrams to drive the detailed design. Now it’s time to make those statements very precise, to turn them into a detailed design that works within the Technical Architecture that you’ve defined. With preliminary design, you made some informal first guesses at how the classes will interact with each other. When you draw sequence diagrams, you’re taking another sweep through the preliminary design, adding in detail. If you figure that preliminary design is all about discovery of classes (aka object discovery), then detailed design is, by contrast, about allocating behavior (aka behavior allocation)-that is, allocating the software functions you’ve identified into the set of classes you discovered during preliminary design. The two main diagram types used in detailed design are sequence diagrams (to allocate behavior to classes) and class diagrams (to record the allocated behavior and show a static overview of your design). Having completed robustness analysis and the PDR, you should now have discovered pretty much all of the domain classes that you’re going to need. In short, your use cases should be in a state where you can create a detailed design from them.Īll 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. Once you’ve finished robustness analysis, and you’ve held a preliminary design review, it’s time to begin the detailed design effort. This page is an excerpt from Chapter 8 of Use Case Driven Object Modeling with UML – Theory and Practice. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |