Business process and practice alignment meta-model

Business Process Modelling (BPM) is one of the most important phases of information system design. Business Process meta-models allow capturing informational and behavioural aspects of business processes. Unfortunately, standard business process meta-modelling approaches, such as the Business Process Model and Notation (BPMN) Meta-model, Quality-Oriented Business Process Meta-Model (QOBPM) and Transactional Meta-Model for Business Process (TMBP) focus just on process description, providing different business process models. According to these meta-modelling approaches, it is not possible to compare and identify related daily practices in order to improve business process models. This lack of information recognizes that further research in Business Process (BP) meta-model is needed to reflect the evolution/change on software processes. Considering this limitation in BP meta-modelling, this paper presents a comparative study of the most recognized business process meta-models approaches and introduces a new BP meta-model designed by Business Process and Practice Alignment Meta-model (BPPAMeta-model). Our intention is to present observed problems in existing approaches and propose a business process meta-model that addresses features related to the alignment between daily work practices and business process descriptions. (C) 2015 The Authors. Published by Elsevier B.V

An ontological approach for recovering legacy business content

Legacy Information Systems (LIS) pose a challenge for many organizations. On one hand, LIS are viewed as aging systems needing replacement; on the other hand, years of accumulated business knowledge have made these systems mission-critical. Current approaches however are often criticized for being overtly dependent on technology and ignoring the business knowledge which resides within LIS. In this light, this paper proposes a means of capturing the business knowledge in a technology agnostic manner and transforming it in a way that reaps the benefits of clear semantic expression - this transformation is achieved via the careful use of ontology. The approach called Content Sophistication (CS) aims to provide a model of the business that more closely adheres to the semantics and relationships of objects existing in the real world. The approach is illustrated via an example taken from a case study concerning the renovation of a large financial system and the outcome of the approach results in technology agnostic models that show improvements along several dimensions

Semantics of trace relations in requirements models for consistency checking and inferencing

Requirements traceability is the ability to relate requirements back to stakeholders and forward to corresponding design artifacts, code, and test cases. Although considerable research has been devoted to relating requirements in both forward and backward directions, less attention has been paid to relating requirements with other requirements. Relations between requirements influence a number of activities during software development such as consistency checking and change management. In most approaches and tools, there is a lack of precise definition of requirements relations. In this respect, deficient results may be produced. In this paper, we aim at formal definitions of the relation types in order to enable reasoning about requirements relations. We give a requirements metamodel with commonly used relation types. The semantics of the relations is provided with a formalization in first-order logic. We use the formalization for consistency checking of relations and for inferring new relations. A tool has been built to support both reasoning activities. We illustrate our approach in an example which shows that the formal semantics of relation types enables new relations to be inferred and contradicting relations in requirements documents to be determined. The application of requirements reasoning based on formal semantics resolves many of the deficiencies observed in other approaches. Our tool supports better understanding of dependencies between requirements