Focus on Well Documented Functional Requirements
by Nathan Weller
Every software product, no matter what its type or application, has Requirements. A Requirement is literally “that which is required; a thing demanded or obligatory”. Every software product created has a purpose – that which it is constructed to achieve – and thus will contain at least one Requirement. After all, if there is no purpose to a product, then it is not constructed – for to do so expends time, money and energy for no return.
Therefore, every software product has an aim. From this, it could easily be assumed that success of the product depends entirely upon the product achieving its preconceived aim. However, the real world is a lot more complex.
| Attachment | Size |
|---|---|
| Focus_on_well_documented_Functional_Requirements.pdf | 158.37 KB |
Sales pitch
I strongly suspect that Mr Weller is a salesman because it is obvious he is no Business Analyst. This document is no more than a sales pitch for his company. Highlighting the dangers and the sort of people you need to avoid them. I have no doubt that Mr Weller and co would be happy to assist anyone having the kind of problems he has highlighted.