| Introduction |
Abstraction is one of the important principles in software development.
A problem often encountered in software projects is that the
development of business logic is dominated by technical details
in a number of ways:
-
Firstly, a significant effort is often spent on technical issues
which do not contribute to the functionality of the software
system. Such a technical issue is, for instance, transaction
handling.
-
Secondly, software is often overloaded with technical details,
which hinders analysis of the implemented business logic, for
instance for reengineering purposes, and thus complicates its
further development and maintenance.
|
|
A solution to problems such as the above can be separation of
the essential aspects of software, i.e. business logic in particular,
from the non-essential, i.e. technical details, by means of abstraction.
Model-driven development can be considered a consequential step
of employing the abstraction principle in software development.
In model-driven development, essential aspects of software are
expressed in the form of models, and transformation of these
models is considered the core of software development. Models
can particularly be transformed to a technical implementation,
i.e. a software system. Such an approach can avoid restricting
oneself to a specific technology in early stages of the development
process and can ensure a consistent architecture throughout the
lifecycle of a software system.
|
|
The Overall Objective of the Book
|
|
The objective of the book is twofold. Firstly, It aims at outlining
the problems and open issues encountered in model-driven development.
Model-driven development significantly differs from other paradigms
and has its own specific problems not encountered in other paradigms.
The differences are not always obvious and need to be outlined.
Secondly, it aims at summarizing current research in the area
of model-driven development. In recent years, significant progress
has been achieved in this area at a conceptual as well as a technical
level.
|
|
The Target Audience
|
|
The target audience will be professionals and researchers working
in the area of model-driven development. The problems and open
issues outlined together with the summary of the contributions
to the area will give a clear insight into the progress achieved
and the possible directions of future research.
|
|
The Contents of the Book
|
|
The book will have three parts. Each of these three parts will
address specific aspects of model-driven development.
|
|
Part I : Conceptual Foundations of Model-Driven Development
|
|
The first part of the book will cover conceptual issues of model-driven
development, irrespective of the various technologies. Such issues
will include, for instance, model semantics and transformation
functions.
|
|
Part II: Technical Infrastructure of Model-Driven Development
|
|
The second part of the book will include descriptions of technology
for model-driven development. Software development in the large
requires the appropriate tools and technologies. This part of
the book will not focus on theory but on practical aspects and
describe those tools and technologies.
|
|
Part III: Case Studies
|
|
The last part of the book will be dedicated to experience reports.
In this part, experts from industry will describe projects in
which model-driven development has been employed and summarize
their experience.
|
|
Submission Procedure
|
Chapter submission deadline: July 1st, 2004
Notification deadline: September 1st, 2004
Researchers and practitioners are invited to submit a chapter
on or before July 1st. The submissions will undergo a thorough
review process and authors will be notified by September 1st,
2004.
Volume I of Research and Practice in Software Engineering entitled
"Testing COTS components and COTS-based systems" will be published
Fall 2004 by Springer.
Chapters submission may not exceed 11000 words, with figures covering
1 page counted as 500 words. Submissions do not have to follow a
specific layout. The layout specification will be provided for
preparation of camera ready versions.
|
|
Submission Site
|
|
http://www.paperdyne.de/mdabook.html
|
|
Contact Info
|
|
Inquiries and submissions can be forwarded electronically to:
|
Sami Beydeda
Tel.: +49 341 97 32347
E-mail: sami.beydeda@informatik.uni-leipzig.de
|
Volker Gruhn
Tel.: +49 341 97 32331
E-mail: volker.gruhn@informatik.uni-leipzig.de
|
|
|
