Scheduled System Maintenance:
On May 6th, system maintenance will take place from 8:00 AM - 12:00 PM ET (12:00 - 16:00 UTC). During this time, there may be intermittent impact on performance. We apologize for the inconvenience.
By Topic

Software, IEEE

Issue 1 • Date Jan. 1991

Filter Results

Displaying Results 1 - 8 of 8
  • Making reuse cost-effective

    Publication Year: 1991 , Page(s): 13 - 24
    Cited by:  Papers (32)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1993 KB)  

    Until reuse is better understood, significant reductions in the cost of building large systems will not be possible. This assertion is based primarily on the belief that the defining characteristic of good reuse is not the reuse of software per se, but the reuse of human problem solving. Analytical approaches for making good reuse investments are suggested in terms of increasing a quality-of-investment measure, Q, which is simply the ratio of reuse benefits to reuse investments. The first strategy for increasing Q is to increase the level of consumer reuse. The second technique for increasing Q is to reduce the average cost of reusing work products by making them easy and inexpensive to reuse. The third strategy is to reduce investment costs. Reuse strategies, and reuse and parameterizations, are discussed.<> View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Experience with inspection in ultralarge-scale development

    Publication Year: 1991 , Page(s): 25 - 31
    Cited by:  Papers (30)  |  Patents (1)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1141 KB)  

    The use of code inspection to detect errors in ultralarge software projects is discussed. In particular, quantitative results based on a 1988 study of inspection of 2.5 million lines of high-level code at Bell-Northern Research are presented. The data represent one of the largest published studies in the industry and confirm that code inspection is still one of the most efficient ways to remove software defects. How to introduce inspections in large-scale production environments successfully is described.<> View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software risk management: principles and practices

    Publication Year: 1991 , Page(s): 32 - 41
    Cited by:  Papers (186)  |  Patents (2)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1317 KB)  

    The emerging discipline of software risk management is described. It is defined as an attempt to formalize the risk-oriented correlates of success into a readily applicable set of principles and practices. Its objectives are to identify, address, and eliminate risk items before they become either threats to successful software operation or major sources of software rework. The basic concepts are set forth, and the major steps and techniques involved in software risk management are explained. Suggestions for implementing risk management are provided.<> View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • MicroTool: an environment for programming microprocessors

    Publication Year: 1991 , Page(s): 42 - 48
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (767 KB)  

    A description is given of MicroTool, a programming environment that reports programming errors immediately, blocking their entry into the database from which both executable code and documentation are derived. MicroTool's primary objective is to maintain a consistent database, meaning that the program is correct as far as MicroTool can tell. Aspects of MicroTool that are discussed include feedback to programmers; smart editing windows; address space layout; the program model; data definition; algorithm definition; combining edit, compile, and link; time and space measurement; and programming style.<> View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Difficulties in integrating multiview development systems

    Publication Year: 1991 , Page(s): 49 - 57
    Cited by:  Papers (25)  |  Patents (1)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1122 KB)  

    Drawbacks of current approaches to integrating multiple perspectives in a development environment are discussed. An integrated environment is defined as one in which a dynamic collection of tools can work together on a single system so that changes made to the system by one tool can be seen by other tools, and integration criteria are set forth. Five representative approaches to systems integration-shared file systems, selective broadcasting, simple databases, view-oriented databases, and canonical representation-are examined, and their relative strengths and weaknesses are summarized. None of the integration mechanisms is shown to be uniformly superior to the others. The issue of environment evolution and its effect on integration is addressed.<> View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Blending imperative and relational programming

    Publication Year: 1991 , Page(s): 58 - 65
    Cited by:  Papers (3)  |  Patents (4)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (926 KB)  

    When imperative (value- or state-oriented) programming and logical (relation-oriented) programming are combined into a single language, the combination is even more powerful than when either technique is used alone. Leda, a strongly typed compiled language that tries to combine features of both, is described. Suggestions for blending the two styles are offered. Logical features of Leda are examined.<> View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • An overview of the Arjuna distributed programming system

    Publication Year: 1991 , Page(s): 66 - 73
    Cited by:  Papers (60)  |  Patents (5)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1269 KB)  

    The use of the objects and actions computational model to develop Arjuna is discussed, and its system architecture is described. An overview of Arjuna's implementation is given. An example is provided to show how to construct Arjuna applications.<> View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Two-dimensional pinpointing: debugging with formal specifications

    Publication Year: 1991 , Page(s): 74 - 84
    Cited by:  Papers (5)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1676 KB)  

    Debugging techniques and tools that draw on both the high-level concepts (defined as functions) used in formal specifications and the abstraction and information-hiding constructs used in modern languages are described. The technique is based on two components. One is a novel specification language with support tools. Ada programs are specified with a language that the authors created called Anna. Their tool set is used to check the Ada program's runtime behavior for consistency with the Anna specifications. The other technique uses the tool set to find missing specifications by comparing the specification with program prototypes and to test and debug Ada programs after an accepted specification has been developed. The approach, called two-dimensional pinpointing, locates inconsistencies in software that is structured in levels.<> View full abstract»

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

Aims & Scope

IEEE Software's mission is to build the community of leading and future software practitioners. The magazine 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