Software tools: Fit for Purpose

Scania has a watch that lets lorry drivers monitor their vehicles

Mark Warren from Perforce Software discusses making software development fit for today's automotive market

 

The pace of change in the automotive market is rapid and demanding. The ability to be competitive in a challenging industry means vehicle and component manufacturers are having to innovate constantly, while at the same time address the need to keep costs down for their more discerning customers. Plus, there is the added requirement to comply with regulations, such as ISO 26262, and bring products and upgrades to market more rapidly.

Vehicles are increasingly dependent on software: it has been reported that an S class Mercedes-Benz requires millions of lines of code, indeed more than an advanced aircraft. In today's digital age, customers expect a great user experience and frequent updates in all aspects of their lives, including vehicles. In the commercial sector, features such as the ability to send information from drivers' cabs back to base are all helping to put software at the forefront of vehicle electronics. The internet of things (IoT) is a universal development trend and the automotive is one of its leaders, with examples including vehicle-to-vehicle communications for smart navigation, or smart devices, such as the watch recently introduced by Scania to enable lorry drivers to monitor their vehicle.

 

Processes and tools

In the same way that production line equipment revolutionised the car industry in the last century, software is doing the same for vehicle innovation in this one. In line with that, many organisations within the industry are re-assessing existing tools and processes to ensure they are fit for purpose and, in many cases, making significant investment to maintain efficiency and increase competitive advantage.

The industry is looking at the achievements in reducing delivery times in other industries for how to modernise their own processes. Agile software development is about being flexible and responsive, while always keeping the end goal in mind. It is also about being highly collaborative and responsive to change. The most widely adopted Agile methodology, Scrum, focuses on short, time-boxed iterations at the end of which there should be a work product that is capable of being used by the target customer.

Lean and Kanban are other methodologies that also have a focus on short iterations, although they tend to allow features to be shipped when ready, rather than waiting for some arbitrary end of sprint release date. The discipline of short, focussed releases encourages incremental changes rather than massive big-bang releases, thereby reducing risk and allowing plans to react to changing market or customer demands.

 

Continuous delivery

Continuous delivery (CD) could be considered an evolution from Agile and Scrum, with a greater focus on shortening the cycle from development to customer, with rapid feedback and iteration built in.

With CD processes, it is assumed that products are always releasable: in other words, at any one time, a product is ready for deployment, even though its development will continue to evolve. Automated systems allow all tested software to be deployed, potentially directly to customers. Of course, if physical products have to be built there will be breaks in the release pipeline while prototypes are built and tested or production systems updated, but having a goal of automating as far through the process with something that is potentially releasable is an important goal. Ultimately, the actual release into production and to customers is a decision for the business.

 

Removing barriers

As with any new methodology, Agile and CD are only as good as their execution; software development is littered with examples of bad practice or failed projects. There are typically a couple of reasons for this, notably culture and tools. For Agile and CD to be truly effective, they need to cascade down throughout the organisation, with the buy-in from the board downwards. They can represent a very different way of working for some people – for instance, the concept of fail early, recover quicker, rather than traditional waterfall style development. Creating internal champions, providing training and support are all essential to embedding these approaches in a company's development culture.

Secondly, Agile and CD can be let down by the software development tools the company is using, particularly if they have not been replaced or evolved during the past few years. As a rule of thumb, any development tools that have not had a major update in the past five years need closer scrutiny.

Common with other manufacturing industries, there is often a reluctance in the automotive sector towards changing software tools, especially if they were expensive and complex to purchase, deploy and manage. The inertia to change is inevitable, however if these tools aren't good enough to support today's challenges, then they certainly are not going to be for the next few years either and will soon become a hindrance rather than a help. There are several areas where change can be crucial.

 

Single source of truth

Consider the varied stack of hardware and software in a final product, such as memory, processors, drivers, graphics, documentation, test plans and simulators. Each may be created using multiple tools and processes, by different people in different teams and may be in different companies or countries. This can lead to a siloed approach to working, which undermines the co-ordination of rapid releases in a highly collaborative environment (on which methods such as Agile and CD are based). This is why, increasingly, companies are implementing a single repository for all the assets associated with a development project, not just code but cad drawings, documents and other supporting content.

This acts as both a single source of truth for the project's current status, but also provides information that can be referred to at a later date, giving detailed information over who did what, when and how. This is particularly important if, for instance, there is a query over ISO 26262 compliance. If required, that repository also provides the means to roll back to a previous version of the product or service in question.

Most organisations may already have software configuration management tools in place, also referred to as version control, version management or source code control. Those that have been in place for some time may not be able to cope with the kind of large binary data files associated with most modern design projects, the diversity of file types or rapid release cycles. So, it may be time to re-assess existing version management tools and, if multiple ones are in place, also look at consolidation onto fewer platforms.

Some will also be aware of the increasing popularity of an open-source version control system known as Git. It chimes well with the automotive industry's adoption of a more open approach and it has its benefits: this is a lightweight software development tool that is easy for software development teams to implement. However, it is not ideal for large binary files, protecting intellectual property or organisation-wide visibility and collaboration, which are the main reasons why there are now tools that enable individuals to continue using their beloved Git tools, while at the same time creating an environment that puts control – particularly around quality and scalability – back in the hands of IT management. So, where Git is part of the current software development environment, look for tools that bridge that gap.

Also look for tools that support automated testing processes. Testing is at the heart of CD in particular, making it easier to deal with the increased volume of testing required, particularly mundane testing tasks that invite human error. In the automotive sector, look for testing tools that support compliance testing (for example for Misra coding standards) and hardware simulators, creating high fidelity emulation and reducing the need for physical prototypes or production testing.

These are exciting times for automotive electronics designers and manufacturers. Software has amazing potential to take innovation to a whole new level, particularly with the advent of advanced driver assistance and driverless vehicles. However, for vehicle electronics companies to compete successfully in this brave new world, it clearly makes sense to review existing processes and tools to make sure they are going to drive that innovation, not create roadblocks.

 

Mark Warren is European marketing director of Perforce Software

 

www.perforce.com

Recommend to Colleagues: