This resource is no longer available
When Karl Wiegers was a software developer, he once reached the end of a project and realized he forgot to implement one of the agreed-upon requirements.
Wiegers came to two conclusions. First, he noted that the least consequence of such an error is unexpected rework and delay. More severe outcomes could include delayed product certification or even potential catastrophe. Second, he realized that his development process was inadequate since it allowed him to make this mistake.
In this report, learn how requirements traceability and embedded systems led Wiegers to success.