Implementation of a Function-Based Navigation Tool for Facilitating the Analysis of UML Design Document

Abstract:

System developers often create design documents using various UML design tools. Extant tools, however, have a serious drawback. They fail to capture relationships inherently existing among design documents such as sequence, state and class diagrams. This drawback may not only disallow developers to freely navigate the relationships, but also make it difficult to automatically enforce the integrity constraints derived from the relationships. To overcome this, more sophisticated tools for facilitating the analysis of the documents are necessary. These tools may be used to understand and verify the whole process of the system by defining relationships between documents and providing efficient navigation methods. In this paper, we developed a navigation tool that enables developers to systematically analyze systems by capturing relationships such as duplication, instance, and transition between documents. In contrast with the navigation facilities of other UML design tools, this tool makes it possible to navigate not only design documents but also design elements. In other words, it can systematically capture and verify both the static structure and the dynamic behavior of the system in more primitive level. To provide such a facility, we addressed the practical issues and formulated a solution for them. The issues that were mainly discussed were the following: 1) definitions of three relationships: duplication, instance, and transition, 2) assignment of relationships to related design elements according to the predefined way, and 3) presentation of a set of functions to navigate them.

• Periodical: Key Engineering Materials (Volumes 277-279)
• Pages: 266-271
• DOI: https://doi.org/10.4028/www.scientific.net/KEM.277-279.266
• Online since: January 2005
• Authors: Won Jung Kim, Myung Nam Bae, Jae Dong Yang, Hyung Jeong Yang
• Keywords: Design Document, Navigation, Relationship, Transition, UML

References

[1] Argo/UML v0. 7: The Cognitive CASE Tool, http: /argouml. tigris. org/, University of California, Irvine, (1999).

[2] Bock, Conrad. and Odell, James, A More Complete Model of Relations and Their Part I: Relations as Object Types, Journal Of Object-Oriented Programming, Vol 10, No 3, pp.38-40, June (1997).

[3] Bock, Conrad. and Odell, James, A More Complete Model of Relations and Their Implementation, Part II: Mappings, Journal Of Object-Oriented Programming, Vol. 10, No 6, pp.28-30, October 1998. Title of Publication (to be inserted by the publisher).

[4] Bock, Conrad. and Odell, James, A More Complete Model of Relations and Their Implementation, Part III: Roles, Journal Of Object-Oriented Programming, Vol 11, No 2, May (1998).

[5] Kohler, Hans J., Ulrich Nickel, Jorg Niere, Albert Zundorf, Integrating UML Diagrams for Production Control Systems, Proceedings of the 2000 International Conference on Software Engineering, pp.241-251, (2000).

DOI: 10.1109/icse.2000.870415

[6] Rational Soft, Corp, Rational Rose 2002, http: /www-3. ibm. com/software/rational.

[7] Robbins, J. E. and Redmiles, D. F., Cognitive support, UML adherence, and XMI interchange in Argo/UML, Information and Software Technology, Volume 42, Issue 2, pp.79-89, 25 January (2000).

DOI: 10.1016/s0950-5849(99)00083-x