Answers are grounded in this paper and cite their sources.
The authors have developed a framework for the specification of generic reusable components existing wholly at the architectural design level. All features of the component necessary for its effective use are stored with the component, including documentation, design rationale, formal specifications, reuse history and access rights. Design-level genericity is introduced to widen the scope of applicability of the component. At design level a generic component is a partially defined object whose behavior depends on the behavior of parts that are not yet designed. It is shown how to integrate the design of such components into the full HOOD life-cycle method.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">></ETX>
No takes yet. Share an insight, caveat, or question.
D'Alessandro et al. (2002) studied this question.
Synapse has enriched 3 closely related papers on similar clinical questions. Consider them for comparative context: