The purpose of this article is to construct the model of the software development process which usually consists of some steps, "analysis of requirement", "definition of functions" and so on, and to discuss the policies for managing the process efficiently, and to prepare the practical and easy implement. First we define the two categories of product specifications according to the mechanism which organizes the appropriate specifications of the product in the mind of the designer. These are called "Tacit Specification" and "Peculiar Specification". The former is the specification which is made unconsciously of the memories/knowledge of the designer. And latter is the one which is peculiar to the product and can not be made only of the memories/knowledge of the designer. Secondly, based on these categories we construct the model of the product development process, which consists of the 2 different kinds of processes which organize the tacit and peculiar specification respectively. And managerial policies for these processes are discussed especially focusing on the prevention and the quick detection of the unpredictable design changes. For this purpose, the easy tool which is the application of IDEF3 is prepared. Finally, these issues are verified using the field studies of the operational software development projects at production plant.
View full abstract