Scheduled System Maintenance
On Saturday, December 10, single article sales and account management will be unavailable from 5:00 AM-7:30 PM ET.
We apologize for the inconvenience.
By Topic

IEEE Software

Issue 6 • Nov.-Dec. 2009

Filter Results

Displaying Results 1 - 25 of 28
  • Front Cover

    Publication Year: 2009, Page(s): c1
    Request permission for commercial reuse | PDF file iconPDF (3383 KB)
    Freely Available from IEEE
  • John Wiley & Sons [advertisement]

    Publication Year: 2009, Page(s): c2
    Request permission for commercial reuse | PDF file iconPDF (236 KB)
    Freely Available from IEEE
  • Requirements Engineering Conference 2010 Advertisement

    Publication Year: 2009, Page(s): 1
    Request permission for commercial reuse | PDF file iconPDF (12063 KB)
    Freely Available from IEEE
  • Table of Contents

    Publication Year: 2009, Page(s):2 - 3
    Request permission for commercial reuse | PDF file iconPDF (3119 KB)
    Freely Available from IEEE
  • A Process That Is Not

    Publication Year: 2009, Page(s):4 - 7
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (619 KB) | HTML iconHTML

    TikiWiki is a large open source project that embraces Eric Raymond's Bazaar model. TikiWiki is highly successful, yet it adopts a process that lacks many of the characteristics that are thought to be necessary for projects of comparable size and complexity. The article discusses TikiWiki's development in the context of these characteristics. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • An Agile Cure for All Ills?

    Publication Year: 2009, Page(s): 8
    Request permission for commercial reuse | PDF file iconPDF (111 KB) | HTML iconHTML
    Freely Available from IEEE
  • The Responsible Designer

    Publication Year: 2009, Page(s):9 - 10
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (250 KB) | HTML iconHTML

    Successful software systems often live far longer than their original designers anticipated. And over their lifetime, most of those systems evolve. Developers who make modifications, fix bugs, and add new features to long-lived systems have an easier time of it if they keep the code base habitable ("Creating Sustainable Designs," Rebecca Wirfs-Brock, IEEE Software, May/June 2009) and preserve desi... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Agile Documentation, Anyone?

    Publication Year: 2009, Page(s):11 - 12
    Cited by:  Papers (7)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (263 KB) | HTML iconHTML

    Software developers are notorious for skimping on design documentation, often eschewing it altogether. This trend has led to claims that it is merely an impediment in the fast-paced and highly pliable world of software development-a useless vestige of old-style engineering that should be eliminated altogether. While recognizing the unique nature of software, the author argues that, because of the ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Oi, Analyst You're Barred!

    Publication Year: 2009, Page(s):13 - 14
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (241 KB) | HTML iconHTML

    The team of international requirements engineering board enabled standardization in what a requirement analyst is and does, the team has established a common vocabulary for talking about task, techniques, skills and roles. It has also created a syllabus and examinations for certifying such analysts, with the goal being that a certified requirements analyst should know important terms and technique... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software Abundance in the Face of Economic Scarcity, Part 2

    Publication Year: 2009, Page(s):15 - 16
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (236 KB) | HTML iconHTML

    The paper is an editorial that discusses the economics aspect of software industry. The author states that we are in a period of global economic funk, by virtually every measure that we can take. The good news is that we've been here before over the years and we've always seemed to get by. Software is still the most fungible and liquid of resources, and its supply is limited only by human imaginat... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Guest Editors' Introduction: Cooperative and Human Aspects of Software Engineering

    Publication Year: 2009, Page(s):17 - 19
    Cited by:  Papers (8)
    Request permission for commercial reuse | PDF file iconPDF (2946 KB) | HTML iconHTML
    Freely Available from IEEE
  • Overcoming Barriers to Self-Management in Software Teams

    Publication Year: 2009, Page(s):20 - 26
    Cited by:  Papers (17)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1277 KB) | HTML iconHTML

    The basic work unit in innovative software organizations is the team rather than the individual. Such teams consist of "a small number of people with complementary skills who are committed to a common purpose, set of performance goals, and approach for which they hold themselves mutually accountable". Work teams have many advantages, such as increased productivity, innovation, and employee satisfa... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • What Makes APIs Hard to Learn? Answers from Developers

    Publication Year: 2009, Page(s):27 - 34
    Cited by:  Papers (42)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (704 KB) | HTML iconHTML

    The paper discusses the application program interface (API). Most software projects reuse components exposed through APIs. In fact, current-day software development technologies are becoming inseparable from the large APIs they provide. An API is the interface to implemented functionality that developers can access to perform various tasks. APIs support code reuse, provide high-level abstractions ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Trust in Distributed Teams: Support through Continuous Coordination

    Publication Year: 2009, Page(s):35 - 40
    Cited by:  Papers (6)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2262 KB) | HTML iconHTML

    In this article we report on our investigation of trust in distributed development teams and the role that software tools can play in supporting teams. Our investigation shows that the continuous coordination paradigm tools Palantir, Ariadne, World View, and Workspace Activity Viewer help distributed teams develop trust by sharing information across boundaries through visualizations and in other w... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • ERP Customization as Software Engineering: Knowledge Sharing and Cooperation

    Publication Year: 2009, Page(s):41 - 47
    Cited by:  Papers (18)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1427 KB) | HTML iconHTML

    Enterprise resource planning (ERP) vendors provide multiple configuration possibilities ranging from module selection to master data provision to steer access rights for different users. These configuration possibilities cover anticipated variability. If the customer requires adaptation beyond what's anticipated, the source code of the product must be adapted. Customizations in this article's cont... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Community Collaboration for ERP Implementation

    Publication Year: 2009, Page(s):48 - 55
    Cited by:  Papers (5)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1253 KB) | HTML iconHTML

    The paper discusses the enterprise resource planning (ERP).ERP implementation solves business problems by customizing and integrating off-the-shelf enterprise software packages. A successful ERP implementation involves extensive collaboration and communication among the customer, implementation consultancy, and software vendor. Collaboration allows implementation personnel from different organizat... View full abstract»

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

    Publication Year: 2009, Page(s):56 - 59
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1294 KB) | HTML iconHTML

    The need for empirical research into the practicality and efficacy of software development methods is obvious but most published papers have inadequate experimental design. The assumption that what programmers do is "natural," and somehow right or practical, needs to be questioned seriously. Human beings haven't evolved by natural selection to be good programmers. There are people alive today who ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software Mythbusters Explore Formal Methods

    Publication Year: 2009, Page(s):60 - 63
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (387 KB) | HTML iconHTML

    In 1990, Anthony Hall identified and challenged seven common myths about formal methods in the IEEE Software article "Seven Myths of Formal Methods." This update re-examines those myths, reflecting both on the authors' experience with formal methods in practice and on their persistent mythic status View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Continuing Prospects for an Engineering Discipline of Software

    Publication Year: 2009, Page(s):64 - 67
    Cited by:  Papers (6)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (355 KB) | HTML iconHTML

    In her 1990 IEEE Software article "Prospects for an Engineering Discipline of Software" (Nov./Dec, pp. 15-24), Mary Shaw identified the key areas that the software development profession must address to become a true engineering discipline. That classic article made the magazine's 25th anniversary top picks list (Jan./Feb. 2009, pp. 9-11). Here, Mary reflects on the evolution of her thinking since... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Learning from Failure, Part 1: Scoping and Requirements Woes

    Publication Year: 2009, Page(s):68 - 69
    Cited by:  Papers (9)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (249 KB) | HTML iconHTML

    The paper is an editorial on software architecture. Software projects fail for the same reasons. The mistakes that can lead software projects to trouble before concrete architecture elaboration even begins include missing, wrong, or creeping system scope; and vague, unnecessary, or extreme nonfunctional requirements. These mistakes aren't the prime responsibility of architects, but architects are ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Parallelizing Bzip2: A Case Study in Multicore Software Engineering

    Publication Year: 2009, Page(s):70 - 77
    Cited by:  Papers (8)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1001 KB) | HTML iconHTML

    We conducted a case study of parallelizing a real program for multicore computers using currently available libraries and tools. We selected the sequential Bzip2 compression program for the study because it's a computing-intensive, widely used, and relevant application in everyday life. Its source code is available, and its algorithm is well documented. In addition, the algorithm is non-trivial, b... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Back to the Future: Omniscient Debugging

    Publication Year: 2009, Page(s):78 - 85
    Cited by:  Papers (13)  |  Patents (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (16500 KB) | HTML iconHTML

    This article presents TOD (trace oriented debugger), a prototype scalable omniscient debugger for Java, which aims at making omniscient debugging practical, at last. Omniscient debuggers, also known as back-in-time or reversible debuggers, record the whole history, or execution trace, of a debugged program and let the user freely explore it. This approach combines the advantages of both log-based ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Basic Etiquette of Technical Communication

    Publication Year: 2009, Page(s):86 - 87
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (240 KB) | HTML iconHTML

    Advice on courteousness and politeness in technical communication is in short supply, yet this is needed when developers communicate with other people. When discussing technical problems, aim to encourage rather than complain, focusing on technology issues rather than the people behind them. Every email should tackle one topic and that topic should be the subject line. Quote email discussions with... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The Task-Based Interface: Not Your Father's Desktop

    Publication Year: 2009, Page(s):88 - 91
    Cited by:  Papers (1)
    Request permission for commercial reuse | PDF file iconPDF (1249 KB) | HTML iconHTML
    Freely Available from IEEE
  • Measuring Developers: Aligning Perspectives and Other Best Practices

    Publication Year: 2009, Page(s):92 - 94
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (327 KB) | HTML iconHTML

    The paper discusses the software metrics programs. Software metrics programs might rank among the all-time touchiest subjects in software development. Done well, a measurement program can prove an effective tool for keeping on top of development effort-especially for large, distributed projects. It can help developers feel that they have a fair and objective way of communicating their progress and... 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