By Topic

IEEE Software

Issue 3 • Date May-June 1997

Filter Results

Displaying Results 1 - 24 of 24
  • Ariane 5: Who Dunnit?

    Publication Year: 1997, Page(s):15 - 16
    Cited by:  Papers (25)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (127 KB)

    First Page of the Article
    View full abstract»

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

    Publication Year: 1997, Page(s):17 - 19
    Cited by:  Papers (11)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (114 KB)

    First Page of the Article
    View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Risk management may not be for everyone

    Publication Year: 1997, Page(s):21 - 24
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (115 KB)

    First Page of the Article
    View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • An Information Architecture For Risk Assessment And Management

    Publication Year: 1997, Page(s):25 - 34
    Cited by:  Papers (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (503 KB)

    First Page of the Article
    View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Classifying software-based cache coherence solutions

    Publication Year: 1997, Page(s):90 - 101
    Cited by:  Papers (7)  |  Patents (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (461 KB)

    The authors propose a classification for software solutions to cache coherence in shared memory multiprocessors and show how it can be applied to more completely understand existing approaches and explore possible alternatives. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Guidelines for applying research results

    Publication Year: 1997, Page(s):102 - 104
    Request permission for commercial reuse | PDF file iconPDF (154 KB)
    Freely Available from IEEE
  • Programming with class: a C++ introduction to computer science [Book Review]

    Publication Year: 1997, Page(s): 122
    Request permission for commercial reuse | PDF file iconPDF (139 KB)
    Freely Available from IEEE
  • The craft software testing [Book Reviews]

    Publication Year: 1997, Page(s): 123
    Request permission for commercial reuse | PDF file iconPDF (130 KB)
    Freely Available from IEEE
  • Operating Systems [Book Reviews]

    Publication Year: 1997, Page(s): 123
    Request permission for commercial reuse | PDF file iconPDF (130 KB)
    Freely Available from IEEE
  • Executive guide to preventing information technology disasters [Book Reviews]

    Publication Year: 1997, Page(s): 124
    Request permission for commercial reuse | PDF file iconPDF (147 KB)
    Freely Available from IEEE
  • Managing a programming project-Processes and People [Book Reviews]

    Publication Year: 1997, Page(s): 124
    Request permission for commercial reuse | PDF file iconPDF (147 KB)
    Freely Available from IEEE
  • Managing risk in software maintenance

    Publication Year: 1997, Page(s):43 - 50
    Cited by:  Papers (17)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (168 KB)

    Software risk management in maintenance differs in major ways from risk management in development. Risk opportunities are more frequent, risks come from more diverse sources, and projects have less freedom to act on them. The authors describe how they dealt with these differences in a large US Navy software maintenance organization View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Gauging software readiness with defect tracking

    Publication Year: 1997
    Cited by:  Papers (6)  |  Patents (15)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (124 KB)

    In the competitive commercial software market, companies feel compelled to release software the moment it is ready. Their task is treacherous, treading the line between releasing poor quality software early and high quality software late, Finding a sound answer to the question: “is the software good enough to release now?” can be critical to a company's survival. That answer is, someti... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Testing for millennium risk management

    Publication Year: 1997, Page(s):126 - 127, 130-1
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (296 KB)

    The Year 2000 conversion is a challenge to the economics of both testing and maintenance, but as a whole we are not responding with balanced priorities. Those looking for Year 2000 solutions typically allocate their first energies and budgets to acquiring automated analysis and conversion deals and services. This disturbing tendency ignores two facts that surface in virtually every analysis of the... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Implementing risk management on software intensive projects

    Publication Year: 1997, Page(s):83 - 89
    Cited by:  Papers (26)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (132 KB)

    Rising costs, falling performance, and slipping schedules are common problems on large scale software projects. The authors describe key risk issues and how they were mitigated in one DoD (military) project View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Risk management is project management for adults

    Publication Year: 1997
    Cited by:  Papers (5)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (132 KB)

    Too often in the software industry, organizations approach project management in the same way a desperate gambler approaches the tables at Las Vegas or Monaco-with only one thought in mind: roll the dice. In a dice-tossing project, there is nothing you can do to improve your odds. Of course, that is not true for your software projects, but nothing you can do will make your risks go away completely... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • How experienced project managers assess risk

    Publication Year: 1997, Page(s):35 - 41
    Cited by:  Papers (39)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (116 KB)

    Software development projects, given their diverse and abstract nature, offer unique challenges and risks. Although a substantial body of literature has been written to address project risk management, my experience in the field led me to question whether this literature accurately mirrors the concerns of real-world project managers. To confirm my suspicions, I surveyed 14 experienced application ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Heuristic risk assessment using cost factors

    Publication Year: 1997, Page(s):51 - 59
    Cited by:  Papers (23)  |  Patents (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (412 KB)

    The author describes an expert system tool that can be used to analyze patterns of software cost driver ratings submitted for a Cocomo cost estimate. These results help users determine and rank associated sources of software project risk View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Integrating risk assessment with cost estimation

    Publication Year: 1997, Page(s):61 - 67
    Cited by:  Papers (18)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (192 KB)

    Incorporating hard data into risk estimates can help make them more accurate. The author developed a quantitative method and a corresponding tool that draw on questionnaires and project history to help calculate software project risk contingencies: RiskMethod and RiskTool View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software “engineer”? Time will tell

    Publication Year: 1997, Page(s):105 - 106
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (84 KB)

    A discussion is given on the legal and policy aspects of information technology use and development in the US. There is a continuing proliferation of individuals and companies who portray themselves as being or employing software “gurus”, “experts” and “engineers”-titles that imply the knowledge and capability to resolve programming problems. Many of these indiv... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Putting risk management into practice

    Publication Year: 1997, Page(s):75 - 82
    Cited by:  Papers (21)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (172 KB)

    The authors use an SEI designed road map as a guide to discussing effective and ineffective risk management methods based on six years' experience with software intensive DoD programs. These programs followed the SEI approach of continuous and team risk management, selecting processes and methods that would best fit their work cultures View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The project scoping gamble

    Publication Year: 1997, Page(s):107 - 109
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (208 KB)

    A discussion is given on how to get people and technology to work together. The authors argue that software project managers can learn important lessons from the gambler. Software development is a gamble. Its a risky game-not unlike high stakes poker. And, like a gambler who must try to figure the best bet, when we're put on the spot trying to “scope” a software project we feel in need... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Estimates, uncertainty, and risk

    Publication Year: 1997, Page(s):69 - 74
    Cited by:  Papers (42)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (132 KB)

    The authors discuss the sources of uncertainty and risk, their implications for software organizations, and how risk and uncertainty can be managed. Specifically, they assert that uncertainty and risk cannot be managed effectively at the individual project level. These factors must be considered in an organizational context View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Let's ask the users [user interfaces]

    Publication Year: 1997, Page(s):110 - 111
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (100 KB)

    Tools, techniques, and concepts to optimize user interfaces are presented. Many aspects of usability can best be studied by simply asking the users. This is especially true for issues related to user satisfaction and anxiety, which are hard to measure objectively. Questionnaires and interviews are two methods you can use to determine how people use a system and what features they particularly like... 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