Model Driven Architecture

The quest for designing secure and trusted software has led to refined Software Engineering methodologies that rely on tools to support the design process. Automated reasoning mechanisms for requirements and software verification are by now a well-accepted part of the design process, and model driven architectures support the automation of the refinement process. We claim that we can further push the envelope towards the automatic exploration and selection among design alternatives and show that this is concretely possible for Secure Tropos, a requirements engineering methodology that addresses security and trust concerns. In Secure Tropos, a design consists of a network of actors (agents, positions or roles) with delegation/permission dependencies among them. Accordingly, the generation of design alternatives can be accomplished by a planner which is given as input a set of actors and goals and generates alternative multiagent plans to fulfill all given goals. We validate our claim with a case study using a state-of-the-art planner.

Service Oriented Architecture (SOA) is an architectural style that is widely used in distributed and dynamic systems. The Service oriented architecture Modeling Language (SoaML) is an OMG standard for modelling SOA independent of a technology. This paper presents a tool for modelling SOA using SoaML and generating OSGi Declarative Services Models from SoaML models. SoaML metamodel has been implemented as an Ecore model using the Eclipse Modeling Framework (EMF). An Eclipse plug-in that allows architects to graphically design SoaML models has been developed using the Graphical Modeling Framework (GMF). We have also implemented a model transformation using ATLAS Transformation Language (ATL) in order to partially generate Declarative Services models. The generated model is used as a Declarative Services Component Description XML specification which is needed to execute code on the OSGi service oriented platform. In this way, we provide SoaML with Model Driven Architecture support.

In a Model Driven Architecture (MDA) software development process, models are repeatedly transformed to other models in order to finally achieve a set of models with enough details to implement a system. Generally, there are multiple ways to transform one model into another model. Alternative target models differ in their quality properties and the selection of a particular model is determined on the basis of specific requirements. Software engineers must be able to identify, compare and select the appropriate transformations within the given set of requirements. The current transformation languages used for describing and executing model transformations only provide means to specify the transformations but do not help to identify and select from the alternative transformations. In this paper we propose a process and a set of techniques for constructing a transformation space for a given transformation problem. The process uses a source model, its meta-model and the meta-model of the target as input and generates a transformation space. Every element in that space represents a transformation that produces a result that is an instance of the target meta-model. The requirements that must be fulfilled by the result are captured and represented in a quality model. We explain our approach using an illustrative example for transforming a platform independent model expressed in UML into platform specific models that represent XML schemas. A particular quality model of extensibility is presented in the paper.

The systematic capture of appropriately annotated experimental data is a prerequisite for most bioinformatics analyses. Data capture is required not only for submission of data to public repositories, but also to underpin integrated analysis, archiving, and sharing -both within laboratories and in collaborative projects. The widespread requirement to capture data means that data capture and annotation are taking place at many sites, but the small scale of the literature on tools, techniques and experiences suggests that there is work to be done to identify good practice and reduce duplication of effort.

This paper aims at demonstrating the benefits and importance of the service concept in the model-driven design of distributed applications. A service defines the observable behaviour of a system without constraining the system's internal structure. We argue that by specifying application-level interaction aspects as a service, and designing application parts in terms of this service, the design of application parts is not constrained by interaction patterns provided by a middleware platform. Therefore, a level of platform-independence can be achieved, so that the design of application parts can be reused across a large set of middleware platforms. The service concept is also used in our approach to describe an abstract platform that defines what characteristics of a potential target middleware platform are considered in platform-independent design. We discuss the trade-offs a designer is confronted with in the definition of an abstract platform, and discuss alternatives for platform-specific realization.

The complex requirements of software systems justify the use of the best existing techniques to guar- antee the quality of speciflcations and to preserve this quality during the programming,phase of a software life-cycle. On the one hand, visual speciflcation lan- guages (such as UML) have been widely used for spec- ifying, visualizing, understanding and documenting software systems, but they

This paper proposes LEAP: a simple framework for Enterprise Architecture (EA) that views an organization as an engine that executes in terms of hierarchically decomposed communicating components. The approach allows all aspects of the architecture to be precisely defined using standard modelling notations. Given that the approach is simple and precisely defined it can form the basis for a wide range of EA analysis techniques including simulation, compliance and consistency checking. The paper defines the LEAP framework and provides an overview in terms of a case study. LEAP does not mandate any specific notation, a UML-style notation is used in this paper and the implications for ArchiMate are analysed.

