Checklist for Identifying Reusable Componenents
The questions should help to identify reusable components.
- Is component functionality required on future implementations?
- How common is the component's function within the application domain?
- Is there duplication of the components's function within the domain?
- Is the component hardware-dependent?
- Does the hardware remain unchanged between implementations?
- Can the hardware-specifics be removed to another component?
- Is the design optimized enough for the next implmentation?
- Can we parameterize a nonreusable component so that it becomes reusable?
- Is the component reusable in many implementations with only minor changes?
- Is reuse through modification feasible?
- Can a nonreusable component be decomposed to yield reusable components?
- How valid is component decomposition for reuse?
Hooper, J.W. and Chester, R.O.: Software Reuse - Guidelines and Methods. Plenum Press, New York, 1991.