*CALL FOR CHAPTERS* Proposal Submission Deadline: October 1, 2010
*"Emerging Technologies for the Evolution and Maintenance of Software Models"* *A book edited by* Jörg Rech (SAP Research Center Karlsruhe, Germany) & Christian Bunse (University of Applied Sciences Stralsund, Germany) *--- To be published by IGI Global ---* *Introduction* Model-driven software development drastically alters the software development process, which is characterized by a high degree of innovation and productivity. Model-driven architectures (MDA) and model-driven software development (MDSD) focuses on the idea of constructing software systems not by programming in a specific programming language but by designing models that are translated into executable software systems by generators. These characteristics enable designers to deliver product releases within much shorter periods of time compared to the traditional methods. In theory, this process makes it unnecessary to care for an executable system’s quality, as it is "optimized" by the generators. Up to now, the research in the MDSD area focussed on the development of software models and required tool environments. While this knowledge is slowly transferred into industrial practice the research now shifts to the maintenance, evolution, re-engineering as well as long-term management of software models. The developed models require new approaches to keep them up-to-date with changing technologies, methodologies, languages, and tool environments. *Objectives of this book* This book aims at publishing original academic work about current research or research projects related to all aspects affecting the maintenance, evolution, and reengineering (MER) as well as long-term management of software models. The book’s mission is to give a comprehensive and central overview of the research and to provide concrete results from ongoing research in the field. This area is wide and entails many facets that the book should clarify, including: * Differences and similarities between MER in traditional (code-based) SE and in MDSD * The state of the art and the state of the practice of MER for MDSD * The basis of (empirical) evidence about MER approaches for MDSD * Identification of ongoing research in MER of software models * Identification of open problems in MER of software models * Model-driven design and development approaches to support MER activities * Evaluation processes of approaches for MER in model-driven development. *Recommended Topics* Recommended topics include, but are not limited to, the following: Introductory * State-of-the-art in maintaining, evolving, and reengineering software models (general overview) * State-of-the-practice in maintaining, evolving, and reengineering software models (general overview) * Terminology in maintaining, evolving, and reengineering software models About Model-driven Software Development for the future * Development processes / Process models for evolution-aware MDSD * Documentation of software models for later maintenance, evolution, and reengineering activities (incl. text, audio, video) * Structuring/Design of software models for later maintenance, evolution, and reengineering activities (incl. patterns, etc.) * Training activities to support later maintenance, evolution, and reengineering activities About Model-driven Software Quality Assurance for the future * Quality Assurance processes / Process models for evolution-aware MDSD * Testing of software models to support later maintenance, evolution, and reengineering activities * Inspection of software models to support later maintenance, evolution, and reengineering activities * Quality defect diagnosis techniques to support later maintenance, evolution, and reengineering activities * Verification and Validation of software models to support later maintenance, evolution, and reengineering activities * Measuring the maintainability, “evolvability”, or “reengineerability” of software models * Documentation of software model tests, inspections, etc. to support later MER activities (data, results, etc.) About Model-driven Software Maintenance * Maintenance processes / Process models to support maintenance activities * Management, administration, or categorization of software models * Versioning of software models * Debugging of software models * Refactoring of software models * Defect and Issue management for software maintenance * Maintaining the documentation and traceability of software models * Preventive & corrective maintenance of software models; Prevent the decay and erosion of software models About Model-driven Software Evolution * Evolution processes / Process models to support evolution activities * Software model co-evolution and consistency management * Change impact analysis and change propagation for software models * Architectures, languages, notations, or tools to support model evolution * Evolution of Hardware/Software co-design (software) models * Traceability from requirements models to design and test models * Tools or technique to support software evolution activities About Model-driven Software Reengineering * Reengineering processes / Process models to support reengineering activities * Reverse-Engineering of source code and software models in new software models * Restructuring, Modernization, Renovation of software models: Methods, tools, and techniques * Development and MER of (forward-) generators/transformers/compilers/interpreters from models to code About Management of MDSD Projects * Project management of MDSD Projects * Processes and methodologies for MER of MDSD * Distributed, parallel and decentralized processes or environments for MER software models * Transition (handover) processes for MDSD projects & products * Economic models to assess and predict the cost of MER activities * Productivity measurement and benchmarking of software models and MER activities * Quality management / Quality assessment of software models (to control/influence MER activities) About Maintaining the modelling infrastructure * Adapting/Evolving the technology stack (VMs, libraries, ...) for software modelling * Adapting/Evolving the tool infrastructure for software modelling * Adapting/Evolving processes for software modelling Miscellaneous * Patterns and anti-patterns for maintaining, evolving, and reengineering software models * Standards for maintaining, evolving, and reengineering software models * Use, Reuse, and recycling of (older) software models * Integrating software models with different base languages (UML & SDL) or with different DSLs * Maintaining fused paradigms (e.g., Product-lines & MDSD, Agent-oriented MDSD, AOP & MDSD, …) * MER, Managing and versioning product lines of models * Teaching principles for maintaining, evolving, and reengineering software models * Education and training of software maintenance architects/designer/modelers About Empiric Topics in this Area * Evaluation of approaches for maintaining, evolving, and reengineering software models (i.e., how to evaluate) * Long-time experiences with the maintenance, evolution, and reengineering of software models * Short-time experiences with the maintenance, evolution, and reengineering of software models * Empirical studies related to software model maintenance, evolution, and reengineering: Controlled experiments, case studies, field studies, etc. * Industrial experience on successes and failures related to MER of software models Outlook * Trends for maintaining, evolving, and reengineering software models (statements, survey, polls, etc.) * Maintenance, evolution, and reengineering of software models in 5, 10 and 25 years (visionary statements) *Timetable for the entire project* Researchers and practitioners are invited to submit on or before October 1, 2010, a 1-4 page manuscript proposal clearly explaining the mission and concerns of the proposed chapter. Authors of accepted proposals will be notified by October 15, 2010 about the status of their proposals and sent chapter organizational guidelines. Full chapters are expected to be submitted by January 15 2010. All submitted chapters will be reviewed on a double-blind review basis. The book is scheduled to be published by IGI Global (http://www.igi-global.com) with an ISBN. *October 1, 2010: Submission of proposals for chapters * October 15, 2010: Notification of proposal acceptance/rejection January 15, 2010: Submission of full chapters March 1, 2010: Notification of the chapter reviews April 1, 2011: Submission of revised/final chapters April 15, 2011: Notification of final acceptance/rejection June 1, 2011: Chapter proofs by authors July 1, 2011: Final submission of all book parts Winter 2011: Book release Papers should be original and should not be submitted for publication or published elsewhere. Electronic submissions are required. All submitted chapters will be reviewed on a blind review basis by chapter authors and external reviewers. Inquiries, and submissions can be forwarded electronically (Word, RTF, or PDF document) to: Joerg Rech ([email protected])
---- [[ Petri Nets World: ]] [[ http://www.informatik.uni-hamburg.de/TGI/PetriNets/ ]] [[ Mailing list FAQ: ]] [[ http://www.informatik.uni-hamburg.de/TGI/PetriNets/pnml/faq.html ]] [[ Post messages/summary of replies: ]] [[ [email protected] ]]
