UML
Home ] Access - Start Here ] Excel In Depth ] MS Office ] Visio Info ] Creating Web Pages ] Technical References ] Viruses ] Points of View ] Gadgets ] Just Links ] Monash ]

   Search this site or the web       powered by FreeFind
 
  Site search Web search

Participate in Ananda's Discussions
Post a message

Monitor page
for changes
    
   it's private  

by ChangeDetection

Up

What is UML?

UML stands for Unified Modelling Language. At the UML Resource Center, it's described thus:

The Unified Modeling Language™ (UML) is the industry-standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems. It simplifies the complex process of software design, making a "blueprint" for construction. UML is the trademark of the Object Management Group.

UML came about from the work of "the Three Amigos" - Grady Booch, James Rumbaugh, Ivar Jacobson. They all work for Rational Software Corporation.

It's a relatively new language, the first specification was published in 1997. The latest specification is Version 1.3

Although it is called a language, it's very visual - UML is fleshed with diagrams. There are ten:

  1. Activity Diagrams
  2. Class Diagrams
  3. Collaboration Diagrams
  4. Component Diagrams
  5. Deployment Diagrams
  6. Object Diagrams
  7. Package Diagrams
  8. Sequence Diagrams
  9. State Diagrams
  10. Use Case Diagrams

Why am I interested?

For a long time, I've made up Access development and web development work in my head. Sometimes, when things are a bit complex, I write out sequences and draw my own simple diagrams. However, nothing that I have made up for myself is global enough as a standard. UML holds great promise in achieving the following goals:

  • Working as a brainstorming / initial interview tool using rough paper and pen drafts when I meet and work with the clients.
  • Working as a formal diagramming tool for verifying with the client that major facets of the project, and prompting both the client and myself for features that have not been understood clearly.
  • Working as a formal modelling tool to document and analyse how a system responds to events i.e. how the thing should work. Keen users may still be in there contributing but it is sufficient that the developer(s) can display what their knowledge and understanding is, of the project.

What Software Tools are available?

What References are available?

Online Articles

Paper Books