Conceivably, it can be used with various software methodologies. It should be stressed that UML is not a methodology, rather it is a language for expressing software models. It has been and is becoming increasingly used in industry and academia. That said, I consider it to be the best means available today for documenting object-oriented software development. Some critics consider that UML is a bloated diagramming language written by a committee. It achieved that goal in 1997 when the (international) Object Management Group (OMG) adopted it as a standard. One goal of UML was to reduce the proliferation of diagramming techniques by standardizing on a common modeling language, thus facilitating communication between developers. The methodologies followed a kind of cookbook style of pushing a software project through a succession of life cycle stages, culminating with a delivered and documented application. Prior to this time, these three amigos, along with about a dozen other practitioners had promoted competing methodologies for systematic software development, each with its own system of diagramming conventions. Introduction Unified Modeling Language (UML) was created in 1995 by merging diagramming conventions used by three software development methodologies: OMT by James Rumbaugh, Objectory by Ivar Jacobson and the Booch Method by Grady Booch. A simple tutorial on using rational rose and UML Michael M Werner 2003 All rights reserved
0 Comments
Leave a Reply. |