Integrating diverse paradigms in evolution and maintenance by an XML-based unified model

Journal of Software Maintenance and Evolution

Volumn 15, Issue 3, 2003, Pages 111-144

  Lu, Chih Wei ^a   Chu, William Cheng Chung ^b   Chang, Chih Hung ^a   Yang, Don Lin ^a   Lian, Wen Da ^b  

^a FENG CHIA UNIVERSITY   (Taiwan)

^b TUNGHAI UNIVERSITY   (Taiwan)

Author keywords

Life cycle; Model integration; Model unification; Ripple effects; Software meta models; Software models; XML

Indexed keywords

COMPUTER SOFTWARE; COSTS; ERROR ANALYSIS; XML;

MODEL UNIFICATION;

SOFTWARE ENGINEERING;

EID: 0042342530     PISSN: 1532060X     EISSN: None     Source Type: Journal    
DOI: 10.1002/smr.272     Document Type: Article

References (31)

1. Sommerville I. Software Engineering (5th edn). Addison-Wesley: Reading MA, 1996; 4-19.
2. Bennett KH. An overview of maintenance and reverse engineering. The REDO Compendium. Wiley: Chichester UK, 1993; 3-18.
3. Canfora G, Cimitile A. Software maintenance. Handbook of Software Engineering and Knowledge Engineering, vol. 1. Knowledge Systems Institute: Skokie IL, 2001; 91-120.
4. Booch G. Object-oriented Design with Applications. Benjamin/Cummings: Redwood City CA, 1991; 1-25.
5. ISO. Quality Systems - Model for Quality Assurance in Design/Development, Production, Installation, and Servicing, ISO9001 (rev. edn). International Organization for Standardization (ISO): Geneva Switzerland, 1994; 1-32.
6. ISO/IEC JTC1/SC7/WG10. Software Process Assessment - Part 5: An Assessment Model and Indicator Guidance (Ist PDTR). International Organization for Standardization (ISO): Geneva Switzerland, 1996; 1-138.
7. Jenner MJ. Software Quality Management and ISO 9001. Wiley: Chichester UK, 1995; 47-160, 223-234.
8. Software Engineering Institute (SEI). Software, Systems Engineering, and Product Development Capability Maturity Models® (CMMs®). Software Engineering Institute (SEI), Carnegie Mellon University: Pittsburgh PA, 2000, http://www.sei.cmu.edu/cmm/cmms/transition.html [27 January 2003].
9. Object Management Group. OMG Unified Modeling Language Specification, version 1.4. Object Management Group, Inc.: Needham MA, 2001, http://www.omg.org/technology/documents/recent/omg_modeling.htm [27 January 2003].
10. Anne CL. XML seen as integral to application integration. IT Professional 1999; 2(5):12-16.
11. Graham IS, Quin L. XML Specification Guide. Wiley: New York NY, 1999.
12. Gamma E, Helm R, Johnson R, Vlissides J. Design Patterns: Elements of Reusable Object-oriented Software. Addison-Wesley: Reading MA, 1995; 3-15.
13. Chu WC, Lu CW, Chang CH, Chung YC. Pattern based software re-engineering. Handbook of Software Engineering and Knowledge Engineering, vol. 1. Knowledge Systems Institute: Skokie IL, 2001; 767-786.
14. Holland I. The design and representation of object-oriented components. Doctorial dissertation, Northeastern University: Boston MA, 1993. Also available at PhD Theses (Northeastern University), http://www.ccs.neu.edu/home/lieber/theses-index.html [27 January 2003].
15. Johnson RE, Foote B. Designing reusable class. Journal of Object-Oriented Programming 1988; l(2):22-35.
16. Lano K, Malik N. Reengineering legacy applications using design patterns Proceedings of the 8th International Workshop on Software Technology and Engineering Practice - 1997, IEEE Computer Society Press: Los Alamitos CA, 1997; 326-338.
17. Meyer B. Tools for the new culture: Lessons from the design the Eiffel libraries. Communications of the ACM 1990; 33(9):68-88.
18. Ossher H, Kaplan M, Harrison W, Katz A, Kruskal V. Subject-oriented composition rules. Proceedings of the Object-Oriented Programming Systems, Languages and Applications Conference 1995, special issue of SIGPLAN Notices. ACM Press: New York NY, 1995; 235-250.
19. Paul S, Prakash A. Framework for source code search using program patterns. IEEE Transactions on Software Engineering 1994; 22(6):463-475.
20. Xiao C. Adaptive software: Automatic navigation through partially specified data structures. Doctorial dissertation, Northeastern University: Boston MA, 1994. Also available at PhD Theses (Northeastern University). http://www.ccs.neu.edu/home/lieber/theses-index.html [27 January 2003].
21. Moser S, Nierstrasz O. The effect of object-oriented frameworks on developer productivity. IEEE Computer 1996; 29(9):45-51.
22. Chapin N. Software maintenance life cycle. Proceedings Conference on Software Maintenance - 1988. IEEE Computer Society Press: Los Alamitos CA, 1988; 6-13.
23. Murphy GC, Notkin D, Sullivan KJ. Software reflexion models: Bridging the gap between design and implementation. IEEE Transactions on Software Engineering 2001; 27(4):364-380.
24. Cheng BHC, Campbell LA, Wang EY. Enabling automated analysis through the formalization of object-oriented modeling diagrams. Proceedings of the International Conference on Dependable Systems and Networks - 2000 (DSN 2000), IEEE Computer Society Press: Los Alamitos CA, 2000; 305-314.
25. Fyson MJ, Boldyreff C. Using application understanding to support impact analysis. Journal of Software Maintenance: Research and Practice 1998; 10(2):93-110.
26. Queille JP, Voidrot JF, Wilde N, Munro M. The impact analysis task in software maintenance: A model and a case study. Proceedings of the International Conference on Software Maintenance. IEEE Computer Society Press: Los Alamitos CA, 1994; 234-242.
27. Yau SS, Colleferro JS. Some stability measures for software maintenance. IEEE Transactions on Software Engineering 1980; 6(6):545-552.
28. Deitel H, Deitel P, Nieto T, Lin T, Sadhu P. XML How to Program. Prentice Hall: Upper Saddle River NJ, 2001; 1-9.
29. Suzuki J, Yamamoto Y. Making UML models exchangeable over the internet with XML: UXF approach. Proceedings of UML'98: Beyond the Notation - International Workshop. Springer: Heidelberg Germany, 1998; 65-74.
30. Holzmann GJ. The model checker SPIN. IEEE Transactions on Software Engineering 1997; 23(5):279-295.
31. Gunter CA, Gunter EL, Jackson M, Zave P. A reference model for requirements and specifications. IEEE Software 2000; 17(3):37-43.