Gundars Alksnis

Lessons learned by using the Integrated Domain Modeling toolset

To contribute with the analysis of tools that attempt to acquire Computation Independent Model (CIM) from the domain system, authors explore the Integrated Domain Modeling toolset, and explain how it automatically acquires a formal CIM from description of a business system in a form of textual business use cases. This paper recognizes the computation independent nature of a Topological Functioning Model and suggests it to be used as a CIM within Model Driven Architecture. Authors of this paper share their experiences of using the toolset and mention several lessons learned during the usage process, as well as, their suggestions for improvements.

Customer-oriented change management for ERP systems

If a deployment of the vendors Enterprise Resource Planning system is integrated with third-party software on a customers premise, then change management highly depends on vendors information about changes between different versions. The problem arises when the vendor cannot predict the impact of the implemented changes on every customers configuration. To tackle this problem we propose a conceptual customer-oriented solution that provides data about the change scope and essentiality for each individual customer.

Containers for Virtualization: An Overview

Abstract Virtualization has enabled the commoditization of cloud computing, as the hardware resources have become available to run different environments and share computing resources amongst different enterprises. Two technology types are commonly used in virtualization of hardware, namely, hypervisor and container. The present paper concerns only container technologies. A comprehensive overview of the container technologies for virtualization and the dynamics of their popularity have not been available yet. Without such an overview, the informed fast choice of technologies is hindered. To fill this knowledge gap, a systemic literature review was conducted to reveal the most popular container technologies and the trends in their research.

Security Evaluation of Wireless Network Access Points

Abstract The paper focuses on the real-world usage of IEEE 802.11 wireless network encryption and Wi-Fi Protected Setup (WPS) function. A brief history on the development of encryption methods and WPS is given. Wireless scanning of 802.11 networks in a capital city has been performed, and the results of it have been analysed. To ascertain the knowledge about the security of wireless networks of the average user, an online survey has been conducted. To test the security of encryption methods and WPS function, practical attacks against private test wireless networks have been made. The authors conclude that the safest way to set up 802.11 network with a pre-shared key is to use Wi-Fi Protected Access 2 (WPA2) encryption without support for WPS function. Statistics in Riga shows that networks are often configured otherwise and thus vulnerable to attacks. Survey results prove that respondents are not well informed regarding the security of wireless networks.

Verification of BPMN Model Functional Completeness by using the Topological Functioning Model

BPMN (Business Process Model and Notation) models are used to specify business knowledge in the language that is familiar for business people. They consist of multiple process diagrams that highlight different aspects of interaction among participants. Verification of BPMN models is important since graphical fragmentary presentation could be a source of errors such as incompleteness, deadlocks, livelocks, incorrect terminations etc. We consider verification of model completeness. The model is transformed to the topological functioning model (TFM) in order to check completeness of inputs, outputs and functioning cycles of the entire specified system. The proposed approach is dedicated to the verification of the model at the beginning of analysis, and it could be supplemented by other methods at the design stage. This approach is more dedicated to analysis of the whole system, than to the verification of the concrete fragment work.

Lessons Learned from Experimental Prototype Development for KPI Acquisition and Modeling from Legacy ERP Systems

In this paper we consider a business case of an Enterprise Resource Planning (ERP) system vendor who needs to introduce qualitative features without making great investments in the legacy source code. We propose to extend legacy ERP system’s functionality by applying the Leading System paradigm so that business process management can be introduced. This enables business process awareness and provides opportunity for qualitative feature set introduction in a legacy ERP system. As a result, Key Performance Indicator (KPI) acquisition, modeling and analysis from the process aware legacy ERP system becomes possible. The main focus in this paper is on lessons learned about a suitable prototype architecture for KPI acquisition, modeling and analysis, and about best practices for KPI analysis from log data of business process execution.

Customer Oriented Management of Changes in ERP Systems: The Vendor’s Side

The paper discusses a business case when customer’s deployment of the Enterprise Resource Planning solution (ERP) is integrated with third-party’s software. Customer’s change management highly depends on vendor’s information about changes between ERP versions. The problem is that the vendor cannot predict the impact of implemented changes on every customer’s business. In the suggested conceptual customer-oriented solution, the conjoint assessment evaluates the size, the scope and the essentiality of ERP changes in order to provide data on changes for a particular customer. The resulting difference model could be enhanced with results of analysis of collected access statistics for customer’s ERP packages. The solution uses a unified data format for data interchange. The final model of ERP changes and their essentiality for a particular customer could be visualized for the further application.

Category theoretic integration framework for formal notations in model driven software engineering

The paper presents research results of formal notations and Unified Modeling Language (UML) integration framework within the model driven software engineering. The originality of the solution is based on the combination of three technologies (formal notations, UML and category theory), in order to ensure their theoretical basis for integration in Model Driven Architecture. Framework is characterized by a principle according to which each UML model and corresponding formal specification is examined as an independent object, while morphisms between them specify how they are mutually linked. This allows to specify specific aspects of the system in a notation that is the best suited.