20. December 2019
We are amazed by the demand for Automotive SPICE™ in China. Rapid progress is being made in the current megatrends in the automotive industry: new drive […]
29. August 2019
The open source world is full of frameworks and platforms. But what is a framework, what is a platform and what is the difference? More to the point, why is this difference important? I am a confessing pedant. Despite my personal failures in this regard, I believe deeply that correct usage of language provides significant added value.To quote the aphorism from Mark Twain: “The difference between the almost right word and the right word is really a large matter. ’tis the difference between the lightning bug and the lightning.”With this in mind, it may make sense that I find the lack of clarity surrounding the two concepts of framework and platform extremely irritating at times. Every company in the world that has anything to do with development has a platform. The open source world is full of frameworks. But when asked, very few people are able to define these concepts. Is it possible to claim full understanding of a subject yet be unable to provide clear definitions for basic terminology?
10. June 2019
Software quality is often treated as an elusive and mysterious goal. Everybody wishes to have it and the strategies for achieving quality are as varied as the companies that claim it. Interestingly enough, very few people are able to provide a clear statement of what software quality is. In my humble opinion this is the crux of the problem, how can a goal be achieved which isn’t clearly defined? There are actually a multitude of software quality definitions that can be found. As so often, Wikipedia provides an interesting starting point for study. The pragmatic difficulty with many definitions of quality is that they are qualitative descriptions and are strongly dependent on the observer’s viewpoint. A pragmatically useful definition of software quality must be objective, reproducible and must deliver quantitative results.
19. May 2019
In the last few months I have been investigating real-time systems and the conflict between two major approaches that are used. These confrontations have caused me to think more deeply about the concept of time-triggered systems and I am beginning to view this as a significant and valuable paradigm shift when compared with my earlier understanding.In order to set the stage properly, we need to start with an understanding of the concept of “real-time”. In this article I will be using “real-time” as a synonym for “deterministic”. This will require that every action that is performed in a real-time system must be done at the required moment (within predetermined margins of error and with a predetermined maximum level of uncertainty, aka jitter).
19. May 2019
Your company has decided to benefit by applying Automotive SPICE® in the development of software-controlled systems? There are many possible motivations for the decision to implement ASPICE including (e.g.) customer expectation, quality improvement, reduction of risks and costs, and improved management of growing complexity. Whatever your primary motivation may be, there are a number of things that must be considered. One factor that often dominates is the choice of the right external consulting and support.
22. March 2019
When a company considers implementing the ASPICE model, usually one question pop-up: can we achieve a return on investment? In this blog post, we examine the topic of ASPICE training ROI.Firstly, let’s talk about the costs of implementing ASPICE. When planning our project, we need to take into account that training costs are much more than the price of traveling, training and the exam/certification fees. Quite often the critical -hidden- costs are the time spent on training and the missing support and achievements in the projects during that time.In general, at any time there seem to be good reasons for postponing an Automotive SPICE® training due to budgetary or workload reasons. But working under this model does have a long list of benefits and is entirely possible to achieve a return on investment in the short or the mid-term.
9. March 2019
Automotive SPICE®, also known as ASPICE, is a standard used as a framework for improving and evaluating processes. The focus is on processes for development of software-based systems. An ASPICE Assessment is a systematic evaluation of the capability level an organizational unit’s processes against the ASPICE model. In other words, in an assessment your current processes are mapped to and compared with the best practices for software and software-based system development for the automotive industry.
28. February 2019
During my years in the medical technology industry I was able to observe a relatively small organization working many years on continuous and incremental improvement of a single core product. Reuse was an automatic result of our focus on a single core application domain and a single product that was evolved over the years. The connection to the customers was loose and delays were never more than an embarrassment.When I moved into the automobile industry the picture changed. I was a member of a large, internationally distributed department. We were working on multiple customer projects in parallel. Most of these projects had huge similarities but every single one had its unique distinguishing factors as well. Instead of a long-term evolutionary plan for a single product, each project was strongly time-bound, budget-bound and subject to constant close tracking and scrutiny by the customer.
22. January 2019
During the week from Dec 3rd to Dec 7th we lead a very successful training workshop “Automotive SPICE for Managers” at a customer in Detroit. 20 managers met outside the office for 2 days, in order to focus on how to drive the change to establish accepted processes.Firstly, we ensured that we are all on the same page according to motivation, objectives and roadmap. We shared some recent experiences and lessons learned and identified the different personal motivations for the same objective of having accepted processes well established. In a teamwork atmosphere a strategy, approaches and plans were developed and already some concrete actions were derived.