Book Objectives & Mission
This book aims at publishing original academic work and experience
reports from industry related to quality assurance for model-driven software
development (QAMDSD). The books mission is to give a clear description of the
fundamentals in QAMDSD theory, to fill the gap in the literature, and to
provide concrete results from software development organizations. Successful
quality assurance for model-driven software development can help participants
in the software development process avoid risks and project failures that are
frequently encountered in traditional and agile software projects. The whole
development process must be analyzed, measured, and validated from the quality
point of view.
The area is wide and entails many facets that
the book must clarify, including:
Differences and
similarities between the traditional and model-driven quality aspects,
Identification of
quality aspects in model-driven development,
Model-driven design and
development of high-quality software,
Evaluation of quality
in model-driven development,
Reports on the
state-of-the-art regarding quality in model-driven development,
Investigation on how
processes affect the quality in model-driven development.
Additionally, this book will provide a
compendium of definitions and explanations of the main terms, concepts, and
topics of quality assurance for model-driven software development.
The target audience for this
book
Professionals and researchers working in the
field of software engineering interested in Quality Assurance for Model Driven
Software Development and the model-driven development process. The book will
provide a comprehensive view of quality in Model Driven Development to project
managers, developers, and researchers interested in promoting Quality Assurance
for Model Driven Software Development. Moreover, the book will provide insights
and support to academic teachers and students seeking a comprehensive tool for
studying Quality Assurance for Model Driven Software Development.
Recommended topics
include, but are not limited to, the following:
Introductory Chapters
State-of-the-art of
quality assurance for model-driven software development
Terminology of quality
assurance for model-driven software development
Quality in model-driven software development
related chapters
Quality aspects in
model-driven development (e.g., maintainability of models)
Process metrics for
model-driven development
Product metrics for
model-driven development
Quality metrics for
model-driven development
Patterns and
anti-patterns for model-driven development
Model and architecture
smells
Performance,
optimization, and tuning of models
Quality-oriented Construction of software
Models related chapters
Requirements for
high-quality software Models
Analysis and design for
high-quality software Models
Project management for
high-quality software Models
Testing in model-driven software
development (Model-based Testing, Testing of Models, Model Validation)
Inspections, review,
walkthroughs or audits in MDSD
Formal approaches for
high-quality software models (Formal Languages, Model checking, Model
Verification)
Quality-oriented Maintenance of High-quality
software Models related chapters
Refactoring of high-quality software models
Re-engineering of
high-quality software models
Ontologies, Semantics, Metadata and Data for
MDSD related chapters
Ontology development
for high-quality software models
Semantics, metadata and
ontologies for high-quality software models
Action languages
supporting high-quality software models
Examples and Evidence related chapters
Examples of
high-quality software models
Quality of model-driven
development experiments and case studies
Miscellaneous related chapters
Management of
high-quality software models
Standards and
high-quality software models
Teaching principles of quality assurance for
model-driven software development
Outlook related chapters
Trends in quality
assurance for model-driven software development
Quality assurance for
model-driven software development in 5, 10, and 25 years
Submission guidelines
Researchers and practitioners are invited to
submit on or before December 1, 2006, a 2-5 page manuscript proposal clearly
explaining the mission and concerns of the proposed chapter. Authors of
accepted proposals will be notified by January 15, 2007 about the status
of their proposals and sent chapter organizational guidelines. Full chapters
are expected to be submitted by May 15, 2007. All submitted chapters
will be reviewed on a double-blind review basis. The book is scheduled to be
published by Idea Group Inc., www.idea-group.com,
publisher of the Idea Group Publishing, Information Science Publishing, IRM
Press, CyberTech Publishing and Idea Group Reference
imprints.
Inquiries
and submissions can be forwarded electronically (Word, RTF, or PDF
document) to:
Joerg Rech
Fraunhofer
Institute for Experimental Software Engineering (IESE)
Fraunhofer-Platz 1, 67663 Kaiserslautern,
Germany
Tel.: +49
631/6800-2210, Fax.: +49 631/6800-1599
email: joerg.rech@iese.fraunhofer.de
