TranspLanMeta: A metamodel for TranspLan modeling language

Transparency and transparent decision making are essential requirements in information systems. To this end, a modeling language called TranspLan has been proposed. TranspLan is a domain-specific modeling language which is designed for the purpose of analysing and modeling transparency requirements in information systems. This paper presents a metamodel for transparency requirements modeling. We are introducing a model-driven approach to TranspLan language specifications to facilitate the use of the language more efficiently in real life cases. Metamodeling is an effective method for formally defining domain specific languages and moving from specifications to computer-aided modeling. In this paper, we propose a metamodel for TranspLan modeling language which is called as TranspLanMeta. The metamodeling process helps us to transfer TranspLan language specifications into a machine-readable format. The metamodel has been developed with GME (Generic Modelling Environment), which is a configurable toolkit for creating domain-specific modeling and program synthesis environments. By developing TranspLanMeta with GME, an automatically-generated modeling tool for TranspLan language is provided as well. In this way, an effective approach for accelerating software development is followed and the auto-generated modeling editor is used to define various models. This work provides a formal and practical solution for transparency modeling and a well-defined basis for using transparency requirements models in the further steps of the business process

Root Cause Analysis in Business Processes

Conceptual modeling is an important tool for understanding and revealing weaknesses of business processes. Yet, the current practice in reengineering projects often considers simply the as-is control flow and uses the respective model barely as a reference for brain-storming about improvement opportunities. This approach heavily relies on the intuition of the participants and misses a clear description of steps to identify root causes of problems. In contrast to that, this paper introduces a systematic methodology to detect and document the quality dimension of a business process. It builds on the definition of softgoals for each process activity, of correlations between softgoals, and metrics to measure the occurrence of quality issues. In this regard our contribution is a foundation of root-cause analysis in business process modeling, and a conceptual integration of goal-based and activity-based approaches to capturing processes

A new formal and analytical process to product modeling (PPM) method and its application to the precast concrete industry

The current standard product (data) modeling process relies on the experience and subjectivity of data modelers who use their experience to eliminate redundancies and identify omissions. As a result, product modeling becomes a social activity that involves iterative review processes of committees. This study aims to develop a new, formal method for deriving product models from data collected in process models of companies within an industry sector. The theoretical goals of this study are to provide a scientific foundation to bridge the requirements collection phase and the logical modeling phase of product modeling and to formalize the derivation and normalization of a product model from the processes it supports. To achieve these goals, a new and formal method, Georgia Tech Process to Product Modeling (GTPPM), has been proposed. GTPPM consists of two modules. The first module is called the Requirements Collection and Modeling (RCM) module. It provides semantics and a mechanism to define a process model, information items used by each activity, and information flow between activities. The logic to dynamically check the consistency of information flow within a process also has been developed. The second module is called the Logical Product Modeling (LPM) module. It integrates, decomposes, and normalizes information constructs collected from a process model into a preliminary product model. Nine design patterns are defined to resolve conflicts between information constructs (ICs) and to normalize the resultant model. These two modules have been implemented as a Microsoft Visio ™ add-on. The tool has been registered and is also called GTPPM ™. The method has been tested and evaluated in the precast concrete sector of the construction industry through several GTPPM modeling efforts. By using GTPPM, a complete set of information items required for product modeling for a medium or a large industry can be collected without generalizing each company's unique process into one unified high-level model. However, the use of GTPPM is not limited to product modeling. It can be deployed in several other areas including: workflow management system or MIS (Management Information System) development software specification development business process re-engineering.Ph.D.Committee Chair: Eastman, Charles M.; Committee Co-Chair: Augenbroe, Godfried; Committee Co-Chair: Navathe, Shamkant B.; Committee Member: Hardwick, Martin; Committee Member: Sacks, Rafae

Beyond Control-Flow: Extending Business Process Configuration to Roles and Objects

A configurable process model is an integrated representation of multiple variants of a business process. It is designed to be individualized to meet a particular set of requirements. As such, configurable process models promote systematic reuse of proven or common practices. Existing notations for configurable process modeling focus on capturing tasks and control-flow dependencies, neglecting equally important aspects of business processes such as data flow, material flow and resource management. This paper fills this gap by proposing an integrated meta-model for configurable processes with advanced features for capturing resources involved in the performance of tasks (through task-role associations) as well as flow of data and physical artifacts (through task-object associations). Although embodied as an extension of a popular process modeling notation, namely EPC, the meta-model is defined in an abstract and formal manner to make it applicable to other notations

Business and Information System Alignment Theories Built on eGovernment Service Practice: An Holistic Literature Review

© 2019 The Author(s). Licensee IntechOpen. This chapter is distributed under the terms of the Creative Commons Attribution 3.0 License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.This chapter examines previous studies of alignment between business and information systems holistically in relation to the development of working associations among professionals from information system and business backgrounds in business organization and eGovernment sectors while investigating alignment research that permits the development and growth of information system, which is appropriate, within budget and on-time development. The process of alignment plays a key role in the construction of dependent associations among individuals from two different groups, and the progress of alignment could be enhanced by emerging an information system according to the investors’ prospects. The chapter presents system theory to gather and analyze the data across the designated platforms. The outcomes classify that alignment among business and information system departments remains a priority and is of worry in different ways in diverse areas, which provides prospects for the forthcoming discussion and research.Final Published versio