ASPICE-Driven Reuse through effective rebasing Strategies

Home - Automotive - ASPICE-Driven Reuse through effective rebasing Strategies
ASPICE-Driven Reuse through effective rebasing Strategies

ASPICE-Driven Reuse through Effective Rebasing Strategies

There is a trend of incremental development of vehicular functionalities in the automotive industry which presents the opportunities of re-using the product artefacts for every product increment both in OEMs and tier 1 suppliers.

In software projects, for an efficient code reuse, a common practice involves branching out code from an existing project to establish the foundation for a new variant or product. However, this process presents challenges in maintaining traceability with requirements and design. Addressing this issue requires a strategic approach to rebase all the project artifacts while preserving traceability, especially in the context of Automotive SPICE (ASPICE) standards.

To achieve a successful rebasing within the spectrum of ASPICE, consider the following best practices:

Establish a Unified Tagging Mechanism:

Identify a consistent tagging mechanism for artifacts within the toolchain. Integration with scripts can facilitate the extraction of planned release labels. Encourage labeling for each engineering or production release, with major release labels in the product plan serving as reference points for branching out new variants or pursuing new customer projects.

Expose Labels in Top-Level Product Plans:

Utilize a well-structured configuration file (e.g., XML) to aggregate labels across various tools. This ensures visibility of labels at the top level of the product plan, providing a comprehensive overview of the release landscape.

Plan and Execute Baselining:

Systematically baseline all artefacts using traceable labels within the linked tools. This step is critical for maintaining a clear understanding of the relationships between different components, requirements, and design elements.

Scripted Branching Through Labels:

Develop scripts that navigate through the toolchain, pointing to respective labels in the product plan. This automated approach streamlines the branching process, reducing the likelihood of errors and ensuring consistency across the rebased artifacts.

Conclusion:
These are some of the best practices for organizations to navigate the complexities of rebasing project artifacts in adherence to ASPICE standards for reused products/ projects. This approach not only facilitates codebase reuse but also maintains a robust traceability framework, aligning with industry expectations and quality standards in the automotive domain.

SiriAB has the capability to address the complexities to develop and manage the requirements, accomplish systems engineering, design, implement and test the software for the ever-demanding and ever-growing automotive industry

About the author

Anand Kulkarni
Anand Kulkarni

Anand is a Senior systems engineer with extensive experience in Requirements
management, cyber security, and functional safety in automotive domain. He is currently working as Requirements Manager for our esteemed client.

Leave A Comment

Tags