The UML is the current stop on the continuum of change in software development techniques.
The UML was created out of a storm of controversy over the best methodology to use to develop and specify software. Dozens of methods were and are in
use, each with a loyal following. Unfortunately, many of us were forced to choose between these warring factions and bear the overhead and frustration of
finding software tools and training.
In 1994, Grady Booch and James Rumbaugh, the two market share leaders in object-oriented (OO) software methods, formally joined forces to develop a
notation standard. A year later, they published the Unified Method version 0.8. Ivar Jacobson, yet another of the most noteworthy names in OO development,
joined the team.
The team of Rumbaugh, Booch and Jacobson were soon after referred to as the "three amigos" within OO circles.
At the same time, the Object Management Group (OMG) was establishing the Object-Oriented Analysis and Design OOA Task Force.
In June 1996, the task force issued a request for proposal (RFP) for a standardized metamodel and technology to support the exchange of CASE tool models.
This was an important first effort in developing a standard for specifying software systems and working toward an end to the notation wars plaguing our industry.
The RFP allowed only CASE tool vendors responsible for implementing the standard to sponsor proposals.
By October 1996, a number of leading CASE tool manufacturers
including IBM and Microsoft, had partnered with Rational Software to sponsor the UML proposal to the task force.
In November 1997, the OMG formally approved the UML version 1.1.
In the next lesson, the UML specification will be discussed.