31,819 research outputs found

    Cloud service localisation

    Get PDF
    The essence of cloud computing is the provision of software and hardware services to a range of users in dierent locations. The aim of cloud service localisation is to facilitate the internationalisation and localisation of cloud services by allowing their adaption to dierent locales. We address the lingual localisation by providing service-level language translation techniques to adopt services to dierent languages and regulatory localisation by providing standards-based mappings to achieve regulatory compliance with regionally varying laws, standards and regulations. The aim is to support and enforce the explicit modelling of aspects particularly relevant to localisation and runtime support consisting of tools and middleware services to automating the deployment based on models of locales, driven by the two localisation dimensions. We focus here on an ontology-based conceptual information model that integrates locale specication in a coherent way

    Exploring Maintainability Assurance Research for Service- and Microservice-Based Systems: Directions and Differences

    Get PDF
    To ensure sustainable software maintenance and evolution, a diverse set of activities and concepts like metrics, change impact analysis, or antipattern detection can be used. Special maintainability assurance techniques have been proposed for service- and microservice-based systems, but it is difficult to get a comprehensive overview of this publication landscape. We therefore conducted a systematic literature review (SLR) to collect and categorize maintainability assurance approaches for service-oriented architecture (SOA) and microservices. Our search strategy led to the selection of 223 primary studies from 2007 to 2018 which we categorized with a threefold taxonomy: a) architectural (SOA, microservices, both), b) methodical (method or contribution of the study), and c) thematic (maintainability assurance subfield). We discuss the distribution among these categories and present different research directions as well as exemplary studies per thematic category. The primary finding of our SLR is that, while very few approaches have been suggested for microservices so far (24 of 223, ?11%), we identified several thematic categories where existing SOA techniques could be adapted for the maintainability assurance of microservices

    Extended enterprise architecture with the FADEE.

    Get PDF
    Business-to-Business integration (B2Bi) is considered to be not merely an IT-issue, but also a business problem. This paper draws attention to the challenges companies within an Extended Enterprise are confronted with when integrating their systems. We primarily pay attention to coordination problems that may arise. To overcome these problems we propose the use of Enterprise Architecture descriptions. We discuss the powers of using Enterprise Architecture descriptions in integration exercises. It will become clear that doing Enterprise Architecture is no longer an option; it is mandatory. Furthermore, we present the FADEE, the Framework for the Architectural Description of the Extended Enterprise. This framework gives an overview of how companies can apply the Zachman framework to do Enterprise Architecture in the realm of the Extended Enterprise.Architecture; Business-to-Business integration; Companies; Coordination; Enterprise architecture; Extended enterprise; Extended enterprise architecture framework; FADEE; Framework; Integration; Problems; Research; Systems;

    Approach to Rapid Software Design of Mobile Applications’ User Interface

    Get PDF
    Mobile applications have a lot of unique challenges during the development process. One of them is monolith architecture that can’t be skipped even for large Mobile Enterprise applications. Software engineer should keep mind the whole source code structure to be effective. This article will introduce an approach to Rapid Software Design that allows to make a working documentation related to code and understandable by all team members. Rapid Software Design is suitable for Waterfall/Agile processes of developing applications with graphical user interface (web, mobile, desktop, embedded) and initially was created for mobile projects. This article contains only the description of User Interface related documentation despite the whole Rapid Software Design also covering the usage of architecture patterns, business logic, services, features of mobile operation systems and writing automated tests

    Data DNA: The Next Generation of Statistical Metadata

    Get PDF
    Describes the components of a complete statistical metadata system and suggests ways to create and structure metadata for better access and understanding of data sets by diverse users

    Facilitating Conflict Resolution of Models for Automated Enterprise Architecture Documentation

    Get PDF
    Enterprise Architecture (EA) management relies on solid and up-to-date information about the current state of an EA. In current practices the manual collection of information is prevailing resulting in an error-prone, time-consuming, and expensive task. Recent research efforts seek to automate this task by integrating existing information sources in the organization to optimize the EA documentation process. While automation of EA documentation enables many advantages, the transformation of the collected information to an EA model remains an unresolved challenge since it cannot be automated completely. In particular, conflicts resulting from partial transformations require involvement of EA Stakeholders possibly not having a technical background. In this paper we propose an approach for the conflict resolution facilitating our long-term goal of automated EA documentation. We illustrate our approach using a productive Enterprise Service Bus from a leading organization of the fashion industry and evaluate our approach with expert interviews
    • …
    corecore