By Topic

Software Maintenance, 1992. Proceerdings., Conference on

Date 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 (7)
    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
  • Migration of procedurally oriented COBOL programs in an object-oriented architecture

    Publication Year: 1992, Page(s):105 - 116
    Cited by:  Papers (19)  |  Patents (7)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (560 KB)

    Consideration is given to the migration of procedurally structured COBOL programs into functionally equivalent object-oriented programs. The major differences in procedural and object-oriented program architecture are described and an approach is presented to bridge the gap between the two. The approach is based on the partitioning of programs into abstract data types and the reallocation of proce... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • An approach to regression testing using slicing

    Publication Year: 1992, Page(s):299 - 308
    Cited by:  Papers (55)  |  Patents (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (744 KB)

    The authors present a novel approach to data-flow-based regression testing that uses slicing type algorithms to explicitly detect definition-use pairs that are affected by a program change. An important benefit of the slicing technique is that, unlike previous techniques, no data flow history is needed nor is the recomputation of data flow for the entire program required to detect affected definit... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Romancing the quantitative maintenance management

    Publication Year: 1992, Page(s):58 - 62
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (356 KB)

    A simple investigation of the use of quantitative techniques for maintenance activities had been carried out previously using a base of approximately 30 Italian companies, showing the state of the art for 1990. The same companies were contacted again two years later to get their sense of the evolution in this area. The major goal of the report presented is to point out what seems to be a differenc... 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.
  • 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.
  • An outline for a software maintenance course

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

    The author briefly discusses the course structure for the graduate software maintenance course offered at Arizona State University. Introduction to software maintenance, forms of maintenance, reverse engineering and re-engineering, maintenance models, and maintenance personnel are the topics examined 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 (31)  |  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.
  • Using semantic differencing to reduce the cost of regression testing

    Publication Year: 1992, Page(s):41 - 50
    Cited by:  Papers (20)  |  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.
  • 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.
  • Traceability based on design decisions

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

    The authors model the different points of view on a software structure as distinct conceptual models. The mapping among models of the same software structure is made through the assumption of design decisions. This mapping is represented as a graph, the model dependency descriptor, which connects components of source models with those in the target models. A traceability relation is set between co... 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 (6)
    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.
  • 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.
  • 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.
  • Tailoring the software engineering Institute's (SEI) Capability Maturity Model (CMM) to a software sustaining engineering organization

    Publication Year: 1992, Page(s):137 - 144
    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.
  • The benefits of maintenance exercises in project-based courses in software engineering

    Publication Year: 1992, Page(s):324 - 325
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (144 KB)

    A particular justification for teaching software maintenance is presented. Specifically, it is pointed out that, when an instructor assigns maintenance exercises in a project-based course in software engineering, and when the assignment includes a carefully organized management model, students learn far more than they would from a traditional from-scratch development project View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Data flow diagrams: reverse engineering production and animation

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

    The authors propose the use of interactive animation techniques as a support to reverse engineering processes oriented to the synthesis of semantic abstractions. Starting from data flow diagrams, a formal model, called dynamic data flow diagrams (DDFDs), has been defined, which can be used for the production of executable models of a software system. A strategy for the DDFD interactive animation i... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Current state of software maintenance in Japan: in depth view

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

    The study activities of the Software Maintenance Study Group (SMSG) in Japan are described. SMSG was established in December 1990 to discuss the problems of the maintenance sections handling very large software systems in about 30 major companies in Japan. SMSG is organized from a program committee and six working groups. The author reports the current progress of these groups, emphasizing groups ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Reliability models and metrics for space shuttle maintenance position statement

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

    The use of software reliability models as an aid to software maintenance, with applications to the space shuttle onboard software, is described. In addition to supporting the maintenance function, the use of reliability models throughout the life of the software supports other functions such as reliability assessment, design feasibility assessment, and management of human and computer resources. R... 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 (14)
    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.
  • Eliminating non-traversable paths from structured programs

    Publication Year: 1992, Page(s):156 - 164
    Cited by:  Papers (1)
    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.
  • 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.
  • Locating user functionality in old code

    Publication Year: 1992, Page(s):200 - 205
    Cited by:  Papers (48)
    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.