We found that process definition was far more time consuming than we had anticipated, due to the complexity of defining a real-world process. Definition of a software process requires the implementation of the same basic life cycle steps of requirements analysis, design, code, integration, test, and maintenance that a software programming effort entails. We discovered that skipping or minimizing some of these steps only causes problems later in the process definition life cycle. Late in phase one, we found that more process requirements analysis activities were necessary to help us understand inputs and outputs and uncover inconsistencies. The second phase was not as time consuming as the first phase since we were more careful to include sufficient analysis work up front. This led to a halving of the amount of time that was needed for process definition, even though a larger process was defined in phase two.