Research Papers

Authors are invited to submit full papers describing original research in all areas of software engineering. Papers describing theoretical or empirical research, new techniques and tools, and in-depth case studies are all welcome. Submissions should be original and must not have been published previously or currently be under consideration for publication elsewhere.

Research paper submissions will be peer reviewed based on originality, technical quality and relevance to the field of software engineering. One author from each accepted paper is required to register as a full-fee delegate and present the paper at the conference.

• Submissions Deadline Friday, 11 June 2010 - EXTENDED
• Acceptance Notification Friday, 6 August 2010
• Final versions due Friday, 3 September 2010

As in previous years, the APSEC 2010 proceedings (research papers) will be published by the Conference Publishing Service (CPS) http://www.computer.org/portal/web/cscps/home. All submissions must be written in English and must be prepared in the IEEE 8.5x11 inch two-column format (http://www.computer.org/portal/web/cscps/formatting). Manuscripts may not exceed 10 pages in length. Manuscripts are to be submitted electronically through the EasyChair conference management system at http://www.easychair.org/conferences/?conf=apsec2010researchpapers.

Accepted Research Papers

• Hareton Leung. Variants of risk and opportunity
• Ashish Sureka and Pankaj Jalote . Automatic Duplicate Bug Report Detecting Using Character N-Gram-Based Features
• Juliana Bowles and Dulani Meedeniya. Formal Transformation from Sequence Diagrams to Coloured Petri Nets
• Hiroki shudo and Atsushi Ohnishi. A Method for Exception Scenarios Generation
• haruhiko kaiya , yuutarou shimizu , hirotaka yasui , kenji kaijiri and motoshi saeki. Enhancing Domain Knowledge for Requirements Elicitation with Web Mining
• Hailong Wang, Juan Li, Qing Wang and Ye Yang. Quantitative Analysis of Requirements Evolution across Multiple Versions of an Industrial Software Product
• Shinpei Hayashi , Takashi Yoshikawa and Motoshi Saeki. Sentence-to-Code Traceability Recovery with Domain Ontologies
• Liang Zhao , Anna Liu and Jacky Keung . Evaluating Cloud Platform Architecture with the CARE Framework
• Hyeonjeong Kim, W. Eric Wong , Vidroha Debroy and DooHwan Bae . Bridging the Gap Between Fault Trees and UML Statemachine Diagrams for Safety Analysis
• Nayoung Hong, Junbeom Yoo and Sungdeok Cha. Customization of Scrum Methodology for Outsourced E-commerce Projects
• Guisheng Fan, Huiqun Yu and Liqiong Chen. Aspect Oriented Approach to Building Service Secure Composition
• Ewan Tempero , Craig Anslow , Jens Dietrich, Ted Han, Jing Li, Markus Lumpe, Hayden Melton and James Noble . Qualitas Corpus: A Curated Collection of Java Code for Empirical Studies
• Graham Jenson , Jens Dietrich and Hans W. Guesgen. A Formal Framework to Optimise Component Dependency Resolution
• shukor sanim mohd fauzi , paul l bannerman and mark staples. Software Configuration Management in Global Software Development: A Systematic Map
• Lee Naish , Hua Jie Lee and Ramamohanarao Kotagiri. Statements versus predicates in spectral bug localization
• Wasif Afzal . Using Faults-Slip-Through Metric As A Predictor of Fault-Proneness
• Qiuming Tao, Wei Wu, Wuwei Shen and Chen Zhao. An Automatic Testing Approach for Compiler Based on Metamorphic Testing Technique
• Baiqiang Chen, Jun Yan and Jian Zhang . Combinatorial Testing with Shielding Parameters
• Yi Liu, Zhiyi Ma and Weizhong Shao. Integrating Non-Functional Requirement - Modeling into Model Driven Development Method
• Markus Jahn , Reinhard Wolfinger , Markus Löberbauer and Hanspeter Mössenböck . Rule-based Composition Behaviors in Dynamic Plug-in Systems
• Hoa Khanh Dam and Aditya Ghose . Supporting change propagation in the maintenance and evolution of service-oriented architectures
• Junqing Chen, Linpeng Huang, Siqi Du and Wenjia Zhou. A Formal Model for Supporting Frameworks of Dynamic Service Update Based on OSGi
• Yoshiaki Matsuzawa, Yasuhiro Noguchi, Takao Mori, Satoshi Shima and Akichika Shiomi. ESAD: An Intensive Retreat Program for Embedded System Architect Developing
• Bixin Li , Ziyong Su and Ying Zhou. Evaluating the Reliability of Web Services Based on BPEL Structure Analysis and Run-Time Information Capture
• Shinya Yamada, Masataka Ugumori and Shinji Kusumoto. A Software Tag Generation System to Realize Software Traceability
• Jacky Keung and Thong Nguyen. Quantitative Analysis for Non-linear System Performance Data using Case-based Reasoning
• Meixia Zhu and Hanpin Wang. The Analysis of Sequence Diagram with Time Properties in Qualitative and Quantitative Aspects by Model Transformation
• Mikio Aoyama , Takako Nakatani, Shinobu Saito, Mikio Suzuki, Kazuaki Fujita, Hiroaki Nakazaki and Ritsuo Suzuki. A Model and Architecture of REBOK(Requirements Engineering Body Of Knowledge) and Its Evaluation
• Jin Shao, Fang Deng, Haiwen Liu, Qianxiang Wang and Hong Mei . Lazy Runtime Verification for Constraints on Interacting Objects
• Guoping Rong, He Zhang and Dong Shao. SCRUM-PSP: Embracing Process Agility and Discipline
• Bandar Alshammari, Colin Fidge and Diane Corney . Assessing The Impact of Refactoring on Security-Critical Object-Oriented Designs
• Bo Wei, Zhi Jin and Lin Liu. A Formalism for Extending the NFR Framework to Support the Composition of the Goal Trees
• Guoheng Zhang, Huilin Ye and Yuqing Lin. Quality Attributes Assessment for Feature-Based Product Configuration in Software Product Line
• Wuwei Shen and Dae-Kyoo Kim . Supporting Flexibile Reification of Design Patterns
• Seung-Yeol Seo, Hyung-Min Koo and In-Young Ko . An Interaction-Pattern-Based Approach to Prevent Performance Degradation of Fault Detection in Service Robot Software
• Julio Sincero, Wolfgang Schröder-Preikschat and Olaf Spinczyk . Approaching Non-Functional Properties of Software Product Lines: Learning from Products
• Chuanqi Tao, Bixin Li and Xiaobing Sun. A Hierarchical Model for Regression Test Selection and Cost Analysis of Java Programs
• Jing Du, Ye Yang, Zhongpeng Lin, Qing Wang, Mingshu Li and Feng Yuan. A Case Study on Usage of a Software Process Management Tool in China
• Hadaytullah , Kai Koskimies and Outi Räihä. Genetic Approach to Software Architecture Synthesis with Work Allocation Scheme
• Jun Sun , yang liu , jin song dong , Geguang Pu and Tian Huat Tan. Model-based Methods for Linking Web Service Choreography and Orchestration
• Wassim EL HAJJ CHEHADE, Ansgar RADERMACHER, Sébastien GERARD and François TERRIER. Detailed Real-time Software Platform Modeling
• Andre L. Ferreira, Ricardo Machado and Mark Paulk . Quantitative Analysis of Best Practices Models in the Software Domain
• Ahyoung Sung, Witawas Srisa-an, Gregg Rothermel and Tingting Yu. Testing Inter-Layer and Inter-Task Interactions in RTES Applications
• Marinos Kintis, Mike Papadakis and Nicos Malevris. Evaluating Mutation Testing Alternatives: A Collateral Experiment
• Daniel Aceituna , Hyunsook Do and Seok-Won Lee . SQ2E: An Approach to Requirements Validation with Scenario Question
• Zahra Shakeri Hossein Abad, Mahsa Hasani Sadi and Raman Ramsin . Towards Tool Support for Situational Engineering of Agile Methodologies
• Hongyu Pei Breivold, Muhammad Aufeef Chauhan and Muhammad Ali Babar. A Systematic Review of Studies of Open Source Software Evolution

