Who needs (final) requirements? | Cypress Semiconductor
Who needs (final) requirements?
I wrote an article last fall based upon a cartoon I saw over 20 years ago:
You lot start coding...I'll go and see what they want.
Embedded Systems Design has just published my article with the title: I don't need no stinkin' requirements! Unfortunately, it was missing this great cartoon that spurred the whole idea (and has stayed with me for over 20 years).
Is it really true? Well if you read the article you will see that I propose a design that doesn't need FINAL requirements and accommodates late changes, tries to minimize the impact of these changes.
Truly, we engineers (even though my card says marketing, my boss will confirm, sadly for him, that I am still very much an engineer) work frequently, and sometimes gladly, from few or ambiguous requirements, and our managers or project leaders are more concerned about that than we are. Because we quickly and constantly are designing in our heads; we write our own requirements on imaginary mental paper. But that's not all bad, as I hope my article supports.
Have a read, a few visitors have left comments on embedded.com with their own views, and it seems I was on the money. Share your thoughts, either at embedded.com or with one of the links below.