By Topic

Software Engineering Conference, 2009. APSEC '09. Asia-Pacific

Date 1-3 Dec. 2009

Filter Results

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

    Page(s): C1
    Save to Project icon | Request Permissions | PDF file iconPDF (478 KB)  
    Freely Available from IEEE
  • [Title page i]

    Page(s): i
    Save to Project icon | Request Permissions | PDF file iconPDF (94 KB)  
    Freely Available from IEEE
  • [Title page iii]

    Page(s): iii
    Save to Project icon | Request Permissions | PDF file iconPDF (151 KB)  
    Freely Available from IEEE
  • [Copyright notice]

    Page(s): iv
    Save to Project icon | Request Permissions | PDF file iconPDF (110 KB)  
    Freely Available from IEEE
  • Table of contents

    Page(s): v - x
    Save to Project icon | Request Permissions | PDF file iconPDF (281 KB)  
    Freely Available from IEEE
  • Conference Chair's Message

    Page(s): xi
    Save to Project icon | Request Permissions | PDF file iconPDF (77 KB)  
    Freely Available from IEEE
  • Program Chairs' Message

    Page(s): xii
    Save to Project icon | Request Permissions | PDF file iconPDF (81 KB)  
    Freely Available from IEEE
  • Conference organizers

    Page(s): xiii - xiv
    Save to Project icon | Request Permissions | PDF file iconPDF (101 KB)  
    Freely Available from IEEE
  • Steering Committee

    Page(s): xv
    Save to Project icon | Request Permissions | PDF file iconPDF (80 KB)  
    Freely Available from IEEE
  • Program Committee

    Page(s): xvi - xvii
    Save to Project icon | Request Permissions | PDF file iconPDF (87 KB)  
    Freely Available from IEEE
  • list-reviewer

    Page(s): xviii
    Save to Project icon | Request Permissions | PDF file iconPDF (63 KB)  
    Freely Available from IEEE
  • Keynotes

    Page(s): xix - xxi
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (155 KB)  

    An organization based on product lines evolves a common marketing strategy, and strengthens core competency around strategic business interests and goals. The goal is to produce quality products consistently and predictably by moving toward an asset-supported, component-based product lines development approach. This transition must be planned carefully encompassing not only technical issues but also organizational and business aspects. Here, some questions referring to the technological challenges of building product lines is addressed. Some of the most relevant contributions in the SPL research timeline from details of a survey conducted, is discussed. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Improving the Accuracy of Software Effort Estimation Based on Multiple Least Square Regression Models by Estimation Error-Based Data Partitioning

    Page(s): 3 - 10
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (338 KB) |  | HTML iconHTML  

    Accurate software effort estimation is one of the key factors to a successful project by making a better software project plan. To improve the estimation accuracy of software effort, many studies usually aimed at proposing novel effort estimation methods or combining several approaches of the existing effort estimation methods. However, those researches did not consider the distribution of historical software project data which is an important part impacting to the effort estimation accuracy. In this paper, to improve effort estimation accuracy by least squares regression, we propose a data partitioning method by the accuracy measures, MRE and MER which are usually used to measure the effort estimation accuracy. Furthermore, the empirical experimentations are performed by using two industry data sets (the ISBSG Release 9 and the Bank data set which consists of the project data performed in a bank in Korea). View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Hierarchical Understandability Assessment Model for Large-Scale OO System

    Page(s): 11 - 18
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (299 KB) |  | HTML iconHTML  

    Understanding software, especially in large-scale, is an important issue for software modification. In large-scale software systems, modularization provides help for understanding them. But, even if a system has a well-modularized design, the modular design can be deteriorated by system change over time. Therefore it is needed to assess and manage modularization in the view of understandability. However, there are rarely studies of a quality assessment model for understandability in the module-level. In this paper, we propose a hierarchical model to assess understandability of modularization in large-scale object-oriented software. To assess understandability, we define several design properties, which capture the characteristics influencing on understandability, and design metrics based on the properties, which are used to quantitatively assess understandability. We validate our model and its usefulness by applying the model to an open-source software system. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • On the Relationship between Different Size Measures in the Software Life Cycle

    Page(s): 19 - 26
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (336 KB) |  | HTML iconHTML  

    Various measures and methods have been developed to measure the sizes of different software entities produced throughout the software life cycle. Understanding the nature of the relationship between the sizes of these products has become significant due to various reasons. One major reason is the ability to predict the size of the later phase products by using the sizes of early life cycle products. For example, we need to predict the Source Lines of Code (SLOC) from Function Points (FP) since SLOC is being used as the main input for most of the estimation models when this measure is not available yet. SLOC/FP ratios have been used by the industry for such purposes even though the assumed linear relationship has not been validated yet. Similarly, FP has recently started to be used to predict the Bytes of code for estimating the amount of spare memory needed in systems. In this paper, we aim to investigate further the nature of the relationship between the software functional size and the code size by conducting a series of empirical studies. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Investigating the Effect of Refactoring on Software Testing Effort

    Page(s): 29 - 34
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (279 KB) |  | HTML iconHTML  

    Refactoring, the process of improving the design of existing code by changing its internal structure without affecting its external behavior, tends to improve software quality by improving design, improving readability, and reducing bugs. There are many different refactoring methods, each having a particular purpose and effect. Consequently, the effect of refactorings on software quality attribute may vary. Software testing is an external software quality attributes that takes lots of time and effort to make sure that the software performs as intended. In this paper, we propose a classification of refactoring methods based on their measurable effect on software testing effort. This, in turn, helps the software developers decide which refactoring methods to apply in order to optimize a software system with regard to the testing effort. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Extracting High-Level Functional Design from Software Requirements

    Page(s): 35 - 42
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (652 KB) |  | HTML iconHTML  

    Practitioners spend significant amounts of time creating high-level design from requirements. Though there exist methodologies to describe and manage requirements and design artifacts, there is not yet an automated way to faithfully translate a requirement into a high-level design. While it is extremely difficult to generate design elements from free-form natural language due to its inherent ambiguity, it is possible to significantly improve the accuracy of the design from relatively structured and constrained natural language. In this paper we propose a technique to generate high-level class diagrams from a set of requirements, using a set of requirement-specific heuristics. In this approach, we leverage work we had previously done to first process a requirement statement to classify it into a requirement type, and then break it into various constituents. Depending on the requirement type and its constituents, our heuristics then discover a functional design comprising of coarse-grained modules, their relationships and responsibilities. We express the design as a UML class diagram in IBM rational software architect (RSA) format. Our preliminary investigation shows that the resulting class diagram is rich, and can be used by practitioners as a basis for further design. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Identifying Fragments to be Extracted from Long Methods

    Page(s): 43 - 49
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (253 KB) |  | HTML iconHTML  

    Long and complex methods are hard to read or maintain, and thus usually treated as bad smells, known as Long Method. On the contrary, short and well-named methods are much easier to read, maintain, and extend. In order to divide long methods into short ones, refactoring Extract Method was proposed and has been widely used. However, extracting methods manually is time consuming and error prone. Though existing refactoring tools can automatically extract a selected fragment from its inclosing method, which fragment within a long method should be extracted has to be determined manually. In order to facilitate the decision-making, we propose an approach to recommend fragments within long methods for extraction. The approach is implemented as a prototype, called AutoMeD. With the tool, we evaluate the approach on a nontrivial open source project. The evaluation results suggest that refactoring cost of long methods can be reduced by nearly 40%. The main contribution of this paper is an approach to recommending fragments within long methods to be extracted, as well as an initial evaluation of the approach. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A Graph Based Approach to Detecting Causes of Implied Scenarios under the Asynchronous and Synchronous Communication Styles

    Page(s): 53 - 60
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (310 KB) |  | HTML iconHTML  

    The implied scenarios are unexpected behaviors in the scenario specifications. Detecting and handling them is essential for the correctness of the scenario specifications. Prior researches focus on detecting those implied scenarios through error traces, and cannot identify where to be considered to handle the implied scenarios. Moreover, most of them do not consider the asynchronous communication style although the implied scenarios may vary according to communication styles. In this paper, we provide a graph based approach to detecting causes of implied scenarios under the asynchronous and synchronous communication styles. The semantics of the scenario specification is defined as a partially ordered set which is represented as a graph. Based on the graph, our approach constructs another graph which represents behaviors of a minimal implementation satisfying the scenario specification. Differentiating between the two graphs identify which part of the scenario specification causes the implied scenarios under the asynchronous communication style. In addition, our approach can be also applied under the synchronous communication styles by adding additional relationships to the two graph. To validate our approach, we provide two case studies. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Extracting Environmental Constraints to Make Reactive System Specifications Realizable

    Page(s): 61 - 68
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (761 KB) |  | HTML iconHTML  

    Many fatal accidents of safety critical reactive systems have occurred in unexpected situations which had not been considered during the design and test phases of the systems. To prevent these accidents, reactive systems should be designed to respond appropriately to any requests of any timing from environments. Verifying this property at specification phase reduces the development costs of safety critical reactive systems. This property of a specification is well known as realizability. If a specification was found not to be realizable, we have to determine the flaws in the unrealizable specification. Unrealizability of a specification arises from arbitrary requirements given by system designers. From a different view, it can be thought that the unrealizable specification implicitly imposes a precondition on the behavior of environment, although a system can not control the behavior of environment. If it is possible to obtain the precondition in intuitively comprehensive forms, it is easy for system designers to understand the cause of flaws in specifications. In this paper, we propose methods for deriving constraints on the behavior of environments, which is implicitly imposed by unrealizable specifications. Instead of realizability, we use strong satisfiability which is a necessary condition for realizability, due to the fact that many practical unrealizable specifications are also strongly unsatisfiable, and strong satisfiability have the advantage of lower complexity for analysis against realizability. These methods derive constraints in propositional linear temporal logic from Buchi automata representing specifications. The expressions of derived constraints are limited to simple and intuitively comprehensive forms where only two temporal operators appear successively. We also give proofs for three correctness properties of our methods, i.e. the termination property, the soundness property, and the weakest constraints derivability. Finally, we discuss applicab- ility of our methods. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Monitoring Composite Services with Universal Modal Sequence Diagrams

    Page(s): 69 - 76
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (892 KB) |  | HTML iconHTML  

    Monitoring is a promising technique to detect erroneous behavior of a composite service at run-time, which is to complement static verification and validation techniques. One of the most important aspects of monitoring approach is that the specification of the properties without losing expressive power should be as simple as possible, facilitating the developers to represent the properties of the composite service. Consequently, we prefer to use Modal Sequence Diagrams that are the modal extension of UML 2.0 Sequence Diagrams as our property specification. Modal Sequence Diagrams are not only simple enough but also have powerful expressive power. We first define the formal syntax and semantics of Modal Sequence Diagrams, and measure the expressiveness based on Property Specification Patterns. Then, a novel framework is proposed to monitor temporal properties of the composite service with Modal Sequence Diagrams. Finally, a series of experiments based on On-the-Job Assistant case study have been conducted to validate our approach. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Critical Barriers for Offshore Software Development Outsourcing Vendors: A Systematic Literature Review

    Page(s): 79 - 86
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (273 KB) |  | HTML iconHTML  

    Software development outsourcing is a contract-based relationship between client and vendor organisations in which a client(s) contracts out all or part of its software development activities to a vendor(s), who provides agreed services for remuneration. The objective of this paper is to identify various barriers that have a negative impact on software outsourcing clients in the selection process of offshore software development outsourcing vendors. We have performed a Systematic Literature Review process for the identification of barriers. We have identified barriers `language and cultural barriers', `country instability', `lack of project management', `lack of protection for intellectual property rights' and `lack of technical capability' that are generally have a negative impact on outsourcing clients. The results also reveal the similarities and differences in the barriers identified in different continents. We suggest vendors have to address different barriers in order to compete in the offshore outsourcing business. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Re-defining the Requirements Engineering Process Improvement Model

    Page(s): 87 - 92
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (268 KB) |  | HTML iconHTML  

    A specialized Requirements Capability Maturity Model (R-CMM) was created by a group of researchers from UK as an attempt to support the requirements engineering phase of software development. The validation performed to this model shows that it has some potentials to be a useful tool for both practitioners and researchers in the field of process improvement and requirements engineering. However, the R-CMM focuses on the requirements engineering process defined within the retired Software Engineering Institute's (SEI's) Software Capability Maturity Model (SW_CMM) process improvement framework. To continue its relevance and usefulness, we re-define the whole R-CMM within the characteristics of the latest Capability Maturity Model for Integration (CMMI) for Development (CMMI-DEV) v1.2. This paper describes how the CMMI-DEV characteristics are used to re-define the R-CMM, and rationale for re-building the requirements engineering model based on the latest process improvement framework. Also, this paper explains how the re-defined R-CMM adapts to the goals and practices set by the CMMI-DEV. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Insights into Domain Knowledge Sharing in Software Development Practice in SMEs

    Page(s): 93 - 100
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (299 KB) |  | HTML iconHTML  

    The collaborative development of shared understanding is crucial to the success of software development projects. It is also a challenging and volatile process in practice. Small organizations may be especially vulnerable due to reliance on key individuals and insufficient resource to employ several domain specialists. There is, however, minimal empirical research on sharing domain understanding in the context of small software organizations. In this paper we present the results of a field study of commercial software development practice in which we conducted semi-structured interviews with practitioners from ten such organizations. The study provides insights into practices, perceptions, and challenges related to developing shared domain understanding. Our results show that smaller organizations place particular emphasis on the use of prototypes or existing products to refine and verify domain understanding. Furthermore they perceive the biggest challenge to developing shared understanding as the quality of the client representative(s). View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The Context Dynamics Matrix (CDM): An Approach to Modeling Context

    Page(s): 101 - 108
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1600 KB) |  | HTML iconHTML  

    Context plays an important role in various analysis techniques across disciplines including software engineering. In software engineering, however, context is typically viewed to be merely representing scope and system boundaries. We present a view of context to be a dynamic element of every stage of (software) development, not limited to analysis and design. We introduce a multi-dimensional view of context based on perception and influence, replacing the typical one-dimensional view. To realize the dynamic behaviour of contextual elements we use a 2×2 matrix to represent four contextual states. The contextual states are a result of either contextual/noncontextual influence(s), or explicit/implicit perception(s). We demonstrate the usefulness of our method through a case-study for requirements developed for a system which marks voters electronically using handheld PDA devices. The requirements are analysed and modelled using focal points, context-centres, and context maps. View full abstract»

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