Comments on: Alt.Net Seattle – Takeaway<DDDD>().Resources http://elegantcode.com/2008/04/30/altnet-seattle-takeawayddddresources/ Wed, 10 Mar 2010 19:57:20 -0600 http://wordpress.org/?v=2.8.6 hourly 1 By: Jarod Ferguson http://elegantcode.com/2008/04/30/altnet-seattle-takeawayddddresources/comment-page-1/#comment-20457 Jarod Ferguson Fri, 02 May 2008 16:54:17 +0000 http://elegantcode.com/2008/04/30/altnet-seattle-takeawayddddresources/#comment-20457 Thanks Evan, I updated the post to include the book. (all I had to go off of in my notes was 'SEI - Quality Attributes') Thanks Evan, I updated the post to include the book. (all I had to go off of in my notes was ‘SEI – Quality Attributes’)

]]> By: Evan http://elegantcode.com/2008/04/30/altnet-seattle-takeawayddddresources/comment-page-1/#comment-20455 Evan Fri, 02 May 2008 16:33:31 +0000 http://elegantcode.com/2008/04/30/altnet-seattle-takeawayddddresources/#comment-20455 The best resource for getting your feet wet with software quality attributes is to read the book Software Architecture in Practice. The PDFs on the SEI website are great, but I don't think you'll get the broad picture from reading them alone. For example, when working with stakeholders on a new system, it's often useful to define a Utility tree to help guide architecture decisions. If the project is very large, a Quality Attribute Workshop might actually help the project drive out some risk. Another tool where quality attributes are used is in doing Architecture Evalutions. This entails an evaluation activity that's designed to drive nonfunctional risks out of large development projects. These things are all related to quality attributes, but if you go for the PDFs alone, you'll miss them (even at an introductory level). The best resource for getting your feet wet with software quality attributes is to read the book Software Architecture in Practice. The PDFs on the SEI website are great, but I don’t think you’ll get the broad picture from reading them alone.

For example, when working with stakeholders on a new system, it’s often useful to define a Utility tree to help guide architecture decisions. If the project is very large, a Quality Attribute Workshop might actually help the project drive out some risk. Another tool where quality attributes are used is in doing Architecture Evalutions. This entails an evaluation activity that’s designed to drive nonfunctional risks out of large development projects.

These things are all related to quality attributes, but if you go for the PDFs alone, you’ll miss them (even at an introductory level).

]]>