This research defines the software life cycle models and refers to the significance of the requirements gathering and analysis. There are many methods for capturing software requirements; this work focuses on one informal, two semiformal and two formal methods. Informal method in the requirements elaboration uses QUARS Tool techniques to deal with natural language. Semiformal methods are Unified Modeling Language (UML) and User Requirements Notation (URN). UML and URN supports different types of diagrams to view the system, URN is different from UML, and it is specially developed for telecommunication services and systems. The conversion of the URN into the other International Telecommunication Union -Telecommunication (ITU-T) languages is also supported. Formal methods use set-theory and logics, Specification and Description Language (SDL) and Knowledge Acquisition in automated specification or?Keep All Objectives Satisfied (KAOS) are examples of formal methods. KAOS uses graphical notations to elaborate the problem. Requirement engineering process has a great importance in the process of software development. Study demonstrates that to produce quality software more attention should be paid in improving the requirement engineering process. In this research five key process areas are described for the improvement of the requirement engineering process. First is the goal-based methodology in requirement engineering process. The second area is to support the cyclical and incremental activities in requirement engineering process. Third area is for encouraging the stakeholders involved in requirement engineering process. Fourth is for the support of management and fifth is for defining the planning phase of requirement engineering process.