A Survey of System Development Process Models



Typical Tasks in the Development Process Life Cycle

Process Model/Life-Cycle Variations

Ad-hoc Development

The Waterfall Model

Iterative Development


The Exploratory Model

The Spiral Model

The Reuse Model

Creating and Combining Models



The Reuse Model

The basic premise behind the Reuse Model is that systems should be built using existing components, as opposed to custom-building new components. The Reuse Model is clearly suited to Object-Oriented computing environments, which have become one of the premiere technologies in today's system development industry.

Within the Reuse Model, libraries of software modules are maintained that can be copied for use in any system. These components are of two types: procedural modules and database modules. When building a new system, the developer will "borrow" a copy of a module from the system library and then plug it into a function or procedure. If the needed module is not available, the developer will build it, and store a copy in the system library for future usage. If the modules are well engineered, the developer with minimal changes can implement them.

The Reuse Model consists of the following steps:

Problems/Challenges Associated with the Reuse Model

A general criticism of the Reuse Model is that it is limited for use in object-oriented development environments. Although this environment is rapidly growing in popularity, it is currently used in only a minority of system development applications.