Software Change Impact Analysis
Software Change Impact Analysis
Distributed and Parallel Databases
Metrics and Laws of Software Evolution - The Nineties View
METRICS '97 Proceedings of the 4th International Symposium on Software Metrics
PRO-ART: Enabling Requirements Pre-Traceability
ICRE '96 Proceedings of the 2nd International Conference on Requirements Engineering (ICRE '96)
Improving Software Comprehension through an Automated Dependency Tracer
IWPC '99 Proceedings of the 7th International Workshop on Program Comprehension
Software Change Impacts - An Evolving Perspective
ICSM '02 Proceedings of the International Conference on Software Maintenance (ICSM'02)
QuaTrace: A Tool Environment for (Semi-) Automatic Impact Analysis Based on Traces
ICSM '03 Proceedings of the International Conference on Software Maintenance
Change Impact Analysis for Requirement Evolution using Use Case Maps
IWPSE '05 Proceedings of the Eighth International Workshop on Principles of Software Evolution
IBM Systems Journal - Model-driven software development
Quantitative Analysis for Requirements Evolution's Ripple-Effect
CAR '09 Proceedings of the 2009 International Asia Conference on Informatics in Control, Automation and Robotics
Patterns-based evaluation of open source BPM systems: The cases of jBPM, OpenWFE, and Enhydra Shark
Information and Software Technology
Selecting among alternatives using dependencies: an NFR approach
Proceedings of the 28th Annual ACM Symposium on Applied Computing
Investigating dependencies in software requirements for change propagation analysis
Information and Software Technology
Hi-index | 0.00 |
Dependencies among software artifacts are very useful for various software development and maintenance activities such as change impact analysis and effort estimation. In the past, the focus on artifact dependencies has been at the design and code level rather than at the requirements level. This is due to the difficulties in identifying dependencies in a text-based requirements specification. We observed that difficulties reside in the disconnection among itemized requirements and the lack of a more systematic approach to write text-based requirements. Business process models are an increasingly important part of a requirements specification. In this paper, we present a mapping between workflow patterns and dependency types to aid dependency identification and change impact analysis. Our real-world case study results show that some participants, with the help of the mapping, discovered more dependencies than other participants using text-based requirements only. Though many of these additional dependencies are highly difficult to spot from the text-based requirements, they are however very useful for change impact analysis.