The existence of so-called reusable modules does not necessarily indicate a correct or even desirable design. However, the design of a reusable Ada module implies an organized attempt to design a reusable Ada simulation. It is this organized approach that must be addressed before a reusable library can be developed. The approach must deal with certain questions:

(1) What are the goals that guide the development and use of the reusable library?

(2) What is the structure of the reusable software?

(3) What is the structure of the reusable simulation?

(4) What are the priorities for the development of software for the library?

An attempt at developing a reusable library without answering these questions is futile. Trade-offs must be performed between such goals as readability, maintainability, genericism, speed, and efficiency. The structure of the reusable softare will facilitate the efficient implementation of the software into a new project. A reusable library is of little use if the software will not fit the mold of the overall simulation. And finally, the plan for the development of software must be prioritized to allow developement based on importance and usefulness. This paper addresses the requirements and the design approach of such a user based reusable simulation software library.