Comments on: Axiomatic Design http://shapingsoftware.com/2009/05/31/axiomatic-design/ Patterns and Practices for Software Success. Tue, 07 Sep 2010 16:35:10 +0000 http://wordpress.org/?v=2.7.1 hourly 1 By: JD http://shapingsoftware.com/2009/05/31/axiomatic-design/comment-page-1/#comment-54086 JD Tue, 16 Jun 2009 06:38:54 +0000 http://shapingsoftware.com/2009/05/31/axiomatic-design/#comment-54086 @ Shuan I agree -- factoring the what's and how's and knowing the relationships can help untangle many complexities. It's a nice principle-based approach. @ Shuan

I agree — factoring the what’s and how’s and knowing the relationships can help untangle many complexities. It’s a nice principle-based approach.

]]> By: Shuan http://shapingsoftware.com/2009/05/31/axiomatic-design/comment-page-1/#comment-53944 Shuan Sat, 13 Jun 2009 11:03:35 +0000 http://shapingsoftware.com/2009/05/31/axiomatic-design/#comment-53944 My grad school thesis was related to axiomatic design. The concepts of differentiating whats and hows and identifying coupling seem to very straightforward yet sometimes very handy in dealing with complexities in general. Thank you for the sharing. It is interesting to me! My grad school thesis was related to axiomatic design. The concepts of differentiating whats and hows and identifying coupling seem to very straightforward yet sometimes very
handy in dealing with complexities in general.

Thank you for the sharing. It is interesting to me!

]]> By: JD http://shapingsoftware.com/2009/05/31/axiomatic-design/comment-page-1/#comment-53628 JD Wed, 03 Jun 2009 10:45:27 +0000 http://shapingsoftware.com/2009/05/31/axiomatic-design/#comment-53628 @ Shuan For me, it's been most helpful to create cuttable scope for projects. Imagine a list of scenarios. Each scenario requires some features to be implemented. Some of those features will be used across scenarios, while other features will be just for a specific scenario. The potential problem I have is where features cut across scenarios. Cutting those scenarios won't necessarily buy me time or might impact quality. On the flip side, where the scenarios don't have shared features, I can cut them and actually save time. I use this information to try to structure the project for my baseline release and then incremental releases. These visuals might help: http://shapingsoftware.com/2008/10/11/scenario-and-feature-frame/ @ Shuan

For me, it’s been most helpful to create cuttable scope for projects.

Imagine a list of scenarios. Each scenario requires some features to be implemented. Some of those features will be used across scenarios, while other features will be just for a specific scenario.

The potential problem I have is where features cut across scenarios. Cutting those scenarios won’t necessarily buy me time or might impact quality. On the flip side, where the scenarios don’t have shared features, I can cut them and actually save time.

I use this information to try to structure the project for my baseline release and then incremental releases. These visuals might help: http://shapingsoftware.com/2008/10/11/scenario-and-feature-frame/

]]> By: Shuan http://shapingsoftware.com/2009/05/31/axiomatic-design/comment-page-1/#comment-53585 Shuan Tue, 02 Jun 2009 15:06:22 +0000 http://shapingsoftware.com/2009/05/31/axiomatic-design/#comment-53585 I'm curious what you think of AD, and how you make use of it at work. Would you care to share a few more thoughts? I’m curious what you think of AD, and how you make use of it at work. Would you care to share a few more thoughts?

]]>