By Topic

IEEE Software

Issue 4 • Date July 1991

Filter Results

Displaying Results 1 - 8 of 8
  • Software process improvement at Hughes Aircraft

    Publication Year: 1991, Page(s):11 - 23
    Cited by:  Papers (54)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1401 KB)

    In 1987 and 1990, the Software Engineering Institute conducted process assessments of the Software Engineering Division (SED) of Hughes Aircraft in Fullerton, CA. The first assessment found the SED to be a level two organization, based on the SEI's process-maturity scale of one to five, where one is worst and five is best. The first assessment identified the strengths and weaknesses of the SED, an... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A critical look at software capability evaluations

    Publication Year: 1991, Page(s):25 - 41
    Cited by:  Papers (13)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1974 KB)

    The methods used by the Software Engineering Institute (SEI's) Software Capability Evaluation program (SCE) are assessed. The goal of the SCE program is to provide the US Defense Department with a method by which it can rank the overall capability of organizations to produce software in a timely, repeatable fashion. Because SEI assessments are a preparation for SCEs, the authors first describe the... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Safety verification of Ada programs using software fault trees

    Publication Year: 1991, Page(s):48 - 59
    Cited by:  Papers (34)  |  Patents (7)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1568 KB)

    The software fault-tree analysis technique is explained. It is then extended to allow its use on a more complex language involving such features as concurrency and exception handling. Ada is used as the example language because many safety-critical projects are using or planning to use Ada. It also contains complex, real-time programming facilities found in other languages used in these types of p... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Implementing design diversity to achieve fault tolerance

    Publication Year: 1991, Page(s):61 - 71
    Cited by:  Papers (17)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1308 KB)

    The software faults that are particularly significant in a real-time concurrent system are identified, and the use of design diversity to prevent their occurrence is examined. Two approaches to enforced diversity, recovery-block software and multiversion software, are discussed. The recovery-block scheme combines N diverse software versions arranged (conceptually, at least) in sequential order, al... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Modular specification and verification of object-oriented programs

    Publication Year: 1991, Page(s):72 - 80
    Cited by:  Papers (9)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (938 KB)

    A method for modular specification and verification using the ideas of subtype and normal type is presented. The method corresponds to informal techniques used by object-oriented programmers. The key idea is that objects of a subtype must behave like objects of that type's supertypes. An example program is used to show the reasoning problems that supertype abstraction may cause and how the method ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Representing design dependencies in an issue-based style

    Publication Year: 1991, Page(s):81 - 89
    Cited by:  Papers (7)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1163 KB)

    A system that superimposes the issue-based and truth-maintenance approaches to provide a merged capability for recording design rationale is presented. The system presents the user with issue-based structures that can be annotated with informal information, and it provides an automated inferencing capability on those structures through an underlying truth-maintenance and expert system. The underly... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • How liable are you for your software?

    Publication Year: 1991, Page(s):94 - 95
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (341 KB)

    The applicability of product-liability law to software is examined, using a hypothetical case to illustrate the difficulties. Product liability is reviewed, and the issue of whether software is a product is explored. The question of what standard of care to use in judging the developer's conduct is considered. Some guidelines for assessing exposure to liability are provided.<> View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Comments on `a critical look' [software capability evaluations]

    Publication Year: 1991, Page(s):42 - 46
    Cited by:  Papers (5)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (444 KB)

    It is maintained that the article by T. Bollinger and C. McGowan, entitled `A critical look at software capability evaluation', see ibid., p.25-41 (1991), contains a serious flaw. The article argues that the process-maturity grading system used by the Software Engineering Institute (SEI) is unfair and provides too narrow a basis for evaluating software organizations. The present authors point out ... View full abstract»

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

Aims & Scope

IEEE Software delivers reliable, useful, leading-edge software development information to keep engineers and managers abreast of rapid technology change.

Full Aims & Scope

Meet Our Editors

Editor-in-Chief
Diomidis Spinellis
Athens University of Economics and Business
28is Oktovriou 76
Athina 104 33, Greece
dds@computer.org