With fifth dimension testing, we use techniques more commonly employed by the “bad guys.” For example, we may execute techniques such as: Fuzzing Response modification using genetic algorithms Input breakdown Overflows Underflows This approach allows for evolution of our test collection. We can automate a significant number of these tests if we have a comprehensive, […]
Extreme testing occurs when we deliberately “torture” both the hardware and software to see what happens under undesirable conditions. Some examples of extreme testing include: Random voltages within the allowable voltage boundaries Voltage slews Deliberately introduced random noise on the data bus Extremely high bus loading (over 80% and sometimes over 90%) to see […]
Stochastic testing occurs when we allow a reasonably well-seasoned test engineer to go with their “gut” and feel their way about the product’s performance. During the development of numerous embedded automotive products, we have seen stochastic testing elicit roughly the same amount of test failures as combinatorial testing. We are not recommending that stochastic testing […]
Requirements management and configuration management are required for anything that even closely resembles effective testing. Experience suggests failing in these two areas unnecessarily complicates the product verification activities, and we will show some of those traumas in the next few posts. An iterative and incremental product development process calls for reviews throughout the development process. […]
We have witnessed a disconcerting trend. That trend is in consolidating risk reserves for projects into one, centrally managed bucket of money. This bucket was once reserved for the unknown-unknowns and was called a Management Reserve. However, more businesses are beginning to strip projects of their known-unknown Project Risk Reserves and placing calculated project contributions […]
By: Rick Edwards A good carpenter never blames his tools. There is also an aphorism “it is the poor musician who blames his instrument”. Why do so many good project managers blame their scheduling tool when their project schedule doesn’t fit their desired schedule? Project managers often struggle with documenting task dependencies utilizing the technology […]
We have recently had a discussion on what it takes to quality assure software. The discussion focused on FMEA and the role it plays in quality assurance. The discussion began to sound as if the FMEA was the panacea for poor quality. There is no silver bullet. To be sure the FMEA (which is essentially […]
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 […]
This may sound difficult, but there are some rules for good requirements. According to the International Council on Systems Engineering (INCOSE http://www.incose.org/chicagoland/docs/Writing%20Effective%20Requirements.pdf), requirements should have the attributes below (similarly can be found at IEEE): Necessary – driven by the objective of the project and business Verifiable – ability to objectively confirmed that the requirement is […]
We have been contemplating the ways we have seen employees respond to the consequences of a decision and the imminent resulting risk. We have noted these responses and know that there are at least two categories of response, Road Sign or Ambulance. Road sign people focus on moving the organization to a better place by […]