Industry Papers

The objective of industry papers is to discuss experiences (both good and bad), obstacles, and lessons learned when applying innovative software development practices in the 'real world'. Experiences from practitioners provide valuable input into future research directions and allow others to learn from successes and failures. Industry papers are an important way of sharing experiences between practitioners and of helping the software industry improve its work practices.

We invite submissions of either extended abstracts or full papers describing practical experiences in all areas of software engineering. Industry papers should be based on actual practice, and should cover all aspects of the experience - strengths and weaknesses, successes and challenges. Submissions will be assessed on originality, clarity, significance and relevance.

One author from each accepted industry paper is required to register as a full-fee delegate and present the paper at the conference. All papers are to be submitted electronically

Guidelines for Authors of Industry Papers

How to submit?

1. Read all of the guidelines prior to writing and submitting your paper
2. Ensure your paper meets all the requirements for industry paper submissions specified
3. Submit the paper through the web-based industry paper submission system

Papers must be submitted electronically through EasyChair

An industry paper template is available for download to assist with paper preparation and formatting. Any similar format (e.g. IEEE) is acceptable.

The deadline for submission is midnight 20 August 2010 AEST. This deadline is hard and non-negotiable.

What is required?

A good extended abstract (1-2 pages) or full paper (maximum 10 pages) provides a high-level summary of what will be presented in the presentation; it contains an overview of the experiences encountered on a software project or ongoing operations and any lessons learned.

