The program dependence graph and its use in optimization
ACM Transactions on Programming Languages and Systems (TOPLAS)
Software processes are software too
ICSE '87 Proceedings of the 9th international conference on Software Engineering
Interprocedural slicing using dependence graphs
ACM Transactions on Programming Languages and Systems (TOPLAS)
Software maintenance: an approach to impact analysis of objects change
Software—Practice & Experience
OPSIS: a view mechanism for software processes which supports their evolution and reuse
Proceedings of the 18th international conference on Software engineering
Computational reflection in software process modeling: the SLANG approach
ICSE '93 Proceedings of the 15th international conference on Software Engineering
Tolerating Deviations in Process Support Systems via Flexible Enactment of Process Models
IEEE Transactions on Software Engineering
Process program change control in a process environment
Software—Practice & Experience
Change impact analysis for object-oriented programs
PASTE '01 Proceedings of the 2001 ACM SIGPLAN-SIGSOFT workshop on Program analysis for software tools and engineering
Theory of Modeling and Simulation
Theory of Modeling and Simulation
Techniques for Process Model Evolution in EPOS
IEEE Transactions on Software Engineering
Recovering Traceability Links between Code and Documentation
IEEE Transactions on Software Engineering
Algorithmic Analysis of the Impact of Changes to Object-Oriented Software
ICSM '96 Proceedings of the 1996 International Conference on Software Maintenance
A Change Impact Analysis Approach for CORBA-Based Federated Databases
DEXA '00 Proceedings of the 11th International Conference on Database and Expert Systems Applications
Recovering documentation-to-source-code traceability links using latent semantic indexing
Proceedings of the 25th International Conference on Software Engineering
Whole program Path-Based dynamic impact analysis
Proceedings of the 25th International Conference on Software Engineering
The program dependence graph in a software development environment
SDE 1 Proceedings of the first ACM SIGSOFT/SIGPLAN software engineering symposium on Practical software development environments
QuaTrace: A Tool Environment for (Semi-) Automatic Impact Analysis Based on Traces
ICSM '03 Proceedings of the International Conference on Software Maintenance
A brief survey of program slicing
ACM SIGSOFT Software Engineering Notes
Verification and change-impact analysis of access-control policies
Proceedings of the 27th international conference on Software engineering
ACM Transactions on Software Engineering and Methodology (TOSEM)
Managing process change in software organizations: Experience and reflection: Research Sections
Software Process: Improvement and Practice - Special Issue on Software Process Simulation
Deriving Software Process Simulation Model from SPEM-based Software Process Model
APSEC '07 Proceedings of the 14th Asia-Pacific Software Engineering Conference
A survey of software project managers on software process change
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement
A Case Retrieval Method for Knowledge-Based Software Process Tailoring Using Structural Similarity
APSEC '08 Proceedings of the 2008 15th Asia-Pacific Software Engineering Conference
Lightweight query-based analysis of workflow process dependencies
Journal of Systems and Software
How to avoid drastic software process change (using stochastic stability)
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Change Impact Analysis of a Software Process Using Process Slicing
QSIC '09 Proceedings of the 2009 Ninth International Conference on Quality Software
Process instance management facilities based on the meta process models
ICCSA'11 Proceedings of the 2011 international conference on Computational science and Its applications - Volume Part V
Hi-index | 0.00 |
When a software process is changed, a project manager needs to perform two types of change impact analysis activities: one for identifying the affected elements of a software process which is affected by the change and the other for analyzing the quantitative impact of the change on the project performance. We propose an approach to obtain the affected elements of a software process using process slicing and developing a simulation model based on the affected elements to quantitatively analyzing the change using simulation. We suggest process slicing to obtain the elements affected by the change. Process slicing identifies the affected elements of a software process using a process dependency model. The process dependency model contains activity control dependencies, artifact information dependencies, and role replacement dependencies. We also suggest transformation algorithms to automatically derive the simulation model from the process model containing the affected elements. The quantitative analysis can be performed by simulating the simulation model. In addition, we provide the tool to support our approach. We perform a case study to validate the usefulness of our approach. The result of the case study shows that our approach can reduce the effort to identify the elements affected by changes and examine alternatives for the project.