Comments on: Describing the Software Development Process http://tynerblain.com/blog/2006/01/29/describing-the-software-development-process/ Software product success. Sun, 12 Feb 2012 19:10:25 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Scott Sehlhorst http://tynerblain.com/blog/2006/01/29/describing-the-software-development-process/comment-page-1/#comment-332 Scott Sehlhorst Tue, 07 Mar 2006 04:49:07 +0000 http://tynerblain.com/blog/2006/01/29/describing-the-software-development-process/#comment-332 I've added links to four more recent posts that expand on these ideas at the end of the post above. Thanks again! I’ve added links to four more recent posts that expand on these ideas at the end of the post above.

Thanks again!

]]> By: Scott Sehlhorst http://tynerblain.com/blog/2006/01/29/describing-the-software-development-process/comment-page-1/#comment-331 Scott Sehlhorst Tue, 07 Mar 2006 04:24:35 +0000 http://tynerblain.com/blog/2006/01/29/describing-the-software-development-process/#comment-331 Barbara, Thanks for commenting and welcome to Tyner Blain! From your description, it sounds like you do two things - interaction design (as Alan Cooper would call it) when working with the product manager to define the requirements, and then interface design (visual, usability, IA?) in iterations with the developers. I think that interaction design plays a role in requirements - specifically in the ideation stage of determining which problems to solve with software. I also believe that the other design elements are more about execution/application of ideas, and fall in the "software design" bucket. Take a look at <a href="http://tynerblain.com/blog/2006/02/20/software-development-process-example/" rel="nofollow">Software development process example</a> for more details. I will update this post now to include a link - it's definitely relevant. Thanks again for reading, and especially for commenting Barbara,

Thanks for commenting and welcome to Tyner Blain!

From your description, it sounds like you do two things – interaction design (as Alan Cooper would call it) when working with the product manager to define the requirements, and then interface design (visual, usability, IA?) in iterations with the developers.

I think that interaction design plays a role in requirements – specifically in the ideation stage of determining which problems to solve with software. I also believe that the other design elements are more about execution/application of ideas, and fall in the “software design” bucket.

Take a look at Software development process example for more details.

I will update this post now to include a link – it’s definitely relevant.

Thanks again for reading, and especially for commenting

]]> By: Barbara Smyth http://tynerblain.com/blog/2006/01/29/describing-the-software-development-process/comment-page-1/#comment-319 Barbara Smyth Sat, 04 Mar 2006 00:42:44 +0000 http://tynerblain.com/blog/2006/01/29/describing-the-software-development-process/#comment-319 I am new to your site, having found it looking for descriptions of MRDs and what is included. I am looking for where you think interface solutions should reside and with whom these solutions should be developed. I typically work with a product manager to develop task flows and screen flows, then include development in discussions when we are ready to solidify screen flows. From there, the PM and I (I am a UI designer) work to create hi-def screen designs, running these past developers to validate approach and constraints. In my present company there is a very different attitude about who develops screen flow and screen design solutions. Looking for other perspectives on this point. I am new to your site, having found it looking for descriptions of MRDs and what is included.

I am looking for where you think interface solutions should reside and with whom these solutions should be developed.
I typically work with a product manager to develop task flows and screen flows, then include development in discussions when we are ready to solidify screen flows. From there, the PM and I (I am a UI designer) work to create hi-def screen designs, running these past developers to validate approach and constraints.

In my present company there is a very different attitude about who develops screen flow and screen design solutions.

Looking for other perspectives on this point.

]]> By: Software requirements - process and roles -Tyner Blain http://tynerblain.com/blog/2006/01/29/describing-the-software-development-process/comment-page-1/#comment-286 Software requirements - process and roles -Tyner Blain Tue, 14 Feb 2006 00:25:51 +0000 http://tynerblain.com/blog/2006/01/29/describing-the-software-development-process/#comment-286 [...] Note that there are also steps involved in assuring the quality of the solution, and feedback loops in a good software development process. We covered this in our earlier post, Where bugs come from. We’ve also talked in more detail about the software development process in our post, Describing the software development process. In order to keep this discussion on task, we’ve simplified our presentation of that material in this post. [...] [...] Note that there are also steps involved in assuring the quality of the solution, and feedback loops in a good software development process. We covered this in our earlier post, Where bugs come from. We’ve also talked in more detail about the software development process in our post, Describing the software development process. In order to keep this discussion on task, we’ve simplified our presentation of that material in this post. [...]

]]> By: Requirements vs design - which is which and why? -Tyner Blain http://tynerblain.com/blog/2006/01/29/describing-the-software-development-process/comment-page-1/#comment-274 Requirements vs design - which is which and why? -Tyner Blain Sat, 11 Feb 2006 19:42:16 +0000 http://tynerblain.com/blog/2006/01/29/describing-the-software-development-process/#comment-274 [...] We’ve described the software development process before as being like an onion - having multiple layers of abstraction within which you describe the problem and solution. In this post we will translate that perspective into “what is a requirement” and “what is design”. [...] [...] We’ve described the software development process before as being like an onion – having multiple layers of abstraction within which you describe the problem and solution. In this post we will translate that perspective into “what is a requirement” and “what is design”. [...]

]]> By: Dilbert does product managers -Tyner Blain http://tynerblain.com/blog/2006/01/29/describing-the-software-development-process/comment-page-1/#comment-178 Dilbert does product managers -Tyner Blain Tue, 31 Jan 2006 13:22:50 +0000 http://tynerblain.com/blog/2006/01/29/describing-the-software-development-process/#comment-178 [...] [...] [...] [...]

]]>