Evolution Traceability Roadmap for Business Processes

Yadav, Vrinda; Joshi, Rushikesh K.; Ling, Sea

doi:10.1145/3299771.3299790

Cited by 4 publications

(3 citation statements)

References 33 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…b) Traceability: In practice, change impact analysis relies on traceability defined as "a discernible association among two or more logical entities such as requirements, system elements, verifications, or tasks" [15]. Albeit traceability is considered as one of the most frequently adopted techniques for change impact analysis [10], it has been argued that a traceability model "is not sufficient to capture the progress of evolving artifacts" [16] as elements at the architectural design may evolve to a new configuration of architectural elements [17]. In view of this, to perform change impact analysis, it is not sufficient to define a traceability representation language and hence to create traceability models.…”

Section: Theoretical Foundations and Related Workmentioning

confidence: 99%

On the Conceptualization of Tools for Traceability-Based Change Impact Analysis Using a Domain-Specific Modeling Approach

Awad,

Boyer

2023

2023 ACM/IEEE International Conference on Model Driven Engineering Languages and Systems Companion (MODELS-C)

View full text Add to dashboard Cite

In the context of system architecture design, design changes are deemed as an important issue in the field of cyber-physical systems. This is due to their costs that can increase up to several folds with each step of the life cycle, from conceptual design to operation. Accordingly, before putting such changes into practice, their impacts need to be analyzed based on traceability of dependencies among elements in system artifacts. However, traceability-based Change Impact Analysis (CIA) is time consuming and error-prone process, if performed manually. Thus, a number of tools have been developed in this regard. Yet, in the absence of approaches guiding the specification and implementation of such tools, research reveals their inadequacy for the needs of the industry. To overcome this, this paper proposes a domain-specific modeling approach for the conceptualization of traceability-based CIA tools. Such approach is composed of three building blocks. First, a language for traceability-based CIA designed around the concept of "CIA parameters" (i.e., all kind of information that could contribute to quantitative or qualitative change impact assessment). Second, a modeling procedure referring to a multi-view modeling approach that explains how to use the traceability language to allow creation and machine processing of models (i.e., analysis of models in terms of change impact). Third, mechanisms and algorithms focusing on the implementation of the modeling procedure on a metamodeling platform. The proposed approach is thus an attempt to bridge the gap between design and implementation of traceability-based CIA tools. The approach is illustrated on an example from the aviation field.

show abstract

Section: Theoretical Foundations and Related Workmentioning

confidence: 99%

On the Conceptualization of Tools for Traceability-Based Change Impact Analysis Using a Domain-Specific Modeling Approach

Awad,

Boyer

2023

2023 ACM/IEEE International Conference on Model Driven Engineering Languages and Systems Companion (MODELS-C)

View full text Add to dashboard Cite

show abstract

“…Keeping the links among software artifacts is a task that software teams should do it from the very beginning of any software project [4]. However, in practice, in most cases, developers are focused on programming tasks and forget their responsibility of creating and maintaining documentation links between the various software artifacts.…”

Section: Introductionmentioning

confidence: 99%

“…However, in practice, in most cases, developers are focused on programming tasks and forget their responsibility of creating and maintaining documentation links between the various software artifacts. Hence, when time permits, the system documentation, and some percentage of links recovery, is left for the final stage of the project [4]. These bad practices lead to significant drawbacks when assessing the quality of the constructed software products as well as the verification of their compliance with the mandatory constraints and stakeholders' needs.…”

Section: Introductionmentioning

confidence: 99%

Automated Fine Grained Traceability Links Recovery between High Level Requirements and Source Code Implementations

Velasco

Aponte

2020

ParadigmPlus

View full text Add to dashboard Cite

Software Traceability has been a matter of discussion in the Software Engineering community for a long time. The process of keeping and recover traces among software artifacts in any system represents a fundamental aspect to properly perform software maintenance tasks and requirements compliance verification. Furthermore, there exist application contexts where this becomes a mandatory process, for instance, banking and healthcare. Software traceability has dedicated efforts in proposing alternatives to recover lost traceability links in a coarse-grained and middle-grained detail by so far, however, proposed techniques are not enough to meet the desired levels of granularity in critical contexts. In this work we propose a fine-grained traceability algorithm designed to recover traces between high level requirements written in human natural language and source code statements where they are implemented. We tested our approach in four open-source healthcare systems to trace constraints requirements specified by the HIPAA law, and we evaluated the results as presented is this paper.

show abstract

Recovering Fine Grained Traceability Links Between Software Mandatory Constraints and Source Code

Velasco

Melo

2019

Communications in Computer and Information Science

View full text Add to dashboard Cite

Evolution Traceability Roadmap for Business Processes

Cited by 4 publications

References 33 publications

On the Conceptualization of Tools for Traceability-Based Change Impact Analysis Using a Domain-Specific Modeling Approach

On the Conceptualization of Tools for Traceability-Based Change Impact Analysis Using a Domain-Specific Modeling Approach

Automated Fine Grained Traceability Links Recovery between High Level Requirements and Source Code Implementations

Recovering Fine Grained Traceability Links Between Software Mandatory Constraints and Source Code

Contact Info

Product

Resources

About