According to John C. Dale, MS MIS, president of Growing Business Solutions, for firms providing software development outsourcing services, the practice of software reuse can reduce overhead and increase margins.

Currently, an alarming number of enterprise software development projects are over budget, delivered late, or both. As software development organizations mature, so too should their ability to deliver increasingly complex software solutions on time and on budget. One strategy for achieving this is to identify opportunities for software reuse. In traditional manufacturing nomenclature, this process would be expressed as "manufacturing efficiency" or "economy of scale."

In this article, Dale discusses one way in which open source J2EE Security Realms can be used to facilitate code reuse - and thus manufacturing efficiency - into the enterprise software manufacturing process.

Subsequently, enterprise software development firms who employ this methodology should expect to deliver software with greater efficiency and predictability at a lower cost.

Read "Reusable Security for Segmented Data Domains".

The Holy Grail of Software Development has been Software Reuse, but how is this different from 'Copy and Paste' Programming? What if the original of your (reused) component changes - do you change the copy? What if the copy has been modified / reconfigured - how do you test the update? Probably an unfair comment (at the global reuse level) as the article is pretty good at what it sets out to do (resuse of security components). Paul , Technology in Plain English Blog

The Holy Grail of Software Development has been Software Reuse, but how is this different from 'Copy and Paste' Programming? What if the original of your (reused) component changes - do you change the copy? What if the copy has been modified / reconfigured - how do you test the update?

Probably an unfair comment (at the global reuse level) as the article is pretty good at what it sets out to do (resuse of security components).

Paul , Technology in Plain English Blog

I take your point to be something like 'what happens if you change a method signature that is used by the majority of the security component's client code'? The answer to this would be (correct me if I have misinterpreted your question) that all client code would have to be re-written to accommodate the change. If at all possible I would deprecate an older method but leave it in service (a common strategy) for a period of time. I'm not really clear on the question, and apologize if I missed the spirit of the comment. Thank you for the kind words and for taking the time to read/respond. John Dale