Showing papers on "View model published in 2019"

Verification of Architectural Views Model 1+5 Applicability

Abstract: The paper presents architectural views model 1+5 which has been proposed for designing integration solutions of collaborating software systems. The author has introduced modeling extensions of Unified Modeling Language (UML) in form of UML profiles. The author has proposed an Integration flow diagram which is special form of UML activity diagram. The diagram arranges mediation mechanisms from UML Profile for Integration Flows into an integration flow. The paper presents transformations of model-to-model and model-to-code types which automate design of integration platform. The 1+5 was successfully applied in Service-Oriented Architecture. The approach reveals its potential in Domain-Driven Design, Micro-services and blockchain solutions.

Extending and Instantiating a Software Reference Architecture for IoT-Based Healthcare Applications

Abstract: The Internet of Things (IoT) is making possible the development of applications in many markets, such as buildings, home, industrial and healthcare. Concerning the healthcare market, there are a lot of challenges in the design, development, and deployment of these applications, such as interoperability, availability, usability, and security. To contribute to solve the aforementioned challenges, we proposed a software reference architecture, named Reference Architecture for IoT-based Healthcare Applications (RAH), to systematically organize the main elements of this domain, its responsibilities and interactions, promoting a common understanding of these applications’ architecture. RAH presents software architectural solutions (i.e., architectural patterns and tactics) documented using architectural views. This work aims to present RAH and instantiate it to design the software architecture of an IoT-based healthcare platform for intelligent remote monitoring of the patient’s health data.

Code-first model-driven engineering: on the agile adoption of MDE tooling

Abstract: Domain models are the most important asset in widely accepted software development approaches, like Domain-Driven Design (DDD), yet those models are still implicitly represented in programs. Model-Driven Engineering (MDE) regards those models as representable entities that are amenable to automated analysis and processing, facilitating quality assurance while increasing productivity in software development processes. Although this connection is not new, very few approaches facilitate adoption of MDE tooling without compromising existing value, their data. Moreover, switching to MDE tooling usually involves re-engineering core parts of an application, hindering backward compatibility and, thereby, continuous integration, while requiring an up-front investment in training in specialized modeling frameworks. In those approaches that overcome the previous problem, there is no clear indication - from a quantitative point of view - of the extent to which adopting state-of-the-art MDE practices and tooling is feasible or advantageous. In this work, we advocate a code-first approach to modeling through an approach for applying MDE techniques and tools to existing object-oriented software applications that fully preserves the semantics of the original application, which need not be modified. Our approach consists both of a semi-automated method for specifying explicit view models out of existing object-oriented applications and of a conservative extension mechanism that enables the use of such view models at run time, where view model queries are resolved on demand and view model updates are propagated incrementally to the original application. This mechanism enables an iterative, flexible application of MDE tooling to software applications, where metamodels and models do not exist explicitly. An evaluation of this extension mechanism, implemented for Java applications and for view models atop the Eclipse Modeling Framework (EMF), has been conducted with an industry-targeted benchmark for decision support systems, analyzing performance and scalability of the synchronization mechanism. Backward propagation of large updates over very large views is instant.

Architecture conformance analysis using model‐based testing: A case study approach

Abstract: Context: The architectural drift problem defines the discrepancy between the architecture description and the code. Deviations of the code from the architecture can occur if architectural constraints as defined in the architectural models are not implemented in the code. For large-scale systems, manually checking the consistency of the architecture with the code is not trivial and cumbersome. Objective: The overall objective of this paper is to propose and analyze the effectiveness and practicality of an architecture conformance analysis approach using model-based testing (ACAMBT) approach for checking the consistency between architectural models and the code. Hereby, we consider the case whereby the architecture is assumed correct, and the code needs to align with the architecture. Method: We propose a model-based testing that uses architectural views to automatically derive test cases for checking the architectural constraints in the code. We have evaluated the approach and the corresponding toolset for a real industrial case study using a systematic case study protocol. Further, we have adopted exhaustive fault-injection techniques to detect the constraint violations. Results: The evaluation of the approach on real code showed that deviations with the architectural constraints could be easily detected in the code. Conclusion: We can conclude that ACAMBT is effective for identifying inconsistencies between the architecture views and the code for the defined view constraints. Our survey study with practitioners showed that adopting the ACAMBT approach is practical and easy to use. The approach as such can be considered as a complimentary tool to the existing testing and reflexion modeling approaches.

Towards a Reference Architecture for ADM-based Modernization Tools

