Abstract not found

A domain-specific language (DSL), whether used for model-driven development or programming, is a piece of critical infrastructure that is developed during the system engineering process. As such, a DSL has its own lifecycle, which in turn may encapsulate the lifecycles of many other system development projects. Understanding the requirements for DSLs in general, and in specific project contexts, is critical in order to improve DSL quality and ensure a direct correspondence between the requirements for system engineering projects and the functionality provided by the language. The quality attributes of a DSL – and its supporting environment (e.g., virtual machines, debuggers, integrated environments) – will have an impact on the quality attributes of the overall systems development process, and the resulting products. We present a partial requirements analysis for DSLs in general, focusing on relevant stakeholders, the system boundary (i.e., where DSLs end and general purpose languages start), and a core set of requirements that are relevant for any DSL. We then discuss open questions, particularly focusing on requirements refinement,

Abstract. The paper presents a questionnaire to assess Domain Specific Languages based on a multi-dimensional framework for characterizing languages. An issue is whether and how to distinguish between characteristics of domain-specific and general purpose languages. We discuss how to emphasize dimensions that are particularly important for domain-specific languages such as being formal, yet transparent as well as integrable with other languages. We consider hazards and potentials of the approach.

Abstract. Quality is often defined as fitness for purpose which is the key property to determine when evaluating quality. This paper presents some general requirements for evaluating quality frameworks. It also discusses characteristics of MDE that are important when building a quality framework, such as its use of models in several stages of development and maintenance, and its multi-abstraction level approach that requires consistency and traceability. MDE should strive for engineering of quality into software. As a step in extending quality frameworks for this purpose, we discuss integrating quality evaluation with quality engineering using MDE approaches. Applying it on transformations, we discuss both the transformability of models and the quality of transformations themselves. While completeness and precision of models are quality criteria for transformability of them, transformations should monitor and preserve model quality, be reusable, simple and efficient. We further discuss quality means and evaluation methods and propose future work. Keywords: Model-driven engineering, quality, transformation, metrics 1

Abstract: Approaching technology-enhanced learning from the perspective of a learner, we foster the idea of learning environment design, learner interactions, and tool interoperability. In this paper, we shortly summarize the motivation for our personal learning environment approach and describe the development of a domain-specific language for this purpose as well as its realization in practice. Consequently, we examine our learning environment design language according to its lexis and syntax, the semantics behind it, and pragmatical aspects within a first prototypic implementation. Finally, we discuss strengths, problematic aspects, and open issues of our approach.

Knowledge management is fast becoming a commercial necessity for many organizations, in order that they manage their intellectual assets and gain competitive advantage. To maximise that advantage, knowledge management needs to be available across the whole of the enterprise. Before a knowledge management system can be built, the knowledge that pervades the organization must be identified and modelled. This paper reviews four important modelling techniques that are used to develop knowledge management systems.

Abstract—Object-oriented modeling has become the de-facto standard in the software development process during the last decades. A great deal of research in this area focuses on proposing modeling languages. In order to properly understand, and assess an object oriented modeling language, we believe that a set of criteria or requirements is needed. This Paper presents a framework to investigate and compare graphical object oriented modeling languages. This framework is based on a requirement set for an ideal object-oriented modeling languages. Index Terms—Object-Oriented modeling languages, comparison framework, requirement set, UML I.

Designing a new domain specific language is as any other complex task sometimes error-prone and usually time consuming, especially if the language shall be of high-quality and comfortably usable. Existing tool support focuses on the simplification of technical aspects but lacks support for an enforcement of principles for a good language design. In this paper we investigate guidelines that are useful for designing domain specific languages, largely based on our experience in developing languages as well as relying on existing guidelines on general purpose (GPLs) and modeling languages. We defined guidelines to support a DSL developer to achieve better quality of the language design and a better acceptance among its users. 1.

Abstract not found