http://tynerblain.com/blog/2007/08/23/requirements-details/ Software product success. Thu, 18 Mar 2010 20:39:50 +0000 http://wordpress.org/?v=2.9.1 hourly 1 http://tynerblain.com/blog/2007/08/23/requirements-details/comment-page-1/#comment-143314 Rolf Mon, 03 Sep 2007 07:20:54 +0000 http://tynerblain.com/blog/2007/08/23/requirements-details/#comment-143314 Excellent article, Scott! I like the (not so new ;-) idea of using diagrams for higher level specifications AND providing detailed written requirements for the elements of the diagram. For me, this is a nice way of drilling down and rolling up. Two audiences served: low domain expertise and high domain expertise. Most of the times I employ use case diagrams, then use caseish descriptions. One level deeper into detail there will be activity diagrams, supported by prose requirements, decision tables or whatever. I found the specification as a whole pretty well suited for both beginners of the domain and experts. The downside: the specification covers both the low and high artifact detail range. The analyst has to be able to stand questions like "what takes you so long?"... Most project lead I encountered seem to be more interested in a spec suitable for the project (quite naturally). Only few have in mind the poor guys who will have to enhance the product after the project is finished. Excellent article, Scott!
I like the (not so new ;-) idea of using diagrams for higher level specifications AND providing detailed written requirements for the elements of the diagram. For me, this is a nice way of drilling down and rolling up. Two audiences served: low domain expertise and high domain expertise.
Most of the times I employ use case diagrams, then use caseish descriptions. One level deeper into detail there will be activity diagrams, supported by prose requirements, decision tables or whatever.
I found the specification as a whole pretty well suited for both beginners of the domain and experts. The downside: the specification covers both the low and high artifact detail range. The analyst has to be able to stand questions like “what takes you so long?”…
Most project lead I encountered seem to be more interested in a spec suitable for the project (quite naturally). Only few have in mind the poor guys who will have to enhance the product after the project is finished.

]]>