Collaborative business models among enterprises require defining collaborative business processes. Enterprises implement B2B collaborations to execute these processes. In B2B collaborations the integration and interoperability of processes and systems of the enterprises are required to support the execution of collaborative processes. From a collaborative process model, which describes the global view of the enterprise interactions, each enterprise must define the interface process that represents the role it performs in the collaborative process in order to implement the process in a Business Process Management System. Hence, in this work we propose a method for the automatic generation of the interface process model of each enterprise from a collaborative process model. This method is based on a Model-Driven Architecture to transform collaborative process models into interface process models. By applying this method, interface processes are guaranteed to be interoperable and defined according to a collaborative process.

Software engineers share a common gene pool Architecture mismatch => early mistakes Programming bugs => latent flaws }a Extinction ! Outlook for software engineering species 0 Significant evolution but still affected with the same old diseases 0 Bleak future for commercial success & long-term survival 0 Species comparison: viruses have greater success at lower cost * A brighter perspective: * UML/MDA: 0 Bridging the gap between programmers & architects JPL follows a similar path in the Mission Data System project Bridging the gap between software & system engineering JPL Unusual Characteristics of Space Missions * Infrequent, scheduled communication The 'network' is not continuously available * Distance, Time, Bandwidth & Navigation Multiple clocks:-10 hour round-trip light-time delay to Pluto Physics limit bandwidth:-300 bitslsec from Pluto

ISO/IEC 15909-2 International Standard defines a universal XML-based transfer syntax for Petri nets. The main objective of this exchange format, namely Petri Net Markup Language (PNML), is to enable compatibility and interoperability among heterogeneous Petri net tools, while keeping expressiveness and extensibility. Hence, it shall support different types of Petri nets and be extensible to allow for future types. To make it applicable and integrable at low cost to existing tools, a software framework is proposed to the Petri net community. This framework enables fast and cost-effective tools adaptation to PNML use by bringing forth model engineering techniques through model transformation, backed on OMG's Model-Driven Architecture principles. This paper shows that the proposed approach is concerned for compliance with the standard, enhancing compatibility between tools. It is realistic and pragmatic. It copes with extensibility issues by allowing fast re-engineering, thanks to model-driven development approach and code generation.

The ecosystem of the Internet of Things is a set of physical devices such as sensors and actuators. It includes a set of servers and gateways that provide connectivity. These devices can be installed at three levels: the edge level, the fog level, and the cloud level. Applications that monitor things and collect data from sensors are deployed at the edge, fog, and cloud levels. These applications can be containerized and deployed in different devices by Docker, which takes advantage of its advantage to create executable containers that are isolated from each other. This paper presents a generic Meta-model of the Internet of Things ecosystem based on microservices and supported by Docker as a containerization tool, Ansible as a monitoring tool and Kubernetes as scaling tool. This Meta-model allows us to generate a system of connected objects that can be deployed on three levels: Fog, Edge, Cloud. This Meta-model can be used in different types of domains such as Smart Home-Smart City-Smart Vehicle-Smart Health-Smart Farm-Smart Factory. The Meta-model proposed in this article is a fusion between 5 Meta-models: Internet of Things-Microservices-Ansible-Docker-Kubernetes.

Model Driven Architecture (MDA) is a software design approach initiated by OMG. Models, Modeling, and Model Driven Architecture are the basis for a set of software development approaches known as model-driven development (MDD). Models are the central artifacts in MDA, which aim at transformation from platform independent to platform dependent models, and eventually to executable source code. Therefore, model transformation plays key roles in making MDA successful. The effective application of the MDA based software development approach subscribes to automated execution of software model transformations. This paper highlights various classifications and salient features of prominent model transformation approaches for transforming PIM to PSM and provides an insight into the complete transformation process with the help of a real-life example. A summary of rules of transforming UML class model into EJB specific model is also given.

Information systems are expected to satisfy increasingly ambitious requirements, while reducing time-to-market has become a primary objective. This trend has necessitated the advent of development approaches that are better equipped and flexible enough to cope with modern challenges. Model-Driven Architecture (MDA) and Situational Method Engineering (SME) are approaches addressing this requirement: MDA provides promising means for automating the software process, and revitalizes the role of modeling in software development; SME focuses on project-specific methodology construction, mainly through assembling reusable method fragments (process patterns) retrieved from a method base. We provide a set of high-level process patterns for model-driven development which have been derived from a study of six prominent MDAbased methodologies, and which form the basis for a proposed generic MDA Software Process (MDASP). These process patterns can promote SME by providing classes of common process components which can be used for assembling, tailoring, and extending MDA-based methodologies.

