The traditional workflow process model is typically illustrated with a graph of activities, tasks, deliverables and techniques. From an object-oriented perspective, every identifiable concept can be depicted with an object, and from this same. perspective, evolution can be demonstrated with object interactions. There are at least two ways to describe the software development process using an object-oriented model. The first, an activity-based approach, uses activities as objects, tasks as object operations and deliverables as operation postconditions. The second, a deliverable-based approach, uses deliverables as objects, tasks as object operations and activities as object states. Techniques are considered the implementation of operations in both cases. The article will:

a.	compare activity-based and deliverable-based object models of development processes and
b.	describe our experience with a deliverable-based object model that we used for about one year when we developed an application used for financial management.