Untitled

edit

I agree


I disagree. Reusability can occur on various levels and various types of objects not just code. Object can be designed for reuse and reusability can occur through deployment, compononet reuse (close to code reuse) as well as indivudual interactions with learning or content objects. In the learning technologies domain, this concept is integral and is not necessariy localized to that of softward engineering.

it is to reus some thing and to help the enviroment.  —Preceding unsigned comment added by 124.189.224.180 (talk) 07:52, 9 February 2009 (UTC)Reply 

Criticisms of reusability

edit

http://www.onstrategies.com/blog/2008/03/05/soa-benefits-too-much-reuse-of-reuse/

  • “What if you built a service-oriented architecture and nothing got reused? Is it still of value to the business, or is it a flop?”
  • "As Brooks pointed out in his _The Mythical Man-Month_ (yes, book more than a little old, still relevant) is that making components reusable is more than abstracting out the functions a bit. You need good release engineering and even worse, good documentation. Most programmers can’t write documentation to save their lives."
  • Hurdles to re-usability:
  1. Cultural limits: using somebody else's work is not creative, clever, or "macho".
  2. Competition limits:
    • "We eventually realized that entity relationships did not adequately address business logic, so we eventually went to objects, followed by coarser grained components, with the idea that if we built that galactic enterprise repository in the sky, that software functionality could be harvested like low hanging fruit."
    • "Then we realized the futility of grand enterprise modeling schemes, because the pace of change in modern economies meant that any enterprise model would become obsolete the moment it was created. And so we pursued SOA, with the idea that we could compose and dynamically orchestrate our way to agility." —Preceding unsigned comment added by 128.138.64.110 (talk) 21:19, 12 October 2009 (UTC)Reply

Difference between Code Reuse and Reusability?

edit

Right now Reusability is defined by "In computer science and software engineering, reusability is the use of existing assets in some form within the software product development process," and Code Reuse is defined by Code reuse, also called software reuse, is the use of existing software, or software knowledge, to build new software,[1] following the reusability principles." I'm not quite sure I understand the difference between the two. Perhaps this difference just needs to made more clear in the introductions. Otherwise, perhaps these two pages would be good for merging. Skiingxmoose (talk) 19:29, 27 December 2014 (UTC)Reply