Abstract
It is generally recognized that problems during a project are often caused by the phases of “requirement definition” or “specifications process”. In this paper the concept of “underlying requirements” is proposed and it is shown that conflicts among underlying requirements may cause such problems. Then it is shown that these problems can be solved applying the principle of “clarification and restriction”, which used to be a tacit understanding, in a new and broader context. Methodologically the argument is developed in the domain abstracted from the author’s experiences and images of the results are illustrated using another experience.