Abstract: Context: The modernization of a legacy software system is a reality of companies that need to improve their systems. Architecture-Driven Modernization (ADM) is a model-driven blueprint that support modernization engineers in the modernization processes. ADM considers the usage of reengineering and model driven architecture (MDA) concepts and advocates the employment of standard metamodels, such as Knowledge Discovery Metamodel (KDM). One of the main challenges while considering ADM is on how modernization tools (MTs) should be developed in order to allow the success of modernization projects that follows the ADM blueprint. Objective: In this paper we address the main requirements and guidelines on how modernization tools should be designed by means of a Reference Architecture (RA) for ADM-based Modernization Tools named RADMoTo. Methodology: We followed a four-steps methodological process to build RADMoTo and to evaluate it we submitted the RA technical report and a survey to ADM experts and software architects in order to get a feedback of the RA acceptance level. Results: As a result, we found out that, in general, the participants believe that our RA provides an acceptable level while considering the architectural views. Conclusion: The feedback from the participants helped in the improvement process of the RA. Thus, we claim that this paper provides concrete guidelines on how modernization tools should be designed and on how architectural instances derived from our RA could benefit from reusability and interoperability.

Controlling Concurrent Change - A Multiview Approach Toward Updatable Vehicle Automation Systems

Abstract: The development of SAE Level 3+ vehicles [{SAE}, 2014] poses new challenges not only for the functional development, but also for design and development processes. Such systems consist of a growing number of interconnected functional, as well as hardware and software components, making safety design increasingly difficult. In order to cope with emergent behavior at the vehicle level, thorough systems engineering becomes a key requirement, which enables traceability between different design viewpoints. Ensuring traceability is a key factor towards an efficient validation and verification of such systems. Formal models can in turn assist in keeping track of how the different viewpoints relate to each other and how the interplay of components affects the overall system behavior. Based on experience from the project Controlling Concurrent Change, this paper presents an approach towards model-based integration and verification of a cause effect chain for a component-based vehicle automation system. It reasons on a cross-layer model of the resulting system, which covers necessary aspects of a design in individual architectural views, e.g. safety and timing. In the synthesis stage of integration, our approach is capable of inserting enforcement mechanisms into the design to ensure adherence to the model. We present a use case description for an environment perception system, starting with a functional architecture, which is the basis for componentization of the cause effect chain. By tying the vehicle architecture to the cross-layer integration model, we are able to map the reasoning done during verification to vehicle behavior.

Architectural design of IoT-based healthcare applications

Abstract: The myriad of connected things promoted by the Internet of Things (IoT) and the data captured by them is making possible the development of applications in various markets, such as transportation, buildings, energy, home, industrial and healthcare. Concerning the healthcare market, it is expected the development of these applications as part of the future, since it can improve e-Health to allow hospitals to operate more efficiently and patients to receive better treatment. The IoT can be the main enabler for distributed healthcare applications, thus having a significant potential to contribute to the overall decrease of healthcare costs while increasing the health outcomes. However, there are a lot of challenges in the development and deployment of this kind of application, such as interoperability, availability, performance, and security. The complex and heterogeneous nature of IoT-based healthcare applications makes its design, development and deployment difficult. It also causes an increase in the development cost, as well as an interoperability problem with the existing systems. To contribute to solve the aforementioned challenges, this thesis aims at improving the understanding and systematization of the IoT-based healthcare applications’ architectural design. It proposes a software reference architecture, named Reference Architecture for IoT-based Healthcare Applications (RAH), to systematically organize the main elements of these applications, its responsibilities and interactions, promoting a common understanding of these applications’ architecture. To establish RAH, a systematic mapping study of existing publications regarding IoT-based healthcare applications was performed, as well the study about quality attributes, tactics, architectural pattern and styles used in software engineering. As a result, RAH presents domain knowledge and software architectural solutions (i.e., architectural patterns and tactics) documented using architectural views. To assess RAH, a case study was performed by instantiating it to design the software architecture of a computational platform based on the Internet of Things (IoT) infrastructure to allow the intelligent remote monitoring of the patient’s health data (biometrics). With this platform, the clinical staff can be alerted of the health events that require immediate intervention and then prevent unwanted complications. Results evidenced that RAH is a viable reference architecture to guide the development of secure, interoperable, available, and efficient IoT-based healthcare applications, bringing contributions for the areas of e-Health and software architecture.

The ALI Architecture Description Language

Abstract: Architecture Description Languages (ADLs) have emerged over the past two decades as a means to abstract details of large-scale systems in order to enable better intellectual control over the complete systems. Recently, there has been an explosion in the number of ADLs created in the research community. However, industrial adoption of these ADLs has been rather limited. This has been attributed to various reasons, including the lack of support of some ADLs for: variability management, requirements traceability, architectural artefact reusability and multiple architectural views. To overcome these limitations, this paper is a report on ALI, an ADL that was designed to complement existing work by adding mechanisms to address the aforementioned limitations. The ALI design principles, concepts, notations and formal semantics are presented in this paper. The notation is illustrated using two distinct case studies, one from the information systems domain " an Asset Management System (AMS); and another from the embedded systems domain - a Wheel Brake System (WBS).

Serialize view model for debugging and application support

