Archive for the
‘Testing’ Category

We have our requirements, our iterative packages and content defined, and now the developers are producing the iterations. During this time, the verification and test folks have been creating the test cases or details on how we intend to confirm the product performance. Our requirements provide the fodder for our testing.  For each requirement there […]

Once we have our captured our requirements. We identify the substance of the content for the iterations from the development.  In fact, recall from the requirements prioritization blog post. That work has given us some insight into how the iterative packages could be developed and what content or capabilities are to be delivered.  In the […]

You need not been so technically skilled to be able to see how many project fail due to requirements.  We provide a brief list of the failings below: Requirements control Insufficient time Did not include the sponsor or customer Late delivery of requirements Requirements traceability We will not write any more on requirements control that […]

We submit that a Failure Mode and Effects Analysis (FMEA) review is a form of design review. After all, one of the purposes of a design review is to try and remove defects before they appear in the product and that is the entire rationale for the FMEA in the first place. Yet, most of […]

We have hardly seen instances of this issue being discussed. We are painfully aware of the large extent we often require of configuration management because we have to work with tools in the embedded environment called “cross-compilers.” These tools allow the developer to work in a familiar programming language such as C and then produce […]

by Jon M Quigley Simulation activities can help evoke the requirements for a product without actually having to build the product first to learn something. Simulation need not be highly technical, though it can be. I have seen simulation of screens for an instrument cluster human machine interface (HMI) that made use of excel links […]

by: Jon M Quigley and Wally Stegall In the last blog post, we discussed how PPAP should be the quality system, although it is not in many cases.  One reason PPAP drops off the map after the start of production, it may have never been a concern during the design is the check box mentality. […]