By Topic

IEEE Transactions on Software Engineering

Issue 2 • Date March-April 2008

Filter Results

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

    Publication Year: 2008, Page(s): c1
    Request permission for commercial reuse | PDF file iconPDF (92 KB)
    Freely Available from IEEE
  • [Inside front cover]

    Publication Year: 2008, Page(s): c2
    Request permission for commercial reuse | PDF file iconPDF (76 KB)
    Freely Available from IEEE
  • Editorial: New Associate Editor Introduction

    Publication Year: 2008, Page(s): 161
    Request permission for commercial reuse | PDF file iconPDF (49 KB)
    Freely Available from IEEE
  • Aspectual Feature Modules

    Publication Year: 2008, Page(s):162 - 180
    Cited by:  Papers (38)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2880 KB) | HTML iconHTML

    Two programming paradigms are gaining attention in the overlapping fields of software product lines (SPLs) and incremental software development (ISD). Feature-oriented programming (FOP) aims at large-scale compositional programming and feature modularity in SPLs using ISD. Aspect-oriented programming (AOP) focuses on the modularization of crosscutting concerns in complex software. Although feature... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Classifying Software Changes: Clean or Buggy?

    Publication Year: 2008, Page(s):181 - 196
    Cited by:  Papers (112)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (4328 KB) | HTML iconHTML

    This paper introduces a new technique for predicting latent software bugs, called change classification. Change classification uses a machine learning classifier to determine whether a new software change is more similar to prior buggy changes or clean changes. In this manner, change classification predicts the existence of bugs in software changes. The classifier is trained using features (in the... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The Effect of Pairs in Program Design Tasks

    Publication Year: 2008, Page(s):197 - 211
    Cited by:  Papers (14)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (3665 KB) | HTML iconHTML

    Pair programming involves-two developers simultaneously collaborating with each other on the same programming task to design and code a solution. Algorithm design and its implementation are normally interwoven in that implementation often provides feedback to enhance the design. Previous controlled pair programming experiments did not explore the efficacy of pairs versus individuals in program des... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The Impact of Employee Participation on the Use of an Electronic Process Guide: A Longitudinal Case Study

    Publication Year: 2008, Page(s):212 - 225
    Cited by:  Papers (9)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2053 KB) | HTML iconHTML

    Many software companies disseminate process knowledge through electronic process guides. A common problem with such guides is that they are not used. Through a case study, we investigated how participation in creating an electronic process guide, through process workshops, influenced the use of the guide. We studied developer and project manager usage with respect to three factors: frequency of us... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Problem Oriented Software Engineering: Solving the Package Router Control Problem

    Publication Year: 2008, Page(s):226 - 241
    Cited by:  Papers (29)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2169 KB) | HTML iconHTML

    Problem orientation is gaining interest as a way of approaching the development of software intensive systems, and yet, a significant example that explores its use is missing from the literature. In this paper, we present the basic elements of Problem Oriented Software Engineering (POSE), which aims at bringing both nonformal and formal aspects of software development together in a single framewor... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The Role of Deliberate Artificial Design Elements in Software Engineering Experiments

    Publication Year: 2008, Page(s):242 - 259
    Cited by:  Papers (22)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2167 KB) | HTML iconHTML

    Increased realism in software engineering experiments is often promoted as an important means of increasing generalizability and industrial relevance. In this context, artificiality, e.g., the use of constructed tasks in place of realistic tasks, is seen as a threat. In this paper, we examine the opposite view that deliberately introduced artificial design elements may increase knowledge gain and ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software Architecture Visualization: An Evaluation Framework and Its Application

    Publication Year: 2008, Page(s):260 - 270
    Cited by:  Papers (7)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2465 KB) | HTML iconHTML

    In order to characterize and improve software architecture visualization practice, the paper derives and constructs a qualitative framework, with seven key areas and 31 features, for the assessment of software architecture visualization tools. The framework is derived by the application of the Goal Question Metric paradigm to information obtained from a literature survey and addresses a number of ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A State-of-the-Practice Survey of Risk Management in Development with Off-the-Shelf Software Components

    Publication Year: 2008, Page(s):271 - 286
    Cited by:  Papers (27)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (6391 KB) | HTML iconHTML

    An international survey on risk management in software development with off-the-shelf (OTS) components is reported upon and discussed. The survey investigated actual risk-management activities and their correlations with the occurrences of typical risks in OTS component-based development. Data from 133 software projects in Norway, Italy, and Germany were collected using a stratified random sample ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Using the Conceptual Cohesion of Classes for Fault Prediction in Object-Oriented Systems

    Publication Year: 2008, Page(s):287 - 300
    Cited by:  Papers (97)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1684 KB) | HTML iconHTML

    High cohesion is a desirable property of software as it positively impacts understanding, reuse, and maintenance. Currently proposed measures for cohesion in Object-Oriented (OO) software reflect particular interpretations of cohesion and capture different aspects of it. Existing approaches are largely based on using the structural information from the source code, such as attribute references, in... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • On the Distribution of Software Faults

    Publication Year: 2008, Page(s):301 - 302
    Cited by:  Papers (19)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (529 KB) | HTML iconHTML

    The Pareto principle is often used to describe how faults in large software systems are distributed over modules. A recent paper by Andersson and Runeson again confirmed the Pareto principle of fault distribution. In this paper, we show that the distribution of software faults can be more precisely described as the Weibull distribution. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Errata for "Discovering Documentation for Java Container Classes" [Aug 07 526-543]

    Publication Year: 2008, Page(s): 303
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (41 KB) | HTML iconHTML

    In the above titled paper (ibid., vol. 33, no. 8, pp. 526-543, Aug 07), there were several mistakes. The corrections are presented here. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Call for Papers: Search-Based Optimization for Software Engineering

    Publication Year: 2008, Page(s): 304
    Request permission for commercial reuse | PDF file iconPDF (43 KB)
    Freely Available from IEEE
  • TSE Information for authors

    Publication Year: 2008, Page(s): c3
    Request permission for commercial reuse | PDF file iconPDF (76 KB)
    Freely Available from IEEE
  • [Back cover]

    Publication Year: 2008, Page(s): c4
    Request permission for commercial reuse | PDF file iconPDF (92 KB)
    Freely Available from IEEE

Aims & Scope

The IEEE Transactions on Software Engineering is interested in well-defined theoretical results and empirical studies that have potential impact on the construction, analysis, or management of software. The scope of this Transactions ranges from the mechanisms through the development of principles to the application of those principles to specific environments. Specific topic areas include: a) development and maintenance methods and models, e.g., techniques and principles for the specification, design, and implementation of software systems, including notations and process models; b) assessment methods, e.g., software tests and validation, reliability models, test and diagnosis procedures, software redundancy and design for error control, and the measurements and evaluation of various aspects of the process and product; c) software project management, e.g., productivity factors, cost models, schedule and organizational issues, standards; d) tools and environments, e.g., specific tools, integrated tool environments including the associated architectures, databases, and parallel and distributed processing issues; e) system issues, e.g., hardware-software trade-off; and f) state-of-the-art surveys that provide a synthesis and comprehensive review of the historical development of one particular area of interest.

Full Aims & Scope

Meet Our Editors

Editor-in-Chief
Matthew B. Dwyer
Dept. Computer Science and Engineering
256 Avery Hall
University of Nebraska-Lincoln
Lincoln, NE 68588-0115 USA
tse-eic@computer.org