modeling.eatop/proposal.html - www.eclipse.org/proposals - Git at Google

 <!--
 	This document is provided as a template along with some guidance for creating
 	your project proposal. This is just a template. Feel free to change it as
 	you see fit (add sections, remove section). We feel, however, that the
 	suggestions represented in this document represent the reasonable minimum
 	amount of information to move forward.

 	Please keep the formatting in this document simple. Please do not edit
 	this document in Microsoft Word as it adds huge piles of markup that make
 	it difficult to restyle.

 	More information is available here:

 	http://wiki.eclipse.org/Development_Resources/HOWTO/Pre-Proposal_Phase

 	Direct any questions about this template to emo@eclipse.org
  -->

 <html>
 <head>

 <!--
 	Include the title here. We will parse it out of here and include it on the
 	rendered webpage. Do not duplicate the title within the text of your page.
  -->

 <title>EATOP</title>
 </head>

 <!--
 	We make use of the 'classic' HTML Definition List (dl) tag to specify
 	committers. I know... you haven't seen this tag in a long while...
  -->

 <style type="text/css">
 dl {
 	margin-bottom:10px;
 }
 dt {
 	display: list-item;
 	list-style-position: outside;
 	list-style-image:
 		url(/eclipse.org-common/themes/Phoenix/images/arrow.gif);
 	margin-left: 16px;
 }

 dd {
 	margin-left: 25px;
 	margin-bottom: 5px;
 }
 </style>

 <body>
 	<p>
 		The EATOP project is a proposed open source project under the <a
 			href="http://www.eclipse.org/projects/project_summary.php?projectid=Modeling">Modeling
 			Project</a>.
 	</p>

 	<!--
 	The communication channel must be specified. Typically, this is the
 	"Proposals" forum. In general, you don't need to change this.
  -->
 	<p>
 		This proposal is in the Project Proposal Phase (as defined in the
 		Eclipse Development Process) and is written to declare its intent and
 		scope. We solicit additional participation and input from the Eclipse
 		community. Please send all feedback to the <a
 			href="http://www.eclipse.org/forums/eclipse.proposals">Eclipse
 			Proposals</a> Forum.
 	</p>

 	<h2>Background</h2>

 	<!--
 	Optionally provide the background that has lead you to creating this project.
  -->

 	<p>Modern vehicles are extremely complex embedded systems that
 		integrate software and hardware from a large set of contributors. In
 		order to cope with this complexity during development, it is getting
 		more and more common to use suitable abstractions, i.e., models that
 		allow for an early validation of important properties. In particular,
 		hardware models are used for analysis. Functional models, like Matlab/
 		Simulink or ASCET, are used in software development, in order to allow
 		for an early validation of software. On Electric/ Electronic (E/E)
 		architecture level, domain specific architecture description languages
 		like EAST-ADL, SysML or the AUTOSAR standard enable properties of the
 		system architecture to be modeled which facilitates system wide
 		analysis, design space exploration, reuse of development artifacts and
 		change management.</p>

 	<h3>EAST-ADL</h3>

 	<p>
 		EAST-ADL is a domain specific language to model functional-, system-,
 		software-, and hardware-architecture in the automotive domain.
 		EAST-ADL has been created by the ITEA (<a href="http://www.itea2.org/">www.itea2.org</a>)
 		funded project EAST/EEA. Further development has been done in two
 		funded projects ATESST and ATESST2. Since 2010 a European funded
 		project MAENAD (<a href="http://www.maenad.eu/">www.maenad.eu</a>)
 		maintains and extends the language with respect to electrified
 		vehicles and safety development lifecycle modeling. For long-term
 		maintenance and dissemination, the EAST-ADL association (<a
 			href="http://www.east-adl.info/">www.east-adl.info</a>) has been
 		founded. It maintains the meta-model definition and makes the latest
 		version available to the public.
 	</p>
 	<p>As of today, the EAST-ADL has been implemented and used through
 		the following tools:</p>


 	<ul>
 		<li>Eclipse MDT project Papyrus provides an UML2 profile for
 			EAST-ADL</li>

 		<li>The Eclipse Industry Working Group PolarSys - a successor of
 			the TOPCASED initiative and the OPEES project - provides an EAST-ADL
 			editor</li>

 		<li>The commercial tool MetaEdit+ from MetaCase provides a
 			meta-model implementation of EAST-ADL and generic editors authoring
 			EAST-ADL model instances</li>

 		<li>The commercial tool System Weaver from Systemite provides
 			editors for the EAST-ADL modeling</li>

 		<li>Further tools exist from Arcticus, Symtavision, Rapita,
 			RealTime@Work, and Chronos</li>
 	</ul>

 	<h3>Relationship to AUTOSAR</h3>

 	<p>
 		AUTOSAR (<a href="www.autosar.org">www.autosar.org</a>) is a software
 		architecture and configuration standard in the automotive industry. It
 		focuses on the software architecture for electronic control units
 		(ECU) in road vehicles, their deployment to networked ECU systems in
 		vehicles, and the configuration of the basic software in such ECUs.
 		The AUTOSAR Tool Platform User Group (Artop) develops and maintains a
 		platform with common base functionality for creating modeling tools
 		supporting the AUTOSAR standard.Artop essentially encompasses
 		implementations of the different releases of the AUTOSAR meta-model
 		plus a rich set of services and components for managing and processing
 		AUTOSAR models.
 	</p>
 	<p>The EAST-ADL meta-model has a close relationship to the AUTOSAR
 		meta-model as both address the model-based development part in a
 		process. EAST-ADL covers the function- and system-architecture and
 		AUTOSAR acts with the system configuration and software architecture.</p>


 	<h2>Scope</h2>

 	<!--
 	All projects must have a well-defined scope. Describe, concisely, what
 	is in-scope and (optionally) what is out-of-scope. An Eclipse project
 	cannot have an open-ended scope.
  -->


 	<p>EATOP is an Eclipse-based implementation of the EAST-ADL
 		standard, which is a domain specific architecture description language
 		(ADL) established in the automotive industry.</p>
 	<p>EATOP will be focused on providing the following main features:</p>

 	<ul>
 		<li>Implementation of important versions and revisions of the
 			EAST-ADL meta-model in EMF</li>
 		<li>Serialization/deserialization of EAST-ADL models/files
 			conforming to the EAST-ADL XSD schema</li>
 		<li>A tool platform and an exemplary basic IDE experience for
 			creating, managing, editing, validating, transforming or otherwise
 			processing EAST-ADL models in the Eclipse workspace.</li>
 	</ul>

 	<p>EATOP is intended to support the work of the EAST-ADL
 		association by providing an Eclipse-based tool platform implementation
 		for the EAST-ADL standard. Up to now, there have been multiple
 		initiatives to create Eclipse-based implementations of EAST-ADL which
 		led to a quite cluttered and redundant tool landscape. The goal of
 		EATOP is to reconcile these initiatives, consolidate the different
 		implementations and shape like a reference implementation of EAST-ADL
 		under the umbrella of this new Eclipse project.</p>
 	<p>Due to the complementary nature and close relation between
 		EAST-ADL and AUTOSAR, EATOP will be closely aligned with Artop. Most
 		important, EATOP will be based on the Sphinx modeling tool platform to
 		enable a maximum of interoperability between EAST-ADL and AUTOSAR
 		tools as well as the creation of integrated tool chains that cover
 		both standards and support a seamless transition between them.</p>


 	<h2>Description</h2>

 	<!--
 	Describe the project here. Be concise, but provide enough information that
 	somebody who doesn't already know very much about your project idea or domain
 	has at least a fighting chance of understanding its purpose.
  -->

 	<p>EATOP is an infrastructure platform implementation of common
 		base functionality for design tools that enable an effective usage of
 		the architecture description language EAST-ADL in software and systems
 		development.&nbsp;It includes the following capabilities:</p>

 	<ul>
 		<li>EMF based access to the EAST-ADL meta-model

 			<ul>
 				<li>Tools to generate an XML schema and an Ecore meta-model
 					from the Enterprise Architect sources of the EAST-ADL releases
 					published by the EAST-ADL association.</li>
 				<li>EMF-based meta-model implementations of several EAST-ADL
 					releases that provide EAST-ADL design tool developers with Java
 					APIs for manipulating EAST-ADL model instances. EATOP contains for
 					each supported EAST-ADL release the required meta-model
 					implementation. The first supported EAST-ADL releases is the
 					version 2.1.10.</li>
 			</ul>
 		</li>

 		<li>File based as well as database persistency management

 			<ul>
 				<li>EATOP provides in combination with Sphinx the functionality
 					to serialize and deserialize the instances of the EAST-ADL
 					meta-model within an EAXML file. The EAXML file is kind of a xml
 					file which contains the serialized form of the EAST-ADL meta-model
 					instances. Its content is conform to the xml schema of the
 					corresponding EAST-ADL release.</li>
 				<li>Database persistence of EAST-ADL models.</li>
 				<li>Management of EAST-ADL models spread over one or multiple
 					XML files in the Eclipse workspace.</li>
 			</ul>
 		</li>


 		<li>Basic Eclipse user interface support

 			<ul>
 				<li>A wizard for creation of an EAST-ADL project</li>
 				<li>A wizard for creation of an EAST-ADL file (.eaxml)</li>
 				<li>An EAST-ADL release preference page</li>
 				<li>A property page for EAST-ADL projects</li>
 				<li>An EATOP perspective</li>
 				<li>An EATOP explorer view which shows only EAST-ADL content
 					and the instances of the EAST-ADL objects in an EAST-ADL file</li>
 				<li>A property tab which shows the properties of EAST-ADL
 					object instances and allows to modify them</li>
 				<li>Undo/Redo functionality</li>
 				<li>Drag and drop functionality between EAST-ADL content</li>
 			</ul>
 		</li>


 		<li>To enable a seamless workflow in a development process,
 			interoperability and interfacing with other tools and platforms will
 			be provided


 			<ul>
 				<li>Bridges between EATOP and Papyrus and synchronization of
 					EMF-based EAST-ADL APIs with UML2 profile based EAST-ADL
 					implementations created with Papyrus.</li>
 				<li>Interface to requirements engineering tools (via ReqIF, see
 					Eclipse/RMF),</li>
 				<li>Interface to software modeling tools (e.g., via AUTOSAR)</li>
 				<li>Interface to other model-based design tools (e.g.
 					Matlab/Simulink)</li>
 				<li>Interoperability with domain independent abstractions of
 					EAST-ADL like the CESAR reference technology platform (<a
 					href="www.cesarproject.eu">www.cesarproject.eu</a>), the MBAT
 					reference technology platform (<a href="www.mbat-artemis.eu">www.mbat-artemis.eu</a>),
 					or PolarSys solution.
 				</li>
 			</ul>
 		</li>


 		<li>Further miscellaneous features will ease the handling of
 			EAST-ADL. Examples are

 			<ul>
 				<li>Model to model transformation between the different
 					abstraction layers within the EAST-ADL meta-model.</li>
 				<li>Variability management supporting both the definition of
 					variant-rich EAST-ADL models as well as creation of fully/partly
 					configured occurrences of these models representing individual
 					variants or variant subsets.</li>
 			</ul>
 		</li>
 		<li>Demonstrators

 			<ul>
 				<li>A standalone application that can be used to conveniently
 					explore EATOP without an existing Eclipse installation. It
 					demonstrates the features and capabilities of EATOP.</li>
 				<li>Experimental graphical editor to create and visualize
 					EAST-ADL based models.</li>
 			</ul>
 		</li>

 	</ul>


 	<h2>Why Eclipse?</h2>

 	<!--
 	Answer these two questions:	What value does this project bring to the Eclipse
 	community? What value do you expect to obtain from hosting your project at Eclipse?

 	What value do you get by having your project at Eclipse over and above the value
 	of hosting at Eclipse Labs?
  -->


 	<p>EATOP has been created in publicly funded European R&amp;D
 		projects. It consolidates the so far different implementations of the
 		EAST-ADL meta-model. Eclipse is more and more accepted as standard
 		tool platform in the automotive industry - the efforts made in the
 		Eclipse Automotive Industry Working Group are a good indicator for
 		that. For these reasons, Eclipse is a widely accepted place for a
 		project like EATOP and an ideal basis to guarantee its long term
 		availability and development.</p>

 	<p>Technically EATOP has many relations to Sphinx and to Artop.
 		Like Artop, EATOP is based on Sphinx. As the EAST-ADL meta-model has
 		many conceptual links to the AUTOSAR meta-model, EATOP naturally has
 		close relationships to Artop. Artop is an industry group driven
 		implementation of the AUTOSAR meta-model based on Eclipse. Therefore,
 		it is an obvious choice to base EATOP on Eclipse as well.</p>


 	<h3>Relationship with other Eclipse Projects</h3>
 	<p>The EATOP project will be based on and use Eclipse Platform,
 		EMF, EMF Transaction, and Sphinx to provide the core functionality. In
 		addition, EMF Validation, GMF and/or Graphiti will be used to support
 		validation and graphical editing of EAST-ADL models.</p>

 	<h2>Initial Contribution</h2>

 	<!--
 	Projects are expected to arrive at Eclipse with existing code.

 	Describe the existing code that will be contributed to the project. Please provide
 	a couple of paragraphs describing the code with modest detail, including important
 	information like code ownership (who holds the copyright?), and some consideration
 	of community that exists around the code. Include a listing of third-party libraries
 	and associated licenses.
  -->


 	<p>The initial contribution consists of sources, tests, build, and
 		documentation and is available in the EclipseLabs space of the Eclipse
 		Automotive Industry Working Group. It has been created within two
 		publicly funded European R&amp;D projects:</p>

 	<ul>
 		<li>MAENAD: Since 2010 the European funded project MAENAD (<a
 			href="www.maenad.eu">www.maenad.eu</a>) maintains and extends the
 			EAST/ADL language. The project encloses tool development. EATOP
 			consolidates the already existing exchange formats by the definition
 			of a common XML schema.
 		</li>
 		<li>SAFE: Since 2011 the ITEA2 project SAFE (<a
 			href="www.safe-project.eu">www.safe-project.eu</a>) works on a safety
 			related meta-model. As this meta-model mainly extends EAST-ADL, the
 			efforts spent on EATOP also helps to create the SAFE tool platform.
 			The SAFE project is organized in the framework of the ITEA2, EUREKA
 			cluster program. The work has been funded by the German Ministry for
 			Education and Research (BMBF), and by the French Ministry of the
 			Economy and Finance (DGCIS).
 		</li>
 	</ul>

 	<h2>Legal Issues</h2>

 	<!--
 	Please describe any potential legal issues in this section. Does somebody else
 	own the trademark to the project name? Is there some issue that prevents you
 	from licensing the project under the Eclipse Public License? Are parts of the
 	code available under some other license? Are there any LGPL/GPL bits that you
 	absolutely require?
  -->

 	<p>There are no known legal issues.</p>


 	<h2>Committers</h2>

 	<!--
 	List any initial committers that should be provisioned along with the
 	new project. Include affiliation, but do not include email addresses at
 	this point.
  -->

 	<p>The following individuals are proposed as initial committers to
 		the project:</p>


 	<p>The following persons are proposed as co-leads of the project:</p>

 	<dl>
 		<dt>Yue Ma, Itemis France (Eclipse expert, release engineering,
 			contribution/release process)</dt>
 		<dt>Stefan Voget, Continental Automotive (Domain expert,
 			community building)</dt>
 	</dl>

 	<p>The following individuals are proposed as initial committers to
 		the project:</p>

 	<dl>
 		<dt>Stephan Eberle, Itemis France</dt>
 		<dt>Judit Simon-Karlsson, Arccore</dt>
 		<dt>Daniels Umanovskis, Arccore</dt>
 	</dl>

 	<p>We welcome additional committers and contributions.</p>

 	<!--
 	Describe any initial contributions of code that will be brought to the
 	project. If there is no existing code, just remove this section.
  -->

 	<h2>Mentors</h2>

 	<!--
 	New Eclipse projects require a minimum of two mentors from the Architecture
 	Council. You need to identify two mentors before the project is created. The
 	proposal can be posted before this section is filled in (it's a little easier
 	to find a mentor when the proposal itself is public).
  -->

 	<p>The following Architecture Council members will mentor this
 		project:</p>

 	<dl>
 		<dt>Ed Merks, Itemis</dt>
 		<dt>Eike Stepper, ESC</dt>
 	</dl>

 	<h2>Interested Parties</h2>

 	<!--
 	Provide a list of individuals, organisations, companies, and other Eclipse
 	projects that are interested in this project. This list will provide some
 	insight into who your project's community will ultimately include. Where
 	possible, include affiliations. Do not include email addresses.
  -->

 	<p>The following individuals, organisations, companies and projects
 		have expressed interest in this project:</p>

 	<dl>
 		<dt>Johan Ekberg, Arccore</dt>
 		<dt>Gerhard Griessnig, AVL</dt>
 		<dt>Helko Glathe, Carmeq</dt>
 		<dt>Paul Hoser, BMW Car IT</dt>
 		<dt>Matthias Tichy Chalmers, University of Technology and
 			University of Gothenburg, Sweden</dt>
 		<dt>Lars Parteto, Chalmers University of Technology and
 			University of Gothenburg, Sweden</dt>
 		<dt>Stefan Kuntz, Continental Automotive GmbH</dt>
 		<dt>Philipp Cuenot, Continental Automotive France SAS</dt>
 		<dt>Ignacio Garro, Continental Teves</dt>
 		<dt>Ralph M&uuml;ller, Eclipse Foundation</dt>
 		<dt>Simon Burton, ETAS GmbH</dt>
 		<dt>Maged Khalil, FORTISS GmbH</dt>
 		<dt>Martin Hillenbrand, FZI Forschungszentrum Informatik</dt>
 		<dt>David Servat, Institut Carnot CEA LIST DILS/LISE</dt>
 		<dt>Sara Tucci, Institut Carnot CEA LIST DILS/LISE</dt>
 		<dt>Chokri Mraidha, Institut Carnot CEA LIST DILS/LISE</dt>
 		<dt>John Favaro, Intecs Informatica e Tecnologia del Software
 			S.p.A.</dt>
 		<dt>Lei Pi, Intecs Informatica e Tecnologia del Software S.p.A.</dt>
 		<dt>Andreas Graf, Itemis Germany</dt>
 		<dt>Matthias Biehl, KTH</dt>
 		<dt>Istvan Horvath, Mentor</dt>
 		<dt>Janne Luoma, Metacase</dt>
 		<dt>Juha-Pekka Tolvanen, Metacase</dt>
 		<dt>Ali Akar, MODELI::SOFT</dt>
 		<dt>Thomas Peikenkamp, OFFIS e.V.</dt>
 		<dt>Ramin Tavakoli Kolagari, Ohm University of Applied Science
 			N&uuml;rnberg</dt>
 		<dt>Friedhelm Stappert, Ohm University of Applied Science
 			N&uuml;rnberg</dt>
 		<dt>Christoph Hammel, Robert Bosch GmbH</dt>
 		<dt>Nigisti Ayele, Systemite</dt>
 		<dt>Mark Oliver Reiser, TU Berlin</dt>
 		<dt>Alexander Metzner, University of Applied Sciences Regensburg
 		</dt>
 		<dt>J&uuml;rgen Mottok, University of Applied Sciences Regensburg</dt>
 		<dt>Bernhard Bauer, University of Augsburg</dt>
 		<dt>Benjamin Honke, University of Augsburg</dt>
 		<dt>Hans Blom, Volvo Group Trucks Technology</dt>
 		<dt>Henrik L&ouml;nn, Volvo Group Trucks Technology</dt>
 	</dl>


 	<h2>Project Scheduling</h2>

 	<!--
 	Describe, in rough terms, what the basic scheduling of the project will
 	be. You might, for example, include an indication of when an initial contribution
 	should be expected, when your first build will be ready, etc. Exact
 	dates are not required.
  -->


 	<dl>
 		<dt>May 2013: Proposal published and announced to Eclipse
 			membership</dt>
 		<dt>September 2013: Creation review</dt>
 		<dt>October 2013: Submission of initial contribution and IP
 			review</dt>
 		<dt>November 2013: Check-in and initial contribution to Eclipse
 			Git repository; setup of builds; update sites / downloads; Bugzilla;
 			Wiki; Website</dt>
 		<dt>Tbd.: First EATOP release</dt>
 		<dt>Tbd.: Integration of EATOP in simultaneous release train</dt>
 	</dl>


 	<h2>Changes to this Document</h2>

 	<!--
 	List any changes that have occurred in the document here.
 	You only need to document changes that have occurred after the document
 	has been posted live for the community to view and comment.
  -->

 	<table>
 		<tr>
 			<th>Date</th>
 			<th>Change</th>
 		</tr>
 		<tr>
 			<td>24-May-2013</td>
 			<td>Document created</td>
 		</tr>
 	</table>
 </body>
 </html>
	<!--
	This document is provided as a template along with some guidance for creating
	your project proposal. This is just a template. Feel free to change it as
	you see fit (add sections, remove section). We feel, however, that the
	suggestions represented in this document represent the reasonable minimum
	amount of information to move forward.

	Please keep the formatting in this document simple. Please do not edit
	this document in Microsoft Word as it adds huge piles of markup that make
	it difficult to restyle.

	More information is available here:

	http://wiki.eclipse.org/Development_Resources/HOWTO/Pre-Proposal_Phase

	Direct any questions about this template to emo@eclipse.org
	-->

	<html>
	<head>

	<!--
	Include the title here. We will parse it out of here and include it on the
	rendered webpage. Do not duplicate the title within the text of your page.
	-->

	<title>EATOP</title>
	</head>

	<!--
	We make use of the 'classic' HTML Definition List (dl) tag to specify
	committers. I know... you haven't seen this tag in a long while...
	-->

	<style type="text/css">
	dl {
	margin-bottom:10px;
	}
	dt {
	display: list-item;
	list-style-position: outside;
	list-style-image:
	url(/eclipse.org-common/themes/Phoenix/images/arrow.gif);
	margin-left: 16px;
	}

	dd {
	margin-left: 25px;
	margin-bottom: 5px;
	}
	</style>

	<body>
	<p>
	The EATOP project is a proposed open source project under the <a
	href="http://www.eclipse.org/projects/project_summary.php?projectid=Modeling">Modeling
	Project</a>.
	</p>

	<!--
	The communication channel must be specified. Typically, this is the
	"Proposals" forum. In general, you don't need to change this.
	-->
	<p>
	This proposal is in the Project Proposal Phase (as defined in the
	Eclipse Development Process) and is written to declare its intent and
	scope. We solicit additional participation and input from the Eclipse
	community. Please send all feedback to the <a
	href="http://www.eclipse.org/forums/eclipse.proposals">Eclipse
	Proposals</a> Forum.
	</p>

	<h2>Background</h2>

	<!--
	Optionally provide the background that has lead you to creating this project.
	-->

	<p>Modern vehicles are extremely complex embedded systems that
	integrate software and hardware from a large set of contributors. In
	order to cope with this complexity during development, it is getting
	more and more common to use suitable abstractions, i.e., models that
	allow for an early validation of important properties. In particular,
	hardware models are used for analysis. Functional models, like Matlab/
	Simulink or ASCET, are used in software development, in order to allow
	for an early validation of software. On Electric/ Electronic (E/E)
	architecture level, domain specific architecture description languages
	like EAST-ADL, SysML or the AUTOSAR standard enable properties of the
	system architecture to be modeled which facilitates system wide
	analysis, design space exploration, reuse of development artifacts and
	change management.</p>

	<h3>EAST-ADL</h3>

	<p>
	EAST-ADL is a domain specific language to model functional-, system-,
	software-, and hardware-architecture in the automotive domain.
	EAST-ADL has been created by the ITEA (<a href="http://www.itea2.org/">www.itea2.org</a>)
	funded project EAST/EEA. Further development has been done in two
	funded projects ATESST and ATESST2. Since 2010 a European funded
	project MAENAD (<a href="http://www.maenad.eu/">www.maenad.eu</a>)
	maintains and extends the language with respect to electrified
	vehicles and safety development lifecycle modeling. For long-term
	maintenance and dissemination, the EAST-ADL association (<a
	href="http://www.east-adl.info/">www.east-adl.info</a>) has been
	founded. It maintains the meta-model definition and makes the latest
	version available to the public.
	</p>
	<p>As of today, the EAST-ADL has been implemented and used through
	the following tools:</p>


	<ul>
	<li>Eclipse MDT project Papyrus provides an UML2 profile for
	EAST-ADL</li>

	<li>The Eclipse Industry Working Group PolarSys - a successor of
	the TOPCASED initiative and the OPEES project - provides an EAST-ADL
	editor</li>

	<li>The commercial tool MetaEdit+ from MetaCase provides a
	meta-model implementation of EAST-ADL and generic editors authoring
	EAST-ADL model instances</li>

	<li>The commercial tool System Weaver from Systemite provides
	editors for the EAST-ADL modeling</li>

	<li>Further tools exist from Arcticus, Symtavision, Rapita,
	RealTime@Work, and Chronos</li>
	</ul>

	<h3>Relationship to AUTOSAR</h3>

	<p>
	AUTOSAR (<a href="www.autosar.org">www.autosar.org</a>) is a software
	architecture and configuration standard in the automotive industry. It
	focuses on the software architecture for electronic control units
	(ECU) in road vehicles, their deployment to networked ECU systems in
	vehicles, and the configuration of the basic software in such ECUs.
	The AUTOSAR Tool Platform User Group (Artop) develops and maintains a
	platform with common base functionality for creating modeling tools
	supporting the AUTOSAR standard.Artop essentially encompasses
	implementations of the different releases of the AUTOSAR meta-model
	plus a rich set of services and components for managing and processing
	AUTOSAR models.
	</p>
	<p>The EAST-ADL meta-model has a close relationship to the AUTOSAR
	meta-model as both address the model-based development part in a
	process. EAST-ADL covers the function- and system-architecture and
	AUTOSAR acts with the system configuration and software architecture.</p>


	<h2>Scope</h2>

	<!--
	All projects must have a well-defined scope. Describe, concisely, what
	is in-scope and (optionally) what is out-of-scope. An Eclipse project
	cannot have an open-ended scope.
	-->



	<p>EATOP is an Eclipse-based implementation of the EAST-ADL
	standard, which is a domain specific architecture description language
	(ADL) established in the automotive industry.</p>
	<p>EATOP will be focused on providing the following main features:</p>

	<ul>
	<li>Implementation of important versions and revisions of the
	EAST-ADL meta-model in EMF</li>
	<li>Serialization/deserialization of EAST-ADL models/files
	conforming to the EAST-ADL XSD schema</li>
	<li>A tool platform and an exemplary basic IDE experience for
	creating, managing, editing, validating, transforming or otherwise
	processing EAST-ADL models in the Eclipse workspace.</li>
	</ul>

	<p>EATOP is intended to support the work of the EAST-ADL
	association by providing an Eclipse-based tool platform implementation
	for the EAST-ADL standard. Up to now, there have been multiple
	initiatives to create Eclipse-based implementations of EAST-ADL which
	led to a quite cluttered and redundant tool landscape. The goal of
	EATOP is to reconcile these initiatives, consolidate the different
	implementations and shape like a reference implementation of EAST-ADL
	under the umbrella of this new Eclipse project.</p>
	<p>Due to the complementary nature and close relation between
	EAST-ADL and AUTOSAR, EATOP will be closely aligned with Artop. Most
	important, EATOP will be based on the Sphinx modeling tool platform to
	enable a maximum of interoperability between EAST-ADL and AUTOSAR
	tools as well as the creation of integrated tool chains that cover
	both standards and support a seamless transition between them.</p>


	<h2>Description</h2>

	<!--
	Describe the project here. Be concise, but provide enough information that
	somebody who doesn't already know very much about your project idea or domain
	has at least a fighting chance of understanding its purpose.
	-->

	<p>EATOP is an infrastructure platform implementation of common
	base functionality for design tools that enable an effective usage of
	the architecture description language EAST-ADL in software and systems
	development. It includes the following capabilities:</p>

	<ul>
	<li>EMF based access to the EAST-ADL meta-model

	<ul>
	<li>Tools to generate an XML schema and an Ecore meta-model
	from the Enterprise Architect sources of the EAST-ADL releases
	published by the EAST-ADL association.</li>
	<li>EMF-based meta-model implementations of several EAST-ADL
	releases that provide EAST-ADL design tool developers with Java
	APIs for manipulating EAST-ADL model instances. EATOP contains for
	each supported EAST-ADL release the required meta-model
	implementation. The first supported EAST-ADL releases is the
	version 2.1.10.</li>
	</ul>
	</li>

	<li>File based as well as database persistency management

	<ul>
	<li>EATOP provides in combination with Sphinx the functionality
	to serialize and deserialize the instances of the EAST-ADL
	meta-model within an EAXML file. The EAXML file is kind of a xml
	file which contains the serialized form of the EAST-ADL meta-model
	instances. Its content is conform to the xml schema of the
	corresponding EAST-ADL release.</li>
	<li>Database persistence of EAST-ADL models.</li>
	<li>Management of EAST-ADL models spread over one or multiple
	XML files in the Eclipse workspace.</li>
	</ul>
	</li>


	<li>Basic Eclipse user interface support

	<ul>
	<li>A wizard for creation of an EAST-ADL project</li>
	<li>A wizard for creation of an EAST-ADL file (.eaxml)</li>
	<li>An EAST-ADL release preference page</li>
	<li>A property page for EAST-ADL projects</li>
	<li>An EATOP perspective</li>
	<li>An EATOP explorer view which shows only EAST-ADL content
	and the instances of the EAST-ADL objects in an EAST-ADL file</li>
	<li>A property tab which shows the properties of EAST-ADL
	object instances and allows to modify them</li>
	<li>Undo/Redo functionality</li>
	<li>Drag and drop functionality between EAST-ADL content</li>
	</ul>
	</li>


	<li>To enable a seamless workflow in a development process,
	interoperability and interfacing with other tools and platforms will
	be provided


	<ul>
	<li>Bridges between EATOP and Papyrus and synchronization of
	EMF-based EAST-ADL APIs with UML2 profile based EAST-ADL
	implementations created with Papyrus.</li>
	<li>Interface to requirements engineering tools (via ReqIF, see
	Eclipse/RMF),</li>
	<li>Interface to software modeling tools (e.g., via AUTOSAR)</li>
	<li>Interface to other model-based design tools (e.g.
	Matlab/Simulink)</li>
	<li>Interoperability with domain independent abstractions of
	EAST-ADL like the CESAR reference technology platform (<a
	href="www.cesarproject.eu">www.cesarproject.eu</a>), the MBAT
	reference technology platform (<a href="www.mbat-artemis.eu">www.mbat-artemis.eu</a>),
	or PolarSys solution.
	</li>
	</ul>
	</li>


	<li>Further miscellaneous features will ease the handling of
	EAST-ADL. Examples are

	<ul>
	<li>Model to model transformation between the different
	abstraction layers within the EAST-ADL meta-model.</li>
	<li>Variability management supporting both the definition of
	variant-rich EAST-ADL models as well as creation of fully/partly
	configured occurrences of these models representing individual
	variants or variant subsets.</li>
	</ul>
	</li>
	<li>Demonstrators

	<ul>
	<li>A standalone application that can be used to conveniently
	explore EATOP without an existing Eclipse installation. It
	demonstrates the features and capabilities of EATOP.</li>
	<li>Experimental graphical editor to create and visualize
	EAST-ADL based models.</li>
	</ul>
	</li>

	</ul>


	<h2>Why Eclipse?</h2>

	<!--
	Answer these two questions: What value does this project bring to the Eclipse
	community? What value do you expect to obtain from hosting your project at Eclipse?

	What value do you get by having your project at Eclipse over and above the value
	of hosting at Eclipse Labs?
	-->


	<p>EATOP has been created in publicly funded European R&D
	projects. It consolidates the so far different implementations of the
	EAST-ADL meta-model. Eclipse is more and more accepted as standard
	tool platform in the automotive industry - the efforts made in the
	Eclipse Automotive Industry Working Group are a good indicator for
	that. For these reasons, Eclipse is a widely accepted place for a
	project like EATOP and an ideal basis to guarantee its long term
	availability and development.</p>

	<p>Technically EATOP has many relations to Sphinx and to Artop.
	Like Artop, EATOP is based on Sphinx. As the EAST-ADL meta-model has
	many conceptual links to the AUTOSAR meta-model, EATOP naturally has
	close relationships to Artop. Artop is an industry group driven
	implementation of the AUTOSAR meta-model based on Eclipse. Therefore,
	it is an obvious choice to base EATOP on Eclipse as well.</p>


	<h3>Relationship with other Eclipse Projects</h3>
	<p>The EATOP project will be based on and use Eclipse Platform,
	EMF, EMF Transaction, and Sphinx to provide the core functionality. In
	addition, EMF Validation, GMF and/or Graphiti will be used to support
	validation and graphical editing of EAST-ADL models.</p>

	<h2>Initial Contribution</h2>

	<!--
	Projects are expected to arrive at Eclipse with existing code.

	Describe the existing code that will be contributed to the project. Please provide
	a couple of paragraphs describing the code with modest detail, including important
	information like code ownership (who holds the copyright?), and some consideration
	of community that exists around the code. Include a listing of third-party libraries
	and associated licenses.
	-->


	<p>The initial contribution consists of sources, tests, build, and
	documentation and is available in the EclipseLabs space of the Eclipse
	Automotive Industry Working Group. It has been created within two
	publicly funded European R&D projects:</p>

	<ul>
	<li>MAENAD: Since 2010 the European funded project MAENAD (<a
	href="www.maenad.eu">www.maenad.eu</a>) maintains and extends the
	EAST/ADL language. The project encloses tool development. EATOP
	consolidates the already existing exchange formats by the definition
	of a common XML schema.
	</li>
	<li>SAFE: Since 2011 the ITEA2 project SAFE (<a
	href="www.safe-project.eu">www.safe-project.eu</a>) works on a safety
	related meta-model. As this meta-model mainly extends EAST-ADL, the
	efforts spent on EATOP also helps to create the SAFE tool platform.
	The SAFE project is organized in the framework of the ITEA2, EUREKA
	cluster program. The work has been funded by the German Ministry for
	Education and Research (BMBF), and by the French Ministry of the
	Economy and Finance (DGCIS).
	</li>
	</ul>

	<h2>Legal Issues</h2>

	<!--
	Please describe any potential legal issues in this section. Does somebody else
	own the trademark to the project name? Is there some issue that prevents you
	from licensing the project under the Eclipse Public License? Are parts of the
	code available under some other license? Are there any LGPL/GPL bits that you
	absolutely require?
	-->

	<p>There are no known legal issues.</p>


	<h2>Committers</h2>

	<!--
	List any initial committers that should be provisioned along with the
	new project. Include affiliation, but do not include email addresses at
	this point.
	-->

	<p>The following individuals are proposed as initial committers to
	the project:</p>


	<p>The following persons are proposed as co-leads of the project:</p>

	<dl>
	<dt>Yue Ma, Itemis France (Eclipse expert, release engineering,
	contribution/release process)</dt>
	<dt>Stefan Voget, Continental Automotive (Domain expert,
	community building)</dt>
	</dl>

	<p>The following individuals are proposed as initial committers to
	the project:</p>

	<dl>
	<dt>Stephan Eberle, Itemis France</dt>
	<dt>Judit Simon-Karlsson, Arccore</dt>
	<dt>Daniels Umanovskis, Arccore</dt>
	</dl>

	<p>We welcome additional committers and contributions.</p>

	<!--
	Describe any initial contributions of code that will be brought to the
	project. If there is no existing code, just remove this section.
	-->

	<h2>Mentors</h2>

	<!--
	New Eclipse projects require a minimum of two mentors from the Architecture
	Council. You need to identify two mentors before the project is created. The
	proposal can be posted before this section is filled in (it's a little easier
	to find a mentor when the proposal itself is public).
	-->

	<p>The following Architecture Council members will mentor this
	project:</p>

	<dl>
	<dt>Ed Merks, Itemis</dt>
	<dt>Eike Stepper, ESC</dt>
	</dl>

	<h2>Interested Parties</h2>

	<!--
	Provide a list of individuals, organisations, companies, and other Eclipse
	projects that are interested in this project. This list will provide some
	insight into who your project's community will ultimately include. Where
	possible, include affiliations. Do not include email addresses.
	-->

	<p>The following individuals, organisations, companies and projects
	have expressed interest in this project:</p>

	<dl>
	<dt>Johan Ekberg, Arccore</dt>
	<dt>Gerhard Griessnig, AVL</dt>
	<dt>Helko Glathe, Carmeq</dt>
	<dt>Paul Hoser, BMW Car IT</dt>
	<dt>Matthias Tichy Chalmers, University of Technology and
	University of Gothenburg, Sweden</dt>
	<dt>Lars Parteto, Chalmers University of Technology and
	University of Gothenburg, Sweden</dt>
	<dt>Stefan Kuntz, Continental Automotive GmbH</dt>
	<dt>Philipp Cuenot, Continental Automotive France SAS</dt>
	<dt>Ignacio Garro, Continental Teves</dt>
	<dt>Ralph Müller, Eclipse Foundation</dt>
	<dt>Simon Burton, ETAS GmbH</dt>
	<dt>Maged Khalil, FORTISS GmbH</dt>
	<dt>Martin Hillenbrand, FZI Forschungszentrum Informatik</dt>
	<dt>David Servat, Institut Carnot CEA LIST DILS/LISE</dt>
	<dt>Sara Tucci, Institut Carnot CEA LIST DILS/LISE</dt>
	<dt>Chokri Mraidha, Institut Carnot CEA LIST DILS/LISE</dt>
	<dt>John Favaro, Intecs Informatica e Tecnologia del Software
	S.p.A.</dt>
	<dt>Lei Pi, Intecs Informatica e Tecnologia del Software S.p.A.</dt>
	<dt>Andreas Graf, Itemis Germany</dt>
	<dt>Matthias Biehl, KTH</dt>
	<dt>Istvan Horvath, Mentor</dt>
	<dt>Janne Luoma, Metacase</dt>
	<dt>Juha-Pekka Tolvanen, Metacase</dt>
	<dt>Ali Akar, MODELI::SOFT</dt>
	<dt>Thomas Peikenkamp, OFFIS e.V.</dt>
	<dt>Ramin Tavakoli Kolagari, Ohm University of Applied Science
	Nürnberg</dt>
	<dt>Friedhelm Stappert, Ohm University of Applied Science
	Nürnberg</dt>
	<dt>Christoph Hammel, Robert Bosch GmbH</dt>
	<dt>Nigisti Ayele, Systemite</dt>
	<dt>Mark Oliver Reiser, TU Berlin</dt>
	<dt>Alexander Metzner, University of Applied Sciences Regensburg
	</dt>
	<dt>Jürgen Mottok, University of Applied Sciences Regensburg</dt>
	<dt>Bernhard Bauer, University of Augsburg</dt>
	<dt>Benjamin Honke, University of Augsburg</dt>
	<dt>Hans Blom, Volvo Group Trucks Technology</dt>
	<dt>Henrik Lönn, Volvo Group Trucks Technology</dt>
	</dl>


	<h2>Project Scheduling</h2>

	<!--
	Describe, in rough terms, what the basic scheduling of the project will
	be. You might, for example, include an indication of when an initial contribution
	should be expected, when your first build will be ready, etc. Exact
	dates are not required.
	-->


	<dl>
	<dt>May 2013: Proposal published and announced to Eclipse
	membership</dt>
	<dt>September 2013: Creation review</dt>
	<dt>October 2013: Submission of initial contribution and IP
	review</dt>
	<dt>November 2013: Check-in and initial contribution to Eclipse
	Git repository; setup of builds; update sites / downloads; Bugzilla;
	Wiki; Website</dt>
	<dt>Tbd.: First EATOP release</dt>
	<dt>Tbd.: Integration of EATOP in simultaneous release train</dt>
	</dl>


	<h2>Changes to this Document</h2>

	<!--
	List any changes that have occurred in the document here.
	You only need to document changes that have occurred after the document
	has been posted live for the community to view and comment.
	-->

	<table>
	<tr>
	<th>Date</th>
	<th>Change</th>
	</tr>
	<tr>
	<td>24-May-2013</td>
	<td>Document created</td>
	</tr>
	</table>
	</body>
	</html>