Germán Antonio Montejano

Transformations from SPEM work sequences to BPMN sequence flows for the automation of software development process

Generally, different companies use distinct software development process. Due to it, OMG has specified an architecture to can define a software development process. This architecture uses a metamodel which is able to be abstracted from particular characteristics and to give the possibility of defining the different software development processes. The Software Process Engineering Metamodel (SPEM) is a metamodel used for describing a concrete software development process. Also, the OMG specify a standardized language to model business processes. This language is called Business Process Modeling Notation (BPMN). In this paper, a formalization of transformations between SPEM and BPMN is specified. The transformations are done using the language of formal specification RSL. One time that we obtain a BPMN specification, it is possible to generate XPDL code or BPEL code. The workflow technology can use this code and execute the process. It allows automate the business process, but in this case, the process is a software development process. Consider that workflow technologies automate, totally or partially, the business processes enabling an interaction between men and machines, under an established set of procedural rules. Such technologies use standard languages, like BPEL or XPDL, to specify the business process which is executed in a workflow engine. The BPMN allows to generate BPEL or XPDL codes. Therefore, if we specify a software development process using SPEM, we will automate this process using the workflow technology due to transformations between SPEM and BPMN done in this paper.

Workflow Models: Management and Quality of Process in the Cloud

It is important to implement a continuous improvement when analyzing the life cycle of Business Process (BP). As a result, organizations are searching for tools like Business Process Management (BPM) using Business Process Management System (BPMS). The Workflow Management System (WfMS) is the most significant BPMS that is used to automatically improve the business process. Organizations require virtual business process on the Internet through cloud computing. WfMS provides computational support to define, synchronize and execute activities using workflows. There are many desirable operational aspects to implement workflow technology, such as task sequence, control and monitoring mechanisms. Workflow allows automation of different aspects of the information flow, for example: address the work in the correct sequence, provide data and document access, and manage the executable condition of the process. Thus Internet conceptual model in the cloud becomes workflow technology by transforming: a) actions into activities or sub process, b) information into data between activities, and c) actors in agents. Another fundamental aspect in a workflow process is measuring the most relevant elements, and detecting process areas that can be improved. Under these considerations, we proposed a framework to analyze and measure workflow process. This framework helps to improve and keep the maintenance of models and processes. All executing business process has an underlying workflow, and given the increasing work in the cloud, we applied this framework for evaluating workflow processes in the cloud. The framework helps to evaluate, compare and improve the workflow and, as a result, leads to the improvement of the processes.

Including workflow concurrent modelling in an extension of the UML activity diagram metamodel

Summary form only given. A workflow is a business process whose execution is controlled in an automated fashion by a workflow management system (wms). A model of the process to be enacted is supplied to the wms through a specification known as process definition. The format of such definition has been standardized by the workflow management coalition (wfmc) with the purpose of satisfying the need of interaction and connectivity between process definition tools and different workflow systems. The workflow process definition standard is specified by a metamodel and the workflow process definition language (wpdl). Both are isomorphic. In business process modelling, the UML standard notation supports less details than the wfmc standard. A wpdl process definition may contain more information than UML activity diagrams. Therefore, a process specification based on activity diagrams does not satisfy the wfmc standard. We propose the integration of the wfmc and the UML standard, and provide a view of how this integration can be achieved through the extension of the UML activity diagram. The extension proposed neither modifies nor restricts the original UML standard. A model built with this extension is easily translated to the wpdl. We show the extension of the UML activity diagram to include the concepts of concurrency and synchronization of workflow processes. In this way, the process definition in UML activity diagram may be interpreted by any wms.

Model Based Evaluation of Cybersecurity Implementations

Evaluation of Cybersecurity implementations is an important issue that is increasingly being considered in the agenda of organisations. We present here a model for the evaluation of Cybersecurity requirements. We start by establishing a set of security requirements in the form of a hierarchical structure to obtain a requirement tree, as it is prescribed by the Logic Score of Preference (LSP) evaluation method. Security requirements have been taken from the ISO/IEC 27002 standard. This requirement tree and an aggregation structure, built into a later step, form our Cybersecurity evaluation model, which allows to obtain a numerical final result for each system under evaluation. These final indicators, ranging into the interval 0..100, clearly show the degree of compliance of the systems under evaluation with respect to the desired requisites.