Java™ Application Development on Linux - Dator

12.7 Analysis Paralysis287• Class Diagram• Sequence Diagram• Collaboration Diagram• Use Case Diagram• Activity Diagram• Component Diagram• Deployment DiagramUsing the simple but effective technique of CRC cards can be a good placeto start, but you may soon want to move up the OOA/OOD ladder to use toolslike Umbrello 6 to make UML diagrams, and perhaps to use the whole UMLtoolset. 7 Many organizations that we know of will pick and choose varioustechniques and tools. No matter how far down the road of formal software engineeringyou go, you must at least make some effort to have a repeatableprocess that incorporates continuous improvement.12.7ANALYSIS PARALYSISThe catchy phrase “analysis paralysis” has become a cliché. (And how could itnot, being so catchy?) What it refers to, of course, is the tendency to becomebogged down in details; or the tendency to refuse to start implementation untilyou are certain that your design is “right.”This is where using a “spiral” development model can pay off. By doingfrequent small releases, you can expose subtle design flaws at an earlier stage indevelopment. Often, you can (to trot out another trendy term) “refactor” asmall part of your design or implementation. If you have clean object interfaces,this can often be done with minimal disruption because a good object modelhides implementation details within classes.In most cases it is best, once you have the use cases and requirements, toproceed to a prototype object model and learn by doing.6. http://uml.sourceforge.net/index.php7. http://www.uml.org/