652:
43:
659:
208:
The ability to reuse relies in an essential way on the ability to build larger things from smaller parts, and being able to identify commonality among those parts. Reusability is often a required characteristic of
342:
Consensus has not yet been reached on this list on the relative importance of the entries nor on the issues which make each one important for a particular class of applications.
163:
are products and by-products of the software development life cycle and include code, software components, test suites, designs and documentation. The opposite concept of
259:
Software reusability more specifically refers to design features of a software element (or collection of software elements) that enhance its suitability for reuse.
445:
205:
offer a more advanced form of reusability, although it has been tough to objectively measure and define levels or scores of reusability.
611:
402:
126:
233:
556:
438:
282:
194:
64:
576:
571:
107:
171:, which modifies existing assets as needed to meet specific system requirements. Because reuse implies the creation of a
156:
79:
60:
31:
627:
525:
327:
662:
637:
606:
372:
86:
688:
485:
431:
198:
632:
316:
93:
546:
229:
53:
581:
566:
561:
237:
182:
75:
306:
683:
510:
500:
490:
245:
214:
210:
144:
300:
241:
186:
202:
515:
454:
140:
480:
475:
332:
253:
406:
100:
520:
221:
677:
321:
287:
252:
issues. If these issues are not considered, software may appear to be reusable from
601:
551:
336:
310:
269:
505:
277:
42:
351:
178:
185:
are the simplest form of reuse. A chunk of code is regularly organized using
541:
225:
190:
17:
30:
This article is about reusability in computer science. For other uses, see
380:
249:
217:
that do not need to be considered when reusability is not required.
423:
262:
Many reuse design principles were developed at the WISR workshops.
292:
427:
36:
265:
Candidate design features for software reuse include:
403:"Design for Reuse and Object Oriented Reuse Methods"
620:
594:
534:
468:
461:
256:point of view, but will not be reused in practice.
67:. Unsourced material may be challenged and removed.
220:Reusability implies some explicit management of
213:software. Reusability brings several aspects to
27:Use of existing assets in software development
439:
8:
405:. Umcs.maine.edu. 1995-01-20. Archived from
173:separately maintained version of the assets
465:
446:
432:
424:
127:Learn how and when to remove this message
371:Lombard Hill Group (October 22, 2014).
363:
7:
658:
379:. Lombard Hill Group. Archived from
157:software product development process
65:adding citations to reliable sources
25:
612:List of system quality attributes
175:, it is preferred over leverage.
657:
651:
650:
41:
52:needs additional citations for
1:
32:Reusability (disambiguation)
628:Software quality management
607:Non-functional requirements
705:
638:Software quality assurance
305:Localization of volatile (
29:
646:
633:Software quality control
373:"What is Software Reuse"
197:. Proponents claim that
155:in some form within the
151:is the use of existing
309:) design assumptions (
215:software development
145:software engineering
61:improve this article
595:Standards and lists
377:www.lombardhill.com
203:software components
671:
670:
590:
589:
516:Understandability
274:Brief: small size
137:
136:
129:
111:
16:(Redirected from
696:
689:Software quality
661:
660:
654:
653:
466:
455:Software quality
448:
441:
434:
425:
418:
417:
415:
414:
399:
393:
392:
390:
388:
368:
174:
141:computer science
132:
125:
121:
118:
112:
110:
69:
45:
37:
21:
704:
703:
699:
698:
697:
695:
694:
693:
674:
673:
672:
667:
642:
616:
586:
530:
481:Maintainability
457:
452:
422:
421:
412:
410:
401:
400:
396:
386:
384:
370:
369:
365:
360:
348:
335:under changing
172:
133:
122:
116:
113:
70:
68:
58:
46:
35:
28:
23:
22:
15:
12:
11:
5:
702:
700:
692:
691:
686:
676:
675:
669:
668:
666:
665:
655:
647:
644:
643:
641:
640:
635:
630:
624:
622:
618:
617:
615:
614:
609:
604:
598:
596:
592:
591:
588:
587:
585:
584:
579:
574:
569:
564:
559:
554:
549:
544:
538:
536:
532:
531:
529:
528:
523:
521:Loose coupling
518:
513:
508:
503:
498:
493:
488:
483:
478:
472:
470:
463:
459:
458:
453:
451:
450:
443:
436:
428:
420:
419:
394:
362:
361:
359:
356:
355:
354:
347:
344:
340:
339:
330:
324:
319:
314:
303:
298:
295:
290:
285:
280:
275:
272:
135:
134:
49:
47:
40:
26:
24:
14:
13:
10:
9:
6:
4:
3:
2:
701:
690:
687:
685:
682:
681:
679:
664:
656:
649:
648:
645:
639:
636:
634:
631:
629:
626:
625:
623:
619:
613:
610:
608:
605:
603:
600:
599:
597:
593:
583:
580:
578:
575:
573:
570:
568:
565:
563:
560:
558:
555:
553:
550:
548:
545:
543:
540:
539:
537:
533:
527:
526:Orthogonality
524:
522:
519:
517:
514:
512:
509:
507:
504:
502:
499:
497:
494:
492:
489:
487:
484:
482:
479:
477:
474:
473:
471:
467:
464:
460:
456:
449:
444:
442:
437:
435:
430:
429:
426:
409:on 1997-07-15
408:
404:
398:
395:
383:on 2014-10-22
382:
378:
374:
367:
364:
357:
353:
350:
349:
345:
343:
338:
334:
331:
329:
325:
323:
322:Orthogonality
320:
318:
315:
312:
308:
304:
302:
299:
296:
294:
291:
289:
288:Extensibility
286:
284:
281:
279:
276:
273:
271:
268:
267:
266:
263:
260:
257:
255:
251:
247:
243:
239:
238:configuration
235:
231:
227:
223:
218:
216:
212:
206:
204:
200:
196:
192:
188:
184:
180:
176:
170:
166:
162:
158:
154:
150:
146:
142:
131:
128:
120:
109:
106:
102:
99:
95:
92:
88:
85:
81:
78: –
77:
76:"Reusability"
73:
72:Find sources:
66:
62:
56:
55:
50:This article
48:
44:
39:
38:
33:
19:
602:ISO/IEC 9126
552:Adaptability
495:
411:. Retrieved
407:the original
397:
385:. Retrieved
381:the original
376:
366:
341:
337:requirements
326:Simple: low
311:David Parnas
264:
261:
258:
234:installation
230:distribution
219:
207:
177:
168:
164:
160:
152:
148:
138:
123:
114:
104:
97:
90:
83:
71:
59:Please help
54:verification
51:
18:Re-usability
684:Source code
557:Correctness
547:Reliability
511:Testability
506:Scalability
501:Readability
496:Reusability
491:Portability
486:Flexibility
283:Correctness
278:Consistency
246:maintenance
179:Subroutines
165:reusability
149:reusability
678:Categories
572:Robustness
567:Efficiency
413:2012-07-31
387:22 October
358:References
352:Code reuse
328:complexity
317:Modularity
307:changeable
242:deployment
191:namespaces
87:newspapers
621:Processes
542:Usability
462:Qualities
333:Stability
270:Adaptable
226:packaging
183:functions
117:July 2012
577:Security
562:Accuracy
535:External
469:Internal
346:See also
297:Flexible
211:platform
169:leverage
159:; these
663:Commons
301:Generic
250:upgrade
199:objects
187:modules
101:scholar
582:Safety
254:design
195:layers
161:assets
153:assets
103:
96:
89:
82:
74:
222:build
193:into
108:JSTOR
94:books
476:Size
389:2014
293:Fast
248:and
201:and
143:and
80:news
189:or
181:or
167:is
139:In
63:by
680::
375:.
244:,
240:,
236:,
232:,
228:,
224:,
147:,
447:e
440:t
433:v
416:.
391:.
313:)
130:)
124:(
119:)
115:(
105:·
98:·
91:·
84:·
57:.
34:.
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
