Conflicts can happen when gathering requirements for software development. This article looks at different types of conflicts that can arise and focuses on conflicts between goals and requirements from different viewpoints. It introduces a common type of conflict called divergence and suggests ways to detect and resolve conflicts systematically. The researchers propose using formal techniques and heuristics to identify conflicts and offer methods to make goals and requirements conflict-free. The findings are discussed within the context of the KAOS methodology for goal-driven requirements engineering.