Vincent Englebert - Academia.edu (original) (raw)
Papers by Vincent Englebert
Proceedings of the Fourth Working Conference on Reverse Engineering
This paper presents a generic methodology for database reverse engineering comprising two main st... more This paper presents a generic methodology for database reverse engineering comprising two main steps, namely Data structure extraction and Data structure conceptualization. The first process tries to elicit the physical data structures of the database, while the second one tries to recover the semantics of these structures. This methodology is illustrated by a small, but non-trivial, example through which a set of COBOL files is transformed into a relational database.
Encyclopedia of Database Systems, 2009
Among the known methods of data mining are neural networks, ILP, associative rules, Bayes network... more Among the known methods of data mining are neural networks, ILP, associative rules, Bayes networks, clustering, decision trees and others. This thesis is about decision trees, their implementation, visualization, extraction rules and the comparison of different decision trees and models of classification data in general. An integral part of the data mining process is preprocessing of data, which plays an important role and is also discussed in this thesis. Part of this thesis also concerns the comparison of different decision tree models such as CART, CHAID, C5.0 (See5) and others on a set of 3 data kinds. Finally, this model's results are compared to its results when data preprocessed by PCA analysis is used
The amount of available connectible devices and Internet of Things (IoT) solutions is increasing ... more The amount of available connectible devices and Internet of Things (IoT) solutions is increasing as such equipments are becoming popular and widely available on the market. This growth in popularity goes together with a keen interest for smart homes where individuals deploy ad hoc solutions in their houses. However, the task to translate the users’ needs into a concrete IoT infrastructure is not straightforward and often require to deal with proprietary APIs, complex interconnection protocols, and various technical details, so that the link to user requirements may be lost, hampering the validity of their interaction properties. In order to define and manipulate devices deployed in domestic environments, we propose IoTDSL, a Domain-Specific Language relying on a high-level rule-based language. Users in charge of the deployment of IoT infrastructures are able to describe and combine in a declarative manner structural configurations as well as event-based semantics for devices. Modell...
2015 3rd International Conference on Model-Driven Engineering and Software Development (MODELSWARD), 2015
Software architecture design is a critical task as lots of requirements can be taken into account... more Software architecture design is a critical task as lots of requirements can be taken into account on which many decisions can be made. The maintenance and evolution of resulting models often become tricky, even impracticable when their rationale is lost. In a previous work, we introduced a set of languages used in a transformation-centric design method meant to tackle this scattering of requirements and to facilitate further model evolutions. But, we did not provided a formal validation of our proposal yet. The present work depicts a comparative case study we conducted on a group of students. The participants were asked to develop an online book store in two phases, the second one simulating an evolution of the system. We evaluated the functional completeness of the created software as well as the traceability of design decisions and rationale. The participants were also asked to criticize the design method and language they used in a textual report and through a questionnaire. Even...
and it is a condition of accessing publications that users recognise and abide by the legal requi... more and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. • Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal ? Take down policy If you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim.
2014 2nd International Conference on Model-Driven Engineering and Software Development (MODELSWARD), 2014
Stakeholders have to face requirements in increasing number and complexity. Their translations to... more Stakeholders have to face requirements in increasing number and complexity. Their translations to system functionalities are often diluted into the overall architecture so that it becomes tricky to undertake future changes. Since information systems are intended to evolve in terms of functionalities and underlying technologies, the link between requirements and design artifacts is primordial. Agile design methods and documentation techniques have emerged in the past years in order to deal with the amount of requirements and to trace the decision process and the rationale sustaining a software model. Also, it is not unusual that numerous technologies with similar purpose are confronted to each other during the design phase. In the present work, we propose an integrated framework combining system requirement definitions, a component-based modeling language and model transformations. Architecturally-significant requirements are explicitly linked to software architecture elements and it...
Proceedings of the 5th International Conference on Model-Driven Engineering and Software Development, 2017
Hidden behind the Internet of Things (IoT), many actors are activelly filling the market with dev... more Hidden behind the Internet of Things (IoT), many actors are activelly filling the market with devices and services. From this profusion of actors, a large amount of technologies and APIs, sometimes proprietary, are available, making difficult the interoperability and configuration of systems for IoT technicians. In order to define and manipulate devices deployed in domestic environments, we propose IoTDSL, a Domain-Specific Language meant to specify, assemble and describe the behaviour of interconnected devices. Relying on a high-level rule-based language, users in charge of the deployment of IoT infrastructures are able to describe and combine in a declarative manner structural configurations as well as event-based semantics for devices. This way, language users are freed from technical aspects, playing with high-level representations of devices, while the complexity of the concrete implementation is handled in a dedicated layer where high-level rules are mapped to vendor's API.
Lecture Notes in Computer Science, 2016
Ambient Assisted Living has been widely perceived as a viable solution to mitigate the astronomic... more Ambient Assisted Living has been widely perceived as a viable solution to mitigate the astronomical increase in the cost of health care. In the context of our Geras Project, we propose a Model-Driven Engineering framework for handling high-level specifications that capture the concerns of elderly people still living at home. These concerns are related to concrete living issues, like being notified of a ringing phone for a deaf people, or receiving adequate assistance after a fall. The framework explicitly models three aspects: agent's goals, formally capturing users' concerns; abstract solutions, defining a canvas for answering the goal; and concrete solutions in terms of APIs or various combination of APIs, for their operationalisation. We illustrate the usage of our framework on two simple scenarios.
Proceedings of the 4th International Conference on Model-Driven Engineering and Software Development, 2016
Software architectures are often abstracted as a combination of reusable components connected to ... more Software architectures are often abstracted as a combination of reusable components connected to each other by various means. Specifications of components' semantics have been widely studied and many modeling languages have been proposed from coarse-grained loosely-defined elements to operational objects with behavioral semantics that may be generated and executed in a dedicated framework. All these modeling facilities have proven their advantages in many domains through either case studies or real-world applications. However, most of those approaches either consider a subset of composition facilities, i.e. the available types of bindings between components, or do not even consider communication properties at all, staying at behavioral-related compatibility between components. Verifications of communication-related properties are then postponed to the hand of software developers and finally considered at deployment-time only. Part of a general architecture framework, we propose an abstraction formalism to specify communication paths between components. This modeling facility relies on a taxonomy of types of links and the specifications of communication protocols. This protocol serves as a reification element between abstract component compositions, architecture instances and deployment infrastructure, making explicit communication-related constraints and properties.
Encyclopedia of Database Systems, 2009
Encyclopedia of Database Systems, 2009
Encyclopedia of Database Systems, 2009
Encyclopedia of Database Systems, 2009
Encyclopedia of Database Systems, 2009
Encyclopedia of Database Systems, 2009
Communications in Computer and Information Science, 2015
The maintenance and evolution of software architecture models may become tricky when design ratio... more The maintenance and evolution of software architecture models may become tricky when design rationale is lost over time. Lots of requirements and decisions must be taken into account when dealing with software architecture, such that proper traceability mechanisms should be used all over the system life-cycle. In a previous work, we specified an architectural framework based on domain specific languages meant to address this traceability problem. We now relate a comparative case study we conducted over a simulated project where participants had to develop an online book store in two phases, the second phase imitating a system evolution. We evaluated the functional completeness of the software they built as well as the traceability of design decisions and rationale. The participants were also asked to criticize the design method and language they used in a feedback report and through a questionnaire. Even if the size of the case study is rather limited, it clearly highlights the advantages of our approach regarding, among others, its expressiveness and decisions traceability (The present paper is a revised version of SA design by stepwise transformations [8]).
Communications in Computer and Information Science, 2015
Stakeholders have to face requirements in increasing number and complexity, and the link between ... more Stakeholders have to face requirements in increasing number and complexity, and the link between these requirements and design artifacts is primordial. Agile design methods and documentation techniques have emerged in the past years in order to trace the decision process and the rationale sustaining a software model. The present work proposes an integrated framework combining system requirement definitions, component-based models and model transformations. Architecturally significant requirements are explicitly linked to software architecture elements and iteratively refined or implemented by model transformations. Any transformation must be documented, even briefly, and the framework retains the transformations tree. This way, the iterative decision and design processes are completely documented for future reference or modification, i.e., designers can (i) see the mapping between a system requirement and its implementation in the architecture model, (ii) explore design alternatives or apply structural modifications without losing previous versions of the model, and finally (iii) at least understand partially the reasons why the model is how it is.
Encyclopedia of Database Systems, 2009
Proceedings of the Fourth Working Conference on Reverse Engineering
This paper presents a generic methodology for database reverse engineering comprising two main st... more This paper presents a generic methodology for database reverse engineering comprising two main steps, namely Data structure extraction and Data structure conceptualization. The first process tries to elicit the physical data structures of the database, while the second one tries to recover the semantics of these structures. This methodology is illustrated by a small, but non-trivial, example through which a set of COBOL files is transformed into a relational database.
Encyclopedia of Database Systems, 2009
Among the known methods of data mining are neural networks, ILP, associative rules, Bayes network... more Among the known methods of data mining are neural networks, ILP, associative rules, Bayes networks, clustering, decision trees and others. This thesis is about decision trees, their implementation, visualization, extraction rules and the comparison of different decision trees and models of classification data in general. An integral part of the data mining process is preprocessing of data, which plays an important role and is also discussed in this thesis. Part of this thesis also concerns the comparison of different decision tree models such as CART, CHAID, C5.0 (See5) and others on a set of 3 data kinds. Finally, this model's results are compared to its results when data preprocessed by PCA analysis is used
The amount of available connectible devices and Internet of Things (IoT) solutions is increasing ... more The amount of available connectible devices and Internet of Things (IoT) solutions is increasing as such equipments are becoming popular and widely available on the market. This growth in popularity goes together with a keen interest for smart homes where individuals deploy ad hoc solutions in their houses. However, the task to translate the users’ needs into a concrete IoT infrastructure is not straightforward and often require to deal with proprietary APIs, complex interconnection protocols, and various technical details, so that the link to user requirements may be lost, hampering the validity of their interaction properties. In order to define and manipulate devices deployed in domestic environments, we propose IoTDSL, a Domain-Specific Language relying on a high-level rule-based language. Users in charge of the deployment of IoT infrastructures are able to describe and combine in a declarative manner structural configurations as well as event-based semantics for devices. Modell...
2015 3rd International Conference on Model-Driven Engineering and Software Development (MODELSWARD), 2015
Software architecture design is a critical task as lots of requirements can be taken into account... more Software architecture design is a critical task as lots of requirements can be taken into account on which many decisions can be made. The maintenance and evolution of resulting models often become tricky, even impracticable when their rationale is lost. In a previous work, we introduced a set of languages used in a transformation-centric design method meant to tackle this scattering of requirements and to facilitate further model evolutions. But, we did not provided a formal validation of our proposal yet. The present work depicts a comparative case study we conducted on a group of students. The participants were asked to develop an online book store in two phases, the second one simulating an evolution of the system. We evaluated the functional completeness of the created software as well as the traceability of design decisions and rationale. The participants were also asked to criticize the design method and language they used in a textual report and through a questionnaire. Even...
and it is a condition of accessing publications that users recognise and abide by the legal requi... more and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. • Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal ? Take down policy If you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim.
2014 2nd International Conference on Model-Driven Engineering and Software Development (MODELSWARD), 2014
Stakeholders have to face requirements in increasing number and complexity. Their translations to... more Stakeholders have to face requirements in increasing number and complexity. Their translations to system functionalities are often diluted into the overall architecture so that it becomes tricky to undertake future changes. Since information systems are intended to evolve in terms of functionalities and underlying technologies, the link between requirements and design artifacts is primordial. Agile design methods and documentation techniques have emerged in the past years in order to deal with the amount of requirements and to trace the decision process and the rationale sustaining a software model. Also, it is not unusual that numerous technologies with similar purpose are confronted to each other during the design phase. In the present work, we propose an integrated framework combining system requirement definitions, a component-based modeling language and model transformations. Architecturally-significant requirements are explicitly linked to software architecture elements and it...
Proceedings of the 5th International Conference on Model-Driven Engineering and Software Development, 2017
Hidden behind the Internet of Things (IoT), many actors are activelly filling the market with dev... more Hidden behind the Internet of Things (IoT), many actors are activelly filling the market with devices and services. From this profusion of actors, a large amount of technologies and APIs, sometimes proprietary, are available, making difficult the interoperability and configuration of systems for IoT technicians. In order to define and manipulate devices deployed in domestic environments, we propose IoTDSL, a Domain-Specific Language meant to specify, assemble and describe the behaviour of interconnected devices. Relying on a high-level rule-based language, users in charge of the deployment of IoT infrastructures are able to describe and combine in a declarative manner structural configurations as well as event-based semantics for devices. This way, language users are freed from technical aspects, playing with high-level representations of devices, while the complexity of the concrete implementation is handled in a dedicated layer where high-level rules are mapped to vendor's API.
Lecture Notes in Computer Science, 2016
Ambient Assisted Living has been widely perceived as a viable solution to mitigate the astronomic... more Ambient Assisted Living has been widely perceived as a viable solution to mitigate the astronomical increase in the cost of health care. In the context of our Geras Project, we propose a Model-Driven Engineering framework for handling high-level specifications that capture the concerns of elderly people still living at home. These concerns are related to concrete living issues, like being notified of a ringing phone for a deaf people, or receiving adequate assistance after a fall. The framework explicitly models three aspects: agent's goals, formally capturing users' concerns; abstract solutions, defining a canvas for answering the goal; and concrete solutions in terms of APIs or various combination of APIs, for their operationalisation. We illustrate the usage of our framework on two simple scenarios.
Proceedings of the 4th International Conference on Model-Driven Engineering and Software Development, 2016
Software architectures are often abstracted as a combination of reusable components connected to ... more Software architectures are often abstracted as a combination of reusable components connected to each other by various means. Specifications of components' semantics have been widely studied and many modeling languages have been proposed from coarse-grained loosely-defined elements to operational objects with behavioral semantics that may be generated and executed in a dedicated framework. All these modeling facilities have proven their advantages in many domains through either case studies or real-world applications. However, most of those approaches either consider a subset of composition facilities, i.e. the available types of bindings between components, or do not even consider communication properties at all, staying at behavioral-related compatibility between components. Verifications of communication-related properties are then postponed to the hand of software developers and finally considered at deployment-time only. Part of a general architecture framework, we propose an abstraction formalism to specify communication paths between components. This modeling facility relies on a taxonomy of types of links and the specifications of communication protocols. This protocol serves as a reification element between abstract component compositions, architecture instances and deployment infrastructure, making explicit communication-related constraints and properties.
Encyclopedia of Database Systems, 2009
Encyclopedia of Database Systems, 2009
Encyclopedia of Database Systems, 2009
Encyclopedia of Database Systems, 2009
Encyclopedia of Database Systems, 2009
Encyclopedia of Database Systems, 2009
Communications in Computer and Information Science, 2015
The maintenance and evolution of software architecture models may become tricky when design ratio... more The maintenance and evolution of software architecture models may become tricky when design rationale is lost over time. Lots of requirements and decisions must be taken into account when dealing with software architecture, such that proper traceability mechanisms should be used all over the system life-cycle. In a previous work, we specified an architectural framework based on domain specific languages meant to address this traceability problem. We now relate a comparative case study we conducted over a simulated project where participants had to develop an online book store in two phases, the second phase imitating a system evolution. We evaluated the functional completeness of the software they built as well as the traceability of design decisions and rationale. The participants were also asked to criticize the design method and language they used in a feedback report and through a questionnaire. Even if the size of the case study is rather limited, it clearly highlights the advantages of our approach regarding, among others, its expressiveness and decisions traceability (The present paper is a revised version of SA design by stepwise transformations [8]).
Communications in Computer and Information Science, 2015
Stakeholders have to face requirements in increasing number and complexity, and the link between ... more Stakeholders have to face requirements in increasing number and complexity, and the link between these requirements and design artifacts is primordial. Agile design methods and documentation techniques have emerged in the past years in order to trace the decision process and the rationale sustaining a software model. The present work proposes an integrated framework combining system requirement definitions, component-based models and model transformations. Architecturally significant requirements are explicitly linked to software architecture elements and iteratively refined or implemented by model transformations. Any transformation must be documented, even briefly, and the framework retains the transformations tree. This way, the iterative decision and design processes are completely documented for future reference or modification, i.e., designers can (i) see the mapping between a system requirement and its implementation in the architecture model, (ii) explore design alternatives or apply structural modifications without losing previous versions of the model, and finally (iii) at least understand partially the reasons why the model is how it is.
Encyclopedia of Database Systems, 2009