• DocumentCode
    2458132
  • Title

    Identifying design-code inconsistencies in object-oriented software: a case study

  • Author

    Fiutem, R. ; Antoniol, G.

  • Author_Institution
    ITC-IRST, Povo, Italy
  • fYear
    1998
  • fDate
    16-20 Nov 1998
  • Firstpage
    94
  • Lastpage
    102
  • Abstract
    Traceability is a key issue to ensure consistency among software artifacts of subsequent phases of the development cycle. However few works have addressed the theme of tracing object oriented design into its software. This paper presents an approach to check the compliance of OO design with respect to source code. The process works on design artefacts expressed in OMT notation and accepts C++ source code. It recovers an “as is” design from the code, compares recovered design with the actual design and helps the user to deal with inconsistency by pointing out regions of code which do not match with design. The recovery process exploits regular expression and edit distance to bridge the gap between code and design. Results as well as consideration related to presentation issues are reported in the paper
  • Keywords
    C++ language; object-oriented programming; software maintenance; C++; OMT notation; case study; design-code inconsistency identification; object oriented design; object-oriented software; software artifact consistency; software development cycle; source code; traceability; Computer aided software engineering; Computer industry; Electrical capacitance tomography; Inspection; Layout; Signal design; Software libraries; Software maintenance; Time to market; Visualization;
  • fLanguage
    English
  • Publisher
    ieee
  • Conference_Titel
    Software Maintenance, 1998. Proceedings., International Conference on
  • Conference_Location
    Bethesda, MD
  • ISSN
    1063-6773
  • Print_ISBN
    0-8186-8779-7
  • Type

    conf

  • DOI
    10.1109/ICSM.1998.738497
  • Filename
    738497