Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EGF"

 
(One intermediate revision by the same user not shown)
Line 30: Line 30:
 
| <br>  
 
| <br>  
 
| valign="top" | '''Follow up'''<br>  
 
| valign="top" | '''Follow up'''<br>  
[https://projects.eclipse.org/projects/modeling.emf.egf/documentation Planned and last releases]<br>[[EGF/Review|EGF Reviews]]<br>[[#Team|Team]]<br>[[EGF Partners|Partners]]<br>  
+
[https://projects.eclipse.org/projects/modeling.emf.egf/documentation Planned and last releases]<br>[https://projects.eclipse.org/projects/modeling.emf.egf/documentation  EGF Reviews]<br>[https://projects.eclipse.org/projects/modeling.emf.egf/who Team]<br>[[EGF Partners|Partners]]<br>  
  
 
|}
 
|}
 
= Team  =
 
 
The EGF committers are:
 
 
*[mailto:benoit.langlois@thalesgroup.com Benoit Langlois] ([http://www.thalesgroup.com/ Thales/TGS/SSE]), project lead
 
*[mailto:thomas.guiu@soyatec.com Thomas Guiu] ([http://www.soyatec.com Soyatec])
 
*[mailto:boubekeur.zendagui@obeo.fr Boubekeur Zendagui] ([http://www.obeo.fr Obeo])
 
*[mailto:laurent.goubet@obeo.fr Laurent Goubet] ([http://www.obeo.fr Obeo])
 
 
<br> Other main EGF contributors are:
 
 
*[mailto:matthieu.helleboid@thalesgroup.com Matthieu Helleboid] ([http://www.thalesgroup.com/ Thales/TGS/SSE])
 
 
 
<br>  
 
<br>  
  

Latest revision as of 12:26, 20 August 2014

Logo EGF.png

Introduction

EGF project page

The EGF project is part of EMF.

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).


Documentware

New And Noteworthy
Documents
Presentations
Proposal
Contact




Software

Download and Installation
Tutorial and use cases
EGF Portfolio
Report a bug
EMF/EGF newsgroup




Follow up

Planned and last releases
EGF Reviews
Team
Partners


Contact

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

Back to the top