Projects fail for many different reasons, but most often because of a lack of clear understanding of the project requirement. The failure to understand the users needs arises for many reasons, many of them associated with the seeming inability to communicate effectively with the user community. If one manages to survive these risks, then a failure to accurately record and analyze the project requirement remains a significant risk. A very significant part of the understanding of the project requirement is expressed in the relationships between the requirements. The formation of an integrated, complete and consistent requirement model is essential.