Submission Criteria

Industry Papers must conform, at the time of submission, to the submission criteria described below.

• All submissions must be in English
• Submissions must be in PDF or zipped PDF format
• An abstract is approximately 250 words
• An abstract has a clear indication of what the presentation will cover (versus just method, philosophy, or a statement of the problem)
• Extended abstract is 1 – 2 pages when combined with title and small abstract
• Full paper is between 8 – 10 pages maximum

Note that the paper submission system requires additional information such as author details and keywords.

Author Agreement

By submitting papers to the conference, authors agree to the following:

• The presentation will not be a marketing pitch
• The presenter is aware of and commits to meet all Conference deadlines
• The presenter understands that if the presenter does not meet all Conference deadlines, the Industry PC Chairpersons may remove the presentation from the Conference program
• The material to be presented and published will meet all legal, copyright, and security requirement.
• The material may be posted to the APSEC Conference website after the Conference, and will be accessible to "everybody"
• The presenter intends to register for, pay for, and attend the Conference, and to make the presentation

It is the responsibility of the submitter to ensure that submissions comply with the submission criteria and author agreement above.

Submissions that do not comply with the guidelines specified above will be rejected without review. However, if time permits, the author may be allowed to re-submit a modified paper.

How will industry papers be reviewed and evaluated?

Each submission will be reviewed by at least two (2) members of the Industry Program Committee. The Conference Program Committee as a whole will make final decisions about which submissions to accept for presentation at the conference. Submissions will be evaluated based on a number of criteria, including and not limited to the following criteria:

• Clarity and completeness
• Organisation of paper
• Relationship to the discipline of software engineering, and
• Interest to other attendees at the conference

What is required if the industry paper is accepted?

If the paper is accepted, submission of a camera-ready final document will be required by the date specified for final camera-ready industry reports.

More details about the format for this final document will be provided if your paper is accepted.

As mentioned above, at least one author of the paper is required to register, attend, and present the paper at the APSEC 2010 Conference.

• Submissions Deadline Friday, 27 August 2010
• Acceptance Notification Friday, 10 September 2010
• Final Versions Deadline Friday, 5 November 2010

Workshops

The 17^th Asia-Pacific Software Engineering Conference (APSEC2010) Organising Committee invites proposals for workshops to be held in conjunction with the main Conference in Sydney, Australia, from 30 November - 3 December, 2010. The workshops are expected to provide a platform for bringing together researchers, practitioners, and academia to present and discuss ideas, challenges, and potential solutions on an established or emerging theme/area of software engineering.

Workshop proposals that have appeal to the software engineering community are sought for APSEC 2010. Workshops (half or full day) will run on the first day of the Conference. Please submit your proposals detailing the topic, background, intended audience, anticipated number of attendees and justification for this estimate, presenters and their affiliations, along with anticipated time requirements following the guidelines.

Workshop organisers should submit their proposals (in a single pdf file) directly to the APSEC workshop chair via email (malibaba@itu.dk):

Workshop proposals should include the following information (with a maximum length of 2 pages):

1. The title and a description of the workshop, including a clear description of the topic and a motivation why the topic is of interest to software engineering community.
2. A draft schedule of the workshop. The schedule should highlight the interactive nature of the proposed workshop.
3. An indication of the expected number of papers/attendees to be attracted for the workshop.
4. The complete contact information of the workshop organizers, including a brief biography and an overview of previous experiences with organizing workshops.

The workshop will be selected based on the scientific/technical interest in the topics, the clarity of the proposal in addressing the requested information, the innovativeness of workshop topics, and the capacity in the Conference workshop program.

The workshop organisers are responsible to:

• Provide information for inclusion on the Conference website
• Advertise the workshop and solicit submissions
• Handle the paper submission and reviewing process and publication of the proceedings of the workshops
• Coordinate the workshop sessions and stimulate discussion
• Proposals Submission Deadline Friday, 4 June 2010
• Acceptance notification Tuesday, 5 July 2009
• Confirmation of programme Friday, 1 October 2010
• Final versions due Friday, 5 November 2010

Tutorials

Guidelines for Authors of Tutorial Proposals

Tutorial proposals that have practical appeal to the software engineering community are sought for APSEC 2010. Tutorials are designed to help software professionals rapidly come up to speed on a specific technology or methodology.

APSEC 2010 tutorials can be lecture-oriented or participatory. They are either half-day sessions consisting of two 90-minute blocks separated by a 30-minute break, or full-day sessions consisting of four 90-minute blocks, with 30-minute breaks in the morning and afternoon, and a one-hour lunch break. Tutorial rooms are equipped with a data projector; attendees are provided with handouts, to be submitted by presenters one month in advance. Computers will not be provided for attendees.

• Proposals Submission Deadline Friday, 4 June 2010
• Acceptance Notification Friday, 5 July 2010
• Confirmation of Program Friday, 1 October 2010
• Final Versions of Tutorial Materials Submission Deadline Friday, 5 November 2010
• Tutorial Day Tuesday, 30 November 2010

Tutorial proposals will be assessed by a panel of academic and industry representatives according to the following criteria:

• Relevance, interest, and value of the topic to APSEC attendees;
• Completeness, clarity, and quality of the tutorial proposal;
• Expertise and experience of the presenters in the proposed topic and in delivering a successful educational presentation; and
• Effectiveness of the proposed presentation approach.

The APSEC Organising Committee reserves the right to cancel tutorials that have not received sufficient registrations by the close of early registration for the conference.

Proposals should be emailed to the tutorial chair Anthony Sloane (Anthony.Sloane@mq.edu.au) with the subject line "APSEC 2010 Tutorial Proposal", in plain text or PDF format. Submissions must include the following information:

1. Title
2. Speaker(s)
3. Contact Person (including full physical and electronic contact details)
4. Topic Area
5. Level: Introductory / Intermediate / Advanced
6. Duration: Half Day / Full Day
7. Tutorial Description. This will be used to advertise the tutorial and should provide a clear indication of the topic to be covered and the expected outcomes for the participants. (Maximum 300 words)
8. Presenters' Biographies (Maximum 200 words each)
9. Content Outline. This should be a detailed description of the tutorial and its content. Included in this description should be an outline indicating time allocated to topics. Tutorial sessions will be scheduled for three and a half hours, including a half hour tea break. Your running time should be for three hours (or six for a full day tutorial). This is where you are selling your tutorial to the conference organisers. Show how this tutorial will benefit attendees and relate to the conference topics and theme.
10. Presenter Resume. In this section provide evidence of your experience in conducting professional tutorials. Include references to past conference tutorials or professional development courses you have conducted. Also indicate if this tutorial has been presented in the past and if it has been modified since the last presentation.
11. Technical Experience. Provide supporting evidence that you are qualified as an expert in the topic area of this tutorial.
12. Supporting Material. Attach any other material that you believe may support your proposal.

