http://chrisdonnan.com/blog/2007/04/21/the-plinko-model-of-software-architecture/ software, trading, family, fun Mon, 11 Jan 2010 03:09:14 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://chrisdonnan.com/blog/2007/04/21/the-plinko-model-of-software-architecture/comment-page-1/#comment-222 Chris Donnan : Programming - Brooklyn Style - More on plinko style architecture - how do we do architecture? Wed, 23 May 2007 10:32:02 +0000 http://chrisdonnan.com/blog/2007/04/21/the-plinko-model-of-software-architecture/#comment-222 [...] In a prior post I talked about how important it is to “slice the work vertically” and not to get lost in BDUF land. In general, I think architecture needs to be “right sized” to the project. A teeny app needs little or no real “architecture planning” a huge app certainly needs some. The trick is not to think you can do BDUF for real, you just hide work and make the other BDUF believers “feel comfortable”. [...] [...] In a prior post I talked about how important it is to “slice the work vertically” and not to get lost in BDUF land. In general, I think architecture needs to be “right sized” to the project. A teeny app needs little or no real “architecture planning” a huge app certainly needs some. The trick is not to think you can do BDUF for real, you just hide work and make the other BDUF believers “feel comfortable”. [...]

]]> http://chrisdonnan.com/blog/2007/04/21/the-plinko-model-of-software-architecture/comment-page-1/#comment-220 Chris Donnan : Programming - Brooklyn Style - Conquest through extreme composition + glue, Part 1 Sat, 19 May 2007 16:23:22 +0000 http://chrisdonnan.com/blog/2007/04/21/the-plinko-model-of-software-architecture/#comment-220 [...] Amidst the course of this spike, we are all coding a lot and talking a lot. The team has lots of smart folks with a collective ton of experience building desktop applications serving the hard demands of traders. We are trying hard to keep our deliverables “end user effecting” yet during the spike, we are basically focused on defining a basic set of architectural buckets (see plinko model) into which our end user effecting features will fall during implementation. [...] [...] Amidst the course of this spike, we are all coding a lot and talking a lot. The team has lots of smart folks with a collective ton of experience building desktop applications serving the hard demands of traders. We are trying hard to keep our deliverables “end user effecting” yet during the spike, we are basically focused on defining a basic set of architectural buckets (see plinko model) into which our end user effecting features will fall during implementation. [...]

]]>