By Topic

Software, IEEE

Issue 2 • Date March-April 2005

Filter Results

Displaying Results 1 - 24 of 24
  • [Front cover]

    Page(s): c1
    Save to Project icon | Request Permissions | PDF file iconPDF (700 KB)  
    Freely Available from IEEE
  • Congratulations to the 2004 CSDPs

    Page(s): 1
    Save to Project icon | Request Permissions | PDF file iconPDF (989 KB)  
    Freely Available from IEEE
  • Table of contents

    Page(s): 2 - 3
    Save to Project icon | Request Permissions | PDF file iconPDF (722 KB)  
    Freely Available from IEEE
  • Article Summaries

    Page(s): 4
    Save to Project icon | Request Permissions | PDF file iconPDF (36 KB)  
    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Constant Connectivity: Just Because You Can Doesn't Mean You Should

    Page(s): 5 - 7
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (160 KB)  

    The Netcraft annual Web server survey indicates more than 56 million Web servers were active at the end of 2004, and an average of 911,000 new sites are added each month. This doesn't include computers connected to the Internet as clients. Software developers continue to take advantage of this widespread connectivity. If developers can reduce that 56 million to only those systems that really need Internet access, they'd significantly reduce the probability of security holes due to mistakes and oversights. The author urges system architects to evaluate if the system they are designing really needs to be accessible via the Internet. They should ask themselves, Is providing information over the Internet really a core mission for my application, or is it just an "extra feature" that's inexpensive to add? The author also urges network engineers to consider laying two network drops when they run a LAN: one for a secure internal LAN and one for an open LAN connected to the Internet through a firewall. View full abstract»

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

    Page(s): 8 - 10
    Save to Project icon | Request Permissions | PDF file iconPDF (216 KB)  
    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Bugzilla, ITracker, and other bug trackers

    Page(s): 11 - 13
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (704 KB)  

    Bug-tracking helps the software developers in knowing what the error is, resolving it, and learning from it. Working on a software project includes managing the bugs we find. At first, we might list them on a spreadsheet. But when the number of bugs becomes too large and a lot of people must access and input data on them, we have to give up the spreadsheet and instead use a bug- or issue-tracking system. Many software projects reach this point, especially during testing and deployment when users tend to find an application's bugs. Nowadays we can choose among dozens of bug-tracking systems. This paper looks at two specific open source products and provides useful hints for working with any bug-tracking tool. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Dear editor [programming tools of the trade]

    Page(s): 14 - 15
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (360 KB)  

    In this article, we give some advices for the programmers for an efficient software design. Programmers are advised not to type what they can automate in the editor environment and don't use the editor feature where they can code. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Editor's Introduction: Software Design in a Postmodern Era

    Page(s): 16 - 18
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (760 KB)  

    Over the last 30 years, software design has made tremendous progress. But this progress hasn't been continuous: it proceeded by jumps and leaps, with some plateaus in between. Reaching a plateau isn't at all negative; it's a necessary step for a discipline to integrate good practices, to reflect, and to produce a critique that will launch further progress. Perhaps we've reached another, more fundamental plateau, wittily called the era of "postmodern programming" by James Noble and Robert Biddle. The author poses three questions regarding software design and then begins to answer them: Where are we? Where do we want to go from here? And what exactly is software design? View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Architecture decisions: demystifying architecture

    Page(s): 19 - 27
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (200 KB)  

    We believe that a key to demystifying architecture products lies in the architecture decisions concept. We can make the architecture more transparent and clarify its rationale for all stakeholders by explicitly documenting major architecture decisions. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • An ontology for microarchitectural design knowledge

    Page(s): 28 - 33
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (312 KB)  

    In this article, we present an ontology that structures and unifies this accumulated OO microarchitectural design knowledge. This ontology differentiates between declarative and operative knowledge, and encompasses rules, patterns, and refactorings. It also encompasses the differences and relationships between these types of knowledge. Our ontology helps to better understand how to implement and refactor OO design knowledge, thereby improving quality, reducing costs, and saving time. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Architecture reviews: practice and experience

    Page(s): 34 - 43
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (440 KB)  

    Architecture reviews have evolved over the past decade to become a critical part of our continuing efforts to improve the state of affairs. We use them to identify project problems before they become costly to fix and to provide timely information to upper management so that they can make better-informed decisions. It provides the foundation for reuse, using commercially available software, and getting to the marketplace fast. The reviews also help identify best practices to projects and socialize such practices across the organization, thereby improving the organization's quality and operations. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Model mapping using formalism extensions

    Page(s): 44 - 51
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (200 KB)  

    The Object Management Group's model driven architecture defines a system development approach that formally separates system specification from platform implementations - in platform-independent models and platform-specific models, respectively. According to MDA, software development involves a sequence of model mappings that transform an initial PIM to a final PSM that is precise enough for direct translation into an executable program. A mapping is a set of rules and techniques for translating one model into another. When the starting and final models are expressed in the same formalism, the mapping is said to be intralanguage; otherwise, it is interlanguage. We focus here on interlanguage mapping, showing the central role of formalism extension mechanisms in managing the abstraction-level gap between languages as well as the platform-level details of specific implementations. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Casting software design in the function-behavior-structure framework

    Page(s): 52 - 58
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (128 KB)  

    In this article, the author cast the software engineering process into the function-behavior-structure framework and thus into the broader framework of engineering design. By doing so, we can draw some lessons about the state of our favorite engineering discipline. The most important lesson might be that many of the analogies we've drawn from other engineering disciplines, especially civil engineering, are somewhat flawed or biased. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Developing the requirements discipline: software vs. systems

    Page(s): 59 - 61
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (160 KB)  

    The software engineering and systems engineering communities are establishing methods for capturing, specifying, and managing requirements. The cultural differences exist between the two. Requirements work is too important to be pioneered by a mainstream software-centric or -ignorant viewpoint. Each community must continue to learn from the other for our understanding of the requirements engineering discipline to continue to grow. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Positive reinforcement as a quality tool

    Page(s): 62 - 63
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (136 KB)  

    Many quality practitioners rely on auditing to verify compliance of process changes. However, when our division used a positive reinforcement approach to verify compliance, we saw deeper institutionalization of the desired organizational change. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Your coffee shop doesn't use two-phase commit [asynchronous messaging architecture]

    Page(s): 64 - 66
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (144 KB)  

    The real world is often asynchronous. Our daily lives consist of many coordinated but asynchronous interactions. This means that an asynchronous messaging architecture can often be a natural way to model these kinds of interactions. It also means that looking at daily life can help us solve our messaging problems. For example in this article we present how a coffee shop processes customer orders and compare it to the asynchronous processing model. View full abstract»

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

    Page(s): 67
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (39 KB)  

    Here is the first installment of a software engineering glossary of terminology for the use case domain. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Hypermedia systems development practices: a survey

    Page(s): 68 - 75
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (368 KB)  

    Merely calling a system "Web-based" doesn't necessarily imply that its software design differs much from that of a traditional system. When Web-based systems assume hypermedia functionality they become substantively different from a design perspective. Hypermedia technologies support much richer user interfaces, more complex navigation mechanisms, and more varied forms of information than traditional computer systems. In recent years, hypermedia systems (particularly Web-based ones) have grown in complexity and scope as they've begun to involve critical organizational activities such as customer support, sales and marketing, and technical support. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Automatic test case optimization: a bacteriologic algorithm

    Page(s): 76 - 82
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (400 KB)  

    Improving test cases automatically is a nonlinear optimization problem. To solve this problem, we've developed a bacteriologic algorithm, adapted from genetic algorithms that can generate and optimize a set of test cases. A .NET component that parses C# source files illustrates our algorithm. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Enter the protectionist dragon? [China's software and standards policies stir debate and reflection]

    Page(s): 83 - 87
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (824 KB)  

    China's economy holds perhaps the greatest opportunities in the world in the coming decades. The makers of all sorts of goods, from soda pop to software, are positioning themselves to take advantage of the projected phenomenal growth of the Chinese marketplace. Since its economic reforms of the late 1970s, China has made huge strides in becoming, a strongpoint for manufacturing and assembling goods to be sold worldwide. However, it has struggled to join the world's software development leaders. To encourage the domestic software industry's development, Chinese policy makers have written a series of regulations in the past five years. These give Chinese software developers tax incentives and mandate that government buyers give preference to domestic software. These regulations also encourage the development of open source software over proprietary software. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Using Test-Driven Software Development Tools

    Page(s): 88 - 91
    Save to Project icon | Request Permissions | PDF file iconPDF (152 KB)  
    Freely Available from IEEE
  • Our 2004 Reviewers

    Page(s): 92 - 93
    Save to Project icon | Request Permissions | PDF file iconPDF (58 KB)  
    Freely Available from IEEE
  • Software Engineering Theory in Practice

    Page(s): 96 - 95
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1336 KB)  

    Whether software engineering "best practices" really are the best depends on the type of project. Applying them could actually cause harm in some cases. 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
Forrest Shull
Fraunhofer Center for Experimental Software Engineering