Doctoral Symposium

Overview
The APSEC 2010 Doctoral Symposium is an international forum for PhD students working in all areas of Software Engineering.

The forum is intended to bring together PhD students and give them the opportunity to present and discuss their research in a constructively critical atmosphere, and to meet fellow researchers at a similar stage of their career.

More precisely, the goals of the APSEC 2010 Doctoral Symposium are:

• to give PhD students a chance to showcase their research, to provide them with feedback from a panel of senior international researchers,
• to facilitate interaction among the participants, to offer PhD students the opportunity to attend the APSEC 2010 conference.

The doctoral symposium will operate in a workshop-like format.

Who should participate
The Doctoral Symposium welcomes PhD students who are somewhere in the middle of their doctoral research, that is:

• students who have settled on a dissertation topic, and whose PhD dissertation will benefit from the feedback received.

Submission instructions:
To apply as a student participant to the Doctoral Symposium, you should prepare a submission package consisting of two parts (described below), both of which must be submitted via Easychair.

Part 1 - Abstract
Your research abstract must be formatted according to the format guidelines. All submissions must be in English. Submissions must be in PDF format. Ensure your paper meets all the requirements for industry paper submissions specified Submit the paper through the web-based doctoral symposium paper submission system

Papers must be submitted electronically through EasyChair http://www.easychair.org/conferences/?conf=apsec10ds We will not accept submission via email.

The abstract should cover:

• Research question - clearly formulate the technical problem to be solved.
• Motivation - justify the importance of the problem.
• State of the art - describe what existing work your research builds upon (citing key publications), and also briefly describe any existing solutions that have been developed or are currently being developed (citing key publications) and why they do not solve the problem.
• Proposed solution - sketch the proposed technical solution.
• Contributions - point out your (existing and planned) contributions to the solution of the problem, and state in what aspects the suggested solution is different, new or better as compared to existing approaches to the problem.
• Research methods - indicate the methods you are using or will use to carry out your research.
• Progress - describe the progress made in solving the stated problem and propose a plan to complete the research. The plan should include your strategy for evaluating your work and presenting credible evidence of your results to the research community.

The sections of the paper need not necessarily follow the above structure, but should feature the required content and allow to identify it easily. We understand that students at a relatively early stage of their research might have some difficulty addressing all of the content requirements, but should attempt to do so as best they can.

The research abstract should include the title of your work, your name, affiliation, email address, postal address, personal website, and a one paragraph short summary in the style of an abstract for a regular paper. Submissions should contain no proprietary or confidential material and should cite no proprietary or confidential publications.

Part 2 - Letter of Recommendation
Ask your (main) dissertation advisor for a letter of recommendation. This letter should include:

• your name,
• a candid assessment of the current status of your dissertation research,
• an expected date for dissertation submission.
• The letter should be in PDF format and should be sent directly by your advisor via e-mail to Didar Zowghi at didar@it.uts.edu.au and Alan Fekete at alan.fekete@sydney.edu.au. The e-mail should have the subject APSEC 2010 DOCTORAL SYMPOSIUM RECOMMENDATION.

Evaluation criteria
Upon receipt of the submissions, the Doctoral Symposium Committee will select participants using the following three criteria:

• The potential quality of the research and its relevance to Software Engineering.
• Quality of the research abstract (see Section above).
• The stage of the research.

Important dates

• Submission deadline (paper + recommendation letter) Friday, 3 September 2010
• Notification of acceptance Friday, 1 October 2010
• Final Version: Friday, 5 November 2010

Doctoral Symposium Committee

• Vincenzo Gervasi Pisa University
• Kevin Ryan, LERO, Ireland
• Aybuke Aurum, UNSW

Doctoral Symposium Co-Chairs

• Didar Zowghi, University of Technology Sydney
• Alan Fekete, University of Sydney

Dr David Skellern

David Skellern is a successful ICT entrepreneur with a background in scientific research, industrial R&D, and engineering education.

