Object-oriented software construction (2nd ed.)
Object-oriented software construction (2nd ed.)
Object-oriented analysis and design, part 2.
C/C++ Users Journal
The unified software development process
The unified software development process
Contract Soundness for object-oriented languages
OOPSLA '01 Proceedings of the 16th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
The Java Language Specification
The Java Language Specification
An Experimental Evaluation of Programming by Contract
ECBS '02 Proceedings of the 9th IEEE International Conference on Engineering of Computer-Based Systems
Developing Sequence Diagrams in UML
ER '01 Proceedings of the 20th International Conference on Conceptual Modeling: Conceptual Modeling
iContract - The Java(tm) Design by Contract(tm) Tool
TOOLS '98 Proceedings of the Technology of Object-Oriented Languages and Systems
| Hi-index | 0.02 |
This paper presents an experimental evaluation carried out in an academic environment. The goal of the experiment was to compare how different methods of documenting semantic information affect software reuse. More specifically, the goal was to measure if there were any differences between the methods with regard to the time needed to implement changes to existing software. Four methods of documentation were used; executable contracts, non-executable contracts, Javadoc-style documentation and sequence diagrams. The results indicate that executable contracts demanded more time than the other three methods and that sequence diagrams and Javadoc demanded the least time.