By Topic

IEEE Transactions on Software Engineering

Issue 1 • Date Jan.-Feb. 2010

Filter Results

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

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

    Publication Year: 2010, Page(s): c2
    Request permission for commercial reuse | PDF file iconPDF (135 KB)
    Freely Available from IEEE
  • Editorial: A New Editor in Chief and the State of the Journal

    Publication Year: 2010, Page(s):1 - 2
    Request permission for commercial reuse | PDF file iconPDF (87 KB) | HTML iconHTML
    Freely Available from IEEE
  • Editorial: A New Decade of TSE

    Publication Year: 2010, Page(s):3 - 6
    Cited by:  Papers (1)
    Request permission for commercial reuse | PDF file iconPDF (226 KB) | HTML iconHTML
    Freely Available from IEEE
  • Better Debugging via Output Tracing and Callstack-Sensitive Slicing

    Publication Year: 2010, Page(s):7 - 19
    Cited by:  Papers (12)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2326 KB) | HTML iconHTML

    Debugging often involves 1) finding the point of failure (the first statement that produces bad output) and 2) finding and fixing the actual bug. Print statements and debugger break points can help with step 1. Slicing the program back from values used at the point of failure can help with step 2. However, neither approach is ideal: Debuggers and print statements can be clumsy and time-consuming a... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • DECOR: A Method for the Specification and Detection of Code and Design Smells

    Publication Year: 2010, Page(s):20 - 36
    Cited by:  Papers (127)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (3343 KB) | HTML iconHTML

    Code and design smells are poor solutions to recurring implementation and design problems. They may hinder the evolution of a system by making it hard for software engineers to carry out changes. We propose three contributions to the research field related to code and design smells: (1) DECOR, a method that embodies and defines all the steps necessary for the specification and detection of code an... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Directed Explicit State-Space Search in the Generation of Counterexamples for Stochastic Model Checking

    Publication Year: 2010, Page(s):37 - 60
    Cited by:  Papers (4)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (7638 KB) | HTML iconHTML

    Current stochastic model checkers do not make counterexamples for property violations readily available. In this paper, we apply directed explicit state-space search to discrete and continuous-time Markov chains in order to compute counterexamples for the violation of PCTL or CSL properties. Directed explicit state-space search algorithms explore the state space on-the-fly, which makes our method ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Effects of Personality on Pair Programming

    Publication Year: 2010, Page(s):61 - 80
    Cited by:  Papers (18)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (6639 KB) | HTML iconHTML

    Personality tests in various guises are commonly used in recruitment and career counseling industries. Such tests have also been considered as instruments for predicting the job performance of software professionals both individually and in teams. However, research suggests that other human-related factors such as motivation, general mental ability, expertise, and task complexity also affect the p... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Generating Event Sequence-Based Test Cases Using GUI Runtime State Feedback

    Publication Year: 2010, Page(s):81 - 95
    Cited by:  Papers (18)  |  Patents (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2978 KB) | HTML iconHTML

    This paper presents a fully automatic model-driven technique to generate test cases for graphical user interfaces (GUIs)-based applications. The technique uses feedback from the execution of a ??seed test suite,?? which is generated automatically using an existing structural event interaction graph model of the GUI. During its execution, the runtime effect of each GUI event on all other events pin... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • How Developers' Experience and Ability Influence Web Application Comprehension Tasks Supported by UML Stereotypes: A Series of Four Experiments

    Publication Year: 2010, Page(s):96 - 118
    Cited by:  Papers (33)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (5735 KB) | HTML iconHTML

    In recent years, several design notations have been proposed to model domain-specific applications or reference architectures. In particular, Conallen has proposed the UML Web Application Extension (WAE): a UML extension to model Web applications. The aim of our empirical investigation is to test whether the usage of the Conallen notation supports comprehension and maintenance activities with sign... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Providing Architectural Languages and Tools Interoperability through Model Transformation Technologies

    Publication Year: 2010, Page(s):119 - 140
    Cited by:  Papers (23)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (4271 KB) | HTML iconHTML

    Many architectural languages have been proposed in the last 15 years, each one with the chief aim of becoming the ideal language for specifying software architectures. What is evident nowadays, instead, is that architectural languages are defined by stakeholder concerns. Capturing all such concerns within a single, narrowly focused notation is impossible. At the same time, it is also impractical t... View full abstract»

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

    Publication Year: 2010, Page(s):141 - 143
    Request permission for commercial reuse | PDF file iconPDF (50 KB)
    Freely Available from IEEE
  • 7 Great Reasons for Joining the IEEE Computer Society [advertisement]

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

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

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