DSpace at Cochin University >
Department of Computer Science >
Seminar Reports >
MTech 2010-2012 Batch >
Please use this identifier to cite or link to this item:
|Title: ||SOFTWARE REUSE|
|Authors: ||Ferose, Babu TA|
|Keywords: ||Develop for reuse, Libraries, Components, Framework, modularity, coupling, cohesion, information hiding, separation of concerns and RRL|
|Issue Date: ||22-Jun-2011|
|Abstract: ||Software reusability is the likelihood a piece of source code that can be used again to add new functionalities with slight or no modification. Programmers have always reused sections of code, functions and procedures. Code reuse is the idea that a partial or complete computer program written at one time is being or should be used in another program written at a later time. The concept of software reuse emerged as a recognized area after proposed basing of industry on reusable components. To achieve full potential of reuse, we need to focus our attention on development for reuse.
Organizations implementing systematic software reuse programs must be able to measure their progress and identify the most effective reuse strategies. Metrics and models with various reuse readiness levels can be used to measure reuse and reusability. Current reuse techniques focus on the reuse of software artifacts on the basis of desired functionality. Non-functional properties of a software system are also crucial. Quality concerns, therefore, should also be the focus for software reuse.
This Mathematical Theory of Intelligence structures objects in such a way that they become maximally reusable, interoperable and archival. The theory claims that reusability of an object is maximized if the object itself is defined as having been produced by maximizing reuse of the operations that were used to produce it. Many metrics and models have been developed for software reuse and reusability|
|Appears in Collections:||MTech 2010-2012 Batch|
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.