By Topic

IEEE Software

Issue 6 • Date Nov.-Dec. 2011

Filter Results

Displaying Results 1 - 25 of 28
  • Front Cover

    Publication Year: 2011, Page(s): c1
    Request permission for commercial reuse | PDF file iconPDF (1123 KB)
    Freely Available from IEEE
  • Charter Business Advertisement

    Publication Year: 2011, Page(s): c2
    Request permission for commercial reuse | PDF file iconPDF (523 KB)
    Freely Available from IEEE
  • IEEE Computer Society CSDP

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

    Publication Year: 2011, Page(s):2 - 3
    Request permission for commercial reuse | PDF file iconPDF (1095 KB)
    Freely Available from IEEE
  • Assuring the Future? A Look at Validating Climate Model Software

    Publication Year: 2011, Page(s):4 - 8
    Request permission for commercial reuse | PDF file iconPDF (2512 KB) | HTML iconHTML
    Freely Available from IEEE
  • What an Agile Architect Can Learn from a Hurricane Meteorologist

    Publication Year: 2011, Page(s):9 - 12
    Cited by:  Papers (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (910 KB) | HTML iconHTML

    You'll have to read further to find out! There are so many interesting things about this article-it's the first in a series based on presentations from the SATURN conference. My first college degree was in chemistry, so there was an immediate connection for me with this story about chemical abstracts. The author brings us architectural wisdom, combined with an agile point of view and weather forec... View full abstract»

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

    Publication Year: 2011, Page(s):13 - 17
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1949 KB) | HTML iconHTML

    Software systems must continually evolve to meet ever changing needs. However, such systems often become legacy systems as a consequence of uncontrolled maintenance combined with obsolete technology. To control maintenance costs and preserve complex embedded business rules, companies must evolve their legacy systems. This article introduces technologies for software reengineering. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The Architecture of Small Things

    Publication Year: 2011, Page(s):18 - 19
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (269 KB) | HTML iconHTML

    There is complexity, and then there is organized complexity. Pure complexity is chaotic; organized complexity is full of patterns. Naming these patterns and respecting their intention is the essence of architecture. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • From Programming to Modeling - and Back Again

    Publication Year: 2011, Page(s):20 - 25
    Cited by:  Papers (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (714 KB) | HTML iconHTML

    The authors describe an issue that they think is extremely important: the relationship between applications and solutions in the software engineering and information systems fields. In particular, they believe the fields desperately need a taxonomy of application domains, a taxonomy of solution approaches, and a mapping between the two. This article has a Web extra that offers an interview with on... View full abstract»

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

    Publication Year: 2011, Page(s):26 - 28
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (686 KB) | HTML iconHTML

    Given the parallels between the complexity of human spaceflight and large software systems, there are many things we developers can learn from successful space programs, such as the Soyuz. First, limiting a project's scope and complexity early on can have a dramatic payoff in its success and longevity. In addition, adding generous margins to early estimates (and any subsequent revisions) will ease... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • To Pay or Not to Pay Technical Debt

    Publication Year: 2011, Page(s):29 - 31
    Cited by:  Papers (6)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (305 KB) | HTML iconHTML

    Ward Cunningham coined the term technical debt as a metaphor for the trade-off between writing clean code at higher cost and delayed de livery, and writing messy code cheap and fast at the cost of higher maintenance efforts once it's shipped. Joshua Kerievsky extended the metaphor to architecture and design. Technical debt is similar to financial debt: it supports quick development at the cost of ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Guest Editors' Introduction: Climate Change - Science and Software

    Publication Year: 2011, Page(s):32 - 35
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2891 KB) | HTML iconHTML

    Climate change is likely to be one of the defining global issues of the 21st century. The past decade—the hottest in recorded history—has witnessed countries around the world struggling to deal with drought, heat waves, and extreme weather. The sheer scale of the problem also makes it hard to understand, predict, and solve. Climate science journals regularly publish special issues ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Clear Climate Code: Rewriting Legacy Science Software for Clarity

    Publication Year: 2011, Page(s):36 - 42
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2954 KB) | HTML iconHTML

    The Clear Climate Code project rewrote GISTEMP, a legacy software system used to produce an important global surface temperature dataset. The focus of the project is on clarity: making the source code as clear as possible to interested people, to improve public understanding. The result is a Python package that's easy to understand, run, and change, which allows any interested person to pose and a... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Managing Software Complexity and Variability in Coupled Climate Models

    Publication Year: 2011, Page(s):43 - 48
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1361 KB) | HTML iconHTML

    Coupled climate models exhibit scientific, numerical, and architectural variability. This variability introduces requirements that give rise to complexity. However, techniques exist that can tame this complexity; one such technique is feature analysis. As climate model fidelity and complexity increase, the climate-modeling community should adopt a systematic way to deal with software variability. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software Testing and Verification in Climate Model Development

    Publication Year: 2011, Page(s):49 - 55
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2449 KB) | HTML iconHTML

    Over the past 30 years, most climate models have grown from relatively simple representations of a few atmospheric processes to complex multidisciplinary systems. Computer infrastructure over that period has gone from punchcard mainframes to modern parallel clusters. Model implementations have become complex, brittle, and increasingly difficult to extend and maintain. Verification processes for mo... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Enabling Open Development Methodologies in Climate Change Assessment Modeling

    Publication Year: 2011, Page(s):56 - 61
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (737 KB) | HTML iconHTML

    Computational simulation models help support scientifically grounded "what if" analyses by translating specialized knowledge into tools that can project the likely future impact of current actions. Models have thus become important in a variety of policy domains. In recent years, several software platforms for environmental policy-making and urban planning have added simulation models to decision ... View full abstract»

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

    Publication Year: 2011, Page(s):62 - 65
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (525 KB) | HTML iconHTML

    In "Open Source Climate Model Development Is Worth It," Isaac Held explains that a fully open source climate-modeling effort could be of great pedagogical value and maybe even of direct scientific importance by providing a toolbox for active researchers and people new to the field. In "Should Climate Models Be Open Source?" David Randall explains that ommunity-based climate model development can b... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Pattern-Based Architecture Reviews

    Publication Year: 2011, Page(s):66 - 71
    Cited by:  Papers (5)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1540 KB) | HTML iconHTML

    Software architecture reviews are effective in identifying potential problems in architectures, however, are expensive, time-consuming, and generally rely on extensive architecture documentation. An architecture review that accommodates projects with very short development cycles, minimal documentation, or frequently changing requirements could be useful if it identifies important architectural is... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Using Guidelines to Improve Quality in Software Nonfunctional Attributes

    Publication Year: 2011, Page(s):72 - 77
    Cited by:  Papers (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1893 KB) | HTML iconHTML

    Software development aims to produce software systems that satisfy two requirement categories: functional and quality. One aspect of software quality is nonfunctional attributes (NFAs), such as security, performance, and availability. Software engineers can meet NFA requirements by applying suitable guidelines during software development. However, this process is complicated by the different effec... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • SASSY: A Framework for Self-Architecting Service-Oriented Systems

    Publication Year: 2011, Page(s):78 - 85
    Cited by:  Papers (11)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2473 KB) | HTML iconHTML

    Making architectural decisions manually in the presence of quality-of-service trade-offs can be complicated. The SASSY (Self-architecting Software Systems) framework automatically generates candidate software architectures and selects the one that best serves stakeholder-defined, scenario-based quality-of-service (QoS) goals. This lets domain experts concentrate on functional and QoS requirements.... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Verification and Validation for Trustworthy Software Systems

    Publication Year: 2011, Page(s):86 - 92
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1225 KB) | HTML iconHTML

    A continuous and proactive process for conducting verification and validation of systems involves using scenario-based testing to validate whether formal assertions correctly capture the intent of the natural language requirements. The process is automated through the use of statechart assertions and runtime execution monitoring. The statechart assertions can be used as part of a system reference ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • 10 MLOC in Your Office Copier

    Publication Year: 2011, Page(s):93 - 95
    Cited by:  Papers (2)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (563 KB) | HTML iconHTML

    Amid the obvious volume of digital copiers and multifunction printers, the system size is in the millions of lines of code with functionality creep into several overlapping areas-a theme of many modern systems. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Developing Fault-Prediction Models: What the Research Can Show Industry

    Publication Year: 2011, Page(s):96 - 99
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (383 KB) | HTML iconHTML

    A systematic review of the research literature on fault-prediction models from 2000 through 2010 identified 36 studies that sufficiently defined their models and development context and methodology. The authors quantitatively analyzed 19 of these studies and the 206 models they presented. They identified several key features to help industry software developers build or optimize fault-prediction m... View full abstract»

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

    Publication Year: 2011, Page(s):100 - 102
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (386 KB) | HTML iconHTML

    Requirements analysts need to ask the right questions repeatedly. They need to be more inquisitive and know why people want things as well as what happens beforehand. This requires them to become less inhibited and keep asking questions until they and their stakeholders are satisfied with the answers. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • All Late Projects Are the Same

    Publication Year: 2011, Page(s): 104
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (353 KB) | HTML iconHTML Multimedia Media

    Lateness is the most common form of software project failure. Its causes can seem complex when viewed from ground level, but surprising simple with a slightly more distanced perspective. Note: Philippe Kruchten's last name is misspelled in the article sidebar. We apologize for this error. 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