In keeping with our requirements work, we will start by identifying the attributes of a good requirement. We start our project off with the requirements, so it stands to reason if we start off poorly or in the wrong direction, we will not make the objective. This situation will get worse the longer we spend […]
Continuous Deliver and Embedded Automotive I have worked on projects that employed continuous delivery for embedded products. The embedded product was an automotive component. The core of the software (the operating system) was specified using conventional approach. This operating system consisted of the maximum model requirements for this globally used component. The component looked and […]
Documentation and Rework Once, a long time ago, I worked at a company that was having some difficulty coordinating their development work. The product that was produced was a complex arrangement of mechanical and electrical / electronic systems. The company was ISO certified and had documentation describing how they would work, including configuration and change management. […]
In the purchasing contract with a tier one supplier, the expected the “0-kilometer” quality or failure rate is not to exceed 500 parts per million (ppm). These are failures seen before the product leaves the OEM manufacturing floor requiring product rework on the assembly line or as the vehicle rolled off the end of the […]
The Emissions Tango There is so much to learn from this case for those who develop products for a living and automotive products in particular. Understanding the impact of concept selection and testing of the product on the project’s success and product quality is important. The early decisions we make regarding the development of the […]
Poor Excuse for Not Automating Testing Recently I came across and participated in a social media exchange that proposed that automating product testing (software) was not helpful. Their assertion was backed with comments about personnel new to testing who cannot learn how to test. Testing and System Complexity System and software complexity, the number of […]
Recently I was talking with a company that has achieved the level 3 (defined) CMMI from the Software Engineering Institute that provides a measure of an organizations maturity and capability. During this conversation, I had a flash to another company that had aspirations of being a level 3 but could never make it beyond their […]
Below is an excerpt from our book, Project Management of Complex and Embedded Systems for those that believe the “V” model means single pass product development (as if) – think again! This book has a significant automotive perspective, complex, highly tooled machines that must meet and government regulations. Embedded Development Overview[1] Embedded software development […]
By Jon M Quigley We have discussed the Failure Mode Effects technique a few times in the past. Though Failure Mode Effects and analysis seems to be a powerful tool, the problem is you do not know if the FMEA is effective and perhaps you will never know. The Failure Mode Effects Analysis tool, theoretically, allows […]
Project Management Tools and Risk Management There still remains meat on the bones of this study from Software Advice. On LinkedIn, Joe Hessmiller had an observation that Client relationship and Risk management was far down on the list of concerns. Under the heading More Buyers Request Advanced Functionality Than Basic[1] client management and risk management was […]