LEADER 04617oam 2200421zu 450 001 996211386303316 005 20210807003600.0 035 $a(CKB)111026746747654 035 $a(SSID)ssj0000827828 035 $a(PQKBManifestationID)12358453 035 $a(PQKBTitleCode)TC0000827828 035 $a(PQKBWorkID)10830007 035 $a(PQKB)10972001 035 $a(NjHacI)99111026746747654 035 $a(EXLCZ)99111026746747654 100 $a20160829d1999 uy 101 0 $aeng 135 $aur||||||||||| 181 $ctxt 182 $cc 183 $acr 200 00$aInternational Conference on Software Maintenance 210 31$a[Place of publication not identified]$cIEEE Computer Society Press$d1999 215 $a1 online resource (xiv, 378 pages) $cillustrations 300 $aBibliographic Level Mode of Issuance: Monograph 311 $a0-8186-8779-7 327 $aMaking Change: The *Other* Components of Software Maintenance,"S. -- Identification of green, yellow and red legacy components,"M. -- Identification of data cohesive subsystems using data mining techniques,"C. -- Code churn: a measure for estimating the impact of code change,"J. -- An empirical study of the effects of minimization on the fault detection capabilities of test suites,"G. -- Empirical evaluation of the textual differencing regression testing technique,"F. -- The visibility of maintenance in object models: an empirical study,"M. -- Hitting the Moving Target: Trials and Tribulations of Modeling Quality in Evolving Software Systems,"P. -- Can a software quality model hit a moving target?,"T. -- Some comments on the software measurement process,"J. -- Using software metrics to control firmware evolution,"T. -- Modeling process and product quality during maintenance,"G. -- Two case studies in measuring software maintenance effort,"F. -- A case study in software wrapping,"H. -- Identifying design-code inconsistencies in object-oriented software: a case study,"R. -- Dynamic model for maintenance and testing effort,"F. -- Software Maintenance Life Cycle Model,"Hsiang-Jui -- An experiment in identifying persistent objects in large systems,"A. -- Building maintainable COTS based systems,"M. -- Practices of software maintenance,"J. -- A study of communication and cooperation in distributed software project teams,"A. -- Are COTS Products and Component Packaging Killing Software Malleability?,"J. -- Maintaining a COTS integrated solution-are traditional static analysis techniques sufficient for this new programming methodology?,"R. -- Experience report: correcting system failure in a COTS information system,"S. -- Evaluating software deployment languages and schema: an experience report," -- Detection of logical coupling based on product release history," -- Investigating component-based maintenance and the effect of software evolution: a reengineering approach using data clustering," -- Implications of evolution metrics on software maintenance," -- Maintaining COTS-based Systems: Is it Possible?," -- COTS evaluation and selection," -- Methods for assessing COTS reliability, maintainability, and availability," -- Assembly to high-level language translation," -- Reengineering object-oriented code," -- Do program transformations help reverse engineering?," -- Investigating maintenance processes in a framework-based environment," -- A survey on the Software Maintenance Process," -- Maintaining maintainability, -- Tackling the abstraction problem for reverse engineering in a system re-engineering approach," -- Improving visual impact analysis," -- Reuse in replaying database design," -- Program understanding during software adaptation tasks," -- Using the O-A diagram to encapsulate dynamic memory access," -- Analysis of dynamic memory access using amorphous slicing," -- Analysis of programs with exception-handling constructs," -- Slicing objects using system dependence graphs," -- Clone detection using abstract syntax trees,". 330 $aThese papers, presented at the 1998 International Conference on Software Maintenance, covers topics including: software system migration and conversion; COTS application maintenance; component-based software maintenance; software modernization; and software re-engineering and restructuring. 606 $aSoftware maintenance$vCongresses 615 0$aSoftware maintenance 676 $a005 702 $aKhoshgoftaar$b Taghi M. 702 $aBennett$b K. H. 801 0$bPQKB 906 $aPROCEEDING 912 $a996211386303316 996 $aInternational Conference on Software Maintenance$92389608 997 $aUNISA