Abstract The Model Driven Architecture (MDA) is meant to facilitate system development by using models for representing both the¿ problem¿ and its¿ solution¿. In its ideal form, software development based on MDA would follow a development process that begins by producing models of the problem domain at a high level of abstraction, and then proceeds by gradually and automatically transforming them into executable code with the help of tools. However, MDA-based development has encountered several setbacks, the mitigation of ...

UML has become the standard language for modelling in different areas and domains, but it is widely recognized that it lacks support for User Interface Design (UID). On the other hand, ConcurTaskTree (CTT) is one of the most widely used notations for task and dialogue modelling. An important achievement is the proposed notation and semantics for CTT by extending the UML metamodel, proving that task modelling in user interface design can be accomplished by a UML compliant notation. For the interface structure design was proposed that UML’s CTT could be complemented with Canonical Abstract Prototypes (CAP) leading to a model-based user interface design method co-specified by the presentation (CAP) and behaviour (UML’s CTT) perspectives. In this paper we propose another step in this UID method by defining a specific model compliant with the OMG recommended Model Driven Architecture (MDA), which will be the intermediary between the design model and an implementation of the user interface. This proposal will align the UID method with the MDA recommendation making it possible to automatically generate interface prototypes from conceptual models.

The purpose of the .NET Technologies conference series (http://dotnet.zcu.cz) is to bring together practitioners and researchers from academia and the industry to discuss the latest developments in .NET and to advance the state of the art in the research on related technologies. Interest in these topics has been continuously growing as a consequence of the importance and the ubiquity of object-oriented technologies.

This paper presents the MOPCOM design methodology, developed to enable the efficient design of real time embedded systems, in particular radio (such as software defined radio) communication and video processing equipment. Based on UML and the model driven architecture approach, it could be advantageously applied for the design of a system on a chip or a system on a programmable chip. The MOPCOM methodology defines a set of rules for building UML models for embedded systems, from which Hardware Description Language code is automatically generated by means of a set of model transformations. The MARTE profile is used to describe real time properties and to perform platform modeling. A wireless communication demonstrator is presented to illustrate the methodology and the tooling.

A standardized core cadastral domain model (CCDM), covering land registration and cadastre in a broad sense (multipurpose cadastre), will serve at least two important goals: 1. avoid reinventing and re-implementing the same functionality over and over again, but provide a extensible basis for efficient and effective cadastral system development based on a model driven architecture (MDA), and 2. enable involved parties, both within one country and between different countries, to communicate based on the shared ontology implied by the model.The second goals is very important for creating standardized information services in an international context, where land administration domain semantics have to be shared between countries (in order to enable needed translations). This paper presents an overview of the core cadastral domain model. The model has been developed in a set of versions, which were each time adjusted based on the discussions at workshops with international experts and the experience from case studies in several countries of the world (Netherlands, El Salvador, and several African and Arab countries). Important conditions during the design of the model were and still are: should cover the common aspects of cadastral registrations all over the world, should be based on the conceptual framework of Cadastre 2014, should follow the international ISO and OGC standards, and at the same time the model should be as simple as possible in order to be useful in practise. The heart of the model is based on the three abstract classes: 1. RegisterObject (including all kinds of immovables and movables), 2. RRR (right, restriction, responsibility), and 3. Person (natural, nonnatural and group). The model supports the temporal aspects of the involved classes and offers several levels of Parcel fuzziness in bothe 2D and 3D space: Parcel (full topology), SpaghettiParcel (only geometry), PointParcel (single point), and TextParcel (no coordinate, just a description). The model is specified in UML class diagrams and it is indicated how this UML model can be converted into and XML schema, which can then be used for actual data exchange in our networked society (interoperability).

Metamodelling is an activity that is getting much more attention by the research community. One of the main causes of this recent interest is being an important piece for the different approaches for Model-Driven Development (MDD). In this context, the definition and implementation of metamodels not only is important for improving the MDD, but also for their later reuse.

Integrated health care systems Systems analysis Software process engineering Model-Driven Architecture Semantic interoperability Unified process HL7 a b s t r a c t Background: Semantic interoperability is a basic challenge to be met for new generations of distributed, communicating and co-operating health information systems (HIS) enabling shared care and e-Health. Analysis, design, implementation and maintenance of such systems and intrinsic architectures have to follow a unified development methodology. Methods: The Generic Component Model (GCM) is used as a framework for modeling any system to evaluate and harmonize state of the art architecture development approaches and standards for health information systems as well as to derive a coherent architecture development framework for sustainable, semantically interoperable HIS and their components. The proposed methodology is based on the Rational Unified Process (RUP), taking advantage of its flexibility to be configured for integrating other architectural approaches such as Service-Oriented Architecture (SOA), Model-Driven Architecture (MDA), ISO 10746, and HL7 Development Framework (HDF).

As part of the AMMA project (ATLAS Model Management Architecture), we are currently building several model management tools to support the tasks of modeling in the large and of modeling in the small. The basic idea is to define an experimental framework based on the principle of models as first class entities. This allows us to investigate issues of conceptual and practical interest in the field of model management applied to data-intensive applications. By modeling in the small, we mean dealing with model and metamodel elements and the relations between them. In this sense, ATL (ATLAS Transformation Language) allows expressing automatic model transformations. We also motivate the need for the "ModelWeaver" which handles fine-grained relationships between elements of different metamodels with a different purpose than automatic model transformation. By modeling in the large, we mean globally dealing with models, metamodels and their properties and relations. We use the notion of a "MegaModel" to describe a registry for models and metamodels. This paper proposes a lightweight architectural style for a model-engineering platform as well as a first prototype implementation demonstrating its feasibility.

An MDA design approach should be able to accommodate designs at different levels of platformindependence. We have proposed a design approach (in [2] and [3]), which allows these levels to be identified. An important feature of this approach is the notion of abstract platform. An abstract platform is determined by the platform characteristics that are relevant for applications at a certain level of platform-independence, and must be established by considering various design goals. In this paper, we define a framework that makes it possible to use RM-ODP concepts in our MDA design approach. This framework proposes a recursive application of the computational viewpoint at different levels of platform-independence. This is obtained by equating the RM-ODP notion of infrastructure to our notion of abstract platform.

Nowadays, service-oriented architectures are becoming gradually more important. The vast diversity of implementation and support platforms for this kind of architectures (such as Web, Grid or even CORBA) increases the complexity of the development process of service-based systems. With the aim of facilitating the development of service oriented solutions, we propose the specification of an architecture centric model driven development method. To achieve this, we study the architectural properties of the SOA paradigm and follow a development approach based on the MDA proposal. MDA proposes a separation of the development process in abstraction levels. This makes MDA suitable to tackle the development of service-oriented systems. This paper describes a UML profile for the PIM-level service-oriented architectural modelling, as well as its corresponding metamodel. PIM (Platform Independent Model) level is chosen because it does not reflect constraints about any specific platform or implementation technology. To exemplify and validate the profile, a case study is presented in which the proposed profile is used.

Use of web services also on mobile devices becomes increasingly relevant. However, realizing such mobile web services based on the standard protocol stack is often inappropriate for resourcerestricted mobile devices in dynamic networks. On the other hand, using specialized alternative protocols restricts compatibility with traditional service applications. Thus, existing approaches often do not allow to integrate heterogeneous service instances dynamically, as it is, e.g., required for executing mobile service-based business processes.

this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means-electronic, mechanical, photocopying, or otherwise-without the prior written permission of the publisher and of the authors. Cover photo: Maximiliano Corredor (Flickr BioMaxi, Creative Commons, some rights reserved).

Electronic health record Smart cards Security Privacy a b s t r a c t Shared care concepts such as managed care and continuity of care are based on extended communication and cooperation between different health professionals or between them and the patient respectively. Health information systems and their components, which are very different in their structure, behavior, data and their semantics as well as regarding implementation details used in different environments for different purposes, have to provide intelligent interoperability. Therefore, flexibility, portability, and future orientation must be guaranteed using the newest development of model driven architecture. The ongoing work for the German health telematics platform based on an architectural framework and a security infrastructure is described in some detail. This concept of future proof health information networks with virtual electronic health records as core application starts with multifunctional electronic health cards. It fits into developments currently performed by many other developed countries.

This paper presents an eXtensible Stylesheet Language Transformation (XSLT)-based approach for automatic generation of the Web Ontology Language (OWL) from a UML model. Similar solutions that treat this problem are mostly partial since they do not use full metamodeling potentials. Although they emphasize the notion of the use UML for ontology development and propose necessary transformations into Semantic Web languages (e.g., RDF Schema, DAML, DAML+OIL), their UML models must be further refined using ontology-specialized tool. None of these approaches enables instance modeling and generation of OWL ontologies. In our efforts to make ontological and software engineering techniques closer, we have firstly defined ontology metamodeling architecture using Model Driven Architecture (MDA) concepts. This architecture consists of the Ontology Definition Metamodel defined using Meta Object Facility (MOF) and based on the OWL, as well as the related Ontology UML Profile (OUP). A transformation, that we present here, extends this metamodeling architecture and transforms an ontology from its OUP definition (i.e., XML Metadata Interchange – XMI) into the OWL description. Accordingly, we illustrate how an OUP-developed ontology can be shared with ontological engineering tools (i.e., Protégé).

Abstract - Increasing market competitiveness has led entrepreneurs to require more and more information from Information Technology areas to allow for efficient decision-making. Two alternatives to solving this problem are allied in this work: use of Model Driven Architecture (MDA) and ...

The Department of Information Science is one of six departments that make up the School of Business at the University of Otago. The department offers courses of study leading to a major in Information Science within the BCom, BA and BSc degrees. In addition to undergraduate teaching, the department is also strongly involved in postgraduate research programmes leading to MCom, MA, MSc and PhD degrees. Research projects in spatial information processing, connectionist-based information systems, software engineering and software development, information engineering and database, software metrics, distributed information systems, multimedia information systems and information systems security are particularly well supported.

This paper presents a methodology for transforming business designs written in OMG's standard Semantics of Business Vocabulary and Rules (SBVR) framework, into a set of UML models. It involves the transformation of business vocabulary and rules written in SBVR's "Structured English" into a set of UML diagrams, which includes Activity Diagram(AD), Sequence Diagram(SD), and Class Diagram(CD). This transformation works by detecting the distinction between rules which will participate in the construction of Activity Diagram and rules which do not. These rules are imperative in nature. The work in the paper also includes the detection of activities embedded implicitly in those rules and establishment of sequence between those activities. These activities incur some action. We also detect their owner and refer to them as the doer of the action. This plays a very important role in the development of Class Diagrams.

The problem of designing suitable conceptual modeling languages for system engineering is far from being solved. In the past years, some works have proposed the use of foundational ontologies as analysis tools to enable semantic coherence when (re)designing such languages. In this paper, we exemplify this approach by applying a foundational ontology named UFO in the design of an agent-oriented modeling language for the ARKnowD methodology. Instead of proposing new concepts and constructs, ARKnowD relies on existing work, combining two different approaches, namely Tropos and AORML. Each work is applied in a different development activity, according to their natural propensity: Tropos in Requirements Analysis and AORML in System Design. Besides the ontological approach, we propose some mapping rules between the notations, inspired in the Model Driven Architecture (MDA) metamodel transformation method. This approach helps to guarantee a smooth transition from one activity to the other.

Currently, standardized distributed simulation systems are likely to follow the High Level Architecture (HLA) standard, not only because it is widely adopted in the United States for DoD applications, but also because it can be seen as the most matured M&S standard in this domain. However, the HLA focuses on the implementation level; thus it cannot solve problems on the conceptual level, such as validation, verification, or composability of models. The Discrete Event System Specification (DEVS) deals successfully with the conceptual challenges, but its application is limited to the academic community. The M&S community is still looking for a general method insuring interoperability on all levels, from the syntactic level via the semantic level to the pragmatic/dynamic level, and maybe even to the most general conceptual level. To this end, the communication-driven ideas of the HLA must be merged with the conceptually driven ideas of DEVS, preferably in a commercially viable way.

Objectives: For establishing trustworthiness in advanced architectures for futureproof health information systems being open, flexible, scaleable, portable, and semantically interoperable, security and privacy services needed must be designed as an inherent part of the architecture. Such architecture has to meet the paradigms of distribution, component orientation, formal modelling, separation of logical and technological aspects, etc. Methods: In model-driven architectures components providing security and privacy services have to be specified using the same methodology of formal models with meta-languages as expression means, as deployed in computational, technical, or medical domains. The resulting approach must be based on the ISO Reference Model--Open Distributed Processing. Results: Currently, standards developing organisation are defining emerging tasks and standards for semantic interoperability and trustworthy collaboration for advanced health information systems. Communication security issues have been specified and implemented, while application security challenges such as privilege management and access control are still under development. Therefore, a series of formal models have been developed by the authors covering, e.g. domains, service delegation, claims control, policies, roles, authorisations, and access control. The required models are introduced and interpreted in a generic way. The crucial concept of security policy and its relationship to the other concepts has been considered in detail. Conclusion: Based on formal models, security services can be integrated into advanced systems architectures enabling semantic interoperability in the context of trustworthiness of communication and co-operation.

This paper describes an approach for generating customized benchmark applications from a software architecture description using a Model Driven Architecture (MDA) approach. The benchmark generation and performance data capture tool implementation is based on widely used open source MDA frameworks. The business logic of the benchmark application is modeled in UML and generated by taking advantage of the existing generation "cartridges" so that the current component technology can be exploited in the benchmark. This greatly reduces the effort and expertise needed for benchmarking with complex component technology. We have also extended the MDA framework to model and generate a load testing suite and automatic performance measurement infrastructure. The approach complements current model-based performance prediction and analysis methods by generating the benchmark application from the same application architecture that the performance models are derived from. This provides the potential for tightly integrating runtime performance measurement with model-based prediction either for model validation or improving model prediction accuracy. We illustrate the approach using a case study based on EJB component technology.

Integrated health care systems Systems analysis Software process engineering Model-Driven Architecture Semantic interoperability Unified process HL7 a b s t r a c t Background: Semantic interoperability is a basic challenge to be met for new generations of distributed, communicating and co-operating health information systems (HIS) enabling shared care and e-Health. Analysis, design, implementation and maintenance of such systems and intrinsic architectures have to follow a unified development methodology. Methods: The Generic Component Model (GCM) is used as a framework for modeling any system to evaluate and harmonize state of the art architecture development approaches and standards for health information systems as well as to derive a coherent architecture development framework for sustainable, semantically interoperable HIS and their components. The proposed methodology is based on the Rational Unified Process (RUP), taking advantage of its flexibility to be configured for integrating other architectural approaches such as Service-Oriented Architecture (SOA), Model-Driven Architecture (MDA), ISO 10746, and HL7 Development Framework (HDF).

More than five years ago, the OMG proposed the Model Driven Architecture (MDA™) approach to deal with the separation of platform dependent and independent aspects in information systems. Since then, the initial idea of MDA evolved and Model Driven Engineering (MDE) is being increasingly promoted to handle separation and combination of various kinds of concerns in software or data engineering. MDE is more general than the set of standards and practices recommended by the OMG's MDA proposal. In MDE the concept of model designates not only OMG models but a lot of other artifacts like XML documents, Java programs, RDBMS data, etc. Today we observe another evolutionary step. A convergence between MDE and DSL (Domain Specific Language) engineering is rapidly appearing. In the same way as MDE is a generalization of MDA, the DSL engineering may be viewed as a generalization of MDE. One of the goals of this paper is to explore the potential of this important evolution of engineering practices. In order to anchor the discussion on practical grounds, we present a set of typical problems that could be solved by classical (object-oriented and others), MDE, or DSL-based techniques. Solutions to these problems will be based on current platforms (EMF, AMMA, GME, etc.). This paper illustrates how powerful model-based frameworks, allowing to use and build a variety of DSLs, may help to solve complex problems in a more efficient way.

Innovation and value proposition in distance-learning-programs (e-learning programs) is a multifaceted-activity with enormous dimensionality. The implementation of information communication technology (ICT) and enhanced enterprise-resource-planning (eERP) for smart-campuses has emerged as inevitability for industrial competitiveness in smart-factories as per the dictates of total quality management (TQM). The philosophy of productivity-management and concurrent engineering stipulates a competitive framework for e-learning for dissemination and absorption of knowledge by the intelligentsia, technologists and students. Conversely, competitiveness in today's global village demands an innovative and systems-approach for improving the learning-curves in a virtual environment. The e-learning-programs have numerous inherent perplexities since in every virtual classroom there is a much higher probability to interact with orthogonal-cultures that too with multiple-intelligences. This paper proposes a “conceptual-strategic-planning-framework” for diffusion of innovative in a distance learning program (Course-Technovation). The framework is based on literature review and field visits encompassing integrated “E-commerce-model-driven architecture” embedded with business intelligence and coupled with eERP-design functionalities.