| |
|
|
|
|
|
|
|
|
1. |
Record Nr. |
UNISA996211386303316 |
|
|
Titolo |
International Conference on Software Maintenance |
|
|
|
|
|
Pubbl/distr/stampa |
|
|
[Place of publication not identified], : IEEE Computer Society Press, 1999 |
|
|
|
|
|
|
|
|
|
Descrizione fisica |
|
1 online resource (xiv, 378 pages) : illustrations |
|
|
|
|
|
|
Disciplina |
|
|
|
|
|
|
Soggetti |
|
|
|
|
|
|
Lingua di pubblicazione |
|
|
|
|
|
|
Formato |
Materiale a stampa |
|
|
|
|
|
Livello bibliografico |
Monografia |
|
|
|
|
|
Note generali |
|
Bibliographic Level Mode of Issuance: Monograph |
|
|
|
|
|
|
Nota di contenuto |
|
Making 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,". |
|
|
|
|
|
|
Sommario/riassunto |
|
These 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. |
|
|
|
|
|
|
|
| |