Home > technical > Software Reuse

Software Reuse

As a follow up to my last post, I decided to post this collection of quotes on software reuse from some industry luminaries:

Planned? Top-down? Upfront? In this age of “agile“, these words border on blasphemy.

  1. September 7, 2012 at 6:35 am

    It’s a popular myth that agile and top-down architecture strategy are mutually exclusive:

    http://charliealfred.wordpress.com/scrum-and-architecture-partners-or-adversaries/

    SCRUM is like driving – it’s a process for getting from one place to another. Architecture strategy is like a GPS. It comes in extremely handy if you are driving in unfamiliar territory and may need to take a detour because of unexpected traffic or construction.

    • September 7, 2012 at 9:01 am

      Thanks once again for stoppin’ by Charlie. Scrum’s a framework, not a process. That’s part of the issue with “agile” stuff. It’s so mushy that no one really knows what it means and it spawns arguments galore within orgs and within the industry. I honestly think nothing is really mutually exclusive. Hybrids can be developed out of almost any two seemingly opposing parts.

  2. Mark
    September 7, 2012 at 8:16 am

    From my experience, this is absolutely true. I was never able to get a commitment to reuse from management at my previous job, nor even agreement from my co-workers that it was possible.

    • September 7, 2012 at 8:53 am

      Thanks for sharing your direct experience Mark.

  3. September 7, 2012 at 9:59 am

    Intra-product reuse should be fairly easy to pull of in that you should have more visibility into what is affected by change and the means to test the effect. The ability to correct failed experiments exists. In this instance, I’d disagree with Bosch.

    Once components start crossing the product boundary, flexibility drastically decreases. A breaking change to shared component creates much more havoc. The only way to manage that risk is via governance and planning.

    As Charlie’s article pointed out, no Big Design Up Front is not the same as no design up front. Tailoring the level of rigor to the context at hand seems much more agile than abandoning all control and hoping for the best.

  4. PNeumiller
    September 7, 2012 at 10:23 am

    I have always thought buying finished software with some versions behind it was the best form of reuse, i.e. don’t reuse code, reuse hardened binaries/libraries whenever possible.

  5. Mohamed Ennahdi El Idrissi
    August 31, 2013 at 5:34 am

    A good document covering the topic of software reuse (different combined techniques in Java):

  1. September 11, 2012 at 3:23 pm

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: