Manufacturers apply application lifecycle management (ALM) tools in an effort to counter the ever-increasing degree of complexity in the automotive industry and in response to the Automotive SPICE requirement for consistent traceability throughout a vehicle’s lifecycle. These tools make it possible to create links between all stages in a development model. The ALM tool codebeamer, for example, is used for central requirements management, software development, hardware development and test management. Codebeamer makes it possible to interlink all stages of development – from drawing up the system specification through to the SOP for a vehicle model. In order to make the numerous advantages of this tool available to customers quickly and throughout companies, the ASAP Group offers a full spectrum of development and integration services for codebeamer. These range from data model and template development to process development in accordance with Automotive SPICE, extension, adapter and methods development, rapid prototyping, automation, project migration and third-level support.
Cross-funktional Teams
ASAP relies on cross-functional teams made up of experts in project and process management, Automotive SPICE, E/E test management, migration and software. The advantage of this approach becomes clear when developing the data model for codebeamer: this involves defining the data model’s basic structure, including all roles, sub-disciplines, domains and reporting requirements, which requires a highly developed understanding of development as a whole. In addition to data model development, ASAP also analyses the development processes and provides advice – such as whether and how these processes can be mapped in codebeamer, or whether adjustments may be needed to ensure A-SPICE compliance. In addition, ASAP has in-depth expertise in relation to the implementation of codebeamer and can refine the tool to meet customer-specific requirements by creating extensions. This means that even highly individual functions can be integrated, with newly developed features forwarded by ASAP to the tool manufacturer for long-term integration and maintenance. As a result, codebeamer can be customised to fulfil the requirements of individual sub-disciplines, making it suitable for use as a central development platform in companies.
Integration of PAK for linking processes, data models and methods
ASAP also develops the adapters required to connect all development tools with codebeamer, which makes exchanging data with the tool as straightforward as possible for all specialist departments. These adapters facilitate a direct exchange of data and thereby also create hard links between data. The challenge lies in creating the necessary interfaces, which may require the integration of business logic to ensure proper data transformation between tools. ASAP therefore uses its Process Automation Kit (PAK) to implement this as quickly and flexibly as possible.
The PAK is a framework for individual, reusable automations and a useful addition to conventional DevOps practices. This automation solution’s modular system concept makes it possible to define and automate development steps for specific developer roles and reuse these later for other processes. Using the PAK, ASAP defines the methods in individual sub-disciplines and creates the interfaces between codebeamer and the required development tools. The PAK guides developers through the workflow defined for them, which leaves more time for creative, value-adding work and improves employee satisfaction. The PAK automatically starts the tools required for the activity, informs the users of the activities they need to carry out, stores all the information and, finally, automatically transfers the required information to codebeamer and the repositories.
ASAP and its automation solution therefore ensure that there is always a link between the abstract process, the data model in codebeamer and the method to be followed. Workflows can be quickly defined in the PAK, which facilitates use of the rapid prototyping approach. It may be helpful to consider a brief use case: if a department’s data model is already integrated in codebeamer but no decision has yet been taken regarding development tools and methods, it would not make sense to implement fixed interfaces at this point. In this case, the PAK offers a clear advantage, as different development tools can be connected with codebeamer quickly and relatively easily. This provides the flexibility needed to try out the tools at their disposal – and determine which are most suitable – before making a final decision. The fixed interface, which requires more extensive programming, is then created following test operation. Then, in ongoing series operation, ASAP migrates all development artefacts into codebeamer, starting by preparing the source system to ensure it is compatible with the target system, codebeamer. In this step, ASAP designs, develops and implements automation solutions that remove the need for manual data migration. ASAP also produces training videos and documentation, holds training sessions and workshops, and provides change management to support the transition to codebeamer.