I didn't read the PDF but it seems a way to formalize the usual analysis of customer requirements. It goes like this: 1. Understand the business of the custome

I didn't read the PDF but it seems a way to formalize the usual analysis of customer requirements. It goes like this: 1. Understand the business of the customer, or any requirement won't make sense. 2. Learn the jargon of the business, or you won't be able to communicate. 3. Use that jargon when naming database tables, software modules, variables, everything, or you'll have to translate between your possibly abstract names and the jargon of the business. So, apparently nothing new but I should read the PDF (too bad it's not HTML) because there could be new useful ideas about the process. Edit: oops, the PDF is only that page as PDF. I'll google for it but does anybody have a good link to a detailed explanation of the method?