Skip to main content


developerWorks  >  Rational | Sample IT projects  >

Exposing design flaws in your code: Part 2, Architectural discovery

developerWorks

Level: Intermediate

David Bridgewater (dbridgewater@jbridge.co.uk), Java/WebSphere Trainer, Studio B

15 Aug 2005

Register now or sign in using your IBM ID and password.

Learn how to identify design problems in your code with the architectural discovery tools in IBM Rational Software Architect. This second tutorial in a two-part series uses a sample Java 2 Platform, Enterprise Edition (J2EE) application to show you how to use architectural discovery to visualize design problems in your code.

Prerequisites

Some familiarity with Java and J2EE programming is assumed. This tutorial does involve some optional programming elements. However, the main focus is on showing how you can use Rational Software Architect to identify and diagnose bad design techniques. This tutorial also assumes that you have reasonable familiarity with Unified Modeling Language (UML) -- in particular, class diagrams.

Exposing design flaws in your code, Part 1: Code review


System requirements

To complete the steps in this tutorial, you need:

  • Rational Software Architect. You can download a trial version at no charge.
  • AntiPatternWeb2.zip (included with the tutorial).


Duration

Under one hour


Formats

html, pdf


Share this....

digg Digg this story del.icio.us del.icio.us Slashdot Slashdot it!


Back to top


Document options

Document options requiring JavaScript are not displayed


My developerWorks needs you!

Connect to your technical community