| reuse of commercial off-the-shelf software | has example take a standard email application and add a feature that would always update the 'address book' with data from the corporate employee and client databases |  |
| is a subtopic of 3.1 - Reuse: Building on the Work and Experience of Others | |
| is a kind of reuse of applications | |
| reuse of applications | involves taking complete applications and adapting them to the needs of the client by adding a small amount of extra software that makes the applications behave in special ways the client wants | |
| reuse | can occur if software developers reuse existing good-quality components, and also contribute to reusable components that others can use | |
| has purpose to reduce the large cost associated with developing the same thing over and over again | |
| has risks | |
| is one of the keys to successful software development | |
| is not a strong part of the development culture of many organizations | |
| is not as extensive in software engineering projects as might be desirable | |
| may be prevented because of a vicious circle: Developers do not develop high quality reusable components, so there is nothing to reuse. Since there is nothing to reuse, software developers take so much time to develop applications that they lack time to invest in reusable frameworks or libraries | |
may not be practised because - developing anything reusable is seen as not directly benefiting the current customer
- If a developer has painstakingly developed a high-quality reusable component, but management only rewards the efforts of people who create the more visible 'final product', then that developer will be reluctant to spend time on reusable components in the future
- Efforts at creating reusable software are often done in a hurry and without enough attention to quality. People thus lose confidence in the resulting components, and in the concepts of reuse and reusability
| |
Object Oriented Software Engineering View all facts Glossary Help
