In this paper we report the adoption of use cases by a small organization in a university setting. Use cases were first introduced in the middle of a huge project and adopted thereafter for later projects. The paper mostly focuses in the first experience, whose most interesting characteristics were the large size of the resulting specification, the fact that it took place once the project had started (for documentation purposes instead of driving the development) and the limitation that resources allocated were not as much as required. We present the lessons learned from this experience.

Peer Reviewed