Advertisement

Odyssey-CCS: A Change Control System Tailored to Software Reuse

  • Luiz Gustavo Lopes
  • Leonardo Murta
  • Cláudia Werner
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4039)

Abstract

Software is constantly changing and these changes may occur at anytime in the software lifecycle. In order to avoid rework and information loss, among other problems, these changes must be controlled in a proper way. When changes affect reused components, possibly composed by other components, it is important to know who is responsible for implementing them. Some consequences of this problem, named Reuse Chain of Responsibility, is the misconception on rights and duties of teams that produce and reuse compo-nents. Aiming to solve this problem, we introduce Odyssey-CCS, a flexible change control system that allows the customization of a change control process to the specific needs of software reuse. Moreover, it keeps a reuse map that holds information about contracts between components producers and reusers. The reuse map is integrated to an existing component library and is queried by Odyssey-CCS within the impact analysis activity.

Keywords

Process Enactment Object Management Group Software Maintenance Template Modeling Software Reuse 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Atkinson, C., Bayer, J., Bunse, C., Kamsties, E., Laitenberger, O., Laqua, R., Muthig, D., Peach, B., Wust, J., Zettel, J.: Component-Based Product Line Engineering with UML. Addison-Wesley, Reading (2001)Google Scholar
  2. 2.
    Atlassian: JIRA - Bug tracking, issue tracking and project management software (accessed February 01, 2006), http://www.atlassian.com/software/jira/docs/latest/
  3. 3.
    Barnson, M.P., Steenhagen, J.: The Bugzilla Guide - 2.17.5 Development Release. The Bugzilla Team (2003)Google Scholar
  4. 4.
    Braga, R.M.M., Werner, C.M.L., Mattoso, M.: Odyssey-Search: A multi-agent system for component information search and retrieval. Journal of Systems and Software 79(2), 204–215 (2006)CrossRefGoogle Scholar
  5. 5.
    Brown, A.W.: Large Scale Component Based Development. Prentice Hall PTR, Englewood Cliffs (2000)Google Scholar
  6. 6.
    Cheesman, J., Daniels, J.: UML Components: A Simple Process for Specifying Component-Based Software. Addison-Wesley, Reading (2000)Google Scholar
  7. 7.
    CMCrossroads: Defect Tracking Software (accessed February 01, 2006), http://resources.cmcrossroads.com/cmcrossroads/search/browse/1715/1715.jsp
  8. 8.
    Conradi, R., Fuggetta, A., Jaccheri, M.L.: Six Theses on Software Process Research. In: Gruhn, V. (ed.) EWSPT 1998. LNCS, vol. 1487, pp. 100–104. Springer, Heidelberg (1998)CrossRefGoogle Scholar
  9. 9.
    D’Souza, D., Wills, A.: Objects, components, and frameworks with UML: The catalysis approach. Addison Wesley, Reading (1998)Google Scholar
  10. 10.
    Dantas, C.R., Murta, L.G.P., Werner, C.M.L.: Consistent Evolution of UML Models by Automatic Detection of Change Traces. In: International Workshop on Principles of Software Evolution (IWPSE), Lisbon, Portugal, September 2005, pp. 144–147 (2005)Google Scholar
  11. 11.
    Estublier, J., Leblang, D., Clemm, G., Conradi, R., Tichy, W., van der Hoek, A., Wiborg-Weber, D.: Impact of the research community on the field of software configuration management: summary of an impact project report. ACM SIGSOFT Software Engineering Notes 27(5), 31–39 (2002)CrossRefGoogle Scholar
  12. 12.
    Flashline: Flashline Registry (accessed March 28, 2006), http://www.flashline.com
  13. 13.
    IEEE: Std 1219 - IEEE Standard for Software Maintenance. Institute of Electrical and Electronics Engineers (1998)Google Scholar
  14. 14.
    IEEE: Std 828 - IEEE Standard for Software Configuration Management Plans. Institute of Electrical and Electronics Engineers (2005)Google Scholar
  15. 15.
    ISO: ISO 10007, Quality Management - Guidelines for Configuration Management. International Organization for Standardization (1995) Google Scholar
  16. 16.
    Kwon, O., Shin, G., Boldyreff, C., Munro, M.: Maintenance with Reuse: An Integrated Approach Based on Software Configuration Management. In: Asia Pacific Software Engineering Conference, Takamatsu, Japan, December 1999, pp. 507–515 (1999)Google Scholar
  17. 17.
    LogicLibrary: Logidex (accessed March 28, 2006), http://www.logiclibrary.com
  18. 18.
    Mantis: Mantis Bug Tracker (accessed March 28, 2005), http://www.mantisbt.org
  19. 19.
    Mili, A., Mili, R., Mittermeir, R.T.: A survey of software reuse libraries. Annals of Software Engineering 5(0), 349–414 (1998)CrossRefGoogle Scholar
  20. 20.
    Morisio, M., Ezran, M., Tully, C.: Success and Failure Factors in Software Reuse. IEEE Transactions of Software Engineering 28(4), 340–357 (2002)CrossRefGoogle Scholar
  21. 21.
    Oliveira, H.L.R., Murta, L.G.P., Werner, C.M.L.: Odyssey-VCS: a Flexible Version Control System for UML Model Elements. In: International Workshop on Software Configuration Management, Lisbon, Portugal, September 2005, pp. 1–16 (2005)Google Scholar
  22. 22.
    OMG: Meta Object Facility (MOF) Specification, version 1.4. Object Management Group (accessed February 01, 2006), http://www.omg.org/technology/documents/formal/mof.htm
  23. 23.
    OMG: Software Process Engineering Metamodel (SPEM), Version 1.1. Object Management Group (accessed February 01, 2006), http://www.omg.org/technology/documents/formal/spem.htm
  24. 24.
    OMG: XML Metadata Interchange (XMI) Specification, Version 2.1. Object Management Group (accessed February 01, 2006), http://www.omg.org/technology/documents/formal/xmi.htm
  25. 25.
    Pressman, R.S.: Software Engineering: A Practitioner’s Approach, 6th edn. McGraw-Hill, New York (2005)Google Scholar
  26. 26.
    Select Business Solutions: Select Component Manager (accessed March 28, 2006), http://www.selectbs.com
  27. 27.
    Smds: Aide de Camp Product Overview. Software Maintenance & Development Systems (1994) Google Scholar
  28. 28.
    Szyperski, C.: Component Software: Beyond object-oriented programming. Addison-Wesley, Reading (2002)Google Scholar
  29. 29.
    Weber, D. W.: Requirements for an SCM Architecture to Enable Component-Based Development. In: Proceedings of Tenth International Workshop on Software Configuration Management (SCM 10), Toronto, Canada (May 2001) Google Scholar
  30. 30.
    White, B.A.: Software Configuration Management Strategies and Rational ClearCase: A Practical Introduction. Addison-Wesley, Reading (2000)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Luiz Gustavo Lopes
    • 1
  • Leonardo Murta
    • 1
  • Cláudia Werner
    • 1
  1. 1.COPPE/UFRJ – Systems Engineering and Computer Science ProgramFederal University of Rio de JaneiroRio de JaneiroBrazil

Personalised recommendations