Software requirements play a very important role in the development and management process of software systems. Development and analysis of requirement specification is a crucial and time-consuming task if it is done manually. Software quality is determined by the accuracy, consistency, and completeness of the requirement specification document. Between business people, requirements researchers, and software developers, there are also frequent discrepancies and ambiguities in the realizing requirements during the requirements elicitation process. Knowledge graphs, which describe information as a semantic graph, have raised a great deal of controversy in both the academic and professional worlds. Their ability to provide information that is semantically organized has led to significant potential solutions for a variety of activities, including question-answering, recommendation, and information retrieval. This paper presents their use in the field of requirement engineering phases of software development. We have discussed the process of creating knowledge graphs, their functioning, and some major approaches discussed in the literature so far, especially in the field of requirement engineering. We also tried to present the positive and negative sides of the approaches and a comparative analysis of these approaches is also included.