Comments for traceinthesand.com Blog http://traceinthesand.com/blog Musing about architecture, architecting and architects Sun, 09 Sep 2007 01:24:14 +0000 http://wordpress.org/?v=2.8.4 hourly 1 Comment on Agile Architecting by Ruth http://traceinthesand.com/blog/2007/09/08/agile-architecting/comment-page-1/#comment-2743 Ruth Sun, 09 Sep 2007 01:24:14 +0000 http://traceinthesand.com/blog/2007/09/08/agile-architecting/#comment-2743 Thanks Arnon! I had read, liked and learned from your Agile Architecture and Documentation post, so I'm very happy you caught my oversight! I really like that you're encouraging (agile) architects to document alternatives considered but ruled out and why. This may seem counter to the agile philosophy of minimalist documentation--there is pushback on documenting at all, so it'd be reasonable to ask why we should document approaches we decided against. But it is not counter to _being_ agile. It's not agile to revisit/rehash decisions, simply because... the collective "we" forgot, someone new came into the room, etc. Jeff Tyree and Art Ackerman's "Architecture Decisions: Demystifying Architecture" http://csdl2.computer.org/persagen/DLAbsToc.jsp?resourcePath=/dl/mags/so/&toc=comp/mags/so/2005/02/s2toc.xml&DOI=10.1109/MS.2005.27 also calls for documenting alternatives not chosen. Anshu Gaind has an architecture decision template that I also like because it explicitly identifies drawbacks of the approach, so that the discussion of downsides to our chosen approach is not swept off the table but rather addressed head on: http://www.bredemeyer.com/pdf_files/WhitePapers/Key%20Decisions%20Template.doc We also encourage architects to "connect the dots," tying decisions to their rationale--business strategy and architecture goals or lessons from our experience. The outcome of our thinking shows up in the code, but not the thought processes, the demands and drivers, the experiences, etc. that we were balancing as we made the architecture decisions. See http://www.bredemeyer.com/HotSpot/20040428EASoapBox.htm Thanks Arnon! I had read, liked and learned from your Agile Architecture and Documentation post, so I’m very happy you caught my oversight!

I really like that you’re encouraging (agile) architects to document alternatives considered but ruled out and why. This may seem counter to the agile philosophy of minimalist documentation–there is pushback on documenting at all, so it’d be reasonable to ask why we should document approaches we decided against. But it is not counter to _being_ agile. It’s not agile to revisit/rehash decisions, simply because… the collective “we” forgot, someone new came into the room, etc.

Jeff Tyree and Art Ackerman’s “Architecture Decisions: Demystifying Architecture” http://csdl2.computer.org/persagen/DLAbsToc.jsp?resourcePath=/dl/mags/so/&toc=comp/mags/so/2005/02/s2toc.xml&DOI=10.1109/MS.2005.27 also calls for documenting alternatives not chosen.

Anshu Gaind has an architecture decision template that I also like because it explicitly identifies drawbacks of the approach, so that the discussion of downsides to our chosen approach is not swept off the table but rather addressed head on: http://www.bredemeyer.com/pdf_files/WhitePapers/Key%20Decisions%20Template.doc

We also encourage architects to “connect the dots,” tying decisions to their rationale–business strategy and architecture goals or lessons from our experience. The outcome of our thinking shows up in the code, but not the thought processes, the demands and drivers, the experiences, etc. that we were balancing as we made the architecture decisions. See http://www.bredemeyer.com/HotSpot/20040428EASoapBox.htm

]]> Comment on Agile Architecting by Arnon Rotem-Gal-Oz http://traceinthesand.com/blog/2007/09/08/agile-architecting/comment-page-1/#comment-2736 Arnon Rotem-Gal-Oz Sat, 08 Sep 2007 20:44:00 +0000 http://traceinthesand.com/blog/2007/09/08/agile-architecting/#comment-2736 Hi Ruth, I also blogged a few post on agile processes and architecture which you may find interesting. such as: http://www.rgoarchitects.com/nblog/2007/06/11/AgileArchitectureAndDocumentation.aspx http://www.rgoarchitects.com/nblog/2007/05/13/EvolvingArchitectures.aspx Hi Ruth,
I also blogged a few post on agile processes and architecture which you may find interesting. such as:

