Software: Right direction

Continuous testing process

In the final article in the series, Niroshan Rajadurai from Vector Software discusses future implications of software testing with the introduction of dev-ops and continuous delivery software production methods

 

Dev-ops and continuous delivery are the current buzzwords surrounding application development methods. While distinctly separate, the methodologies have similar aims to align more closely the communities and processes involved in software development and deployment.

These aims help reduce the cost, time and risk of delivering changes, and ultimately increase value to customers by combining resources to allow more incremental changes to applications in production. While the terminology dev-ops and continuous delivery might be new, the principles they uphold are not.

Rewind to the early 1900s; Henry Ford was pioneering his own version of dev-ops. Early automotive production teams were highly skilled, cross-functional teams who manufactured, assembled and tested each vehicle to produce the optimum quality output. Ford’s goals were in common with ours today – to increase time to market and quality to gain a competitive edge. Even in this age, teams were working with an Agile approach, adapting quickly to changing needs and requirements of their customers.

So what has changed for our generation, how have things become so complicated? Put simply, an increase in volume, consumer expectation and demand, and the sheer advance in technological capability – we want it all and fast.

Henry Ford’s wisdom and insight meant he focussed on two main ingredients he thought necessary for success – the ability to repeat processes and standardise inputs and outputs. These two key practises helped reduce costs and increase quality, and these are exactly the same goals we strive for today. Understandably, the market has changed dramatically in scale and complexity since Ford’s time but standardisation and repeatable processes are at the heart of successful dev-ops and continuous delivery.

For software engineers in the 21st century, standardisation of inputs enables the repetition of processes that leads to system automation and the ability to manufacture a vehicle that satisfies not only consumer demand but industry regulations. The view of a dev-ops approach is positive overall. At worst, the feeling is one of confusion about how to implement such a strategy. What is certain is that without the standardisation of inputs we are taken back more than 100 years to manual methodologies, which in the current climate would not produce vehicles fit for purpose.

Once understood, the benefits of a dev-ops approach are extensive, but what are the implications for the modern day automotive manufacturer?

As discussed previously, embedded software in the automotive industry is big business capable of swaying brand loyalty. The challenge with a dev-ops methodology in this sector is that automotive manufacture, and specifically embedded software development, is so fragmented. One of the goals of dev-ops is to align functionally separated departments, but with such a plethora of tools across the supply chain, creating and testing to prove software quality is a challenge.

In this safety critical industry, sub-standard software is simply not an option with so many features and functions relying on embedded software. In reaction to this Asil, Autosar and ISO 26262 have been introduced to mitigate catastrophic failures, but still software glitches continue to make the news – Fiat and Jeep to name just two in 2015. Industry analysts have mooted that the auto industry will not be able to adopt ISO 26262 across the entire supply chain before 2020 as was hoped.

So what can be done to ensure a quality standard and compliance? As an interim, some major manufacturers are implementing ISO/IEC 15504 Software process improvement and capability determination (Spice) as a cross-functional standard for software quality and testing compliance as it is more straightforward to implement and prove that adequate testing has been achieved.

With so many regulations to comply with and numerous invested parties, it is clear to see that a more simple yet comprehensive answer needs to be found. If a dev-ops culture is the future of automotive manufacture, an easier way needs to be found to allow everyone in the supply chain to work together to uphold a quality standard and meet production deadlines.

IT is a central component of the dev-ops method, and with most of the development in the automotive industry being software driven, it comes as no surprise that an answer lies in improving processes through IT service delivery and removing computer-based tooling constraints. Dev-ops focuses on bringing people and teams together through improving collaboration between operations and development. Testing is a fundamental process in development and impacts on operational departments and so becomes the lynch pin.

Optimising a testing infrastructure by offering a common platform with test automation facilitates the dynamic structure that dev-ops demands. With such a focus on requirements-based testing and meeting changing customer needs, a test driven development practice with a test suite that offers functionality such as auto test code generation has to be the way forward, especially given the increasing speed of software development life cycles. Shortening the lead time for software tests through automation ensures that valuable time can be regained to develop software and APIs to enhance quality and therefore customer satisfaction.

Failure to involve downstream departments such as operations in a dev-ops environment means the production bottleneck is simply shifted further to the right. By making the software testing suite accessible to all, everyone can reap the benefits of faster testing, continuous and safe services delivered on time and on budget, with applications always being release ready. A report by Gartner says “to deliver at dev-ops speed and scale, the technology framework must be designed for human by exception, where as much work as possible is performed by programmatic means”.

With the challenge of accommodating changing requirements and the cyclical nature of the dev-ops environment, an automated testing platform allows all engineers the ability to test earlier; tests are faster and can be repeated as often as necessary. Extensive automation, whether it be test automation or application release automation, should become the hallmark of a dev-ops team. Not only does automation increase the speed at which products can be released but it also reduces the opportunity for human error that is a given in manual processes, thus increasing software quality. In a compliance-driven world, automating testing processes and a common platform make it easy to provide proof of compliance and provide seamless integration across the tool chain.

 

Conclusion

It is clear that a dev-ops approach fits with the automotive industry’s goals to produce vehicles with maximum software quality, minimal technical debt, and a fast time to market. The hurdle is being able to roll out an effective dev-ops environment with the right tools. Over time, if a common testing platform is implemented the catalogue of automated test cases will increase in line with the rate of change based on developing customer requirements. Achieving this will allow manufacturers to release products faster and with greater confidence in software quality.

 

Niroshan Rajadurai is director of EMEA for Vector Software

 

See Part 1

See Part 2

See Part 3

 

www.vectorcast.com

 

Recommend to Colleagues: