You are required to read and agree to the below before accessing a full-text version of an article in the IDE article repository.

The full-text document you are about to access is subject to national and international copyright laws. In most cases (but not necessarily all) the consequence is that personal use is allowed given that the copyright owner is duly acknowledged and respected. All other use (typically) require an explicit permission (often in writing) by the copyright owner.

For the reports in this repository we specifically note that

  • the use of articles under IEEE copyright is governed by the IEEE copyright policy (available at
  • the use of articles under ACM copyright is governed by the ACM copyright policy (available at
  • technical reports and other articles issued by M‰lardalen University is free for personal use. For other use, the explicit consent of the authors is required
  • in other cases, please contact the copyright owner for detailed information

By accepting I agree to acknowledge and respect the rights of the copyright owner of the document I am about to access.

If you are in doubt, feel free to contact

Client-side Web Application Slicing


Publication Type:

Conference/Workshop Paper


ASE 2011 - Automated Software Engineering




Highly interactive web applications that offer user experience and responsiveness of standard desktop applications are becoming prevalent in the web application domain. However, with these benefits come certain drawbacks. For example, the event-based architectural style, and poor support for code organization, often lead to a situation where code responsible for a certain behavior is intermixed with irrelevant code. This makes development, debugging and reuse difficult. One way of locating code implementing a certain behavior is program slicing, a method that, given a subset of a program’s behavior, reduces the program to a minimal form that still produces that behavior. In this paper we present a semi- automatic clientside web application slicing method, describe the web page dependency graph, and show how it can be used to extract only the code implementing a certain behavio


author = {Josip Maras and Jan Carlson and Ivica Crnkovic},
title = {Client-side Web Application Slicing},
pages = {504--507},
month = {November},
year = {2011},
booktitle = {ASE 2011 - Automated Software Engineering},
publisher = {ASE},
url = {}