1. Software Engineering 1 Object-oriented Analysis and Design Chap 22 UML Tools and UML as Blueprint

2. Software Engineering 2 Object-oriented Analysis and Design Forward, Reverse, and Round-Trip Engineering  Forward engineering m the generation of code from diagrams;  Reverse engineering m generation of diagrams from code  Round-trip engineering m generation in either direction and can synchronize between UML diagrams and code, ideally automatically and immediately as either is changed.  All UML tools claim to support these features, but many are half crippled. m code isn't just declarations of variables, it's dynamic behavior. m If tool can generate a sequence diagram from the code, you can then much more easily follow the call-flow logic of the system to learn its basic collaborations.

3. Software Engineering 3 Object-oriented Analysis and Design Common Report of Valuable Features  the most consistent report of UML tool value m for reverse engineering, m as a visualization learning aid to understand existing code. m Generating UML package, class, and interaction diagrams from code and viewing the diagrams on a monitor, or printing them on large plotter paper,  More UML tools become well-integrated with text- strong IDEs (Eclipse, Visual Studio..), and their usability improves m more consistent value reported in using the tools for both forward and round-trip engineering.

4. Software Engineering 4 Object-oriented Analysis and Design Look For in a Tool  Choosing a UML tool m try a free UML tool. m try it on a real project with as many developers as possible, before making a decision. m Decide based on the guidance of your developers who have really used it for a long period. m integrates into your favorite text-strong IDE. m supports reverse engineering sequence diagrams from code. m Choose a tool that supports printouts to a plotter, on large plotter paper, in large font and diagram sizes, so that large- scale visualization is possible.

5. Software Engineering 5 Object-oriented Analysis and Design Update the Diagrams After Coding 1  If using a UML tool integrated with an IDE, working alone, and not doing wall sketching m synchronizing the diagrams is a simple reverse- engineering operation in the IDE.  If working with a small team and want to spend a modeling day each iteration at the whiteboards, applying UML as sketch. Consider this scenario: m At the start of a three-week time boxed iteration, there was a modeling day involving UML wall sketches. m This is followed by about three weeks of code and test. m it's time to start the next iteration's modeling day.

6. Software Engineering 6 Object-oriented Analysis and Design Update the Diagrams After Coding 2  if you wanted to do some wall sketching, based on the existing state of the code base. m Just before the modeling day, use a UML tool to reverse engineer the code into UML diagrams, package, class, and interaction diagrams. m for the most interesting ones, print them large on long plotter paper. Hang them relatively high in the modeling room on the walls m during the modeling day, developers can refer to them, sketch on top of them, and sketch below them on whiteboards or static cling sheets.