Scope
<p dir="ltr"><strong>Eclipse SDV Hephaestus</strong> centralizes and standardizes build, tooling, and development environments across Eclipse SDV projects to reduce duplication, enable seamless integration and open-source development workflows.</p><p dir="ltr"><em><strong>In Scope</strong></em></p><ul><li dir="ltr" data-list-item-id="e1e6964685712f34b1fd9c09f9b037225">Bazel-based build and dependency management as the harmonized build system, enabling joint integration of multiple Eclipse SDV components</li><li dir="ltr" data-list-item-id="e7a10c828eb0e8b7edab8f0373e0f0312">Other build and dependency management systems e.g. Cargo should be supported</li><li dir="ltr" data-list-item-id="e457d7d2aff028050674b68444abefde6">Doc-as-Code via Sphinx-Needs, establishing a digital thread linking requirements to technical specifications and test execution results</li><li dir="ltr" data-list-item-id="ecbead9ff3161e16f05a7cec524acbbf6">Using the Eclipse Common Build Infrastructure</li><li dir="ltr" data-list-item-id="ed71498ad88839fa97a20f38683a5da45">Pilot adoption with <a href="https://projects.eclipse.org/projects/automotive.score">Eclipse S-CORE</a>, <a href="https://projects.eclipse.org/projects/automotive.opensovd">Eclipse OpenSOVD</a>, and <a href="https://projects.eclipse.org/projects/automotive.autoapiframework">Ecli… Automotive API Framework</a></li><li dir="ltr" data-list-item-id="e7dee003c87a833c260b7ec27ae924039">SIL KIT (Eclipse OpenXilEnv) as a candidate for tool integration.</li><li dir="ltr" data-list-item-id="e48b79deea2707106496990305e48c57b">Qualification process compliant with ASPICE and ISO 26262, preparation and tooling support only</li><li dir="ltr" data-list-item-id="eed256827994eeb519f367b71c0e3665f">Automotive Edge but exploring potential synergies between edge and cloud</li></ul><p dir="ltr"><em><strong>Out of Scope</strong></em></p><ul><li dir="ltr" data-list-item-id="ec9ec21b7532b33e4a7d1f44ee98dc910">Actual Safety Certification (such as receiving a final product certificate) and the management of associated liability are excluded, because this is considered as a part of a business model or private agreement between contractual partners</li><li dir="ltr" data-list-item-id="ef5043bb7761859d13c3772561dade19a">Mandatory integration of commercial or closed-source tools. These remain optional via well-defined plugin interfaces</li><li dir="ltr" data-list-item-id="e8d3d2a01382e88f087e005ace791447f">Replacing project-specific domain logic</li></ul>
