<p>
[We apologize if you receive multiple copies]
</p>
<p>
CALL FOR BOOK CHAPTERS (EXTENDED)
</p>
<p>
-------------------------------------------------------
</p>
<p>
PROPOSAL SUBMISSION DEADLINE: June 18, 2009 (EXTENDED)<br />
FULL CHAPTERS DUE: July 20, 2009<br />
-------------------------------------------------------
</p>
<p>
MODEL-DRIVEN DOMAIN ANALISYS AND SOFTWARE DEVELOPMENT: ARCHITECTURES AND FUNCTIONS
</p>
<p>
A book edited by Dr. Janis Osis and Dr. Erika Asnina, <br />
Riga Technical University, Latvia
</p>
<p>
<br />
To be published by IGI Global: <a href="http://www.igi-global.com/requests/details.asp?ID=614">http://www.igi-global.com/requests/details.asp?ID=614</a>
</p>
<p>
<br />
Introduction<br />
-------------
</p>
<p>
Software developers use different techniques for identification and specification of a domain’s characteristics and requirements for a planned application. Primarily these techniques are aimed at application analysis, while the problem domain is regarded almost as a black box describing a number of aspects of the system. The fact that system requirements are constraints set by real world phenomena not vice versa is underestimated. Software developers implement not what the customer needs, but what the customer wants. The reason is that proper problem domain analysis requires additional time and effort, while customers want to receive a working application as soon as possible. However, the customer’s needs and wants can differ. Thus a gap between the application and real world exists, creating the question of what domain is to be modeled at the beginning: the domain of today’s reality or the domain of customer’s expected reality. It is impossible to be highly efficient with a weak beginning, even with a strong end of the software development life cycle. <br />
In order to develop software to be used for real-world purposes, we must know how it will affect this world, where the implications can be far-reaching. This understanding has critical importance for mechatronic, embedded and high risk systems as well, where failure could cost human lives. It is also important for complex business systems, wherein failures could lead to huge financial losses. Developers must not ignore modeling the existing domain, where the planned application will work within, because this application placed in operation will certainly change the existing domain.<br />
OMG Model Driven Architecture (MDA) uses a principle of the separation of concerns. MDA utilizes three independent but related views: Computation Independent View, Platform Independent View, and Platform Specific View. Two latter views are related to customer’s expected reality. The theoretical foundation of the first view is not sufficiently clear. Considering its definition, we can assume that it is related not only to customer’s expected reality, but also to the domain of today’s reality. Thus to get really model-driven development this model should be formal (should reduce inaccuracies and ambiguities of specifications), and transformable. However, there is not enough research on this area. Another issue is application of MDA for advanced domains such as e-commerce, finance, manufacturing, web-services, enterprise computing etc.<br />
There exists a need for an edited collection of publications on keeping and improving the mechanisms of MDA for business modeling and advanced domains.
</p>
<p>
<br />
Objective of the Book<br />
------------------------
</p>
<p>
This book will aim to provide theoretical frameworks and the latest empirical research findings in improving model-driven domain analysis and software development. The viability of the proposed topics is provided by the viability of Model Driven Architecture that is still young and growing. It will be written for professionals who want to improve their understanding of the important role of the domain modeling in model-driven software development to make its models more formal and, thus, automatically transformable; to enable developers not to avoid proper problem domain analysis and to promote them (and tool vendors) to include formal construction and analysis of the problem domain into the industrial software development process using MDA.
</p>
<p>
<br />
Target Audience<br />
--------------------
</p>
<p>
This book is primarily intended for three groups of people: computer science students who ought to become practicing software engineers, users of the most advanced methods and approaches, experienced software developers who wish to acquire knowledge in applying Model Driven Architecture, and people interested in improvements to productivity of software development or quality of software products.
</p>
<p>
<br />
Recommended topics include, but are not limited to the following:<br />
-------------------------------------------------------------------
</p>
<p>
Model Driven Architecture and Means for Domain Modeling:
</p>
<p>
What is a Domain Model?<br />
•Domain Modeling: A Problem, Requirements and Solutions <br />
•Business Models and Requirements Models<br />
A Domain Model and Model-Driven Architecture<br />
•MDA Computation Independent (Domain) Model VS Requirements Model<br />
•The Role of Domain Model in Traditional and MDA Software Development Life Cycles<br />
Means for Domain Modeling<br />
•Business Modeling Approaches Proposed by OMG<br />
•Use Case Driven Modeling Approaches<br />
•Goal-Oriented Requirements Engineering Approaches<br />
•Quality of Domain Models<br />
Improvement of MDA Domain Modeling by a Formal Business Model
</p>
<p>
MDA for Advanced Application Domains:
</p>
<p>
Contributions for E-Commerce<br />
•Model-Driven Engineering for E-Commerce<br />
•Business Patterns for E-Commerce<br />
Contributions for Finance<br />
•Business-Focused Models for Financial Services<br />
•Model-Driven Engineering in a Large Financial Institution<br />
•MDA Application for Business Applications in Financial Organizations<br />
Contributions for Manufacturing<br />
•Model Driven Engineering for Product Lines<br />
•Model Driven Manufacturing Systems<br />
•Holistic Model-Driven Manufacturing Systems<br />
•Model Driven Engineering for Flexible Manufacturing Systems <br />
Contributions for Enterprise Computing<br />
•Model Driven Web-Services<br />
•Model-Driven Enterprise Computing<br />
•Model-Driven Business Integration<br />
•Model-Driven Distributed Systems
</p>
<p>
<br />
Submission and Review Procedure<br />
----------------------------------
</p>
<p>
Authors are invited to submit chapters describing original, high-quality research on topics of relevance for this book. A 3-5 pages chapter proposal (in Word format) should be sent by e-mail to both editors at <a href="mailto:janis.osis@cs.rtu.lv">janis.osis@cs.rtu.lv</a> and <a href="mailto:erika.asnina@rtu.lv">erika.asnina@rtu.lv</a>, with Subject “IGI Book Chapter Proposal” on or before June 18, 2009. A chapter proposal should contain title, author details (names, affiliations, and e-mail addresses), and an extended abstract, suggested chapter structure, an explanation of relevance for this book and brief biographies of the authors. The authors will be notified about the acceptance of their chapter proposals on or before June 25, 2009 and sent chapter guidelines. Full chapters are expected to be submitted by July 20, 2009. If authors need an additional time to complete full chapters, we would like to ask them to submit their requests to our approval. All submitted chapters will be reviewed on a double-blind review basis. The process for selecting which submitted chapters will be accepted will be competitive. Contributors may also be requested to serve as reviewers for this project.
</p>
<p>
<br />
Publisher<br />
------------
</p>
<p>
This book is scheduled to be published by IGI Global (formerly Idea Group Inc.), publisher of the “Information Science Reference” (formerly Idea Group Reference), “Medical Information Science Reference” and “IGI Publishing” imprints. For additional information regarding the publisher, please visit <a href="http://www.igi-global.com/">www.igi-global.com</a>. This publication is anticipated to be released in 2010.
</p>
<p>
<br />
Important Dates<br />
----------------
</p>
<p>
JUNE 18, 2009: Proposal Submission Deadline<br />
JUNE 25, 2009: Notification of Acceptance<br />
JULY 20, 2009: Full Chapter Submission Deadline<br />
August 15, 2009: Review Result Returned<br />
September 15, 2009: Revised Chapter Submission Deadline<br />
September 30, 2009: Final Acceptance Notification<br />
October 15, 2009: Final Chapter Submission Deadline
</p>
<p>
<br />
Editorial Advisory Board Members:<br />
------------------------------------
</p>
<p>
Eduardo Fernandez-Medina Paton, University of Castilla-La Mancha, Spain<br />
Jeff Gray, University of Alabama at Birmingham, USA<br />
Stan Hendryx, Hendryx & Associates, USA<br />
Marite Kirikova, Riga Technical University, Latvia<br />
Ricardo J. Machado, University of Minho, Portugal<br />
Sjir Nijssen, PNA, The Netherlands<br />
Dilip Patel, London South Bank University, UK<br />
Juan-Carlos Trujillo Mondejar, University of Alicante, Spain<br />
Yiyu Yao, University of Regina, Canada
</p>
<p>
</p>
<p>
Inquiries and submissions can be forwarded electronically (Word document) or by mail to:<br />
----------------------------------------------------------------------------------------
</p>
<p>
Dr. Janis Osis<br />
Department of Applied Computer Science<br />
Faculty of Computer Sciences and Information Technology<br />
Riga Technical University<br />
Meza iela 1/3, Riga, LV 1048, Latvia<br />
Email: <a href="mailto:janis.osis@cs.rtu.lv">janis.osis@cs.rtu.lv</a> <br />
Tel. Office: (+371) 67089523<br />
Fax: (+371) 67089596
</p>
<p>
and
</p>
<p>
Dr. Erika Asnina<br />
Department of Applied Computer Science<br />
Faculty of Computer Sciences and Information Technology<br />
Riga Technical University<br />
Meza iela 1/3, Riga, LV 1048, Latvia<br />
Email: <a href="mailto:erika.asnina@rtu.lv">erika.asnina@rtu.lv</a> <br />
Fax: (+371) 67089596S
</p>