By Topic

IEEE Transactions on Software Engineering

Issue 12 • Date Dec. 1985

Filter Results

Displaying Results 1 - 21 of 21
  • IEEE Transactions on Software Engineering - Table of contents

    Publication Year: 1985, Page(s): c1
    Request permission for commercial reuse | PDF file iconPDF (400 KB)
    Freely Available from IEEE
  • IEEE Computer Society

    Publication Year: 1985, Page(s): c2
    Request permission for commercial reuse | PDF file iconPDF (264 KB)
    Freely Available from IEEE
  • Foreword Software Reliability

    Publication Year: 1985, Page(s):1409 - 1410
    Cited by:  Papers (4)
    Request permission for commercial reuse | PDF file iconPDF (1672 KB)
    Full text access may be available. Click article title to sign in or learn about subscription options.
  • List of referees

    Publication Year: 1985, Page(s): 1410
    Request permission for commercial reuse | PDF file iconPDF (1404 KB)
    Freely Available from IEEE
  • Software Reliability Models: Assumptions, Limitations, and Applicability

    Publication Year: 1985, Page(s):1411 - 1423
    Cited by:  Papers (392)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2992 KB)

    A number of analytical models have been proposed during the past 15 years for assessing the reliability of a software system. In this paper we present an overview of the key modeling approaches, provide a critical analysis of the underlying assumptions, and assess the limitations and applicability of these models during the software development cycle. We also propose a step-by-step procedure for f... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A Statistical Method for Software Quality Control

    Publication Year: 1985, Page(s):1424 - 1430
    Cited by:  Papers (12)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2360 KB)

    This paper proposes a statistical method that can be used to monitor, control, and predict the quality (measured in terms of the failure intensity) of a software system being tested. The method consists of three steps: estimation of the failure intensity (failures per unit of execution time) based on groups of failures, fitting the logarithmic Poisson model to the estimated failure intensity data,... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software Reliability Growth Modeling: Models and Applications

    Publication Year: 1985, Page(s):1431 - 1437
    Cited by:  Papers (174)  |  Patents (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2168 KB)

    This paper summarizes existing software reliability growth models (SRGM's) described by nonhomogeneous Poisson processes. The SRGM's are classified in terms of the software reliability growth index of the error detection rate per error. The maximum-likelihood estimations based on the SRGM's are discussed for software reliability data analysis and software reliability evaluation. Using actual softw... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Effect of System Workload on Operating System Reliability: A Study on IBM 3081

    Publication Year: 1985, Page(s):1438 - 1448
    Cited by:  Papers (43)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (3384 KB)

    This paper presents an analysis of operating system failures on an IBM 3081 running VM/SP. We find three broad categories of software failures: error handling (ERH), program control or logic (CTL), and hardware related (HS); it is found that more than 25 percent of software failures occur in the hardware/software interface. Measurements show that results on software reliability cannot be considere... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Toward High Confidence Software

    Publication Year: 1985, Page(s):1449 - 1455
    Cited by:  Papers (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2680 KB)

    Moving toward high confidence software that can meet ever increasing demands for critical DOD applications will require planning, specifying, selecting, and managing the necessary development and testing activities that will ensure the success of the software project. In order to trust the decisions being made, there must be evidence (i.e., an information base of data and facts) that techniques an... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Assessing (Software) Reliability Growth Using a Random Coefficient Autoregressive Process and Its Ramifications

    Publication Year: 1985, Page(s):1456 - 1464
    Cited by:  Papers (51)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2824 KB)

    In this paper we motivate a random coefficient autoregressive process of order 1 for describing reliability growth or decay. We introduce several ramifications of this process, some of which reduce it to a Kalman Filter model. We illustrate the usefulness of our approach by applying these processes to some real life data on software failures. Finally, we make a pairwise comparison of the models in... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Bayesian Extensions to a Basic Model of Software Reliability

    Publication Year: 1985, Page(s):1465 - 1471
    Cited by:  Papers (30)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2080 KB)

    A Bayesian analysis of the software reliability model of Jelinski and Moranda is given, based upon Meinhold and Singpurwalla. Important extensions are provided to the stopping rule and prior distribution of the number of defects, as well as permitting uncertainty in the failure rate. It is easy to calculate the predictive distribution of unfound errors at the end of software testing, and to see th... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software Reliability: The Stopping Rule Problem

    Publication Year: 1985, Page(s):1472 - 1476
    Cited by:  Papers (15)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (600 KB)

    When a new computer software package is developed and all obvious erros removed, a testing procedure is often put into effect to eliminate the remaining errors in the package. One common procedure is to try the package on a set of randomly chosen problems. We suppose that whenever a program encounters an error, a system failure results. At this point the software is inspected to determine and remo... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Partition Analysis: A Method Combining Testing and Verification

    Publication Year: 1985, Page(s):1477 - 1490
    Cited by:  Papers (58)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (4680 KB)

    The partition analysis method compares a procedure's implementation to its specification, both to verify consistency between the two and to derive test data. Unlike most verification methods, partition analysis is applicable to a number of different types of specification languages, including both procedural and nonprocedural languages. It is thus applicable to high-level descriptions as well as t... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The N-Version Approach to Fault-Tolerant Software

    Publication Year: 1985, Page(s):1491 - 1501
    Cited by:  Papers (423)  |  Patents (15)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (4192 KB)

    Evolution of the N-version software approach to the tolerance of design faults is reviewed. Principal requirements for the implementation of N-version software are summarized and the DEDIX distributed supervisor and testbed for the execution of N-version software is described. Goals of current research are presented and some potential benefits of the N-version approach are identified. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software Fault Tolerance: An Evaluation

    Publication Year: 1985, Page(s):1502 - 1510
    Cited by:  Papers (34)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (3040 KB)

    In order to assess the effectiveness of software fault tolerance techniques for enhancing the reliability of practical systems, a major experimental project has been conducted at the University of Newcastle upon Tyne. Techniques were developed for, and applied to, a realistic implementation of a real-time system (a naval command and control system). Reliability data were collected by operating thi... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A Theoretical Basis for the Analysis of Multiversion Software Subject to Coincident Errors

    Publication Year: 1985, Page(s):1511 - 1517
    Cited by:  Papers (164)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2720 KB)

    Fundamental to the development of redundant software techniques (known as fault-tolerant software) is an understanding of the impact of multiple joint occurrences of errors, referred to here as coincident errors. A theoretical basis for the study of redundant software is developed which 1) provides a probabilistic framework for empirically evaluating the effectiveness of a general multiversion str... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • 1985 Index IEEE Transactions on Software Engineering Vol. SE-11

    Publication Year: 1985, Page(s): 1517
    Request permission for commercial reuse | PDF file iconPDF (2321 KB)
    Freely Available from IEEE
  • IEEE Finding Your Way

    Publication Year: 1985, Page(s): 1517-j
    Request permission for commercial reuse | PDF file iconPDF (112 KB)
    Freely Available from IEEE
  • Call for Papers

    Publication Year: 1985, Page(s): 1517
    Request permission for commercial reuse | PDF file iconPDF (1354 KB)
    Freely Available from IEEE
  • IEEE Computer Society Publications

    Publication Year: 1985, Page(s): 1517-l
    Request permission for commercial reuse | PDF file iconPDF (376 KB)
    Freely Available from IEEE
  • Call for Papers

    Publication Year: 1985, Page(s): 1517
    Request permission for commercial reuse | PDF file iconPDF (190 KB)
    Freely Available from IEEE

Aims & Scope

The IEEE Transactions on Software Engineering is interested in well-defined theoretical results and empirical studies that have potential impact on the construction, analysis, or management of software. The scope of this Transactions ranges from the mechanisms through the development of principles to the application of those principles to specific environments. Specific topic areas include: a) development and maintenance methods and models, e.g., techniques and principles for the specification, design, and implementation of software systems, including notations and process models; b) assessment methods, e.g., software tests and validation, reliability models, test and diagnosis procedures, software redundancy and design for error control, and the measurements and evaluation of various aspects of the process and product; c) software project management, e.g., productivity factors, cost models, schedule and organizational issues, standards; d) tools and environments, e.g., specific tools, integrated tool environments including the associated architectures, databases, and parallel and distributed processing issues; e) system issues, e.g., hardware-software trade-off; and f) state-of-the-art surveys that provide a synthesis and comprehensive review of the historical development of one particular area of interest.

Full Aims & Scope

Meet Our Editors

Editor-in-Chief
Matthew B. Dwyer
Dept. Computer Science and Engineering
256 Avery Hall
University of Nebraska-Lincoln
Lincoln, NE 68588-0115 USA
tse-eic@computer.org