The Experts below are selected from a list of 626187 Experts worldwide ranked by ideXlab platform
Jon Whittle - One of the best experts on this subject based on the ideXlab platform.
-
model driven Engineering for multi tenant saas application development
European Conference on Computer Systems, 2016Co-Authors: Assylbek Jumagaliyev, Jon WhittleAbstract:Cloud computing allows development of multi-tenant applications by sharing computing and storage resources. Cloud computing and model driven Engineering (MDE) approaches can be mutually beneficial. With MDE, developers can focus on designing the structure, functionality and behaviour of software systems without considering specific implementation and platform details. In this poster paper, we examine opportunities of exploiting MDE by analysing variability challenges during a multi-tenant application development.
-
model driven Engineering practices in industry
Science of Computer Programming, 2014Co-Authors: J Hutchinson, Jon Whittle, Mark RouncefieldAbstract:In this article, we attempt to address the relative absence of empirical studies of model driven Engineering (MDE) in two different but complementary ways. First, we present an analysis of a large online survey of MDE deployment and experience that provides some rough quantitative measures of MDE practices in industry. Second, we supplement these figures with qualitative data obtained from some semi-structured, in-depth interviews with MDE practitioners, and, in particular, through describing the practices of four commercial organizations as they adopted a model driven Engineering approach to their software development practices. Using in-depth semi-structured interviewing, we invited practitioners to reflect on their experiences and selected four to use as exemplars or case studies. In documenting some details of their attempts to deploy model driven practices, we identify a number of factors, in particular the importance of complex organizational, managerial and social factors-as opposed to simple technical factors-that appear to influence the relative success, or failure, of the endeavor. Three of the case study companies describe genuine success in their use of model driven development, but explain that as examples of organizational change management, the successful deployment of model driven Engineering appears to require: a progressive and iterative approach; transparent organizational commitment and motivation; integration with existing organizational processes and a clear business focus. We present extensive results from a survey of MDE practices in industry.We present case studies of the adoption of model driven Engineering (MDE) by four companies.We identify important factors that can affect the success or failure of MDE use from both the survey and case studies.MDE provides genuine benefits to those companies who use its appropriate contexts.Success/failure appears to be more dependent on organizational factors than technical.
-
the state of practice in model driven Engineering
IEEE Software, 2014Co-Authors: Jon Whittle, J Hutchinson, Mark RouncefieldAbstract:Despite lively debate over the past decade on the benefits and drawbacks of Model-Driven Engineering (MDE), there have been few industry-wide studies of MDE in practice. A new study that surveyed 450 MDE practitioners and performed in-depth interviews with 22 more suggests that although MDE might be more widespread than commonly believed, developers rarely use it to generate whole systems. Rather, they apply MDE to develop key parts of a system.
-
industrial adoption of model driven Engineering are the tools really the problem
Model Driven Engineering Languages and Systems, 2013Co-Authors: Jon Whittle, J Hutchinson, Mark Rouncefield, Hakan Burden, Rogardt HeldalAbstract:An oft-cited reason for lack of adoption of Model-Driven Engineering MDE is poor tool support. However, studies have shown that adoption problems are as much to do with social and organizational factors as with tooling issues. This paper discusses the impact of tools on MDE adoption and places tooling within a broader organizational context. The paper revisits previous data on MDE adoption 19 in-depth interviews with MDE practitioners and re-analyzes the data through the specific lens of MDE tools. In addition, the paper presents new data 20 new interviews in two specific companies and analyzes it through the same lens. The key contribution of the paper is a taxonomy of tool-related considerations, based on industry data, which can be used to reflect on the tooling landscape as well as inform future research on MDE tools.
-
industrial adoption of model driven Engineering are the tools really the problem
Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics), 2013Co-Authors: Jon Whittle, J Hutchinson, Mark Rouncefield, Hakan Burden, Rogardt HeldalAbstract:An oft-cited reason for lack of adoption of Model-Driven Engineering (MDE) is poor tool support. However, studies have shown that adoption problems are as much to do with social and organizational factors as with tooling issues. This paper discusses the impact of tools on MDE adoption and places tooling within a broader organizational context. The paper revisits previous data on MDE adoption (19 in-depth interviews with MDE practitioners) and re-analyzes the data through the specific lens of MDE tools. In addition, the paper presents new data (20 new interviews in two specific companies) and analyzes it through the same lens. The key contribution of the paper is a taxonomy of tool-related considerations, based on industry data, which can be used to reflect on the tooling landscape as well as inform future research on MDE tools. © 2013 Springer-Verlag.
Santiago Meliá - One of the best experts on this subject based on the ideXlab platform.
-
Empirical study on the maintainability of Web applications: Model-Driven Engineering vs Code-centric
Empirical Software Engineering, 2014Co-Authors: Yulkeidi Martínez, Cristina Cachero, Santiago MeliáAbstract:Model-Driven Engineering (MDE) approaches are often acknowledged to improve the maintainability of the resulting applications. However, there is a scarcity of empirical evidence that backs their claimed benefits and limitations with respect to code-centric approaches. The purpose of this paper is to compare the performance and satisfaction of junior software maintainers while executing maintainability tasks on Web applications with two different development approaches, one being OOH4RIA, a Model-Driven approach, and the other being a code-centric approach based on Visual Studio .NET and the Agile Unified Process. We have conducted a quasi-experiment with 27 graduated students from the University of Alicante. They were randomly divided into two groups, and each group was assigned to a different Web application on which they performed a set of maintainability tasks. The results show that maintaining Web applications with OOH4RIA clearly improves the performance of subjects. It also tips the satisfaction balance in favor of OOH4RIA, although not significantly. Model-Driven development methods seem to improve both the developers’ objective performance and subjective opinions on ease of use of the method. This notwithstanding, further experimentation is needed to be able to generalize the results to different populations, methods, languages and tools, different domains and different application sizes.
-
applying model driven Engineering to the development of rich internet applications for business intelligence
Information Systems Frontiers, 2013Co-Authors: Jesús M. Hermida, Santiago Meliá, Andrés Montoyo, Jaime GomezAbstract:Business Intelligence (BI) applications have been gradually ported to the Web in search of a global platform for the consumption and publication of data and services. On the Internet, apart from techniques for data/knowledge management, BI Web applications need interfaces with a high level of interoperability (similar to the traditional desktop interfaces) for the visualisation of data/knowledge. In some cases, this has been provided by Rich Internet Applications (RIA). The development of these BI RIAs is a process traditionally performed manually and, given the complexity of the final application, it is a process which might be prone to errors. The application of Model-Driven Engineering techniques can reduce the cost of development and maintenance (in terms of time and resources) of these applications, as they demonstrated by other types of Web applications. In the light of these issues, the paper introduces the Sm4RIA-B methodology, i.e., a Model-Driven methodology for the development of RIA as BI Web applications. In order to overcome the limitations of RIA regarding knowledge management from the Web, this paper also presents a new RIA platform for BI, called [email protected], which extends the functionalities of traditional RIAs by means of Semantic Web technologies and B2B techniques. Finally, we evaluate the whole approach on a case study--the development of a social network site for an enterprise project manager.
-
the websa approach applying model driven Engineering to web applications
Journal of Web Engineering, 2006Co-Authors: Santiago Meliá, Jaime GomezAbstract:The Web Engineering research community has proposed several Web design methods that have proven successful in the specification of the functional aspects (such as domain, navigation and presentation) posed by Web applications. However, the architectural aspects are often ignored in the design and the Web application is not specified enough. This development process produces a gap between the Web design models and the final implementation. To overcome this limitation, we extend the different Web methodologies with a generic approach called WebSA. WebSA is based on the Model Driven Engineering (MDE) paradigm that promotes models as the primary artifacts needed to carry out a software project from beginning to end. To do this, WebSA proposes a Model Driven Development made up of a set of UML architectural models and QVT model transformations as a mechanism for (1) integrating the functional aspects of the current Web methodologies with the architectural models as well as for (2) defining a set of transformations from the architectural models to platform-specific models such as J2EE, .NET, etc. To illustrate our approach, in this paper we combine WebSA with the OO-H method, to tackle the design of a running example such as the Travel Agency system.
Jeanmarie Favre - One of the best experts on this subject based on the ideXlab platform.
-
a model driven Engineering approach for the usability of plastic user interfaces
Engineering Interactive Systems, 2008Co-Authors: Jeansebastien Sottet, Gaelle Calvary, Joelle Coutaz, Jeanmarie FavreAbstract:Plastic User Interfaces (UI) are able to adapt to their context of use while preserving usability. Research efforts have focused so far, on the functional aspect of UI adaptation, while neglecting the usability dimension. This paper investigates how the notion of mapping as promoted by Model Driven Engineering (MDE), can be exploited to control UI adaptation according to explicit usability criteria. In our approach, a run-time UI is a graph of models related by mappings. Each model (e.g., the task model, the Abstract UI, the Concrete UI, and the final UI) describes the UI from a specific perspective from high-level design decisions (conveyed by the task model) to low-level executable code (i.e. the final UI). A mapping between source and target models specifies the usability properties that are preserved when transforming source models into target models. This article presents a meta-model for the notion of mapping and shows how it is applied to plastic UIs.
-
towards model driven Engineering of plastic user interfaces
Lecture Notes in Computer Science, 2006Co-Authors: Jeansebastien Sottet, Gaelle Calvary, Jeanmarie Favre, Joelle Coutaz, Alexandre Demeure, Lionel BalmeAbstract:Ubiquitous computing has introduced the need for interactive systems to run on multiple platforms in different physical environments. Providing a user interface specially crafted for each context of use ( ) is costly, may result in inconsistent behaviors [5] and above all is limited to the contexts of use that have been envisioned at design time. Opportunistic interaction in a changing environment requires enabling approaches and techniques for gracefully adapting the interactive system to its context of use. In Human-Computer Interaction, this ability of an interactive system to withstand variations of context of use while preserving its quality in use is called plasticity [7]. This paper shows how Model Driven Engineering is suited for supporting plasticity both at design time and run time.
-
towards a basic theory to model model driven Engineering
2004Co-Authors: Jeanmarie Favre, Adele TeamAbstract:What is a model? What is a metamodel? What is a language? What is a transformation? How are these concepts related? It is striking to see that, though MDE is supposed to be about precise modelling, MDE core concepts are usually described in natural language or at best, using sketchy UML diagrams. When precise descriptions are provided, it is only to describe a specific technology. But Model Driven Engineering is about supporting multiple Technological Spaces (TS). The concepts of model, metamodel, and transformation must be understood, not only in the context of the MDA TS, but also in the Grammarware TS, the Documentware TS, the Dataware TS, etc. This paper shows how the set theory and language theory could help in understanding essential MDE concepts. A first version of a very rudimentary theory for reasoning about MDE concepts is provided in the form of a megamodel.
Muhammad Uzair Khan - One of the best experts on this subject based on the ideXlab platform.
-
a product line model driven Engineering approach for generating feature based mobile applications
Journal of Systems and Software, 2017Co-Authors: Muhammad Usman, Muhammad Zohaib Iqbal, Muhammad Uzair KhanAbstract:Abstract A significant challenge faced by the mobile application industry is developing and maintaining multiple native variants of mobile applications to support different mobile operating systems, devices and varying application functional requirements. The current industrial practice is to develop and maintain these variants separately. Any potential change has to be applied across variants manually, which is neither efficient nor scalable. We consider the problem of supporting multiple platforms as a ‘software product-line Engineering’ problem. The paper proposes a novel application of product-line Model-Driven Engineering to mobile application development and addresses the key challenges of feature-based native mobile application variants for multiple platforms. Specifically, we deal with three types of variations in mobile applications: variation due to operation systems and their versions, software and hardware capabilities of mobile devices, and functionalities offered by the mobile application. We develop a tool MOPPET that automates the proposed approach. Finally, the results of applying the approach on two industrial case studies show that the proposed approach is applicable to industrial mobile applications and have potential to significantly reduce the development effort and time.
Jeansebastien Sottet - One of the best experts on this subject based on the ideXlab platform.
-
a model driven Engineering approach for the usability of plastic user interfaces
Engineering Interactive Systems, 2008Co-Authors: Jeansebastien Sottet, Gaelle Calvary, Joelle Coutaz, Jeanmarie FavreAbstract:Plastic User Interfaces (UI) are able to adapt to their context of use while preserving usability. Research efforts have focused so far, on the functional aspect of UI adaptation, while neglecting the usability dimension. This paper investigates how the notion of mapping as promoted by Model Driven Engineering (MDE), can be exploited to control UI adaptation according to explicit usability criteria. In our approach, a run-time UI is a graph of models related by mappings. Each model (e.g., the task model, the Abstract UI, the Concrete UI, and the final UI) describes the UI from a specific perspective from high-level design decisions (conveyed by the task model) to low-level executable code (i.e. the final UI). A mapping between source and target models specifies the usability properties that are preserved when transforming source models into target models. This article presents a meta-model for the notion of mapping and shows how it is applied to plastic UIs.
-
towards model driven Engineering of plastic user interfaces
Lecture Notes in Computer Science, 2006Co-Authors: Jeansebastien Sottet, Gaelle Calvary, Jeanmarie Favre, Joelle Coutaz, Alexandre Demeure, Lionel BalmeAbstract:Ubiquitous computing has introduced the need for interactive systems to run on multiple platforms in different physical environments. Providing a user interface specially crafted for each context of use ( ) is costly, may result in inconsistent behaviors [5] and above all is limited to the contexts of use that have been envisioned at design time. Opportunistic interaction in a changing environment requires enabling approaches and techniques for gracefully adapting the interactive system to its context of use. In Human-Computer Interaction, this ability of an interactive system to withstand variations of context of use while preserving its quality in use is called plasticity [7]. This paper shows how Model Driven Engineering is suited for supporting plasticity both at design time and run time.
