Comments on: Gathering Implicit Requirements http://tynerblain.com/blog/2006/11/17/gathering-implicit-requirements/ Software product success. Thu, 18 Mar 2010 20:39:50 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Creating Software: Getting the Requirements | devjargon http://tynerblain.com/blog/2006/11/17/gathering-implicit-requirements/comment-page-1/#comment-400407 Creating Software: Getting the Requirements | devjargon Wed, 09 Jul 2008 13:02:54 +0000 http://tynerblain.com/blog/2006/11/17/gathering-implicit-requirements/#comment-400407 [...] problem though, is that implicit requirements are still requirements. If you fulfill all of the explicit requirements but miss the implicit ones, the client won’t [...] [...] problem though, is that implicit requirements are still requirements. If you fulfill all of the explicit requirements but miss the implicit ones, the client won’t [...]

]]> By: Andy Smith http://tynerblain.com/blog/2006/11/17/gathering-implicit-requirements/comment-page-1/#comment-73805 Andy Smith Tue, 27 Feb 2007 11:31:59 +0000 http://tynerblain.com/blog/2006/11/17/gathering-implicit-requirements/#comment-73805 We usually create storyboard screens using a tool in Visio (stpBA storyboarding). This approach has saved us a lot of time and rework as we are in a better position to get a clear understanding of the customers requirements (including implicit) at an early stage. Our customers usually independently review the storyboard screens and provide us useful feedback which was lacking prior to using this approach. However I'm sure that by observing the customers interacting with the storyboards we could also get a far better understanding of the implicit requirements. We usually create storyboard screens using a tool in Visio (stpBA storyboarding). This approach has saved us a lot of time and rework as we are in a better position to get a clear understanding of the customers requirements (including implicit) at an early stage.

Our customers usually independently review the storyboard screens and provide us useful feedback which was lacking prior to using this approach. However I’m sure that by observing the customers interacting with the storyboards we could also get a far better understanding of the implicit requirements.

]]> By: Ten Requirements Gathering Techniques « Little K’s Blog http://tynerblain.com/blog/2006/11/17/gathering-implicit-requirements/comment-page-1/#comment-57200 Ten Requirements Gathering Techniques « Little K’s Blog Thu, 23 Nov 2006 05:14:10 +0000 http://tynerblain.com/blog/2006/11/17/gathering-implicit-requirements/#comment-57200 [...] The study of users in their natural habitats is what observation is about. By observing users, an analyst can identify a process flow, awkward steps, pain points and opportunities for improvement. Observation can be passive or active (asking questions while observing). Passive observation is better for getting feedback on a prototype (to refine requirements), where active observation is more effective at getting an understanding of an existing business process. Either approach can be used to uncover implicit requirements that otherwise might go overlooked. [...] [...] The study of users in their natural habitats is what observation is about. By observing users, an analyst can identify a process flow, awkward steps, pain points and opportunities for improvement. Observation can be passive or active (asking questions while observing). Passive observation is better for getting feedback on a prototype (to refine requirements), where active observation is more effective at getting an understanding of an existing business process. Either approach can be used to uncover implicit requirements that otherwise might go overlooked. [...]

]]>