By Topic

Software Engineering, IEEE Transactions on

Issue 1 • Date Jan. 2004

Filter Results

Displaying Results 1 - 11 of 11
  • Assessing staffing needs for a software maintenance project through queuing simulation

    Publication Year: 2004 , Page(s): 43 - 58
    Cited by:  Papers (23)
    Save to Project icon | Request Permissions | Click to expandAbstract | PDF file iconPDF (1182 KB) |  | HTML iconHTML  

    We present an approach based on queuing theory and stochastic simulation to help planning, managing, and controlling the project staffing and the resulting service level in distributed multiphase maintenance processes. Data from a Y2K massive maintenance intervention on a large COBOL/JCL financial software system were used to simulate and study different service center configurations for a geograp... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Confirming configurations in EFSM testing

    Publication Year: 2004 , Page(s): 29 - 42
    Cited by:  Papers (50)
    Save to Project icon | Request Permissions | Click to expandAbstract | PDF file iconPDF (610 KB) |  | HTML iconHTML  

    We investigate the problem of configuration verification for the extended FSM (EFSM) model. This is an extension of the FSM state identification problem. Specifically, given a configuration ("state vector") and an arbitrary set of configurations, determine an input sequence such that the EFSM in the given configuration produces an output sequence different from that of the configurations in the gi... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Using machine learning for estimating the defect content after an inspection

    Publication Year: 2004 , Page(s): 17 - 28
    Cited by:  Papers (7)
    Save to Project icon | Request Permissions | Click to expandAbstract | PDF file iconPDF (814 KB) |  | HTML iconHTML  

    We view the problem of estimating the defect content of a document after an inspection as a machine learning problem: The goal is to learn from empirical data the relationship between certain observable features of an inspection (such as the total number of different defects detected) and the number of defects actually contained in the document. We show that some features can carry significant non... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Technology for testing nondeterministic client/server database applications

    Publication Year: 2004 , Page(s): 59 - 77
    Cited by:  Papers (5)
    Save to Project icon | Request Permissions | Click to expandAbstract | PDF file iconPDF (2075 KB) |  | HTML iconHTML  

    The execution of a client/server application involving database access requires a sequence of database transaction events (or, T-events), called a transaction sequence (or, T-sequence). A client/server database application may have nondeterministic behavior in that multiple executions thereof with the same input may produce different T-sequences. We present a framework for testing all possible T-s... View full abstract»

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

    Publication Year: 2004 , Page(s): 3 - 16
    Cited by:  Papers (65)
    Save to Project icon | Request Permissions | Click to expandAbstract | PDF file iconPDF (1565 KB) |  | HTML iconHTML  

    A testability transformation is a source-to-source transformation that aims to improve the ability of a given test generation method to generate test data for the original program. We introduce testability transformation, demonstrating that it differs from traditional transformation, both theoretically and practically, while still allowing many traditional transformation rules to be applied. We il... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • IEEE Transaction on Software Engineering - Table of Contents

    Publication Year: 2004 , Page(s): 0_1
    Save to Project icon | Request Permissions | PDF file iconPDF (283 KB)  
    Freely Available from IEEE
  • IEEE Transactions on Software Engineering - Staff List

    Publication Year: 2004 , Page(s): 0_2
    Save to Project icon | Request Permissions | PDF file iconPDF (240 KB)  
    Freely Available from IEEE
  • Editorial: AE introduction

    Publication Year: 2004 , Page(s): 1 - 2
    Save to Project icon | Request Permissions | PDF file iconPDF (248 KB)  
    Freely Available from IEEE
  • 2003 Reviewers list

    Publication Year: 2004 , Page(s): 78 - 80
    Save to Project icon | Request Permissions | PDF file iconPDF (177 KB)  
    Freely Available from IEEE
  • TSE: Information for authors

    Publication Year: 2004 , Page(s): 81
    Save to Project icon | Request Permissions | PDF file iconPDF (240 KB)  
    Freely Available from IEEE
  • IEEE Computer Society Information

    Publication Year: 2004 , Page(s): 82
    Save to Project icon | Request Permissions | PDF file iconPDF (283 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
tseeicdwyer@computer.org