ACM Home Page
Please provide us with feedback. Feedback
A case study on the application of UML in legacy development
Full text PdfPdf (327 KB)
Source International Symposium on Empirical Software Engineering archive
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering table of contents
Rio de Janeiro, Brazil
SESSION: Software design table of contents
Pages: 124 - 133  
Year of Publication: 2006
ISBN:1-59593-218-6
Authors
Bente Anda  Simula Research Laboratory, Lysaker, Norway
Kai Hansen  ABB Corporate Research Center, Billingstad, Norway
Sponsors
ACM: Association for Computing Machinery
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 19,   Downloads (12 Months): 151,   Citation Count: 2
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

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

ABSTRACT

Model-driven development with UML is becoming a de facto standard in industry, but although much of today's software development is about enhancing existing systems, there is no welldefined process for model-driven development in the context of legacy systems. To ensure the relevance of research on modeldriven development with UML, there is a need for studies of actual use of UML in software development companies. As part of a software process initiative, we conducted a case study in a large development project where some of the development teams enhanced existing components, while other teams developed software from scratch. The results from this case study showed that those who applied UML in modelling and enhancing legacy software experienced more challenges and fewer benefits from the use of UML than did the developers who modelled and developed new software. Overall our results show a need for better methodological support on applying UML in legacy development.


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
Arisholm, E., Briand, L.C., Hove, S.E. and Labiche, Y. The Impact of UML Documentation on Software Maintenance: An Experimental Evaluation, IEEE Transactions on Software Engineering,Vol. 32, No. 6, pp. 365--381, 2006.
 
4
Baker, P., Loh, S. and Weil, F. Model-Driven Engineering in a Large Industrial Context -- Motorola Case Study. In L. Briand and C. Williams (Eds.) in MoDELS 2005, LNCS 3713, pp. 476--491, Springer-Verlag, 2005.
 
5
6
 
7
 
8
 
9
IEC 61508: Functional safety of electrical/electronic/programmable electronic safety-related systems, (http://www.iec.ch/),1998.
 
10
 
11
 
12
Otero, M.C. and Dolado, J.J. Evaluation of the comprehension of the dynamic modeling in UML. Information and Software Technology, Vol. 46, pp. 35--53, 2004.
 
13
Pettit, R.G. Lessons Learned Applying UML in Embedded Software Systems Designs. Proceedings of the Second IEEE Workshop on Software Technologies for Future Embedded and Ubiquitous Systems (WSTFEUS'04), pp. 75--79, Vienna, Austria, May 11-12, 2004.
 
14
 
15
 
16
Yin, R. Case Study Research: Design and Methods. 3rd edition. SAGE Publications, Inc., Thousand Oaks, CA, 2003.