By Topic

IEEE Software

Issue 5 • Date Sept. 1993

Filter Results

Displaying Results 1 - 12 of 12
  • Software-engineering research revisited

    Publication Year: 1993, Page(s):19 - 28
    Cited by:  Papers (40)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1269 KB)

    The author discusses three major changes that he suggests are occurring as a result of the software engineering industry adopting the industry-as-laboratory approach, in which researchers identify problems through close involvement with industrial projects and create and evaluate solutions in an almost indivisible research activity. This approach emphasizes what people actually do or can do in pra... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The software rush hour (software engineering)

    Publication Year: 1993, Page(s):29 - 37
    Cited by:  Papers (6)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1196 KB)

    The author states that, in his experience, software engineering most resembles a dynamically overloaded queue or rush-hour traffic jam. A change measurement model that is unique because it puts the development process in the context of the larger business enterprise and partitions work into dynamic tangible activities, separating work demand from work services, is proposed. Because the change-mana... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Lessons from three years of inspection data (software development)

    Publication Year: 1993, Page(s):38 - 45
    Cited by:  Papers (39)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1038 KB)

    The implementation of an inspection program as part of a standard development process for an operating system at Bull HN Information Systems Major Systems Division is reviewed. The methods used to collect and analyze the data and provide feedback to the development staff are described. The data are examined from the point of view of the entire organization and as they apply in individual case stud... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Learning from bugs (software quality control)

    Publication Year: 1993, Page(s):46 - 54
    Cited by:  Papers (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1698 KB)

    The SWQC program, a software quality-control program implemented at NEC that instills quality and teaches responsibility on the individual, group, and organizational levels, is reviewed. The critical elements of the program, the top-down and grass roots organizational models used in software quality control, and the twelve grass-roots quality-control activities used in SWQC are discussed, as are t... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Five ways to destroy a development project (software development)

    Publication Year: 1993, Page(s):55 - 58
    Cited by:  Papers (14)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (427 KB)

    The author discusses five problems that can contribute to a software project's failure. The five pitfalls are: inadequate system engineering during the proposal and during front-end development; inadequate tracing, tracking, and management of system and software requirements; improper sizing of the target hardware; selection of design, production, and integration and test methodologies that are in... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Lessons learned in an industrial software lab (software development)

    Publication Year: 1993, Page(s):58 - 61
    Cited by:  Papers (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (432 KB)

    The author offers a personal account of the issues and challenges that have confronted the software developer over the last few decades. The failures and successes associated with formal methods, the realities of reuse, and the implementation of development process models and goals are discussed.<> View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Get the design right (software prototyping)

    Publication Year: 1993, Page(s):61 - 63
    Cited by:  Papers (6)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (315 KB)

    The author suggests that prototyping, in addition to end-user interaction, is the best technique for developing correct software designs. He offers a personal account of a software project in which the need for end-user interaction became apparent, even though prototyping was used. Two problems associated with relying too much on prototyping are discussed.<> View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • What makes software tools successful?

    Publication Year: 1993, Page(s):63 - 65
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (338 KB)

    The author discusses ways to successfully move software technology forward. He relates his experiences in the field of software engineering to illustrate what he believes to be the problems of technology transfer and the requirements for successful technology transfer.<> View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Distributed, collaborative software inspection

    Publication Year: 1993, Page(s):66 - 75
    Cited by:  Papers (20)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1596 KB)

    The Collaborative Software Inspection (CSI) tool, which provides a distributed, structured environment for performing inspections on all software-development products, including specifications, designs, code, and test cases, is described. The inspection environment lets geographically distributed inspection participants meet with people in other cities through workstations at their desks. The curr... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Interfaces for the ordinary and beyond

    Publication Year: 1993, Page(s):76 - 78
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (541 KB)

    Several ways in which current computer interfaces discriminate against those who do not fit the accepted profile of the average user are described. A needs continuum for describing users' abilities and characteristics is presented. The parameters affecting a person's position within the continuum are discussed. The ways in which interface designers take into account a range of needs is also discus... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Trend is toward less copyright protection

    Publication Year: 1993, Page(s):82 - 84
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (366 KB)

    The cases of Whelan Associates vs. Jaslow Dental Laboratory, Computer Associates International Inc. vs. Altai, and Apple Computer Inc. vs. Microsoft Inc. are discussed to illustrate trends suggesting that software protection is shrinking, although that could result in the development of more program applications. The traditional and emerging standards of applying copyright protection to software a... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • How quality fits into package development

    Publication Year: 1993, Page(s):85 - 86
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (224 KB)

    The software-package segment of the software market most closely resembles the manufacturing-for-consumption model on which most quality techniques are based. The author reports on observations of the development processes in 15 package companies, specifically how these developers view quality-assurance practices and what they have in place.<> 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