The object advantage: business process reengineering with object technology
The object advantage: business process reengineering with object technology
The Impact Analysis Task in Software Maintenance: A Model and a Case Study
ICSM '94 Proceedings of the International Conference on Software Maintenance
Supporting impact analysis: a semi-automated technique and associated tool
ICSM '95 Proceedings of the International Conference on Software Maintenance
Journal of Software Maintenance and Evolution: Research and Practice - Seventh European Conference on Software Maintenance and Reengineering (CSMR 2003)
Proceedings of the 2008 ACM symposium on Applied computing
Supporting requirements in a traceability approach between business process and user interfaces
Proceedings of the VIII Brazilian Symposium on Human Factors in Computing Systems
Model-driven approach for user interface: business alignment
Proceedings of the 1st ACM SIGCHI symposium on Engineering interactive computing systems
Measuring the alignment between business processes and software systems: a case study
Proceedings of the 2010 ACM Symposium on Applied Computing
KALCAS: a framework for semi-automatic alignment of data and business processes architectures
ADBIS'12 Proceedings of the 16th East European conference on Advances in Databases and Information Systems
Hi-index | 0.00 |
Business processes and existing software systems must be aligned so that software systems can adequately support the business processes in order to be effectively used within them. The alignment characteristic needs to be considered even during the execution of an evolution process. In particular, a strict relationship exists between the evolution of a legacy system and that of the supported business process. Therefore, the requirements for evolving a software system embedded in a business process are to be defined on the basis of the change needing to be performed on the process activities. In fact, any modification performed in the business process activities and/or supporting software system may impact the process activities in terms of input/output and/or purpose of the software system and, therefore, cause misalignment. A coarse grained strategy is proposed for detecting misalignment between software systems and supported business processes when a change is executed. In addition, the strategy supports the identification of all the objects, either software system components or process activities, affected by a change and needing to be considered during the evolution process, for keeping the alignment and ensuring the technological support to the business process. The strategy proposes the exploitation of quality parameters, for codifying the alignment concept, and impact analysis techniques, for propagating the change and identifying all the objects affected by a change and requiring new evolution interventions.