tag:blogger.com,1999:blog-10280668.post1935597439560084532..comments2023-09-22T06:05:17.495-05:00Comments on Brad Appleton's ACME Blog: Software Architecture Quality AttributesBrad Appletonhttp://www.blogger.com/profile/15136106921504315995noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-10280668.post-29883711662810803702010-03-09T08:45:01.360-06:002010-03-09T08:45:01.360-06:00Hi Braad,
I have begun my PhD in Software Architec...Hi Braad,<br />I have begun my PhD in Software Architecture Qualities. I read your post and it cleared a lot of ideas in my mind. Now I will read and know more about your Blog. <br /><br />Thank you so much for your contributions.<br /><br />EudisEudisley Gomeshttps://www.blogger.com/profile/17621416218446489077noreply@blogger.comtag:blogger.com,1999:blog-10280668.post-51857610689532099612008-12-03T07:59:00.000-06:002008-12-03T07:59:00.000-06:00" But what I look most about it is that fact that ..." But what I look most about it is that fact that it makes explicit the kinds of quality attributes and their non-functional use-cases or "stories" which can then have business value/priority associated with it, and thereby justify the existence of activities that help realize those attributes of the system."<BR/><BR/>Brad thanks for making me aware of ADD. I wasn't. And should be.<BR/><BR/>I have campaigned since 'time immemorial' (Software Metrics book 1976 for example) to get quality factors integrated into our development process. There is some progress, but the Agile community is a step backward in that they really manage to ignore qualities, and focus on coding functions etc.<BR/><BR/>I have a great deal more to say with pragmatic detail at www.gilb.com<BR/><BR/>Tom@Gib.comAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-10280668.post-41976879252682258202008-06-29T17:24:00.000-05:002008-06-29T17:24:00.000-05:00Hi Anilkuppa,I;m not sure I understand your questi...Hi Anilkuppa,<BR/><BR/>I;m not sure I understand your question. I'm not sure what specific part or parts of the paper you reference you feel relate to what I said. I didn't see any examples of CMMI-based process there. I saw things that described the CMMI framework and principles and concepts.<BR/><BR/>What I didn't see was one or examples of instances of CMMI-based processes. I think there are lots of things that get left out when folks try to apply CMM or CMMI in their own environment. That includes a great many things that even the CMM/CMMI say is important, but which are all too commonly passed over somehow (despite even CMM/CMMI saying they are important)Brad Appletonhttps://www.blogger.com/profile/15136106921504315995noreply@blogger.comtag:blogger.com,1999:blog-10280668.post-68304656219848437002008-06-23T18:27:00.000-05:002008-06-23T18:27:00.000-05:00Hi Bradd,Interesting to read your thoughts.However...Hi Bradd,<BR/>Interesting to read your thoughts.<BR/>However, 1 point regarding the following quote of yours<BR/>---------------------------------------<BR/>--quote<BR/>---------------------------------------<BR/>Seems to me that in Agile development, we're really not anti-process, but there are some really important things (quality attributes of a process?) that we feel are often left out to pasture by a lot of the very formal, CMMI-based processes we witness. Perhaps they're ignoring these important process-design quality attributes? (as embodied in the Agile Manifesto?)<BR/>---------------------------------------<BR/>--unquote------------------------------<BR/>---------------------------------------<BR/><BR/>Question / Request for verification/explanation of the above after reading the below link<BR/>http://www.sei.cmu.edu/pub/documents/07.reports/07tn002.pdfanilkuppahttps://www.blogger.com/profile/12621174227914347433noreply@blogger.com