By Topic

IEEE Transactions on Software Engineering

Issue 9 • Date Sept. 2006

Filter Results

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

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

    Publication Year: 2006, Page(s): c2
    Request permission for commercial reuse | PDF file iconPDF (89 KB)
    Freely Available from IEEE
  • Guest Editors' Introduction to the Special Issue on the International Conference on Software Maintenance and Evolution

    Publication Year: 2006, Page(s):625 - 626
    Request permission for commercial reuse | PDF file iconPDF (63 KB) | HTML iconHTML
    Freely Available from IEEE
  • Feature Identification: An Epidemiological Metaphor

    Publication Year: 2006, Page(s):627 - 641
    Cited by:  Papers (36)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (3037 KB) | HTML iconHTML

    Feature identification is a technique to identify the source code constructs activated when exercising one of the features of a program. We propose new statistical analyses of static and dynamic data to accurately identify features in large multithreaded object-oriented programs. We draw inspiration from epidemiology to improve previous approaches to feature identification and develop an epidemiol... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Toward the Reverse Engineering of UML Sequence Diagrams for Distributed Java Software

    Publication Year: 2006, Page(s):642 - 663
    Cited by:  Papers (76)  |  Patents (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (6517 KB) | HTML iconHTML

    This paper proposes a methodology and instrumentation infrastructure toward the reverse engineering of UML (Unified Modeling Language) sequence diagrams from dynamic analysis. One motivation is, of course, to help people understand the behavior of systems with no (complete) documentation. However, such reverse-engineered dynamic models can also be used for quality assurance purposes. They can, for... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Static Analysis of Object References in RMI-Based Java Software

    Publication Year: 2006, Page(s):664 - 681
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (3828 KB) | HTML iconHTML

    Distributed applications provide numerous advantages related to software performance, reliability, interoperability, and extensibility. This paper focuses on distributed Java programs built with the help of the remote method invocation (RMI) mechanism. We consider points-to analysis for such applications. Points-to analysis determines the objects pointed to by a reference variable or a reference o... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Incremental Maintenance of Software Artifacts

    Publication Year: 2006, Page(s):682 - 697
    Cited by:  Papers (16)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (3812 KB)

    Software is multidimensional, but the tools that support it are not. This lack of tool support causes the software artifacts representing different dimensions to evolve independently and to become inconsistent over time. In order to properly support the evolution of software, one must ensure that the different dimensions evolve concurrently. We have built a software development tool, CLIME that us... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Tool-Supported Refactoring of Existing Object-Oriented Code into Aspects

    Publication Year: 2006, Page(s):698 - 717
    Cited by:  Papers (38)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (5656 KB) | HTML iconHTML

    Aspect-oriented programming (AOP) provides mechanisms for the separation of crosscutting concerns - functionalities scattered through the system and tangled with the base code. Existing systems are a natural testbed for the AOP approach since they often contain several crosscutting concerns which could not be modularized using traditional programming constructs. This paper presents an automated ap... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Identifying Failure Causes in Java Programs: An Application of Change Impact Analysis

    Publication Year: 2006, Page(s):718 - 732
    Cited by:  Papers (25)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2896 KB) | HTML iconHTML

    During program maintenance, a programmer may make changes that enhance program functionality or fix bugs in code. Then, the programmer usually will run unit/regression tests to prevent invalidation of previously tested functionality. If a test fails unexpectedly, the programmer needs to explore the edit to find the failure-inducing changes for that test. Crisp uses results from Chianti, a tool tha... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • On the Use of Mutation Faults in Empirical Assessments of Test Case Prioritization Techniques

    Publication Year: 2006, Page(s):733 - 752
    Cited by:  Papers (73)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (4676 KB) | HTML iconHTML

    Regression testing is an important activity in the software life cycle, but it can also be very expensive. To reduce the cost of regression testing, software testers may prioritize their test cases so that those which are more important, by some measure, are run earlier in the regression testing process. One potential goal of test case prioritization techniques is to increase a test suite's rate o... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The SEXTANT Software Exploration Tool

    Publication Year: 2006, Page(s):753 - 768
    Cited by:  Papers (6)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1749 KB) | HTML iconHTML

    In this paper, we discuss a set of functional requirements for software exploration tools and provide initial evidence that various combinations of these features are needed to effectively assist developers in understanding software. We observe that current tools for software exploration only partly support these features. This has motivated the development of SEXTANT, a software exploration tool ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • TSE Information for authors

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

    Publication Year: 2006, Page(s): c4
    Request permission for commercial reuse | PDF file iconPDF (135 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