Home |  Download |  Documentation |  Domain Share |  Contact Author
Project Introduction

By pursuing the vision of creating intelligent solutions through the use of MDA, SOA and Web Services, this project presents research conducted with the purpose of proving that domain-driven approaches can promote a more efficient and rich development environment, which lay down an architecture that will adapt to ongoing changes in the business environment.
mda4eclipse is currently on its early stages and aims to create a composition of development tools capable of controlling software development life-cycle. The professional version of the plug-in will be composed of 3 modules:
  1. The MDA environment, which will be responsible for modelling the business domain and generate the application code;
  2. The Assessment environment, which will be responsible of controlling the development cycle, regarding requisite, business models, software code, and test cases artefacts.
  3. Domain-sharing environment, which will be responsible for controlling the distributed and cooperative domain sharing development.
mda4eclipse basically consists of a set of integrated tools, such as the Eclipse IDE, and other co-related projects like testing, modelling, and metrics.

Features

In every project, artefact development is standardized, both by the way analysis and design models are conceived and the way in which the software is generated. If modelling and code generation are done in a standard way, regardless of the project site, sharing domain models from project to project becomes possible. Therefore, all that the architect needs to do is to locate if the service one needs is available at any project site and download it. After obtaining this model the MDA framework will generate the same product as the one in the original project.

For example, whenever a new service is modelled, the architect is responsible for publishing it in the projects Web service. Any other project inside the organization might execute a look up query to try to obtain that service. If the architect finds the service model, it is incorporated within the business domain and might be altered to support specific business rules; if the architect does not find any service that matches one’s needs, then a new service model is created and published in the projects Web service.

Finally, the intention is to obtain development gains in scheduling and in cost. According to preliminary analysis results, the environment was able to use previously created domain models to give a head start to new projects, and consequently promote the necessary corrections to ensure the code generated is reliable and optimized.

mda4eclipse has the following dependencies:
  1. UML2 Tool Plug-in;
  2. Struts 2;
  3. Hibernate 3;
  4. MySQL;
  5. Ajax DWR;
MZ - Soluções em Gestão Empresarial Ltda | Copyright 2010