Art of Software Reuse

Have a plan for every reusable asset. At a minimum the plan needs to address:

1. The scope of the asset’s functionality for your immediate deliverable
2. The asset’s place in within your product line
3. The impact to your existing design and overall architecture
4. Tentative road-map for evolving the reusable asset over several iterations or releases

You don’t have to get answers for all these areas rightaway! The point is to think about them so you can make decisions on scope and effort. In the midst of an iteration there will be several questions about whether or not to invest time in refactoring or developing a feature. You can use this tiny list as a guide to help you make decisions on what to refactor or build and whether or not it is in line with your overall strategy.

Like this post? Subscribe to RSS feed or get blog updates via email.

: : : : :

This entry was posted on Sunday, May 10th, 2009 at 11:57 am and is filed under General, Planning, Reuse. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.