Abstract is missing.
- Software measurement for the space shuttle HAL/S maintenance environmentJohn C. Munson, Taghi M. Khoshgoftaar. [doi]
- Reliability models and metrics for space shuttle maintenance position statementNorman F. Schneidewind. [doi]
- Maintaining the software processBill Curtis. 2-8 [doi]
- Delphi study of software maintenance problemsSasa Dekleva. 10-17 [doi]
- Software maintenance: an analysis of industrial needs and constraintsMarc Haziza, J. F. Voidrot, E. Minor, L. Pofelski, Sandrine Blazy. 18-26 [doi]
- Current state of software maintenance in Japan: in depth viewMakoto Ino. 27-29 [doi]
- Reverse engineering: resolving conflicts between expected and actual software designsStephen B. Ornburn, Spencer Rugaber. 32-40 [doi]
- Using semantic differencing to reduce the cost of regression testingDavid W. Binkley. 41-50 [doi]
- Incorporating the inspection process into a software maintenance organizationRobert J. Kosman, Thomas J. Restivo. 51-56 [doi]
- Romancing the quantitative maintenance managementLoredana Mancini. 58-62 [doi]
- Software lifetime and its evolution process over generationsTetsuo Tamai, Yohsuke Torimitsu. 63-69 [doi]
- Cost benefit analysis and the art of software maintenanceSusan A. Sherer. 70-77 [doi]
- Paradigms for maintenanceMari Georges. 80-86 [doi]
- A study of portability problems and evaluationMikio Tanaka. 90-95 [doi]
- A framework for dynamic evolution of object-oriented specificationsMohammed Erradi, Gregor von Bochmann, Rachida Dssouli. 96-104 [doi]
- Migration of procedurally oriented COBOL programs in an object-oriented architectureHarry M. Sneed. 105-116 [doi]
- A task-based approach to improving the software maintenance processLarry Cousin, James S. Collofello. 118-126 [doi]
- A process model for the maintenance of large space systems softwareDel-Raj Harjani, Jean-Pierre Queille. 127-136 [doi]
- Tailoring the software engineering Institute's (SEI) Capability Maturity Model (CMM) to a software sustaining engineering organizationDaniel W. Drew. 137-144 [doi]
- A transformation system for maintenance-turning theory into practiceKeith H. Bennett, Tim M. Bull, Hongji Yang. 146-155 [doi]
- Eliminating non-traversable paths from structured programsMark G. Pleszkoch, Richard C. Linger, Alan R. Hevner. 156-164 [doi]
- Software restructuring by enforcing localization and information hidingWilliam C. Chu, Sukesh Patel. 165-172 [doi]
- Developing a model to manage the software maintenance processDavid S. Hinley, Keith H. Bennett. 174-182 [doi]
- COMFORM-a software maintenance method based on the software configuration management disciplineMiriam A. M. Capretz, Malcolm Munro. 183-192 [doi]
- A redefined software life cycle model for improved maintenanceTorbjørn Skramstad, Khaled M. Khan. 193-197 [doi]
- Locating user functionality in old codeNorman Wilde, Juan A. Gomez, Thomas Gust, Douglas Strasburg. 200-205 [doi]
- A quick tools strategy for program analysis and software maintenanceBret Johnson, Steve Ornburn, Spencer Rugaber. 206-213 [doi]
- Problem domain, structural and logical abstractions in reverse engineeringWilliam E. Howden, Suehee Pak. 214-224 [doi]
- A conceptual foundation for software re-engineeringEric J. Byrne. 226-235 [doi]
- Evaluating the Surgeon's Assistant: results of a pilot studyKeith Brian Gallagher. 236-244 [doi]
- A framework for process maintenance [software]Nazim H. Madhavji, Kamel Toubache, Won-Kook Hong. 245-254 [doi]
- Maturity of maintenance [software]Pasi Kuvaja, Günter Koch. 259-260 [doi]
- A firewall concept for both control-flow and data-flow in regression integration testingLee J. White, Hareton K. N. Leung. 262-271 [doi]
- Data flow testing of parallelized codeMary Jean Harrold, Brian A. Malloy. 272-281 [doi]
- Identification of program modifications and its applications in software maintenanceJanusz W. Laski, Wojciech Szermer. 282-290 [doi]
- Software transition: experience and lessons learnedThomas M. Pigoski, Craig A. Cowden. 294-298 [doi]
- An approach to regression testing using slicingRajiv Gupta 0001, Mary Jean Harrold, Mary Lou Soffa. 299-308 [doi]
- Traceability based on design decisionsAniello Cimitile, Filippo Lanubile, Giuseppe Visaggio. 309-317 [doi]
- An outline for a software maintenance courseFrank W. Calliss. 320-321 [doi]
- Can software maintenance be taught?James E. Cardow. 322-323 [doi]
- The benefits of maintenance exercises in project-based courses in software engineeringKeith R. Pierce. 324-325 [doi]
- A classification procedure for the effective management of changes during the maintenance processLionel C. Briand, Victor R. Basili. 328-336 [doi]
- Metrics for assessing a software system's maintainabilityPaul W. Oman, Jack R. Hagemeister. 337-344 [doi]
- Effects of software changes on module cohesionLinda M. Ott, James M. Bieman. 345-353 [doi]
- Program dependence analysisPanos E. Livadas, Prabal K. Roy. 356-365 [doi]
- Data flow diagrams: reverse engineering production and animationGerardo Canfora, Lucio Sansone, Giuseppe Visaggio. 366-375 [doi]
- Improved maintenance support by multi-version visualizationsBjørn Gulla. 376-383 [doi]