Dr Skellern spent 10 years designing, building and commissioning instrumentation and extensions for the Fleurs Synthesis Radiotelescope before joining the Sydney University's Electrical Engineering Department. In 1989 he moved to Macquarie University and in 1997 co-founded Radiata which demonstrated the world's first IEEE 802.11a chip-set in September 2000. Radiata was subsequently acquired by Cisco Systems and Dr Skellern moved to California as Technology Director of Cisco's Wireless Networking Business Unit.

Dr Skellern has been CEO of National ICT Australia (NICTA) since mid-2005.

Judith Bishop

Judith Bishop is Director of Computer Science in External Research at Microsoft Research, based in Redmond, USA. Her role is to create strong links between Microsoft's research groups and universities globally, through encouraging projects, supporting conferences and engaging directly in
research. Her goal and passion is to clearly demonstrate the effectiveness and applicability of Microsoft technologies to computer science research and teaching today.

Judith has a distinguished background in academia, having been a professor most recently at the University of Pretoria, South Africa. She has had visiting positions in the UK, Germany, Canada, Italy and the USA. Her expertise is in programming languages and distributed systems, with a strong
practical bias and an interest in compilers and design patterns. After doing her undergraduate degrees at Rhodes and Natal in South Africa, she received her PhD from the University of Southampton in 1977 on the relationship of languages to computer architecture. She has over 90 publications including 15 books on programming languages that are available in six languages and
read worldwide. She has presented many keynotes, tutorials and special lectures. She is currently an Honorary Professor at the University of Cape Town.

Judith serves frequently on international editorial, programme and award committees, and has received numerous awards and distinctions, in particular the IFIP Outstanding Service Award in 2009 and the IFIP Silver Core Award 2006 for service to the worldwide computer science community, the Computer Society Fellowship Award in 2008, the South African DTI Award for Distinguished Woman Scientist of the Year for Innovation 2005 and one of 100 Leading Mind Awards from her University in its Centenary Year 2008. She is a Fellow of the British Computer Society, the Royal Society of South Africa and of many other prestigious bodies.

Mr Martin Nally

Martin Nally is an IBM Fellow and currently the Chief Technology Officer for the Rational Software division of IBM. Martin joined IBM in 1990 with 10 years' prior industry experience. He has held several architecture and development positions in IBM including lead architect and developer for IBM VisualAge/Smalltalk and VisualAge/Java. Martin was one of a team of three that launched the IBM project that later became the Eclipse framework and he led the architecture, design and development of WebSphere Studio, IBM's flagship Eclipse-based developer tool-suite that later evolved into Rational Application Developer.

Cloud Workshop

Call for Papers
Date: 30 November 2010

Cloud computing is an emerging computing paradigm for business computing that aims to streamline the on-demand provisioning of software, hardware, and data as services to allow flexibility in IT resource management, agility as well as economies of scale. Deploying applications on a Cloud can help to achieve scalability and maintain a flexible infrastructure.

Major cloud computing providers such as Amazon, Google and Microsoft are providing different cloud platforms, offering different pricing models and solutions. A variety of challenges arise when deploying and operating applications and services on a Cloud in dynamic and evolving environments.

The goal of the workshop is to bring together industry practitioners and researchers for discussion and presentation on the emerging aspects pertaining to cloud computing, including immediate challenges and solutions, as well as potential techniques that can be utilized for cloud computing. The workshop provides a forum to present new ideas and to explore future directions related to the intersection of cloud computing and software engineering.

Download the pdf version

Submissions:
Email: cloud@apsec2010.com
We seek quality research and industry experience reports not exceeding 6 pages in IEEE
Computer Society Conference format (two-column style). Only PDF files will be accepted.

Topics of Interest - Relating to Cloud Computing

• Software Engineering for Cloud Computing
• Enterprise use of Cloud Computing
• Cloud Software Architecture
• Data Management in Cloud
• Cost / Benefit Analysis
• Risk Mitigation
• Reliability, Quality Assurance, SLA
• Capacity and Resource Planning
• Deployment and Configuration
• Security and Privacy
• Performance Analysis, Metrics
• Research challenges in Cloud Computing
• Service composition and integration
• Best Practice, Industry Experience Report
• Monitoring and management
• Alignment of Application and Infrastructure/Platform architectures

