Business process archeology using MARBLE

Pérez‐Castillo, Ricardo; Guzmán, Ignacio García Rodriguez de; Piattini, Mario

doi:10.1016/j.infsof.2011.05.006

Cited by 49 publications

(24 citation statements)

References 32 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Description Archaeology Analysis of existing systems to understand their functionality, quality, and usage (Pérez-Castillo, Garciía-Rodríguez de Guzmán et al 2011). …”

Section: Techniquementioning

confidence: 99%

Requirements Engineering: Best Practice

Fricker

Grau²,

Zwingli

2014

Requirements Engineering for Digital Health

View full text Add to dashboard Cite

Abstract. Many software solutions have failed because they did not meet stakeholder needs. In response to this problem a massive amount of techniques were developed to elicit stakeholder needs, to analyze the implications of these needs on the software, to specify proposed software products, and to check acceptance of these proposals. However, many of these techniques did not become industrial practice because they were not practicable or ineffective when used in real-world projects. To obtain an overview of what common practice is and to understand which techniques reflect best practice because they are particularly effective, we have surveyed a large number of industry projects. Based on 419 valid answers, this chapter gives an overview of commonly used requirements engineering techniques. It also shows which of the techniques, when used in a software project, correlate with requirements engineering success. The chapter concludes with recommendations for software projects and future research to improve requirements engineering practice.

show abstract

“…Description Archaeology Analysis of existing systems to understand their functionality, quality, and usage (Pérez-Castillo, Garciía-Rodríguez de Guzmán et al 2011). …”

Section: Techniquementioning

confidence: 99%

Requirements Engineering: Best Practice

Fricker

Grau²,

Zwingli

2014

Requirements Engineering for Digital Health

View full text Add to dashboard Cite

show abstract

“…Ghose et al [13], in turn, consider other software artifacts as a set of text-based queries in documentation for extracting business knowledge, but the approach is not based on the MDA. Perez-Castillo et al [2], use standards in their approach to obtain process models. They propose MARBLE to obtain a first approximation of business process that is especially useful for organizations that have never modeled their processes, while their legacy information systems do embed knowledge during its maintenance (knowledge that is only present in the source code, not in the documentation).…”

Section: Related Workmentioning

confidence: 99%

“…Assumption 1. One of the assumptions of the repair technique is that the process models are obtained using MARBLE (Modernization Approach for Recovering Business process from LEgacy systems) [2], a framework for obtaining business processes from legacy information systems (LIS for short), focusing on the phase of reverse engineering. MARBLE is based on KDM, which is recognized as an ISO/IEC 19506 standard [15] and allows abstract conceptual representations of the different views of the architecture of legacy information systems.…”

Section: Technique For Repairing Business Process Modelsmentioning

confidence: 99%

Repairing Business Process Models as Retrieved from Source Code

Fernández-Ropero

Reijers

Pérez‐Castillo

et al. 2013

Enterprise, Business-Process and Information Systems Modeling

Self Cite

View full text Add to dashboard Cite

Abstract. The static analysis of source code has become a feasible solution to obtain underlying business process models from existing information systems. Due to the fact that not all information can be automatically derived from source code (e.g., consider manual activities), such business process models may not entirely reflect the original behavior of the organization. This paper provides a technique to repair such business process models on the basis of event logs collected during the execution of information systems. The technique detects missing sequence flows regarding the event log and tidily adds these sequence flows to the target business process model. In order to enhance its applicability, this technique is tool-supported. Additionally, this paper provides a case study with a real-life system to demonstrate its feasibility.

show abstract

“…According to van der Aalst [20], LDBs store a lot of hidden evidence or knowledge related to process execution, so that they may be good sources to extract Process dimensions, even in the case of Non-PAISs. Regarding BPD from Non-PAISs, some authors, such as Adam et al [21] and Zou et al [22], propose techniques to recover processes, whereas other researchers, such as Pérez-Castillo et al [10,23,24], Arevalo [25], and Arevalo et al [26][27][28], use an MDA-based approach called Process Archeology (PA) for that purpose.…”

Section: Introductionmentioning

confidence: 99%

Practical Experiences in the Use of Pattern-Recognition Strategies to Transform Software Project Plans into Software Business Processes of Information Technology Companies

Arévalo

Ramos

Gutiérrez

et al. 2019

Scientific Programming

View full text Add to dashboard Cite

Business process management (BPM) is a strategic advantage for all kinds of organizations, including information technology companies (ITCs), which cannot stay out of the BPM approach. ITCs manage business processes like projects to create and maintain software. Although Project Management Systems (PMSs), such as Microsoft™ Project Server® (MPS®), are considered as non-process-aware information systems (Non-PAISs), they may be a source to generate processes. In this paper, we propose a reverse engineering approach, which uses patterns to transform software projects stored in MPS® legacy databases into software business processes. For this, we base on the model-driven engineering paradigm and deal with the time perspective of the processes. This kind of experiences are scarce or almost nonexistent, so we show the AQUA-WS project case study, which runs with MPS® as source system and software process modeling languages as target systems. ITCs can benefit from this research by gathering knowledge about perspectives of their processes that would otherwise be wasted, such as executed projects or expired documents used in Non-PAISs. This fact can become a key factor for ITCs, which can increase their competitiveness and reduce software costs, as part of the BPM lifecycle of continuous improvement.

show abstract

Business process archeology using MARBLE

Cited by 49 publications

References 32 publications

Requirements Engineering: Best Practice

Requirements Engineering: Best Practice

Repairing Business Process Models as Retrieved from Source Code

Practical Experiences in the Use of Pattern-Recognition Strategies to Transform Software Project Plans into Software Business Processes of Information Technology Companies

Contact Info

Product

Resources

About