Results 211 to 220 of about 952,227 (243)

Model Driven Development

Informatik-Spektrum, 2008
The model-driven architecture (MDA) paradigm is well-known and widely used in the field of model-based software development. However, there are still some issues that are problematic and that need to be dealt with carefully. In this paper we present a metaphor that explains how MDA grows in complexity as problems faced become more difficult or “wicked”,
Shashi Shekhar, Hui Xiong
openaire   +2 more sources

Model driven development

Companion of the 18th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications - OOPSLA '03, 2003
In this paper, we offer an alternative vision for domain driven development (3D). Our approach is model driven and emphasizes the use of generic and specific domain oriented programming (DOP) languages. DOP uses strong specific languages, which directly incorporate domain abstractions, to allow knowledgeable end users to succinctly express their needs ...
Dave Thomas, Brian M. Barry
openaire   +1 more source

Model-driven Web services development

IEEE International Conference on e-Technology, e-Commerce and e-Service, 2004. EEE '04. 2004, 2004
Web service technologies are becoming increasingly important for integrating systems and services. There is much activity and interest around standardization and usage of Web service technologies. Contemporary Web services are described in the Web Service Description Language (WSDL).
Roy Gronmo   +3 more
openaire   +1 more source

Model Driven Development - Attention to People and Processes

Parallel and Distributed Computing and Networks / 720: Software Engineering, 2011
Model Driven Development (MDD) can potentially offer great benefits to software development companies, for example, in the sense of improved productivity. However, MDD still suffers from challenges that complicate its wider use in companies. This paper presents a study in which several challenges to MDD use were identified, based on a number of ...
Teppola, Susanna, Parviainen, Päivi
openaire   +2 more sources

Model-driven systems development

IBM Systems Journal, 2006
Traditional systems development methods are designed to create a "point solution"- that is, a solution for a specific and static set of requirements. These methods result in systems that are sluggish in their response to dynamic conditions and changing requirements, expensive to maintain over extended periods of time, and prone to system failure. As an
L. Balmelli   +3 more
openaire   +1 more source

Model Driven, Component-Based Development

2003
As complex behavioral abstractions, business components in many ways can be viewed as (sub)systems in their own right, and thus need to be treated as such. In particular, techniques are needed that enable the properties, requirements and architectures of business components to be modeled in the early analysis and design phases of software development ...
Atkinson, Colin, Groß, Hans-Gerhard
openaire   +2 more sources

Home - About - Disclaimer - Privacy