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.
Case Driven Object Modeling - This is what I have beens saying for the past 5 years to my Colleagues and co-working Engineers: 'Visually define Behavior and Allocation of your Objects and Classes so the next person who looks at your Design / Procedures and Code can easily and quickly understand what you are trying to do and what were "your" state of mind when you designed what you did.' But I guess, at least most of us, are either too lazy to add this one extra step to our software cycle or we are looking for job security. The harder the code is to understand the more job security we have with the company that we work for.
No comments:
Post a Comment