Difference between revisions of "EGF"

From Eclipsepedia

Jump to: navigation, search
(Roadmap)
(Roadmap)
Line 40: Line 40:
 
* Common features: release engineering, JUnit tests
 
* Common features: release engineering, JUnit tests
 
* Portfolio: EMF patternization for EMF customization (initial version)
 
* Portfolio: EMF patternization for EMF customization (initial version)
 +
<br>
  
 
=Team=
 
=Team=

Revision as of 06:08, 15 December 2009

Contents

Introduction

The EMFT EGF project is part of EMFT (EMF Technology).

In order to improve the software development industrialization, a major step consists in mass-producing software. This mass-production must be customizable, and must be able to support complex, large-scale and heterogeneous generations. Given the today’s available Eclipse tools, the issue here is not to provide either a new transformation engine (model-to-model, model-to-text, text-to-model, text-to-text) or DSL (Domain-Specific Language) editor but to realize their integration for flexible software mass-production. This is the purpose of EGF.

EGF federates generation around the pivotal element of factory component. A factory component is a unit of generation with a clear objective of generation. It has a contract to declare the factory component parameters. Contrary to a classic generation which aggregates all the generation parameters, generation data are organized by viewpoints, such as generation pattern, license description or deployment declaration. Altogether, viewpoints explicitly configure all the generation parameters. The generation orchestration is defined by a production plan. A generation step of the production plan can either be a Java task or, by assembly, an invocation to another factory component. Regarding the lifecycle, a factory component can be edited and executed.

A factory component encapsulates generation know-how. A portfolio is a consistent set of factory components with a common generation objective, valuable for a development team or a user community. The purpose is to create off-the-shelf factory components. For instance, a technical infrastructure factory provides all the needed mechanisms for an application development (e.g., transaction management, persistence policy).

Resources

Factory Components
Proposal
Contact

Development

Roadmap
Team
Report a bug


Roadmap

EGF 0.1.0 - Eclipse 3.5 - July, 2009

  • Edition and execution of factory component
  • Generation Pattern edition and execution with Jet-1


EGF 0.2.0 - Eclipse 3.5 - December, 2009

  • Common features: Storage: in fcore files, Dynamic execution of factory component and task, UI improvement
  • EGF structure: Extensibility of EGF in order to support contributions (e.g. new viewpoints)
  • Pattern: Improvement of pattern inheritance, pattern call, infrastructure able to support new engines


EGF 0.2.1 - Eclipse 3.5 - January, 2010

  • Common features:
  • EGF structure: improvement of generation workflow
  • Pattern: Improvement pattern call, pattern strategy, pattern template editor


EGF 0.3.0 - Eclipse 3.5 - March, 2010

  • Common features: release engineering, JUnit tests
  • Portfolio: EMF patternization for EMF customization (initial version)


Team

The component developers are :

Contact

Any issue should be reported to the Bugzilla You may also contact the team using the EMFT newsgroup.