Issue 6 • Nov. 1996

Filter Results

Displaying Results 1 - 6 of 6
  • Specifying user knowledge for the design of interactive systems

    Publication Year: 1996, Page(s):323 - 333
    IEEE is not the copyright holder of this material | Click to expandAbstract | PDF file iconPDF (1119 KB)

    Minimum requirements for interactive systems to be usable and reliable include computer systems performing as intended, and users not making errors in issuing commands or in interpreting information from the device display, Traditionally, most approaches to software engineering have focused on the first of these concerns: correctness of system performance. However, it is equally important to deal ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Modelling status and event behaviour of interactive systems

    Publication Year: 1996, Page(s):334 - 346
    Cited by:  Papers (2)
    IEEE is not the copyright holder of this material | Click to expandAbstract | PDF file iconPDF (1582 KB)

    Interactive systems involve both events, which occur at specific moments (e.g. keystrokes, mouse clicks and beeps), and more persistent "status phenomena", which can be observed at any time (e.g. the position of the mouse or the image on the screen). Most formalisms used for interactive systems concentrate on one aspect or the other, and may be asymmetric in their treatment of input and output. No... View full abstract»

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

    Publication Year: 1996, Page(s):347 - 354
    IEEE is not the copyright holder of this material | Click to expandAbstract | PDF file iconPDF (955 KB)

    A simple language is demonstrated that combines specifications and manuals. This shows firstly that a user manual can be automatically reconstructed from a logic specification that is effectively identical to the original logic (up to ambiguities in natural language), and secondly that such an automated process can help detect errors. The process is fast and is suitable for use in participatory de... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Extending the application of formal methods to analyse human error and system failure during accident investigations

    Publication Year: 1996, Page(s):355 - 365
    Cited by:  Papers (2)
    IEEE is not the copyright holder of this material | Click to expandAbstract | PDF file iconPDF (1331 KB)

    Recent disasters at Bhopal, Chernobyl, Habsheim and Kegworth illustrate the point that software is rarely the sole cause behind major accidents. Operator intervention, hardware faults, even the weather conditions and malicious acts all combine to create the conditions for failure. In the aftermath of these accidents, it seems difficult for software engineers, systems developers, forensic scientist... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software Engineering Journal index

    Publication Year: 1996, Page(s):367 - 377
    IEEE is not the copyright holder of this material | PDF file iconPDF (968 KB)
    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Distributed software engineering [Book Review]

    Publication Year: 1996, Page(s): 381
    IEEE is not the copyright holder of this material | PDF file iconPDF (107 KB)
    Full text access may be available. Click article title to sign in or learn about subscription options.

Aims & Scope

Published from 1986-1996, Software Engineering Journal included original contributions of interest to practitioners, researchers and managers who were engaged in software engineering. It covered reports on practical experience using software engineering methods and tools, and papers on long-term research activities.

Full Aims & Scope