Important Dates:

• Workshop: 30 November 2010
• Submission: 15 October 2010
• Notification : 30 October 2010

Program

Accepted Research Papers

• Hareton Leung. Variants of risk and opportunity
• Ashish Sureka and Pankaj Jalote . Automatic Duplicate Bug Report Detecting Using Character N-Gram-Based Features
• Juliana Bowles and Dulani Meedeniya. Formal Transformation from Sequence Diagrams to Coloured Petri Nets
• Hiroki shudo and Atsushi Ohnishi. A Method for Exception Scenarios Generation
• haruhiko kaiya , yuutarou shimizu , hirotaka yasui , kenji kaijiri and motoshi saeki. Enhancing Domain Knowledge for Requirements Elicitation with Web Mining
• Hailong Wang, Juan Li, Qing Wang and Ye Yang. Quantitative Analysis of Requirements Evolution across Multiple Versions of an Industrial Software Product
• Shinpei Hayashi , Takashi Yoshikawa and Motoshi Saeki. Sentence-to-Code Traceability Recovery with Domain Ontologies
• Liang Zhao , Anna Liu and Jacky Keung . Evaluating Cloud Platform Architecture with the CARE Framework
• Hyeonjeong Kim, W. Eric Wong , Vidroha Debroy and DooHwan Bae . Bridging the Gap Between Fault Trees and UML Statemachine Diagrams for Safety Analysis
• Nayoung Hong, Junbeom Yoo and Sungdeok Cha. Customization of Scrum Methodology for Outsourced E-commerce Projects
• Guisheng Fan, Huiqun Yu and Liqiong Chen. Aspect Oriented Approach to Building Service Secure Composition
• Ewan Tempero , Craig Anslow , Jens Dietrich, Ted Han, Jing Li, Markus Lumpe, Hayden Melton and James Noble . Qualitas Corpus: A Curated Collection of Java Code for Empirical Studies
• Graham Jenson , Jens Dietrich and Hans W. Guesgen. A Formal Framework to Optimise Component Dependency Resolution
• shukor sanim mohd fauzi , paul l bannerman and mark staples. Software Configuration Management in Global Software Development: A Systematic Map
• Lee Naish , Hua Jie Lee and Ramamohanarao Kotagiri. Statements versus predicates in spectral bug localization
• Wasif Afzal . Using Faults-Slip-Through Metric As A Predictor of Fault-Proneness
• Qiuming Tao, Wei Wu, Wuwei Shen and Chen Zhao. An Automatic Testing Approach for Compiler Based on Metamorphic Testing Technique
• Baiqiang Chen, Jun Yan and Jian Zhang . Combinatorial Testing with Shielding Parameters
• Yi Liu, Zhiyi Ma and Weizhong Shao. Integrating Non-Functional Requirement Modeling into Model Driven Development Method
• Markus Jahn , Reinhard Wolfinger , Markus Löberbauer and Hanspeter Mössenböck . Rule-based Composition Behaviors in Dynamic Plug-in Systems
• Hoa Khanh Dam and Aditya Ghose . Supporting change propagation in the maintenance and evolution of service-oriented architectures
• Junqing Chen, Linpeng Huang, Siqi Du and Wenjia Zhou. A Formal Model for Supporting Frameworks of Dynamic Service Update Based on OSGi
• Yoshiaki Matsuzawa, Yasuhiro Noguchi, Takao Mori, Satoshi Shima and Akichika Shiomi. ESAD: An Intensive Retreat Program for Embedded System Architect Developing
• Bixin Li , Ziyong Su and Ying Zhou. Evaluating the Reliability of Web Services Based on BPEL Structure Analysis and Run-Time Information Capture
• Shinya Yamada, Masataka Ugumori and Shinji Kusumoto. A Software Tag Generation System to Realize Software Traceability
• Jacky Keung and Thong Nguyen. Quantitative Analysis for Non-linear System Performance Data using Case-based Reasoning