Model-driven business process security requirement specification

Software engineering is continuously evolving, and its tasks are expanding. Nowadays, it includes not only software code development, but business process analysis as well. Information that is gained as a result of such analysis can be used for model that describe processes under automation development. Model driven software engineering also includes application of such models for automated software code or other artefact generation. In comparison to so called “model-based” engineering, model driven engineering uses strictly defined models and its processing algorithms during whole software lifecycle. While ideas, that model driven software engineering is based upon, seem to provide several benefits – for example, initial system representation understood not only by developers, but also by business area experts and, possibly, customers – its adoption is still in the initial phase. This can be explained by both the low level of automation, as well as, inappropriate source model usage. In this thesis, author offers a possible solution to this problem by defining transformation rules for so called Two-Hemisphere Model. This model is a combination of business process and concept diagrams and offered transformation rules allow for a software code generation from it. Additionally, improvements for the Two-Hemisphere model are offered. These improvements are required for enabling of code generation. Also, an algorithm for defining class relationships that can be used also outside of model driven software engineering is described. In this thesis author provides an insight to defined transformation rules by using pseudocode, as well as, an example of its’ application and resulting Java programming language code that was generated from the example model.

Download Full-text

Tool Based Integration of Requirements Modeling and Validation into Business Process Modeling

Software Design and Development ◽

10.4018/978-1-4666-4301-7.ch016 ◽

2014 ◽

pp. 285-309

Author(s):

Sven Feja ◽

Sören Witt ◽

Andreas Speck

Keyword(s):

Business Process ◽

Process Modeling ◽

Process Models ◽

Software Systems ◽

Functional Requirements ◽

Model Driven ◽

Level Of Abstraction ◽

Textual Representations ◽

Model Driven Software Development ◽

The One

Business process models (BPM) are widely used for specification of software systems, as the basis for model driven software development. Hence, it is crucial to ensure that these BPMs fulfill the requirements they have to comply with. These requirements may originate from various domains. Many may be considered non-functional requirements. They are affecting privacy, security, as well as compliance or economic aspects. In order to avoid error-prone manual checking, automated checking techniques should be applied wherever possible. This requires expressing requirements in a formal manner. The common textual representations for such formal requirements are not well accepted in the modeling domain, since they are settled on a lower level of abstraction, compared to BPMs. In this chapter, the authors present the Business Application Modeler (BAM), which integrates formal requirement specification and automated checking with process modeling. On the one hand BAM supports different notations for process modeling. On the other hand a graphical notation, called G-CTL, for the formal specification of requirements is provided. G-CTL is based on temporal logic, and statements are expressed on the level of abstraction of the graphical process models. Furthermore BAM provides the ability to define selective views on process models. This allows complex domain specific annotations of processes as well as the assignment of responsibilities regarding functional domains. Moreover, BAM integrates into common requirements engineering processes.

Download Full-text

Automate Model Transformation From CIM to PIM up to PSM in Model-Driven Architecture

Modern Principles, Practices, and Algorithms for Cloud Security - Advances in Information Security, Privacy, and Ethics ◽

10.4018/978-1-7998-1082-7.ch013 ◽

2020 ◽

pp. 262-283

Author(s):

Yassine Rhazali ◽

Asma El Hachimi ◽

Idriss Chana ◽

Mohammed Lahmer ◽

Abdallah Rhattoy

Keyword(s):

Life Cycle ◽

Software Development ◽

Business Process ◽

Model Transformation ◽

Source Code ◽

Elementary Transformation ◽

Multiple Points ◽

Model Driven ◽

Computer Scientists ◽

Synthesis Methodology

The CIM, PIM, and PSM models are the main levels of the MDA approach. Model transformation is an important step in the MDA process. Indeed, in MDA there are two elementary transformation kinds: CIM to PIM transformation and PIM to PSM transformation. However, most searches propose approaches transforming PIM to PSM, since there are multiple points in common between PIM and PSM. Nevertheless, transforming CIM to PIM is rarely addressed in research because these two levels are mainly different. However, there is not a synthesis work that makes it possible to carry out a model transformation from CIM to PIM towards PSM until obtaining the code. This synthesis methodology allows controlling models transformation from CIM to PIM to PSM, indeed, up to obtaining code according the MDA. This approach makes it possible to limit the intervention of computer scientists in the life cycle of software development. Indeed, this methodology allows modeling only CIM, the business process, and then obtains the source code through successive semi-automatic transformations.

Download Full-text

Compiling Business Process Models into Executable Code

Handbook of Research on Business Process Modeling ◽

10.4018/978-1-60566-288-6.ch015 ◽

2011 ◽

pp. 218-337

Author(s):

Cesare Pautasso

Keyword(s):

Business Process ◽

Process Modeling ◽

Workflow Management ◽

Workflow Engine ◽

Process Models ◽

Management Tool ◽

Business Process Models ◽

Model Driven ◽

Java Bytecode ◽

High Level

Model-driven architecture (MDA), design and transformation techniques can be applied with success to the domain of business process modeling (BPM) with the goal of making the vision of business-driven development a reality. This chapter is centered on the idea of compiling business process models for executing them, and how this idea has been driving the design of the JOpera for Eclipse workflow management tool. JOpera presents users with a simple, graph-based process modeling language with a visual representation of both control and data-flow aspects. As an intermediate representation, the graphs are converted into Event-Condition-Action rules, which are further compiled into Java bytecode for efficient execution. These transformations of process models are performed by the JOpera process compiler in a completely transparent way, where the generated executable artefacts are kept hidden from users at all times (i.e., even for debugging process executions, which is done by augmenting the original, high level notation). The author evaluates his approach by discussing how using a compiler has opened up the several possibilities for performing optimization on the generated code and also simplified the design the corresponding workflow engine architecture.

Download Full-text

Modeling Process-Driven SOAs

Handbook of Research on Business Process Modeling ◽

10.4018/978-1-60566-288-6.ch002 ◽

2011 ◽

pp. 27-48

Author(s):

Huy Tran ◽

Ta’id Holmes ◽

Uwe Zdun ◽

Schahram Dustdar

Keyword(s):

Business Process ◽

Process Development ◽

Control Flow ◽

Levels Of Abstraction ◽

Service Oriented Architectures ◽

Model Driven ◽

Service Oriented ◽

The One ◽

Abstraction Levels ◽

Model Driven Approach

This chapter introduces a view-based, model-driven approach for process-driven, service-oriented architectures. A typical business process consists of numerous tangled concerns, such as the process control flow, service invocations, fault handling, transactions, and so on. Our view-based approach separates these concerns into a number of tailored perspectives at different abstraction levels. On the one hand, the separation of process concerns helps reducing the complexity of process development by breaking a business process into appropriate architectural views. On the other hand, the separation of levels of abstraction offers appropriately adapted views to stakeholders, and therefore, helps quickly re-act to changes at the business level and at the technical level as well. Our approach is realized as a model-driven tool-chain for business process development.

Download Full-text