16. April 2020
We have further improved our ASPICE Guide and it is now available as PDF or brochure in DIN A6 format. The new ASPICE® Guide contains notes and dependency diagrams that the experts at Knüvener Mackert have derived from the VDA Automotive SPICE® Guide. In this way, the ASPICE practices and the notes from the VDA guide can be read side by side, making the ASPICE guide extremely valuable for process improvement, assessment preparation and the assessment itself.
26. March 2020
How to make online trainings effective? Pros and cons of online training Are online trainings effective, and can they, therefore, be an alternative to classroom training? […]
9. March 2020
The strengths of agile development teams should be incorporated into the projects evaluated according to ASPICE criteria. Agile and ASPICE want the same thing: efficient development of good software. While in agile terms such as Epic, User Story, Backlog, Sprint are defined and lived, in Automotive SPICE™ project plan, defined milestones, quality management, configuration management etc. are in the foreground. In Agile SPICE, process attributes are now redefined to include agility in team orientation, flexible reaction to change and cooperation with the customer.
7. February 2020
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.