Expand DevOps individually with a process automation suite
Automated Software Development: The ASAP Group has developed the Process Automation Suite, a framework for single, reusable automation that complements common DevOps practices.
Standardized and understandable processes, methods, and tools (PMT) are a prerequisite for successful automotive software development. OEMs and suppliers have always worked on an end-to-end landscape of processes, relying on automation and agile work. Despite all the automation, people remain the deciding factor: new processes must be monitored by all participants and the DevOps culture must survive. At the same time, standards and norms such as A-SPICE, ISO26262, and domain-specific features provide a complex framework.
The challenge is to pass on their tasks and what is expected of them to all operational developers in their specific roles. The ASAP Group, a partner in the development of the automotive industry, has developed the “Process Automation Kit” (PAK). An automation solution starts where others stop – at the developer level: PAK enables complex PMTs for organizations and their projects to be uniformly planned at the developer level and fully automated.
PAK focuses on people and is a suitable concept for any DevOps-oriented organization or those who want to become one as a meaningful addition to their automation.
One source of truth for automated process steps
With its modular system, PAK allows you to define and automate development steps for specific developer roles and use them in other processes. With PAK, a marketplace for process automation can be offered to all teams down to the organizational level or in PMTs across domains – which can be used and expanded across divisions.
This creates a method set in which all the automations of the process steps are stored, which does not require any creative work from the developer. Thus, the PAK serves as a single source of truth: all sections are based on the set of methods. The automation developed here is stored as “orders”, tested and approved, up-to-date and usable at any time for the newly developed processes.
Once developed, the commands can be used as often as you like in any future workflow model. Thus new processes can be automated more quickly. The result: Using a single process language ensures a uniform and consistent definition of processes and methods for all teams and projects. With PAK, developers no longer need to know the steps of the process by heart and have more freedom for creative development work. PAK frees you from process steps that don’t add value, guides you through the development process and informs you as soon as you need to take action. In this way, PAK not only ensures more time for creative performance, but also ensures that employees are more satisfied.
Many advantages to develop
In addition, developers benefit from the multilingual character of PAK: unlike most frameworks, commands can be written in any programming language. The automation tool can also be used at the lifecycle level. In the value chain of a new function, all process steps of a multi-user process can be combined into a continuous automated process.
Individual development steps cannot simply be skipped or forgotten – established quality standards and process compliance are reliably observed. In addition to significantly faster identification, fewer errors occur because automation prevents documents and their configurations from being stored incorrectly.
In addition to software development processes, all business processes can be automated using PAK. Thus, the tool serves as a basis for process development at A-SPICE Level 3, with subsequent adaptation of development projects (A-SPICE Level 2). Thus, with PAK, all the processes, methods and tools of an organization can be continuously designed at the developer level.
PAK: proven in practice
The fully automated original development tool has already been successfully used in OEM software and functionality development for ten years. Based on the requirements and results from productive use, the PAK has been fundamentally redeveloped using the latest technologies from the DevOps environment. The following example shows how much time was saved: Ten years ago, without automation, a total of about six working days was needed for a new integration case of full functionality and software development at an OEM.
At that time, there were about 50 integration suites per year. As of today, there are about 1,000 integration suites per year, where the developer only has to spend a maximum of 1.5 working hours. The rest is automated. Despite a twenty-fold increase in the number of integration stages per year, the number of developers deployed – and therefore development costs as well – remained stable. For more information on the PAK, see asap.de/pak.