REQUIREMENTS !

I am reading the beautiful book "More About Software Requirements: Thorny Issues and Practical Advice" by Karl E. Wiegers. I'd like to share with you two of the most important points of his "10 cosmic truth",  that to me are #6 and #9. #6 The requirements might be vague, but the product will be specific. I would say this is the usual point of "Natura abhorret a vacuo", that is here... each gap n requirements will be filled by some bad feature. #9 The customer is not always right, but the customer always has a point. Never underrate your key users

Something we should never forget: some people use the products, some OTHER people gathers requirement for those products. So, to gather requirements is as easy as... walking on water. When it's frozen .

In writing requirements, synonyms do not exist . An example is "tree" and "plant".  The two words seem similar, but they have different meanings. Tree:   "a usually tall plant that has a thick, wooden stem and many large branches" Plant:   "organism belonging to the vegetable kingdom" Please note also that tree can mean"a drawing that connects things with lines to show how they are related to each other", while plant suggests a "factory and its buildings and equipment".

We do like Don Estes' blogs: we always find something to learn.. This page is about Business Rules, but you will find many interesting concepts abut requirements. I think this two images are very important, too