References of Maintenance_Metrics

    Applying Software Complexity Metrics to Program Maintenance, W. Harrison and K. Magel and R. Kluczny and A. DeKock
    @Article{	  harrison.magel.ea:applying,
      author	= {W. Harrison and K. Magel and R. Kluczny and A. DeKock},
      title		= {Applying Software Complexity Metrics to Program
    		  Maintenance},
      journal	= {IEEE Computer},
      year		= {1982},
      volume	= {15},
      number	= {9},
      month		= sep,
      pages		= {65-79},
      class		= {Software_Reverse_Engineering, Reverse_Design,
    		  Metric-Based_Methods_in_Reverse_Design, Metrics,
    		  Maintenance_Metrics}
    }
    
    
    Experience with the accuracy of software maintenance task effort prediction models, M. Jorgensen
    @Article{	  jorgensen:experience,
      title		= {Experience with the accuracy of software maintenance task
    		  effort prediction models},
      author	= {M. Jorgensen},
      journal	= {IEEE Transactions on Software Engineering},
      pages		= {674--681},
      volume	= {21},
      number	= {8},
      year		= {1995},
      note		= {Eleven software maintenance effort prediction models are
    		  discussed},
      class		= {Software_Reverse_Engineering, Reverse_Design,
    		  Metric-Based_Methods_in_Reverse_Design, Metrics,
    		  Maintenance_Metrics}
    }
    
    
    Metrics for Assessing a Software System's Maintainability, Paul Oman and Jack Hagemeister
    @InProceedings{	  oman.hagemeister:metrics,
      author	= {Paul Oman and Jack Hagemeister},
      title		= {Metrics for Assessing a Software System's
    		  Maintainability},
      pages		= {337-344},
      booktitle	= {Proceedings of the  International Conference on Software
    		  Maintenance ~1992},
      year		= {1992},
      publisher	= {IEEE Computer Society Press},
      month		= nov,
      abstract	= {The factors of software that determine or influence
    		  maintainability can be organized into a hierarchical
    		  structure of measurable attributes. For each of these
    		  attributes we show a metric definition consistent with the
    		  published definitions of the software characteristic being
    		  measured. The result is a tree structure of maintainability
    		  metrics which can be used for purposes of evaluating the
    		  relative maintainability of the software system. In this
    		  paper the authors define metrics for measuring the
    		  maintainability of a target software system and discuss how
    		  those metrics can be combined into a single index of
    		  maintainability.},
      class		= {Software_Reverse_Engineering, Reverse_Design,
    		  Metric-Based_Methods_in_Reverse_Design, Metrics,
    		  Maintenance_Metrics}
    }
    
    
    A Field Study of the Relationship of Information Flow and Maintainability of COBOL Programs, M.M. Pickard and B.D. Carter
    @Article{	  pickard.carter:field,
      title		= {A Field Study of the Relationship of Information Flow and
    		  Maintainability of COBOL Programs},
      author	= {M.M. Pickard and B.D. Carter},
      journal	= {Information and Software Technology},
      volume	= {37},
      number	= {4},
      pages		= {195--202},
      year		= {1995},
      note		= { The results of a field study of the relationship of
    		  information flow to the maintainability of COBOL modules in
    		  a data processing environment are presented. There is a
    		  significant correlation between maintainability and
    		  information flow and with (information flow) metrics it is
    		  possible to identify poorly maintained modules},
      class		= {Software_Reverse_Engineering, Reverse_Design,
    		  Metric-Based_Methods_in_Reverse_Design, Metrics,
    		  Maintenance_Metrics}
    }
    
    
    A study on the Effect of Reengineering on Maintainability, Harry M. Sneed and Agnes Kaposi
    @InProceedings{	  sneed.kaposi:study,
      author	= {Harry M. Sneed and Agnes Kaposi},
      title		= {A study on the Effect of Reengineering on
    		  Maintainability},
      booktitle	= {Proceedings of the  International Conference on Software
    		  Maintenance ~1990},
      year		= {1990},
      pages		= {91-99},
      organization	= {IEEE},
      publisher	= {IEEE Computer Society Press},
      abstract	= {The report presented here on the effect of reengineering
    		  upon software maintainablility stems from a laboratory
    		  experiment conducted within the METKIT research project of
    		  the European ESPRIT program for the study and promotion of
    		  the use of metrics in Software-Engineering. The experiment
    		  was conducted as a case study in measuring software
    		  complexity and maintainablility. However, the results also
    		  serve to assess the benefits of reengineering old programs.
    		  Maintainability is defined as the effort to perform
    		  maintenance tasks, the impact domain of the maintenance
    		  actions and the error rate caused by those actions.
    		  Complexity is defined as a combination of code, data, data
    		  flow, structure, and control flow metrics. From the data
    		  collected it demonstrates that reengineering can decrease
    		  complexity and increase maintainability, but that
    		  restructuring has only a minor effect on maintainability.},
      class		= {Reengineering_in_General, Experiences,
    		  Software_Reverse_Engineering, Reverse_Design,
    		  Metric-Based_Methods_in_Reverse_Design, Metrics,
    		  Maintenance_Metrics}
    }
    

koschke@informatik.uni-stuttgart.de (Feedback).
Copyright © 1998-2000 University of Stuttgart, Germany. $Revision: 1.5 $
Date: Sat Nov 21 21:48:42 CET 2009