AUTOSAR

AUTOSAR

Posts 1-4 of 4
  • Andreas Graf
    Andreas Graf    Premium Member
    The company name is only visible to registered members.
    Artop plans to contribute to Sphinx
    From: http://www.eclipse.org/proposals/sphinx/

    Sphinx is a proposed new open source project under the Eclipse Model Development Tools (MDT) subproject to provide an extensible platform that eases the creation of integrated modeling tool environments supporting individual or multiple modeling languages (which can be UML-based or native DSLs) and has a particular focus on industrial strength and interoperability.

    This project is in the Proposal Phase (as defined in the Eclipse Development Process) and this document is written to declare its intent and scope. This proposal is written to solicit additional participation and input from the Eclipse community. You are invited to comment and/or join in the development of the project. Please send all feedback to the eclipse.modeling.mdt forum.

    The initial code contribution will come from the Artop project. Artop is based on Eclipse and provides common base functionality for creating modeling tools supporting the AUTOSAR standard. AUTOSAR is a design standard from the automotive industry focusing on the system architecture of control software for road vehicles, its deployment to networked ECU (Electronic Control Unit) devices in vehicles, and the configuration of the basic software in such ECUs.


    Sphinx can therefore be seen as a generalization of the Artop idea aiming at a modeling tool platform for arbitrary design standards and modeling languages in arbitrary vertical domains being available under EPL. Thanks to the architecture of Artop, this can be achieved quite quickly: An important portion of the services and components in Artop has been realized in a generic way and is located in a separate layer (Eclipse Complementary Layer, ECL). It has no dependencies to the other AUTOSAR-specific layer of the platform (Artop AUTOSAR Layer, AAL) which contains the AUTOSAR meta-model implementations plus some related services and is subject to AUTOSAR IP regulations. The idea therefore is to move the complete ECL layer from Artop to Sphinx and provide mature initial implementations for the components proposed above right away.
    • 28 Feb 2010, 12:14 pm
  • User photo
    Henning Riedel
    The company name is only visible to registered members.
    Re: Artop plans to contribute to Sphinx
    Hi,

    Just wanted to ask, what the status of Sphinx is.
    There is just a proposal, but nothing else.

    Regards,
    Henning
    • 29 Sep 2010, 01:26 am
  • Dr. Stephan Eberle
    Dr. Stephan Eberle
    The company name is only visible to registered members.
    Re^2: Artop plans to contribute to Sphinx
    Hi,

    The current status of Sphinx is that the provisioning (i.e., creation of SVN repository, Bugzilla components, mailinglists, etc.) at Eclipse.org has been completed since this week. We are currently in the process of doing a last review of the part of the Artop code which we want to contribute (to be sure that it does not accidentally include any AUTOSAR references) and are looking forward to move it in at Eclipse.org by mid of October 2010.

    After that we will work on getting a build for Sphinx up and running such that we can provide a Sphinx SDK for download and a Sphinx update site. We also want to provide some more examples such as to have something like Artop Technology Demonstrator for Sphinx. We work upon making both available before Eclipse Summit Europe 2010 (Nov 2 - 4, 2010).

    Regards,

    Stephan
    • 29 Sep 2010, 12:06 pm
  • Will Zhong
    Will Zhong
    The company name is only visible to registered members.
    Re^3: Artop plans to contribute to Sphinx
    It sounds really nice.
    I am looking forwards to see that coming. The most great thing that working on a open source project (e.g. Artop) is that you could know what's going on.
    • 30 Sep 2010, 03:47 am