Introduction to the Unified Modeling Language
The first five articles form a 5 part mini-series introducing UML
to Java developers published on www.informit.com
This is followed by articles on the UML 2.1. I use UML
all the time as it is the best general purpose modelling notation for
software systems available. However, there are things about it I'd like
to change and one or two of them are discussed below.
- A Picture Can Save a Thousand Words: UML Class Diagrams and
Java
A gentle introduction to UML and object modeling from a Java programmer's perspective. Although it's tempting to spend time considering the history and philosophy behind UML, let's get straight down to business and look at how UML represents classes; we can do historical and philosophical stuff as we go.
Read the full article...
- Inheritance and Interfaces in Java and UML
This article considers the two 'I's of UML class diagrams: inheritance and interfaces.
Read the full article...
- Just Typical: UML Stereotypes and Class Archetypes
In this article, we start from the opposite end and look at the effect a UML mechanism has on the way we work with our code.
Read the full article...
- Getting Dynamic: Java and UML Interaction Diagrams
In this article, we move on to consider another type of UML diagram: the interaction diagram.
Read the full article...
- More Symbols, More Diagrams, More UML - Beyond Class and Interaction Diagrams
Other types of diagrams defined in the UML specification may be less directly related to Java source code than the more glamorous class and interaction diagrams, but your UML toolkit is incomplete without them.
Read the full article...
- Names of Model Elements in UML Models
UML modeling tools should always enable a user to choose between tight compliance with the UML specification, or compliance with common sense and ease of use where the two occasionally diverge.
Read the full article...
- Descriptions of Model Elements in UML 2.1 Models
The different types of model elements in the UML 2.1 specification do not have a description property. Initially this looks like an obvious oversight because a textual description is one of the key bits of information of most elements in a model. It would be unthinkable to have classes or components in any serious model without descriptions.
Read the full article...
- Is UML out of date?
When UML was created from various methods and notations, the most popular OO languages were Smalltalk and C++. Java was just starting to appear on the horizon. In many ways, the core concepts within UML reflect this situation by mirroring the core concepts in Smalltalk and C++ at that time. Over the last few years, additional concepts have been made more explicit in languages such as Java, Eiffel and C#. UML has needed to be extended to handle these concepts or has left it to 'convention between the user and any modeling tools and code generators'.
Read the full article...