Comments on: Requirements Document Proliferation http://tynerblain.com/blog/2006/01/20/document-proliferation/ Software product success. Thu, 18 Mar 2010 00:01:42 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: brainmates » Blog Archive » Flavours of Requirements Documents http://tynerblain.com/blog/2006/01/20/document-proliferation/comment-page-1/#comment-54819 brainmates » Blog Archive » Flavours of Requirements Documents Mon, 28 Aug 2006 05:38:33 +0000 http://tynerblain.com/blog/2006/01/20/document-proliferation/#comment-54819 [...] Check out what Scott from Tyner Blain has to say on the subject of product requirements. [...] [...] Check out what Scott from Tyner Blain has to say on the subject of product requirements. [...]

]]> By: Describing the software development process -Tyner Blain http://tynerblain.com/blog/2006/01/20/document-proliferation/comment-page-1/#comment-186 Describing the software development process -Tyner Blain Thu, 02 Feb 2006 03:47:02 +0000 http://tynerblain.com/blog/2006/01/20/document-proliferation/#comment-186 [...] Requirements. Different processes will use different names for these. In a process that uses structured requirements, this is the functional requirements, user requirements and business requirements. These can be captured in an FRS, SRS, or PRD (but please no, not all three!). [...] [...] Requirements. Different processes will use different names for these. In a process that uses structured requirements, this is the functional requirements, user requirements and business requirements. These can be captured in an FRS, SRS, or PRD (but please no, not all three!). [...]

]]> By: From MRD to PRD: The key to defining a spec -Tyner Blain http://tynerblain.com/blog/2006/01/20/document-proliferation/comment-page-1/#comment-172 From MRD to PRD: The key to defining a spec -Tyner Blain Mon, 30 Jan 2006 17:19:37 +0000 http://tynerblain.com/blog/2006/01/20/document-proliferation/#comment-172 [...] A market requirements document (MRD), as we discussed earlier, discusses the problems (to be solved) or the needs of the market. When working with a customer, that customer will identify one or more strategic objectives. [...] [...] A market requirements document (MRD), as we discussed earlier, discusses the problems (to be solved) or the needs of the market. When working with a customer, that customer will identify one or more strategic objectives. [...]

]]> By: Cote' http://tynerblain.com/blog/2006/01/20/document-proliferation/comment-page-1/#comment-120 Cote' Sun, 22 Jan 2006 19:01:52 +0000 http://tynerblain.com/blog/2006/01/20/document-proliferation/#comment-120 I like the way you're thinking ;) I couldn't find your trackpack URL, so here'a direct link to my reply post: <a href="http://www.drunkandretired.com/2006/01/21/technical-vs-non-technical-or-re-the-process-variant-of-conway%e2%80%99s-law/" rel="nofollow">http://www.drunkandretired.com/2006/01/21/technical-vs-non-technical-or-re-the-process-variant-of-conway%e2%80%99s-law/</a>. I like the way you’re thinking ;)

I couldn’t find your trackpack URL, so here’a direct link to my reply post: http://www.drunkandretired.com/2006/01/21/technical-vs-non-technical-or-re-the-process-variant-of-conway%e2%80%99s-law/.

]]>