Generating reusable, searchable and executable “architecture constraints as services”

Tibermacine

Information and Software Technology

et al. 2018

Self Cite

Context: Architecture constraints are specifications of conditions to which an architecture model must adhere in order to satisfy an architecture decision imposed by a given design principle. These constraints can be specified with predicate languages like OCL at design time and checked on design artifacts. Objective: Many works in the literature studied the importance of checking these constraints to guarantee quality on design models, and to prevent technical debt and maintenance difficulties. In this paper, we propose a process whose ultimate goal is to enable the checking of these constraints in the implementation stage. Method: The proposed process takes as input a textual specification of an architecture constraint specified at design stage. It translates this specification into meta-programs and then it uses them with aspect-oriented programming to check constraints at the implementation stage and at run-time on objectoriented programs. Results: We experimented an implementation of this process on a set of 12 architecture constraints. The results of this experimentation showed that our process is able to statically and dynamically detect architecture constraint violations on toy object-oriented applications, but also on real-world ones. Conclusion: The automatic checking of architecture constraints is important

Section: Discussionmentioning

confidence: 99%

Specification and automatic checking of architecture constraints on object oriented programs

Tibermacine

Information and Software Technology

et al. 2018

Self Cite

“…The version currently used is just focused on those manually made. The development of automatic mechanisms between these layers that can be reused [43] requires a software‐intensive development approach which is out of the scope of this paper. The drawings in Fig.…”

Section: Architecture and Solutionmentioning

confidence: 99%

Assessing source code vulnerabilities in a cloud‐based system for health systems: OpenNCP

2019

Healthcare systems have been improved in order to provide support to cross-border situations where one citizen from one country travels to another country and requires the use of their health records. Several initiatives have been carried out to tackle this problem. This is the case for the OpenNCP which is supported by the European Commission by providing a common network and an infrastructure to connect different national healthcare systems which most of the times are cloud-based systems. The OpenNCP plays a key role in communicating health records among European Union's member states, and therefore it manages sensitive information. Therefore, this study provides a security analysis of this platform and a prototype is developed for identifying secure patterns in source code.

Computer Languages, Systems & Structures

“…Alternatively, other process modelling techniques use so-called contextual data that add properties (tagged values) of a model element to model languages [35]. Moreover, some models integrate available data before process execution, like the definition in advance of specific services matching constraints and run upon request [36]. Alternatives using MDA have been developed to adapt system architectures to a mobile network [37] and a ubiquitous system [38].…”

Section: Contextual Model and Model-driven Engineeringmentioning

confidence: 99%

Automatized integration of a contextual model into a process with data variability

Simonin

Puentes

2018

Existent process models can hardly cope with the emerging issue of modelling exponential variable data volumes in systems' workflow, from specifications to operation. Given the strong relation between data context and data variability, this paper considers the automated integration of contextual models for processes with data variability. The proposed approach extends methodologically a platform independent model process, using a contextual data model, to obtain automatically the corresponding platform specific model. Contextual data are thus integrated to a process as a model, within a process. Two particular cases of contextual data models are studied in detail: substitution, when the contextual data model defines generated code, and enhancement, when learned data descriptions constitute the contextual data model. The feasibility and value of integrating a contextual model into a process to handle data variability are shown in detail describing these two use cases. Contextual model integration by substitution to include automatically variable ready to use application services to generate code, and contextual model integration by enhancement applied to supervised image classification based on variable descriptors. Results show that relating data variability and its context by means of automated integration of a designed system component model, simplifies variable data processing of system process models.