default search action
ICSM 1988: Scottsdale, AZ, USA
- Proceedings of the Conference on Software Maintenance, ICSM 1988, Scottsdale, AZ, USA, 24-27 October, 1988. IEEE 1988, ISBN 0-8186-0879-X
- Chris F. Kemerer:
Production process modeling of software maintenance productivity. - David E. Peercy:
Risk Assessment Methodology for Software Supportability (RAMSS). - Marc I. Kellner:
Software process modeling at SEI. - Ned Chapin:
Software maintenance life cycle. 6-13 - Shehab A. Gamalel-Din, Leon J. Osterweil:
New perspectives on software maintenance processes. 14-22 - Bruce I. Blum:
Documentation for maintenance: a hypertext design. 23-31 - C. G. Davies, Paul J. Layzell:
Rules to govern change in JSP-based systems. 34-39 - Mikio Aoyama, Yoshihiiku Hanai, Makoto Suzuki:
An integrated software maintenance environment: bridging configuration management and quality management. 40-44 - James S. Collofello, Mikael Orn:
A practical software maintenance environment. 45-51 - Nigel T. Fletton, Malcolm Munro:
Redocumenting software systems using hypertext technology. 54-59 - Jane E. Huffman, Clifford G. Burgess:
Partially automated in-line documentation (PAID): design and implementation of a software maintenance tool. 60-65 - L. D. Landis, P. M. Hyland, A. L. Gilbert, A. J. Fine:
Documentation in a software maintenance environment. 66-73 - Gregory A. Hansen:
Modeling the software maintenance process: process-focused models. 76-77 - Chris Wild, Kurt Maly:
Towards a software maintenance support environment. 80-85 - Linore Cleveland:
A user interface for an environment to support program understanding. 86-91 - Václav Rajlich, Nicholas Damaskinos, Panagiotis K. Linos, João H. Silva, Wafa Khorshid:
Visual support for programming-in-the-large. 92-99 - Harry M. Sneed, Gabor Jandrasics:
Inverse transformation of software from code to specification. 102-109 - Steven E. Keller:
Grammar-based program transformation. 110-117 - C. Michael Overstreet, Ji Chen, Frank Byrum:
Program maintenance by safe transformations. 118-123 - Lynn H. Greene:
Self-identifying software. 126-131 - Suresh Subramanian:
CRUISE: using interface hierarchies to support software evolution. 132-142 - Paul A. Bicknell:
Software development and configuration management in the Cronus distributed operating system. 143-147 - Patricia K. Lawlis:
Ada and software maintenance. 152-158 - Sheryl Kempton, Chris Sobell, Carol Withrow:
DOD-STD-2167A applied to software maintenance. 159-164 - Rodger L. Fritz, Fred Shocket:
LAMPS-demonstrated maintainability through application of MIL-SPEC software development techniques. 165-170 - Kumar Venkatramani, Roger Clark:
Using configured directories to solve software maintenance problems. 172-177 - Thomas F. Linehan Jr.:
Application software configuration management and testing in a pharmaceutical laboratory automation environment. 178-182 - E. N. Herness, R. M. Chance:
Software maintenance features for library systems. 183-190 - Richard W. Selby, Victor R. Basili:
Error localization during software maintenance: generating hierarchical system descriptions from the source code alone. 192-197 - Mark E. Segal, Ophir Frieder:
Dynamic program updating in a distributed computer system. 198-203 - Mark V. Lindberg, Pei Hsia, Rodney M. Bond:
A study of requirements change effects on incrementally delivered systems. 204-211 - Nancy R. Mead, Daniel Ehrenfried, John R. Rymer:
Designing Ada software for maintainability. 214-215 - David G. Wright:
Configuration management in a heterogeneous environment. 218-221 - Hal S. Render, Roy H. Campbell:
CLEMMA: the design of a practical configuration librarian. 222-228 - C. G. Horne, R. Saeger:
An advanced configuration management tool set. 229-234 - David P. Hale, Dwight A. Haworth:
Software maintenance: a profile of past empirical research. 236-240 - Ie-Hong Lin, David A. Gustafson:
Classifying software maintenance. 241-247 - C. K. S. Chong Hok Yuen:
On analyzing maintenance process data at the global and the detailed levels: a case study. 248-255 - Paul J. Layzell, Pericles Loucopoulos:
A rule-based approach to the construction and evolution of business information systems. 258-264 - James R. Lyle, Keith B. Gallagher:
Using program decomposition to guide modifications. 265-269 - Paul C. Jorgensen:
An operational approach to corrective software maintenance. 270-276 - Keith W. Miller, Larry J. Morell, W. Robert Collins:
Maintaining FORTRAN software by enforcing abstract data types. 286-291 - Richard C. Linger:
Software maintenance as an engineering discipline. 292-297 - Robert D. Cameron:
The introspection technique in maintenance metaprogramming. 298-301 - Louis-François Pau, J. M. Negret:
SOFTM: a software maintenance expert system in Prolog. 306-311 - Mehdi T. Harandi, Jim Q. Ning:
PAT: a knowledge-based program analysis tool. 312-318 - Frank W. Calliss, M. Khalil, Malcolm Munro, Martin Ward:
A knowledge-based system for software maintenance. 319-324 - J. Meekel, M. Viala:
Logiscope: a tool for maintenance. 328-334 - James Keables, Katherine Roberson, Anneliese von Mayrhauser:
Data flow analysis and its application to software maintenance. 335-347 - Michael Frame:
A lexical comparison program to simplify the maintenance of portable software. 348-350 - Paolo Benedusi, Aniello Cimitile, Ugo de Carlini:
Post-maintenance testing based on path change analysis. 352-361 - Mary Jean Harrold, Mary Lou Soffa:
An incremental approach to unit testing during maintenance. 362-367 - J. Hartmann, Dave J. Robson:
Approaches to regression testing. 368-372 - Stephen S. Yau, Pao-Sheng Chang:
A metric of modifiability for software maintenance. 374-381 - Steve Wake, Sallie M. Henry:
A model based on software quality factors which predicts maintainability. 382-387 - Frank A. Cioch:
An audiovisual document for software maintenance. 390-395 - Ronald E. Backus:
Applying instructional systems development to software maintenance education. 396-401 - Tomaz Dogsa, Ivo Rozman:
CAMOTE-computer aided module testing and design environment. 404-408 - D. J. Newman:
A test harness for maintaining unfamiliar software. 409-416
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.