ACM Home Page
Please provide us with feedback. Feedback
UML formalization is a traceability problem
Full text PdfPdf (205 KB)
Source Automated Software Engineering archive
Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineering table of contents
Long Beach, California
SESSION: Traceability techniques table of contents
Pages: 31 - 36  
Year of Publication: 2005
ISBN:1-59593-243-7
Authors
R. E. K. Stirewalt  Michigan State University, East Lansing, MI
Min Deng  Michigan State University, East Lansing, MI
Betty H. C. Cheng  Michigan State University, East Lansing, MI
Sponsors
SIGSOFT: ACM Special Interest Group on Software Engineering
SIGART: ACM Special Interest Group on Artificial Intelligence
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 4,   Downloads (12 Months): 65,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1107656.1107664
What is a DOI?

ABSTRACT

Largely driven by the widespread interest in using UML, significant efforts have investigated how to formalize its semantics in terms of well-defined target languages. Associating target language specifications with the UML models enables automated analysis of its many graphical diagrams. Unfortunately, UML formalizations have proved difficult to completely automate. This paper posits that UML formalization is essentially a traceability problem, which means to rigorously link elements of a given UML diagram to relevant regions of code in a given target model according to the intended formalization semantics. We present a graph-theoretic model for formally defining this link-retrieval problem. We also introduce a framework for assessing whether a UML formalization is amenable to efficient link retrieval techniques without sacrificing precision and/or recall.


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.

 
1
 
2
3
 
4
M. Deng, R. E. K. Stirewalt, and B. H. C. Cheng. Retrieval by construction: A traceability technique to support verification and validation of UML formalizations. International Journal of Software Engineering and Knowledge Engineering, Oct. 2005. to appear.
 
5
 
6
 
7
 
8
G. Holzmann. The SPIN model checker. Addison-Wesley Publisher, 2004.
9
 
10
S.-K. Kim and D. A. Carrington. A formal denotational semantics of UML in Object-Z. L'OBJET: Software, Databases, Networks, 7(1), 2001.
11
 
12
 
13
 
14
 
15
Object Management Group. UML Specifications, Version 1.5, March 2003. http://www.omg.org/uml.
 
16
Promela language reference. http://spinroot.com/spin/Man/promela.html.
 
17
S. W. Reyner. An analysis of a good algorithm for the subtree problem. SIAM Journal on Computing, 6(4):730--732.
 
18
 
19
 
20
 
21
 
22
M. C. Tanuan. Automated analysis of unified modeling language (UML) specifications. Master's thesis, Univ. of Waterloo, August 2001.
 
23
A. Zisman, G. Spanoudakis, E. Peres-Minana, and P. Krause. Tracing software engineering artifacts. In Proceedings of the 2003 International Conference on Software Engineering Research and Practice (SERP'03), 2003.

Collaborative Colleagues:
R. E. K. Stirewalt: colleagues
Min Deng: colleagues
Betty H. C. Cheng: colleagues