You are hereGoedelWorks v.2.6 - OpenComRTOS Qualification Package update

GoedelWorks v.2.6 - OpenComRTOS Qualification Package update

By eric.verhulst - Posted on 03 March 2015

Printer-friendly version

GoedelWorks is Altreonic’s environment for supporting engineering teams, small and large, in developing “trustworthy” products and systems. The environment is developed as a web application with a central server implementing Altreonic’s systems engineering meta-model. It supports engineering teams in defining Process flows, executing specific Engineering Projects and Work Flow management. Organisations can define their own Process flow or base it on the preconfigured ASIL process flow.

Keywords are traceability and configuration management from requirements to the smallest implementation detail. Within GoedelWorks a key entity in the Process flow is the Work Package. Team managers assign Resources, define a timeline (which is then displayed as a GANNT chart) whereby GoedelWorks will automatically generate a template for the concise but complete set of Activities and Artefacts that are needed for qualification. These Activities start with a Design activity and end with Confirmation Reviews. Contrary to many other solutions on the market, GoedelWorks provides and end-to-end solution and is domain independent, which simplifies the engineering process but also enhances the cooperation and communication between teams from different domains. For software specifically, an interface is provided to access the software repository.

The latest v.2.6 update contains numerous improvements and supporting tools that improve the usability. GoedelWorks itself is validated by in-house projects like the Qualification of the OpenComRTOS kernel and the development of a scalable electric vehicle.

OpenComRTOS V.1.6 Qualification Package updated

One of the projects developed in GoedelWorks is the OpenComRTOS Designer Qualification Package. Following an external review (for which GoedelWorks has support), some documentation issues were discovered and remedied. While this still requires manual work, a lot of time was saved because all the evidence and dependency relationships are stored in a central repository. All changes are logged as well.




Syndicate content