Microservices Container Security Orchestration Framework within Kubernetes and Docker for Business-Critical Applications within Digital Transformation

Container virtualization technology facilitates the creation of microservices-based systems through continuous integration. Container-based apps can be deployed more easily when they use orchestration systems like Kubernetes, which has become the de facto standard. It can be difficult to create effective and precise orchestration systems, nevertheless. The scheduler, a crucial orchestrator task that allocates physical resources to containers, is the subject of this article. Scheduling strategies are developed using several Quality-of-Service metrics. The CI in CI/CD stands for continuous integration. Continuous integration drives the automation in the development and delivery of the code and developers frequently apply code changes. It’s an automated process that allows multiple developers to contribute software components to the same project without integration conflicts. CI also triggers the process of testing the applications automatically upon code commit into the repository. Container virtualization technology facilitates the creation of microservices-based systems through continuous integration. Container-based apps can be deployed more easily when they use orchestration systems like Kubernetes, which has become the de facto standard. It can be difficult to create effective and precise orchestration systems, nevertheless. The scheduler, a crucial orchestrator task that allocates physical resources to containers, is the subject of this article. Scheduling strategies are developed using several Quality of Service metrics

OntoMaven: Maven-based Ontology Development and Management of Distributed Ontology Repositories

In collaborative agile ontology development projects support for modular reuse of ontologies from large existing remote repositories, ontology project life cycle management, and transitive dependency management are important needs. The Apache Maven approach has proven its success in distributed collaborative Software Engineering by its widespread adoption. The contribution of this paper is a new design artifact called OntoMaven. OntoMaven adopts the Maven-based development methodology and adapts its concepts to knowledge engineering for Maven-based ontology development and management of ontology artifacts in distributed ontology repositories.Comment: Pre-print submission to 9th International Workshop on Semantic Web Enabled Software Engineering (SWESE2013). Berlin, Germany, December 2-5, 201

Git4Voc: Git-based Versioning for Collaborative Vocabulary Development

Collaborative vocabulary development in the context of data integration is the process of finding consensus between the experts of the different systems and domains. The complexity of this process is increased with the number of involved people, the variety of the systems to be integrated and the dynamics of their domain. In this paper we advocate that the realization of a powerful version control system is the heart of the problem. Driven by this idea and the success of Git in the context of software development, we investigate the applicability of Git for collaborative vocabulary development. Even though vocabulary development and software development have much more similarities than differences there are still important differences. These need to be considered within the development of a successful versioning and collaboration system for vocabulary development. Therefore, this paper starts by presenting the challenges we were faced with during the creation of vocabularies collaboratively and discusses its distinction to software development. Based on these insights we propose Git4Voc which comprises guidelines how Git can be adopted to vocabulary development. Finally, we demonstrate how Git hooks can be implemented to go beyond the plain functionality of Git by realizing vocabulary-specific features like syntactic validation and semantic diffs

On the symbiosis between conceptual modeling and ontology engineering : recommendation-based conceptual modeling

Within an enterprise, different conceptual models, such as process, data, and goal models, are created by various stakeholders. These models are fundamentally based on similar underlying enterprise (domain) concepts, but they have a different focus, are represented using different modeling languages, take different viewpoints, utilize different terminology, and are used to develop different enterprise artefacts (such as documents, software, databases, etc.); therefore, they typically lack consistency and alignment. Another issue is that modelers have different vocabulary selections and different modeling styles. As a result, the enterprise can find itself accumulating a pile of models which cover similar aspects in different manners. Those models are not machine-readable and cannot be processed automatically. Enterprise-Specific Ontologies (ESOs) aim to solve this problem by serving as a reference during the conceptual model creation. Using such a shared semantic repository makes conceptual models semantically aligned and facilitates model integration. However, managing those ontologies is complicated; an enterprise is an evolving entity, and as it changes, the ESO might become outdated. During the years of research dedicated to this dissertation, the Recommendation-Based Conceptual Modeling and Ontology Evolution (CMOE+) framework was developed. This framework establishes a symbiotic relationship between the Ontology engineering and the Conceptual modeling fields. CMOE+ consists of two cycles: the Ontology Evolution cycle and the Conceptual Modeling cycle. The Ontology Evolution cycle is responsible for setting up the initial version of the ESO and updating it as the knowledge within the enterprise evolves. Additionally, this cycle encapsulates recommendation services to perform ontology look-up and to present the most relevant ESO concepts in support of the modeler. The Conceptual Modeling cycle is responsible for the creation of conceptual models in different modeling languages based on the ESO. This cycle is also concerned with the quality evaluation of the created models. CMOE+ was developed based on requirements identified as a result of a literature review and a case study. The development process follows the Design Science Research Methodology (DSRM). After the initial version of CMOE+ was put forward, our focus was narrowed towards the recommendation-based conceptual modeling part of CMOE+, and we continued to gradually improve the framework in iterations until it reached its current state. The Ontology Evolution Cycle is not fully addressed within the scope of this dissertation. In order to demonstrate the performance and usability of CMOE+, it was exemplified for process modeling using BPMN and goal modeling using i*. This thesis presents a detailed instantiation, and explains steps to be performed in order to instantiate CMOE+ for other modeling languages. In order to evaluate the process modeling instance of CMOE+, a CMOE+BPMN tool was implemented. This tool incorporates a BPMN modeler, facilitates storage and access of the ESO, and includes all algorithms functioning within CMOE+ for the BPMN modeling language (as some of the algorithms are language dependent). Next, CMOE+ was exemplified using the i* goal modeling language. Finally, we demonstrated the ability of CMOE+ to perform alignment between i* and BPMN models, in order to show that CMOE+ is indeed beneficial in achieving interoperability among models created in different modeling languages and covering distinct aspects of the enterprise