@inproceedings{BenekenSeifertBaehretal.2004, author = {Beneken, Gerd and Seifert, T. and Baehr, N. and Hanschke, I. and Rauch, O.}, title = {Referenzarchitekturen und MDA, In INFORMATIK 2004 - Informatik verbindet}, series = {Beitr{\"a}ge der 34. Jahrestagung der Gesellschaft f{\"u}r Informatik e.V.}, booktitle = {Beitr{\"a}ge der 34. Jahrestagung der Gesellschaft f{\"u}r Informatik e.V.}, year = {2004}, abstract = {Dieser Beitrag beschreibt, wie Referenzarchitekturen die MDA nutzbar machen. Die Referenzarchitekturen liefern dabei die konzeptionelle Unterst{\"u}tzung f{\"u}r die Konstruktion und Implementierung von Software und die MDA bietet den Rahmen f{\"u}r eine Werkzeugunterst{\"u}tzung. Die praktische Umsetzbarkeit wird mit dem OpenSource Framework AndroMDA und einer Referenzarchitektur der Firma iteratec GmbH gezeigt.}, language = {de} } @inproceedings{WongYeapSchmidt2009, author = {Wong, C.K. and Yeap, W.K. and Schmidt, Jochen}, title = {Our Next Generation of Robotics Researchers? Teaching Robotics at Primary School Level.}, series = {Readings in Technology and Education: Proceedings of International Conference on Information Communication Technologies in Education}, booktitle = {Readings in Technology and Education: Proceedings of International Conference on Information Communication Technologies in Education}, year = {2009}, abstract = {In this paper, we present our experience in designing and teaching of our first robotics course for students at primary school level. The course was carried out over a comparatively short period of time, namely 6 weeks, 2 hours per week. In contrast to many other projects, we use robots that researchers used to conduct their research and discuss problems faced by these researchers. Thus, this is not a behavioural study but a hands-on learning experience for the students. The aim is to highlight the development of autonomous robots and artificial intelligence as well as to promote science and robotics in schools.}, language = {de} } @inproceedings{SeifertBenekenBaehr2004, author = {Seifert, T. and Beneken, Gerd and Baehr, N.}, title = {Engineering Long-Lived Applications Using MDA}, series = {Intl. Conference on Software Engineering and Applications, pp. 241-246, Cambridge}, booktitle = {Intl. Conference on Software Engineering and Applications, pp. 241-246, Cambridge}, year = {2004}, abstract = {Creating long-lived software systems requires a technol ogy to build systems with good maintainability. One of the core ideas of the Model Driven Architecture (MDA) is to ease the change of the run-time platform by raising the level of abstraction in which just the business aspects are modelled, and by separating business aspects from techni cal issues and implementation details. This article anal yses the MDA approach with respect to maintainability. We argue that MDA systems will become even harder to maintain because the maintainability depends on the sys tem's (development) environment. MDA, UML and other base technologies are still under development, therefore the tools will change considerably. While the MDA possibly eases the change of the run-time platform, we show that it is quite difficult to exchange a link in the development tool chain. Our argumentation is based on the general proper ties of software evolution and the dependency chains in the development and run-time environments. It is backed by experiences with MDA development as well as by analo gies to general maintenance experiences.}, language = {en} } @inproceedings{BenekenHammerschallBroyetal.2003, author = {Beneken, Gerd and Hammerschall, U. and Broy, M. and Cengarle, M.V. and J{\"u}rjens, J. and Pretschner, A. and Rumpe, B. and Sch{\"o}nmakers, M.}, title = {Componentware - State of the Art, Background Paper for the Understanding Components}, series = {Workshop of the CUE Initiative at the Univerita Ca Foscari di Venezia Venice}, booktitle = {Workshop of the CUE Initiative at the Univerita Ca Foscari di Venezia Venice}, year = {2003}, abstract = {Components and component-based technologies (componentware) are well-known and widely used in software development. There is a large amount of work and research in componentware. The number of available componentware approaches increases steadily and it is quite difficult to keep track of current trends in this area. In this paper, we survey the current state of the art in componentware, introduce and compare several well-known componentware approaches and classify them according to outstanding characteristics. We discuss a list of open issues in resarch and practical use of componentware and offer some proposals for further development. In our practical considerations we focus on embedded systems and business information systems because most of our partners in industry work in one of these two domains. We hope to start a broader discussion on componentware and to get a common understanding, which open issues are most important in research and industry (as a research agenda).}, language = {en} } @inproceedings{BenekenMarschallRausch2005, author = {Beneken, Gerd and Marschall, F. and Rausch, A.}, title = {A Model Framework Weaving Approach, In: Proceedings of the First Workshop on Models and Aspects - Handling Crosscutting Concerns in MDSD at the 19th European Conference on Object-Oriented Programming (ECOOP 2005)}, series = {19th European Conference on Object-Oriented Programming (ECOOP 2005)}, booktitle = {19th European Conference on Object-Oriented Programming (ECOOP 2005)}, year = {2005}, abstract = {Nowadays, in software development usually various models and description fragments are created. Some of these artifacts describe the core of the application, such as the data model or the user interaction model. Other artifacts describe cross-cutting concerns, such as security or the requirement: "every change of data has to be confirmed by the user, before it is written into the database". During the development process these artifacts are combined, transformed, and finally implemented manually or even automatically. For instance a designer may combine a model of a dialog component specifying an action, that changes data, with a common description of a generic confirm dialog. The integrated dialog description may be afterwards implemented by a programmer. The manual combination of both artifacts and the transformation of the combined description into code are errorprone and hard to change. Industry basically tests or actually uses two approaches for the combination today: 1. At the level of code and execution Aspect-Oriented Programming (AOP) is used [KLM+97]. An aspect defines a cross-cutting concern and the weaving instructions. A code weaver provides the actual weaving at compile or runtime. 2. At the level of design models and analysis models Model-Driven Software Development (MDSD) is used [KWB03]. A model in MDSD is a first class development artifact. Thus models are significantly more abstract than the implementation of code. However, these models cannot be executed. Hence, a abstract model is transformed into another, typically more detailed. A series of such transformations results in executable code. Thereby, a model transformer or a code generator reads some of the artifacts. The other artifacts and the combination rules are implemented in transformation rules or code generation templates (or somewhere else in the transformation / generation approach).}, language = {en} }