Scheduled System Maintenance:
Some services will be unavailable Sunday, March 29th through Monday, March 30th. We apologize for the inconvenience.
By Topic

Software, IEEE

Issue 1 • Date Jan.-Feb. 2007

Filter Results

Displaying Results 1 - 25 of 30
  • [Front cover]

    Publication Year: 2007 , Page(s): c1
    Save to Project icon | Request Permissions | PDF file iconPDF (1606 KB)  
    Freely Available from IEEE
  • Leading the Way in Software Engineering

    Publication Year: 2007 , Page(s): c2
    Save to Project icon | Request Permissions | PDF file iconPDF (1043 KB)  
    Freely Available from IEEE
  • Software 2007 Editorial Calendar

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

    Publication Year: 2007 , Page(s): 2 - 3
    Save to Project icon | Request Permissions | PDF file iconPDF (1564 KB)  
    Freely Available from IEEE
  • Article summaries

    Publication Year: 2007 , Page(s): 4
    Save to Project icon | Request Permissions | PDF file iconPDF (45 KB)  
    Freely Available from IEEE
  • IEEE Software--2007 and Beyond

    Publication Year: 2007 , Page(s): 5 - 7
    Save to Project icon | Request Permissions | PDF file iconPDF (155 KB) |  | HTML iconHTML  
    Freely Available from IEEE
  • Letters: Software Engineering Curricula Shortfalls

    Publication Year: 2007 , Page(s): 8
    Save to Project icon | Request Permissions | PDF file iconPDF (36 KB) |  | HTML iconHTML  
    Freely Available from IEEE
  • Driven to ... Discovering Your Design Values

    Publication Year: 2007 , Page(s): 9 - 11
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (2593 KB) |  | HTML iconHTML  

    Software development approaches all emphasize a core set of values and principles around which practices, techniques, and tools have emerged. A thoughtful designer should be able to pick and choose among practices without losing their essence. But not all practices are congruent View full abstract»

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

    Publication Year: 2007 , Page(s): 12 - 13
    Cited by:  Papers (1)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (179 KB) |  | HTML iconHTML  

    The Unix system and its pipelines are a model of software reuse. Although many subsequent developments weren't similarly successful, by looking at Wikipedia and its MediaWiki engine, we find many levels of successful reuse. It seems that software repositories, package-management systems, shared-library technologies, and language platforms have increased reuse's return on investment. The Internet has also catalyzed software reuse by bringing both developer groups and development efforts closer to their users View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • It Is What It Is Because It Was What It Was

    Publication Year: 2007 , Page(s): 14 - 15
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (405 KB) |  | HTML iconHTML  

    Software systems usually have the same basic architectural pattern as their earlier incarnations, manifesting in decreasingly refined forms as we move back in time. Similarly, when a new problem confronts us, we try many different approaches, but over time, for the same kind of problem, solutions tend to converge to the same, more constrained, solution space View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Personal Planning [Not Just Coding]

    Publication Year: 2007 , Page(s): 16 - 17
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (830 KB) |  | HTML iconHTML  

    Experienced programmers plan, while junior programmers jump into their work. Some simpler personal planning techniques can help you eliminate waste when you work, write less code, design more simply, inject fewer defects, and generally deliver sooner. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Guest Editors' Introduction: Why are Small Software Organizations Different?

    Publication Year: 2007 , Page(s): 18 - 22
    Cited by:  Papers (8)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1441 KB) |  | HTML iconHTML  

    Small software organizations--independently financed and organized companies with fewer than 50 employees--are fundamental to many national economies' growth. In the US, Brazil, Canada, China, India, Finland, Ireland, Hungary, and many other countries, small companies represent up to 85 percent of all software organizations. However, to persist and grow, small software companies need efficient, effective software engineering solutions. View full abstract»

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

    Publication Year: 2007 , Page(s): 23
    Save to Project icon | Request Permissions | PDF file iconPDF (36 KB)  
    Freely Available from IEEE
  • Adept: A Unified Assessment Method for Small Software Companies

    Publication Year: 2007 , Page(s): 24 - 31
    Cited by:  Papers (3)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1302 KB) |  | HTML iconHTML  

    Software process assessments are typically the first step to commencing software process improvement. Small software companies find that many assessment methods are linked to plan-driven improvement models and can be expensive in terms of the resources required. The authors support these claims with statistics from the Irish software industry and present a lightweight assessment method called Adept. Adept unifies an existing plan-driven assessment method and an adapted, risk-based agility/discipline assessment method. Adept has a low resource overhead and does not dictate either a plan-driven or agile process improvement model, making it an attractive assessment method for small software companies View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Value-Oriented Requirements Prioritization in a Small Development Organization

    Publication Year: 2007 , Page(s): 32 - 37
    Cited by:  Papers (8)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (151 KB) |  | HTML iconHTML  

    Requirements engineering, especially requirements prioritization and selection, plays a critical role in overall project development. In small companies, this often difficult process can affect not only project success but also overall company survivability. A value-oriented prioritization (VOP) framework can help this process by clarifying and quantifying the selection and prioritization issues. A case study of a small development company shows a successful VOP deployment that improved communications and saved time by focusing requirements decisions for new product releases on core company values View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Introducing Version Control to Database-Centric Applications in a Small Enterprise

    Publication Year: 2007 , Page(s): 38 - 44
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (267 KB) |  | HTML iconHTML  

    Employing version control and separating test and production systems from each other are well-known software engineering practices. However, small software development organizations sometimes neglect the corresponding tools and processes, partly because they lack experience, and partly because of genuine technical challenges. For example, decoupling the production and test environments using version control software is no trivial exercise in an environment of conflicting requirements, tight budget constraints and a high-volume, business-critical online database that must be kept synchronized with the source code. The authors' method of database schema version control converts schema elements into textual configuration items that an organization can manage using freely available open source tools View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • IEEE Computer Society Information

    Publication Year: 2007 , Page(s): 45
    Save to Project icon | Request Permissions | PDF file iconPDF (524 KB)  
    Freely Available from IEEE
  • An Open Source Approach to Developing Software in a Small Organization

    Publication Year: 2007 , Page(s): 46 - 53
    Cited by:  Papers (5)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (557 KB) |  | HTML iconHTML  

    The software development approach that developers at Kitware use borrows techniques from agile development and extreme programming and emphasizes long-term, ongoing projects. The company has used this approach on open source and closed-source projects in a wide range of sizes View full abstract»

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

    Publication Year: 2007 , Page(s): 54 - 57
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (191 KB) |  | HTML iconHTML  

    Sales, profits, and success are the goals of any business, large or small. Many factors can influence success, but when software development is an important business constituent, the relationship between the software product's characteristics and business goals is strong. We don't always recognize this, of course, because most of us became engineers for nobler reasons than serving a business - the intellectual challenge, the free T-shirts, the 2 a.m. beer and pizza to celebrate unit tests that are finally passing. But ultimately we must allow the choices we make in software development to be influenced by business goals, or else risk business failure View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Achieving Quality in Open-Source Software

    Publication Year: 2007 , Page(s): 58 - 64
    Cited by:  Papers (11)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (677 KB) |  | HTML iconHTML  

    The open source software community has published a substantial body of research on OSS quality. Focusing on this peer-reviewed body of work lets us draw conclusions from empirical data rather than rely on the large volume of evangelical opinion that has historically dominated this field. This body of published research has become much more critical and objective in its efforts to understand OSS development, and a consensus has emerged on the key components of high-quality OSS delivery. This article reviews this body of research and draws out lessons learned, investigating how the approaches used to deliver high-quality OSS differ from, and can be incorporated into, closed-source software development View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A Quantitative Approach to Software Development Using IEEE 982.1

    Publication Year: 2007 , Page(s): 65 - 72
    Cited by:  Papers (2)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (448 KB) |  | HTML iconHTML  

    Although software's complexity and scope have increased tremendously over the past few decades, advances in software engineering techniques have been only moderate at best. Software measurement has remained primarily a labor-intensive effort and thus subject to human limitations. The Space Shuttle's avionics software is an excellent example of how applying standards such as IEEE 982.1 can help alleviate human limitations by providing a quantitative roadmap to answer key questions View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Practitioner Tools and Workstyles for User-Interface Design

    Publication Year: 2007 , Page(s): 73 - 80
    Cited by:  Papers (2)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (610 KB) |  | HTML iconHTML  

    Many studies have analyzed general software development practices and how organizations can better support them. However, literature that qualitatively studies user-interface-related work practices in software development is relatively rare. Supporting workstyle transitions in UI practices is nonetheless important. A survey of 370 practitioners about their workstyles and tool use offers concrete examples of design tools that support the most important workstyle transitions. The survey also resulted in recommendations for making design tools more human-centric and appealing to practitioners interested in the UI aspects of software development View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • IEEE Computer Society Membership Information

    Publication Year: 2007 , Page(s): 81
    Save to Project icon | Request Permissions | PDF file iconPDF (3555 KB)  
    Freely Available from IEEE
  • CLAM: A Framework for Audio and Music Application Development

    Publication Year: 2007 , Page(s): 82 - 85
    Cited by:  Papers (4)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1047 KB) |  | HTML iconHTML  

    The CLAM (C++ Library for Audio and Music) development framework offers a complete R&D platform for the audio and music domain. Winner of the 2006 ACM Open Source Multimedia Software Competition, CLAM originated in an effort to organize a repository of audio-processing algorithms. Today it includes an abstract model for audio systems, a repository of processing algorithms and data types, and several tools and stand-alone applications. Developers can exploit all these features to build cross-platform applications or rapid prototypes for testing signal- and media-processing algorithms and systems View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • My Requirements? Well, That Depends

    Publication Year: 2007 , Page(s): 86 - 87
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (141 KB) |  | HTML iconHTML  

    Using scenarios can help you quantify your requirements. Scenarios make requirements quantification easier by describing and restricting the context necessary for quantification 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
Diomidis Spinellis
Athens University of Economics and Business
28is Oktovriou 76
Athina 104 33, Greece
dds@computer.org