Evaluation of UML for OOA/D

Abstract
Unified Modeling Language (UML) defines a standard notation for object-oriented systems. Using UML enhances communication between domain experts, workflow specialists, software designers and other professionals with different backgrounds. UML can be used on a general level, which is intuitive for the users of workflow systems. In spite of this, UML symbols also have defined semantics, which means that the visual workflow description can be used as a software specification. This position paper explains how to use UML for specification of workflow management systems, how to trace the description of business processes to the object-oriented software design and how to structure the project repository with UML deliverables. The Unified Modeling Language (UML) is a modeling language for specifying, visualizing, constructing, and documenting the artifacts of a system-intensive process. It was originally conceived by Rational Software Corporation and three of the most prominent methodologists in the information systems and technology industry, Grady Boochj James Rumbaugh, and Ivar Jacobson (the Three Amigos). The language has gained significant industry support from various organizations via the UML Partners Consortium and has been submitted to and approved by the Object Management Group (OMG) as a standard (November 17, 1997). UML provides a unique opportunity for tool development: by unifying the user community it increases the potential rewards from building powerful tools, and the fact that UML is a (comparatively) carefully defined language with a (comparatively) well developed notion of model consistency makes more exciting capabilities possible. Tools for UML are developing fast, but there is enormous scope for improvement; indeed the current market leaders have been described as "glorified drawing tools"
Description
Keywords
Citation
Collections