[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to main content

Transactions on Aspect-Oriented Software Development VI

Special Issue on Aspects and Model-Driven Engineering

  • Book
  • © 2009

Overview

Part of the book series: Lecture Notes in Computer Science (LNCS, volume 5560)

Part of the book sub series: Transactions on Aspect-Oriented Software Development (TAOSD)

This is a preview of subscription content, log in via an institution to check access.

Access this book

Subscribe and save

Springer+ Basic
£29.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

eBook GBP 35.99
Price includes VAT (United Kingdom)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book GBP 44.99
Price includes VAT (United Kingdom)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Other ways to access

Licence this eBook for your library

Institutional subscriptions

About this book

work for small problems, but it introduces signi?cant accidental complexities when tackling larger problems. Notethattherealchallengehereisnothowtodesignthesystemtotakeap- ticular aspect into account: there is signi?cant design know-how in industry on this and it is often captured in the form of design patterns. Taking into account more than one aspect can be a little harder, but many large scale successful projects in industry provide some evidence that engineers know how di?erent concerns should be handled. The real challenge is reducing the e?ort that the engineerhasto expendwhengrapplingwithmanyinter-dependentconcerns.For example, in a product-line context, when an engineer wants to replace a variant of an aspect used in a system, she should be able to do this cheaply, quickly and safely. Manually weaving every aspect is not an option. Unlike many models used in the sciences, models in software and in lingu- tics have the same nature as the things they model. In software, this provides an opportunity to automatically derive software from its model, that is, to - tomate the weaving process. This requires models to be formal, and the weaving process be described as a program (i.e., an executable meta-model) manipul- ing models to produce a detailed design. The detailed design produced by the weaving process can ultimately be transformed to code or at least test suites.

Similar content being viewed by others

Keywords

Table of contents (7 chapters)

  1. Special Issue: Aspects and Model-Driven Engineering

Reviews

From the reviews:

“This collection targets various facets of aspect-oriented software development (AOSD) in the context of model-driven engineering (MDE)--an approach in which models are used to drive the development throughout the entire life cycle of the software. … This systemic approach is still in the research stage, and the book contains these research reports. The book will be of interest to university research teams concerned with aspect orientation.” (Pierre Radulescu-Banu, ACM Computing Reviews, December, 2010)

Editors and Affiliations

  • Department of Computer Science, The Technion, Haifa, Israel

    Shmuel Katz

  • IBM Thomas J. Watson Research Center, Yorktown Heights, USA

    Harold Ossher

  • Computer Science Department, Colorado State University, Fort Collins, USA

    Robert France

  • IRISA, Université de Rennes 1, Rennes Cedex, France

    Jean-Marc Jézéquel

Bibliographic Information

Publish with us