Documenting framework behavior [1 citations — 0 self]
Abstract:
Abstract: Object-Oriented frameworks must be equipped with appropriate documentation; otherwise application developers will be forced to go through the code of the framework they are using in order to see how to use it, thereby minimizing the advantages of frameworks. We point out the need for a new approach to the specification of the behavior of frameworks, outline a possible approach, and briefly consider how an application developer can combine a framework specification of the type proposed with appropriate information about the code he supplies to arrive at a specification of his particular application.
Citations
| 1219 | Object-oriented Software Construction – Meyer - 1988 |
| 354 | A behavioral notion of subtyping – Liskov, Wing - 1994 |
| 134 | Proofs of networks of processes – Misra, Chandy - 1981 |
| 114 | Contracts: Specifying Behavioral Compositions in Object-Oriented Systems – Helm, Holland, et al. - 1990 |
| 25 | Modular reasoning in the presence of subclassing – Stata, Guttag - 1995 |
| 20 | A technique for documenting the framework of an object-oriented system – Campbell, Islam - 1993 |
| 15 | Inheriting and modifying behavior – Soundarajan, Fridella - 1997 |
| 11 | Mastering Object-Oriented Design in C – Horstmann - 1995 |
| 7 | Design Patterns: Elements of Reusable OO Soft – Gamma, Helm, et al. - 1995 |
| 6 | Special issue on object oriented application frameworks – Fayad, Schmidt - 1997 |
| 4 | Axiomatic semantics of CSP – Soundarajan - 1984 |
| 1 | governed support for realizing design patterns – Law - 1995 |
| 1 | Understanding frameworks, technical report, available at www.cis. ohiostate. edu/neelam – Soundarajan - 1997 |