http://www.rgoarchitects.com/nblog/2007/06/11/AgileArchitectureAndDocumentation.aspx
http://www.rgoarchitects.com/nblog/2007/05/13/EvolvingArchitectures.aspx

]]> Comment on Architecture Documentation: Courage to Fly in the Face of Convention by A Trace in the Sand » Agile Architecting http://traceinthesand.com/blog/2006/08/25/architecture-documentation-courage-to-fly-in-the-face-of-convention/comment-page-1/#comment-2717 A Trace in the Sand » Agile Architecting Sat, 08 Sep 2007 12:30:56 +0000 http://traceinthesand.com/blog/2006/08/25/architecture-documentation-courage-to-fly-in-the-face-of-convention/#comment-2717 [...] Architecture Documentation: Courage to fly in the face of convention [...] [...] Architecture Documentation: Courage to fly in the face of convention [...]

]]> Comment on About Ruth Malan by A Trace in the Sand » Agile Architecting http://traceinthesand.com/blog/about/comment-page-1/#comment-2715 A Trace in the Sand » Agile Architecting Sat, 08 Sep 2007 12:21:57 +0000 #comment-2715 [...] About Ruth Malan [...] [...] About Ruth Malan [...]

]]> Comment on Exploring HelpMatch Value by Ruth http://traceinthesand.com/blog/2007/03/11/exploring-helpmatch-value/comment-page-1/#comment-191 Ruth Fri, 16 Mar 2007 16:18:16 +0000 http://traceinthesand.com/blog/2007/03/11/exploring-helpmatch-value/#comment-191 Yes! You put it so well! It is going to be really exciting thinking these trust mechanisms through, and building them. There's precedent (I like the eBay metaphor), and new ground to break on this. Yes! You put it so well!

It is going to be really exciting thinking these trust mechanisms through, and building them. There’s precedent (I like the eBay metaphor), and new ground to break on this.

]]> Comment on HelpMatch: Collaboration Tools Selection Subcommittee by Ruth http://traceinthesand.com/blog/2007/03/02/helpmatch-collaboration-tools-selection-subcommittee/comment-page-1/#comment-190 Ruth Fri, 16 Mar 2007 16:13:16 +0000 http://traceinthesand.com/blog/2007/03/02/helpmatch-collaboration-tools-selection-subcommittee/#comment-190 Wahoo! Jarvis Ka is working on this too. I'll connect you, and others as they step up to this challenge. I agree, it's a really interesting and broadly relevant area, and central to getting our HelpMatch architecture team geared up fully. Wahoo! Jarvis Ka is working on this too. I’ll connect you, and others as they step up to this challenge. I agree, it’s a really interesting and broadly relevant area, and central to getting our HelpMatch architecture team geared up fully.

]]> Comment on HelpMatch: Collaboration Tools Selection Subcommittee by Craig Cody http://traceinthesand.com/blog/2007/03/02/helpmatch-collaboration-tools-selection-subcommittee/comment-page-1/#comment-189 Craig Cody Fri, 16 Mar 2007 01:46:01 +0000 http://traceinthesand.com/blog/2007/03/02/helpmatch-collaboration-tools-selection-subcommittee/#comment-189 I would like to volunteer for this committee. I interested in collaboration tools and their application both in and out of the work place. I've looked at a few, but there are still so many out there that I haven't gotten to yet. I would love to hear what has worked for others and what hasn't. I hope to learn from the experience of others while at the same time perhaps contributing my own. Interesting conundrum: collaborating on collaboration tools. I would like to volunteer for this committee. I interested in collaboration tools and their application both in and out of the work place. I’ve looked at a few, but there are still so many out there that I haven’t gotten to yet. I would love to hear what has worked for others and what hasn’t. I hope to learn from the experience of others while at the same time perhaps contributing my own.

Interesting conundrum: collaborating on collaboration tools.

]]> Comment on Exploring HelpMatch Value by Craig Cody http://traceinthesand.com/blog/2007/03/11/exploring-helpmatch-value/comment-page-1/#comment-188 Craig Cody Fri, 16 Mar 2007 01:40:45 +0000 http://traceinthesand.com/blog/2007/03/11/exploring-helpmatch-value/#comment-188 Perhaps the HelpMatch network can also help from a security perspective. I would expect that there would be those in a position to assist who might be looking for some kind of assurance that they weren't falling victim to some kind of fraud. This risk of fraud could be mitigated by the network. Resources within the network having earned a "trustworthy" reputation, might vouch for project in need. One need only look to eBay for a "trust" metaphor. How do you know that you won't be ripped off on eBay? You don't. But there is a "feedback score" for buyers and sellers. Epinions.com could serve as another metaphor. Those projects in need that are worthy could separate from those that are not on the vetting done by the network. Perhaps the HelpMatch network can also help from a security perspective. I would expect that there would be those in a position to assist who might be looking for some kind of assurance that they weren’t falling victim to some kind of fraud.

This risk of fraud could be mitigated by the network. Resources within the network having earned a “trustworthy” reputation, might vouch for project in need. One need only look to eBay for a “trust” metaphor. How do you know that you won’t be ripped off on eBay? You don’t. But there is a “feedback score” for buyers and sellers. Epinions.com could serve as another metaphor.

Those projects in need that are worthy could separate from those that are not on the vetting done by the network.

]]> Comment on What is Software Architecture? by sanjib pandey http://traceinthesand.com/blog/2006/05/07/what-is-software-architecture/comment-page-1/#comment-165 sanjib pandey Thu, 01 Mar 2007 10:39:40 +0000 http://traceinthesand.com/blog/2006/05/07/what-is-software-architecture/#comment-165 Dear sir, i have am just starting with learning what is architecture… Want to grow as Software architectural consultant… I have some questions that need to be addressed 1. when some one have talent and can grow in any of the dimensions and he has not mention his designation and having good skill set of software architech, it is fair to reject any CV with out desination even he have exellent skill set. 2. What is need to now…to convince our CEO of our company.he is basically booky knowldge man and he could not get the point of tech knoeldge so please give good defination of s/w architec did he need desination give me suggestion, so that i can convince my CEO thanks Regards Sanjib Dear sir,
i have am just starting with learning what is architecture… Want to grow as Software architectural consultant…

I have some questions that need to be addressed

1. when some one have talent and can grow in any of the dimensions and he has not mention his designation and having good skill set of software architech, it is fair to reject any CV with out desination even he have exellent skill set.
2. What is need to now…to convince our CEO of our company.he is basically booky knowldge man and he could not get the point of tech knoeldge
so please give good defination of s/w architec did he need desination give me suggestion, so that i can convince my CEO
thanks
Regards
Sanjib

]]> Comment on That Vision Thing by John Wu http://traceinthesand.com/blog/2006/10/25/that-vision-thing/comment-page-1/#comment-107 John Wu Fri, 26 Jan 2007 19:42:55 +0000 http://traceinthesand.com/blog/2006/10/25/that-vision-thing/#comment-107 The link : http://e-cio.org/lea_book.htm http://blogs.ittoolbox.com/cio/lea/archives/distinguish-ea-from-business-transformation-8704 The link :

http://e-cio.org/lea_book.htm

http://blogs.ittoolbox.com/cio/lea/archives/distinguish-ea-from-business-transformation-8704

]]>