Introduction to OMG's Unified Modeling Language (UML)

Large enterprise applications - the ones that execute core business applications, and keep a company going - must be more than just a bunch of code modules. They must be structured in a way that enables scalability, security, and robust execution under stressful conditions, and their structure - frequently referred to as their architecture - must be defined clearly enough that maintenance programmers can (quickly!) find and fix a bug that shows up long after the original authors have moved on to other projects. That is, these programs must be designed to work perfectly in many areas, and business functionality is not the only one (although it certainly is the essential core). Of course a well-designed architecture benefits any program, and not just the largest ones as we've singled out here. We mentioned large applications first because structure is a way of dealing with complexity, so the benefits of structure (and of modeling and design, as we'll demonstrate) compound as application size grows large. Another benefit of structure is that it enables code reuse: Design time is the easiest time to structure an application as a collection of self-contained modules or components. Eventually, enterprises build up a library of models of components, each one representing an implementation stored in a library of code modules. When another application needs the same functionality, the designer can quickly import its module from the library. At coding time, the developer can just as quickly import the code module into the application.

UML Resource Page (2005). Articles>Information Design>XML>UML

UML 3.0 and the Future of Modeling  

The major revision work for UML 2.0 is complete, and it is now an OMG Final Adopted Specification. This is a good time to reflect on UML's future, and the future of model-driven development.

Kobryn, Cris. UML Forum (2004). Articles>Information Design>XML>UML

A UML Primer  

This document covers key areas in UML (the Unified Modeling Language), such as Association, Multiplicity, Aggregation, Generalization and diagrams such as the Use Case diagram, Class Diagram, and Sequence Diagram.

Sundaram, Elango. Yahoo (2003). (Farsi) Articles>Information Design>XML>UML