By Topic

Proceedings Conference on Software Maintenance 1992

9-12 Nov. 1992

Filter Results

Displaying Results 1 - 25 of 48
  • A classification procedure for the effective management of changes during the maintenance process

    Publication Year: 1992, Page(s):328 - 336
    Cited by:  Papers (10)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (598 KB)

    The authors address the issue of assessing the difficulty of a change based on known or predictable data. They consider the present work as a first step towards the construction of customized economic models for maintainers. They propose a modeling approach, based on regular statistical techniques, that can be used in a variety of software maintenance environments. This approach can be easily auto... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • COMFORM-a software maintenance method based on the software configuration management discipline

    Publication Year: 1992, Page(s):183 - 192
    Cited by:  Papers (3)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (688 KB)

    COMFORM (configuration management formalisation for maintenance), a method which provides guidelines and procedures for carrying out a variety of activities performed during the maintenance process, is discussed. The proposed method accommodates a change control framework around which the software configuration management discipline is applied. The aim is to exert control over an existing software... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Conference on Software Maintenance 1992 (Cat.No.92CH3206-0)

    Publication Year: 1992
    Request permission for commercial reuse | PDF file iconPDF (72 KB)
    Freely Available from IEEE
  • Maintaining the software process

    Publication Year: 1992, Page(s):2 - 8
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (548 KB)

    The software process movement is described. Organization-wide software processes and the maintenance of defined software processes are considered. It is suggested that the software process movement will find the software maintenance community directly in its mainstream. Even more important, the maintenance community is about to face a double challenge. First, it must struggle to adopt more effecti... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A transformation system for maintenance-turning theory into practice

    Publication Year: 1992, Page(s):146 - 155
    Cited by:  Papers (24)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (684 KB)

    An outline of the principles and design features of the Maintainer's Assistant is presented. The main results presented concern the method by which the previously developed theoretical approach has been interpreted to provide the means to address the reverse engineering of real-world programs of medium size, written in IBM 370 Assembler. In particular, the use of appropriate metrices to guide the ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Cost benefit analysis and the art of software maintenance

    Publication Year: 1992, Page(s):70 - 77
    Cited by:  Papers (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (612 KB)

    As software maintenance requirements continue to grow, conflicting with demands for new development, managers must continually evaluate the cost effectiveness of various maintenance strategies. He shows that one can measure and use a significant benefit from maintenance-the reduction in failure risk-to evaluate maintenance strategies. The ability to measure the differential risk of failure in modu... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A quick tools strategy for program analysis and software maintenance

    Publication Year: 1992, Page(s):206 - 213
    Cited by:  Papers (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (580 KB)

    A strategy for quickly producing special-purpose tools is described. The strategy combines existing tools including simple off-the-shelf text processing tools; rule-based, language-specific analysis tool; and a commercial CASE (computer-aided software engineering) tool. The strategy has been successfully used in the context of the maintenance and reverse engineering of a large, real-time software ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Delphi study of software maintenance problems

    Publication Year: 1992, Page(s):10 - 17
    Cited by:  Papers (13)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (612 KB)

    The Delphi technique was used to compile a list of major problems in software maintenance, quantify them, and strengthen the consensus in iterations. Forty-four experienced software maintenance professionals responded in the final round. Assembled rationales and arguments provide an abundance of information on maintenance problems, and their causes and consequences. Maintenance problems were group... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Eliminating non-traversable paths from structured programs

    Publication Year: 1992, Page(s):156 - 164
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1044 KB)

    A formal procedure is given based on the use of regular expressions, to identify and eliminate nontraversable paths in a structured program. By reducing the use of control variables, the program is transformed into an unstructured variant and then restructured into a semantic equivalent of the original program with nontraversable paths eliminated. The authors demonstrate this procedure with an exa... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Paradigms for maintenance

    Publication Year: 1992, Page(s):80 - 86
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (60 KB)

    A discussion on paradigms for maintenance covers the following topics: the object-oriented paradigm for software maintenance; an integrated approach to reverse engineering; arguments for developing and accepting multiple paradigms for software maintenance; and reverse engineering versus re-engineering View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Problem domain, structural and logical abstractions in reverse engineering

    Publication Year: 1992, Page(s):214 - 224
    Cited by:  Papers (6)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (6536 KB)

    Reverse engineering abstractions are considered. Three kinds of abstractions are identified: problem domain, structural, and logical. Problem domain abstractions correspond to concepts from a program's application area. Structural abstractions are used to eliminate implementation details and redundant information. Logical abstractions are properties that can be logically derived from code. A metho... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Identification of program modifications and its applications in software maintenance

    Publication Year: 1992, Page(s):282 - 290
    Cited by:  Papers (39)  |  Patents (7)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (660 KB)

    It is pointed out that a major problem in software maintenance is the revalidation of a modified code. It is economically desirable to restrict that process only to those parts of the program that are affected by the modifications. Towards that goal, a formal method is needed to identify the modifications in an automatic way. Such a method is proposed in the present work. The modifications are loc... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Incorporating the inspection process into a software maintenance organization

    Publication Year: 1992, Page(s):51 - 56
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (432 KB)

    The results are given of introducing the inspection process into an established software life cycle maintenance organization. The results were obtained while implementing a major system enhancement and support the continued use of software inspection in the maintenance environment, for both system enhancements and problem corrections. The defect data collected provided the quantitative information... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software maintenance: an analysis of industrial needs and constraints

    Publication Year: 1992, Page(s):18 - 26
    Cited by:  Papers (7)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (712 KB)

    The results are given of a series of case studies conducted at different industrial sites in the framework of the ESF/EPSOM (Eureka Software Factory/European Platform for Software Maintenance) project. The approach taken in the case studies was to directly contact software maintainers and obtain their own view of their activity, mainly through the use of interactive methods based on group work. Th... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software restructuring by enforcing localization and information hiding

    Publication Year: 1992, Page(s):165 - 172
    Cited by:  Papers (7)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (508 KB)

    It is shown how the semantic basis underlying modern system structure constructs (supported in languages such as Ada and C++) can be used to simplify the understanding of software written in conventional imperative languages. The restructuring technique analyzes the input source code system into a hierarchical system structure that exploits information hiding and localization properties. This hier... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A study of portability problems and evaluation

    Publication Year: 1992, Page(s):90 - 95
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (384 KB)

    The portability aspects of the FORTRAN and C languages are discussed and the results of porting evaluation are reported. Several experiments were carried out on transferring a fourth-generation language system named STYLE. STYLE was developed for business transaction processing and is designed to greatly speed up application program development. This system is based on the client and server model.... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A conceptual foundation for software re-engineering

    Publication Year: 1992, Page(s):226 - 235
    Cited by:  Papers (18)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (752 KB)

    The author presents a conceptual foundation for software re-engineering. The foundation is composed of properties and principles that underlie re-engineering methods, and assumptions about re-engineering. The value of this conceptual foundation is its ability to model understanding of re-engineering, how it is practiced, and how it can be practiced. A general model of software re-engineering is es... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Metrics for assessing a software system's maintainability

    Publication Year: 1992, Page(s):337 - 344
    Cited by:  Papers (38)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (516 KB)

    It is noted that the factors of software that determine or influence maintainability can be organized into a hierarchical structure of measurable attributes. For each of these attributes the authors 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 purpose... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software transition: experience and lessons learned

    Publication Year: 1992, Page(s):294 - 298
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (460 KB)

    While operating a software maintenance organization, the authors were faced with the challenge of accepting maintenance responsibility from a software developer for several systems. Transition of the first two systems was painful. Based on the experience gained, the authors developed procedures for transition. They believe that those procedures improve the ability of the maintenance organization t... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Tailoring the software engineering Institute's (SEI) Capability Maturity Model (CMM) to a software sustaining engineering organization

    Publication Year: 1992, Page(s):137 - 144
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (508 KB)

    The Software Engineering Institute's Softwares Process Maturity Model was developed to provide a basis for assessing an organization's ability to perform software engineering activities. It also provides a guide for improving an organization's software engineering capability. The maturity model was designed on the basis of concepts associated with developing new, large, complex systems. This has l... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software lifetime and its evolution process over generations

    Publication Year: 1992, Page(s):63 - 69
    Cited by:  Papers (18)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (464 KB)

    It is noted that the software evolution process does not end at the death of an individual software system but usually continues over generations through being replaced by newly built software. To explore this research topic, the authors conducted a survey, collecting data of software lifetimes, replacement practices, and factors of replacement. They report the results of the survey and discuss so... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Locating user functionality in old code

    Publication Year: 1992, Page(s):200 - 205
    Cited by:  Papers (51)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (460 KB)

    It is pointed out that software maintainers often have to recover requirements traceability in old code. In other words, they need to determine in which parts of the program the functionality X is implemented. The authors propose a methodology for answering this question based on the use of carefully designed test cases as probes into the code. While the methodology is not applicable to a... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software measurement for the space shuttle HAL/S maintenance environment

    Publication Year: 1992
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (60 KB)

    The authors discuss the development of a complexity domain model for the HAL/S programming language in which all of the space shuttle software is written. Their research has indicated that some aspects of software complexity in other programming language environments are strongly related to software problems incurred during software maintenance. The goal of the current research effort is to establ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Data flow testing of parallelized code

    Publication Year: 1992, Page(s):272 - 281
    Cited by:  Papers (5)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (732 KB)

    The authors present a novel system for re-engineering and retesting programs for execution in a shared memory multiprocessor environment. The system consists of two main components: a compiler that reengineers a sequential program for execution on shared memory multiprocessors, and a data-flow tester for the parallelized code. Several important enhancements to an existing parallelizing compiler ha... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Using semantic differencing to reduce the cost of regression testing

    Publication Year: 1992, Page(s):41 - 50
    Cited by:  Papers (25)  |  Patents (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (768 KB)

    An algorithm is presented that reduces the cost of regression testing by reducing the number of test cases that must be rerun and by reducing the size of the program that they must be run on. The algorithm uses dependence graphs and program slicing to partition the components of the new program into two sets: preserved points-components that have unchanged run-time behaviour; and affected points-c... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.