|
|||||||||||||||||||||
|
|||||||||||||||||||||
ABSTRACT
UML diagrams are used to model real-world ideas and help users understand complex programming concepts. Developers and writers need to produce well-formed UML diagrams that can convey these ideas, and that are suitable for publishing in technical documentation. This paper examines the evolution of UML diagrams and tooling, with a focus on practices at the IBM Toronto Software Laboratory. It reviews the findings of two previous papers, which described obstacles to creating UML diagrams for publication and outlined numerous steps to help developers, writers, and graphic designers create useful UML diagrams. It shows how developers at the IBM Toronto Software Laboratory have added new features to existing modeling programs to improve the usability and design functions in IBM's suite of modeling tools. It describes the relative strengths and weaknesses of the two main types of graphics, and illustrates the beneficial impact of the addition of the SVG graphic export function to IBM's tooling. It shows how these functional improvements have resulted in a higher quality of UML diagrams submitted for publication by both technical and non-technical users. REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references. INDEX TERMS
Primary Classification:
Additional Classification:
General Terms:
Keywords:
|
|||||||||||||||||||||