Comments on: Continously Align Your Software Assets To Be More Reusable

By: The Systematic Software Reuse Roadmap « Art of Software Reuse

The Systematic Software Reuse Roadmap « Art of Software Reuse — Sun, 08 Nov 2009 23:41:20 +0000

[...] refactoring, iteration planning, and pair programming used to identify and refine assets in a continuous fashion. Consumers increasingly use reusable assets to build applications and start to co-create assets. [...]

By: Silo Thinking Hurts Systematic Reuse « Art of Software Reuse

Silo Thinking Hurts Systematic Reuse « Art of Software Reuse — Fri, 06 Nov 2009 02:56:46 +0000

[...] Silo thinking specific to an application means potentially reusable assets are not created and existing reusable assets are not leveraged. Think about the application’s needs to get reference data or connect with external systems or format data per a destination’s specific needs. Is your application using reusable assets? If not, is there an opportunity to create one by building or refactoring? [...]

By: Agile Software Reuse – Key Ingredients « Art of Software Reuse

Agile Software Reuse – Key Ingredients « Art of Software Reuse — Fri, 21 Aug 2009 00:11:16 +0000

[...] meant to make every feature reusable or every iteration produce reusable assets. Just the opposite. Continuous alignment accepts that building reusable software is hard, takes time, and is iterative. You can fight that [...]

By: vijaynarayanan

vijaynarayanan — Tue, 02 Jun 2009 02:09:06 +0000

Thanks Jing. The business being involved in design reviews is a very good thing. That way it becomes easier for IT to demonstrate the business benefits of certain design approaches.

By: Jing

Jing — Tue, 02 Jun 2009 01:41:13 +0000

The business are never involved in code reviews. We do, however, present our design to the business once it’s finalized among the tech teams. Being in the Internet industry, our business team is probably relatively more tech-savvy than those from the financial industry, and are generally interested in the technical solutions we come up with.

By: vijaynarayanan

vijaynarayanan — Mon, 25 May 2009 15:32:38 +0000

My experience has been the same Jing. All kinds of interesting things come up with design reviews and code reviews. Most of the developer to developer communication that is essential to reuse is facilitated by reviews. It is interesting that you include the business team – how has that worked out in terms of design/code review effectiveness?

By: Jing

Jing — Mon, 25 May 2009 14:21:57 +0000

“Align your software assets closer and closer to a desired state using relentless refactoring and code reviews.” I agree with this completely. I’m a big fan of code reviews, especially when it’s a team effort. I’ve had code review sessions scheduled for each project at my company, and I learn something new each time. These sessions also put me in a mindset of writing better code, because I know they will be reviewed at the end.

What I find even more helpful though, is design review. Components reuse can sometimes come out of these discussions. One developer may have designed and written something in a previous project that can now be reused with just a little refactoring or tweaking. Without these reviews, duplicate components would have been written without anyone knowing it. We sometimes even involve the business team in these reviews so that they are also on-board for reusing existing components.

Good stuff!