By Topic

Software Maintenance, 1988., Proceedings of the Conference on

Date 24-27 Oct. 1988

Filter Results

Displaying Results 1 - 25 of 60
  • Proceedings of the Conference on Software Maintenance - 1988 (IEEE Cat. No.88CH2615-3)

    Publication Year: 1988
    Request permission for commercial reuse | PDF file iconPDF (33 KB)
    Freely Available from IEEE
  • Dynamic program updating in a distributed computer system

    Publication Year: 1988, Page(s):198 - 203
    Cited by:  Papers (4)  |  Patents (11)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (500 KB)

    The authors present an approach to update a computer program dynamically (i.e., while it is executing). Such an approach is important in applications where the cost of stopping and restarting the program makes doing so impractical. The approach works with programs written in procedural languages such as Pascal, C, and Fortran, and it scales to a distributed computer system. The authors assume that... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Grammar-based program transformation

    Publication Year: 1988, Page(s):110 - 117
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (700 KB)

    A grammar-based technique is introduced for making sweeping changes, involving substantial restructuring, to large-scale software programs. Pervasive structural changes are often required to make changes in data structures, computational forms, or programming style during software maintenance. The concept of a grammar-based editor is introduced. It is a well-defined system that applies the descrip... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Using program decomposition to guide modifications

    Publication Year: 1988, Page(s):265 - 269
    Cited by:  Papers (9)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (340 KB)

    The authors use data-flow techniques to form a notion of direct sum decomposition for programs. The decomposition yields a method and guidelines for software maintainers to use so that changes can be assured to be completely contained in the modules under consideration and that there are no undetected linkages between the modified and unmodified code. Thus, the impact of small changes can be gauge... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Redocumenting software systems using hypertext technology

    Publication Year: 1988, Page(s):54 - 59
    Cited by:  Papers (13)  |  Patents (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (420 KB)

    The majority of software maintenance activity is performed on systems that are poorly documented and were built without the benefit of modern design practices. A discussion is presented of the importance of documentation in the maintenance phase, and a tool based on hypertext technology is proposed that can meet a number of the documentation needs of the maintenance programmer. This tool supports ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Program maintenance by safe transformations

    Publication Year: 1988, Page(s):118 - 123
    Cited by:  Papers (1)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (512 KB)

    A class of program transformations and data-flow-analysis tools is reviewed. The authors focus on supporting code reuse and maintenance by exploring transformations which modify programs. Typical purposes of modifications are to simplify programs, make side effects more visible, improve locality, or detect useless code. The authors review several methods which have been described for program simpl... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Visual support for programming-in-the-large

    Publication Year: 1988, Page(s):92 - 99
    Cited by:  Papers (3)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (472 KB)

    A brief description of the VIFOR (visual interactive Fortran) environment is given. VIFOR is based on a simple, but effective data model of Fortran programs containing three entity classes and three relation classes only. Programs can be displayed and edited in two forms: the traditional one (i.e., code) and the visual form. VIFOR contains transformation tools for both directions, i.e., from code ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Maintaining FORTRAN software by enforcing abstract data types

    Publication Year: 1988, Page(s):286 - 291
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (492 KB)

    The principles of data abstraction facilitate maintenance and enhance software reliability. However, FORTRAN includes features that undermine data abstraction. A FORTRAN preprocessor called FAD enforces data abstraction when reusing FORTRAN-callable subprograms. Using FAD, reusable software is organized as the implementation of abstract data types (ADTs). FAD users access the reusable software by ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • An operational approach to corrective software maintenance

    Publication Year: 1988, Page(s):270 - 276
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (488 KB)

    The author argues that maintenance practitioners are served well by an operational view of a system, in which the sequential behavior is emphasized, as opposed to the visual hierarchy of functions viewpoint. The traditional and operational view of software development are compared, and an entity-relationship model of operational software development is offered. A typical corrective maintenance act... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Application software configuration management testing in a pharmaceutical laboratory automation environment

    Publication Year: 1988, Page(s):178 - 182
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (396 KB)

    A discussion is presented of the use of the computer system accounting structure to control software change, provide phased software testing, and handle software and data files in parallel with the software life-cycle. The US Food and Drug Administration, as the federal regulating body for the industry, directly influences software maintenance practices and procedures. Traceability to back version... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • LAMPS-demonstrated maintainability through application of MIL-SPEC software development techniques

    Publication Year: 1988, Page(s):165 - 170
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (532 KB)

    LAMPS is a major weapon system developed for the US Navy involving extensive software development for embedded processors. The development approach, a precursor to the requirements of US Dept. of Defense standards DOD-STD-1679 and DOD-STD-2167, produced highly successful results. Maintenance costs have been low because the software delivered to the operational environment has been relatively defec... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Configuration management in a heterogeneous environment

    Publication Year: 1988, Page(s):218 - 221
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (276 KB)

    The author describes the Networked Automated Versioning Environment (NAVE), a configuration management system that meets the requirements of a heterogeneous environment by supporting three different types of workstations for software and firmware development using six languages, for three different execution architectures. NAVE maintains a set of integrated configuration management (CM) tools that... View full abstract»

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

    Publication Year: 1988, Page(s):328 - 334
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (404 KB)

    Logiscope is an automated source-code analyzer that provides complexity analysis and test coverage analysis. Logiscope visualizes the internal logic structure of each module of code, as well as the structural relationships of all the modules. In this way Logiscope provides the visibility and control required to ensure cost-effective maintenance of software. The authors explain the role of Logiscop... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A metric of modifiability for software maintenance

    Publication Year: 1988, Page(s):374 - 381
    Cited by:  Papers (3)  |  Patents (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (716 KB)

    A model for measuring software modifiability is presented. In this model, the key to the modifiability of a program module is attributed to its localization property, which can be interpreted as indicating whether changes made to the module would have only a localized effect or not. The localization property of a module can be further broken down into intramodular localization and intermodular loc... View full abstract»

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

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

    The common view in the software field is to regard the software maintenance life cycle (SMLC) as being essentially the same as the life cycle for software development (SDLC). The examination that is presented of the nature of the actual work performed, however, does not support this common view. Even after taking into account definitional variation and situational adjustments, the two life cycles ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Inverse transformation of software from code to specification

    Publication Year: 1988, Page(s):102 - 109
    Cited by:  Papers (24)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (572 KB)

    A description is given of a schema supported by automated tools for the retranslation of software code back into an application specification by the process of inverse transformation. The code of Cobol programs is first retranslated into an intermediate design schema based on a set of normalized relational tables for the modules, data capsules, and interfaces extracted from the source programs. In... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Documentation in a software maintenance environment

    Publication Year: 1988, Page(s):66 - 73
    Cited by:  Papers (8)  |  Patents (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (496 KB)

    An approach has been defined, and a system developed, to aid the maintenance programmer by producing documentation from source code input. A system called the Parser/Documenter has been developed which is designed to accept source code from a variety of third-generation languages and outputs one of several documentation tools. The authors discuss current documentation methodologies, the developmen... View full abstract»

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

    Publication Year: 1988, Page(s):390 - 395
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (456 KB)

    Three criteria are used to determine the form and content of a proposed audiovisual document containing videotaped walkthroughs: (1) walkthroughs should be structural behavioral; (2) the maintenance programmer should be able to relate new knowledge to existing knowledge; and (3) the walkthroughs should allow the maintenance programmer to learn by example. The audiovisual document is developed by c... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Partially automated in-line documentation (PAID): design and implementation of a software maintenance tool

    Publication Year: 1988, Page(s):60 - 65
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (400 KB)

    The importance of accurate technical documentation to the maintenance process is presented. A possible solution to the lack of adequate technical documentation is suggested in the form of a partially automated in-line documentation system. This system uses software metrics to determine where comments should be placed in source programs. The system can be used as a tool in software development and/... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Using configured directories to solve software maintenance problems

    Publication Year: 1988, Page(s):172 - 177
    Cited by:  Patents (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (500 KB)

    Most software systems are maintained in a controlled baseline environment, and changes to it are typically made outside of the baseline (usually in the individual's workspace), then tested, verified and resubmitted into the baseline. This mode of operation has a set of problems associated with it. An explanation is presented of how the authors' configuration management system provides a general so... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Towards a software maintenance support environment

    Publication Year: 1988, Page(s):80 - 85
    Cited by:  Papers (7)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (540 KB)

    The authors have designed a software maintenance support environment (SMSE) to assist in the maintenance of existing source code. They model software maintenance as a hybrid distributed problem-solving activity, in which the application-dependent knowledge is provided by the system, and common sense, programming expertise, and problem-solving knowledge are provided by the people on the project tea... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • CLEMMA: the design of a practical configuration librarian

    Publication Year: 1988, Page(s):222 - 228
    Cited by:  Patents (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (504 KB)

    A configuration management system organizes large software systems and helps maintain those systems over a long lifetime. The problems that arise in the design of such a tool include the manipulation and accurate representation of system configurations, versions and derivation histories. Access control, the large quantities of data, and the evolutionary nature of software development all help to c... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Data flow analysis and its application to software maintenance

    Publication Year: 1988, Page(s):335 - 347
    Cited by:  Papers (10)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (728 KB)

    Algorithms are presented that limit the scope of recalculation of data-flow information for representative program changes. A prototype data-flow analysis program has been developed for a subset of the Ada language. An example analyzed by the prototype shows its possible use by program maintenance personnel View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • An incremental approach to unit testing during maintenance

    Publication Year: 1988, Page(s):362 - 367
    Cited by:  Papers (39)  |  Patents (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (568 KB)

    An incremental testing system to aid in unit testing during the maintenance stage is described. Based on data-flow testing, the system is designed for use in a programming environment; it shares common information and techniques with tools typically found in programming environments. In response to a change in a module, the incremental tester reuses the analysis and test cases from the previous te... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Self-identifying software

    Publication Year: 1988, Page(s):126 - 131
    Cited by:  Patents (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (396 KB)

    The self-identifying software (SIDS) concept, which has reduced software maintenance costs by greatly reducing the time required to determine the revision level of the software being diagnosed, is described. The SIDS (revision) elements can easily be controlled by an automated software configuration manager if a large number of software modules are involved. Implementation of SIDS does require add... View full abstract»

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