Abstract: Techniques for generating serialized view models that are used for both debugging an application and application support. The techniques include executing an application, creating a view model associated with the application, the view model including information associated with a service provided by the application, and presenting a user interface associated with the view model. The techniques can further include identifying, while presenting the user interface, an error occurring with the application, capturing a stack trace corresponding to the error, capturing a process image of the view model, serializing the process image of the view model to generate a serialized view model, and sending the stack trace and the serialized view model to a service. The service can then use the stack trace and the serialized view model to debug the application.

Ad-Hoc Architecture of Systems for Disaster Risk Management

Abstract: The essence of functioning of present-day systems of disasters risk management is information processing for decision making in target domain of risk management. Risk management is the specific field of situational management. Disasters is a result of evolution of situations concerned with different environment natural, technogenic, and human activity processes. The main purpose of disasters risks management (DRM) systems is to provide organizational and technological services to participants in risk management processes to perform the functions assigned to them. DRM system is a complex organizational and technical system. The result of its configuration should be accorded with the architectural model of the organization and cover all levels of organizational and technical means that ensure its operation. Ad-hoc architectural views should reflect point of views concerted with situation context (semantics), stakeholders’ positions and available required management means. Organization of DRM system based on ad-hoc architecture approach is proposed in the paper.

Architectural Approach to Ontological Maintenance of Solving the Project Tasks in Conceptual Designing a Software Intensive System

Abstract: The paper focuses on developing a complex means of ontological maintenance (OM) in designing the software intensive systems (SIS). The essential feature of an offered version of the OM is accessible to such means via interfaces based on architectural views, any of which is realized in the form of the block-and-line scheme reflecting the states of possible applying the OM. Thus, any of such views is applied for developing the OM and its using via the certain interface presented in the understandable form. The prototype version of the OM was developed in the toolkit WIQA (Working In Questions and Answers), which provides the solution of design tasks at the conceptual stage of the development of the SIS. In the described case, this toolkit is applied for solving the task of developing the OM as the complex embedded to the WIQA. In its turn, the complex is intended for the ontological maintenance of solving the project task in conceptual designing of any SIS.

Beyond Digitalization Traps: A 4-Layer Model of IoT Service Engineering In an Enterprise Context

Abstract: With advances in information and communication technologies (ICT), the Internet of Things (IoT) penetrates into enterprise computing. However, despite positive attitudes in many enterprises, many IoT-based solutions have stagnated at a stage of Proof of Concept (PoC). The author analyzes obstacles in this challenge. Then, the author presents a concept of digitalization trap. The author presents a simple use case in enterprise computing. From the four different viewpoints to solve the use case, the author presents a 4-layer view model of enterprise computing. In order to deal with this digitalization trap, the author describes the implications of the 4-layer view model. With an increased number of IoT technology available, the author presents importance of a layered view model to identify the critical focal point of service engineering in an enterprise context.

An urban and rural road passenger transport integrated development level monitoring system and method

Abstract: The invention discloses an urban and rural road passenger transport integrated development level monitoring system and method. The system is divided into three parts: a front-end part, a middle-stagelogic processing part, a background data persistence and object storage part, wherein the front-end part architecture is based on an MVVM scheme, a presentation layer focuses on page presentation andinteraction event processing, a view model layer processes the business logic related to the view, and a Model layer stores the model data while taking the logic of the background data processing intoaccount; middle-stage logic processing is based on a mature SpringMVC scheme, the Java language is adopted for development in terms of language, development efficiency and operation efficiency are both considered, security check is carried out through multiple stages of Filters, communication with a persistent layer is carried out through JDBC connection, and the whole middle-stage processing logic is deployed into a Servlet container; the background data is persistently stored in a MySQL database and communicates with the middle stage through network connection, data migration backup is facilitated, large objects, namely report files and pictures, are mainly stored in a special object storage area, and centralized management is facilitated.

Motivational and Goal-Oriented Viewpoint for Architectural Modeling of Software Intensive Systems

Abstract: The paper deals with the use of the design thinking approach in creating the architectural views considering the motivational excitement and goal setting in designing the software intensive systems (SIS). In this case, any architectural view is formed in work with the system of conceptual equations, solving of which is based on the designer’s reasoning of the abductive type. In conditions of automated design thinking, such reasoning helps to define constructive relations binding motives, goals, and requirements integrated into the corresponding view. For all views included in the architectural description, these relations are useful to combine, visualize, and interpret as motivationally targeted view demonstrated which architectural decisions correspond to the intended goals.

Method for rapidly realizing the application layer layout of a mobile terminal, and framework

Abstract: The invention provides a method for rapidly realizing the application layer layout of a mobile terminal and a framework. The method comprises the following steps: at least two function modules are created; each function module comprises a model Model, a view View, a coordinator Coordinator and a view model ViewModel. Corresponding to a specific function, adding a corresponding view event responseand view logic in a coordinator of a function module, and binding a view View and a view model ViewModel; According to the specific functions of the page requirements, the corresponding functional modules are assembled into the controller Controller of the page. The invention has the advantages of clear code logic, easy maintenance, easy operation, high reusability and testability, unified frameuse standard, beautiful appearance and the like.