Comprehensive requirement engineering (RE) process acts as a backbone of any successful project. RE processes are very complex because most of the requirement engineering documentation is written in natural languages, which are less formal and often distract the designers and developers of the system. To streamline different phases of the software lifecycle, first we need to model the requirement document so that we can analyze and integrate the software artifacts. Designers can ensure completeness and consistency of the system by generating models using the requirement documents. In this paper, we have made an attempt to analyze extreme programming based RE approach to understand its utility in the requirement elicitation phase. In this study, different RE process models are evaluated and a comparison of the extreme programming technique is drawn to highlight the merits of the latter technique over the conventional RE techniques.

A requirement is a capability to which a product or service should conform to. A meticulous consideration to requirements engineering acts as a backbone of software projects. Ambiguous and unrealistic requirements are major source of failure in the software-intensive systems. Requirements engineering processes are complex as most of the requirements engineering documentation is written in natural languages which are less formal and often distract the designers and developers. Requirements management is a continuous process throughout the project lifecycle and relates to documenting, analyzing, tracing and prioritizing requirements and then finally controlling changes. The main issues related to requirements management are usually social, political and cultural. Software requirement engineers who gather the requirements generally consider that such issues are beyond the scope of their profession as they deem them within the project management ambit. In this study, we highlight the management issues that arise in the requirements engineering process and explore the possibilities to tackle them amicably. The study is supplemented with a critical review of the existing methodologies for resolving and managing software requirements.

Most of the software projects fail to meet the desired level of quality and standards due to different types of defects introduced during the course of requirement solicitation, designing and development. These defects inexorably hinder the secure deployment or smooth operations of the software systems. One of the key reasons for this misfortune is the lack of proper defect prevention planning while formulating the software architecture. Defect prevention needs to be a thorough and critical phase because it has a direct impact on quality of the product which cannot be compromised. This paper looks into different defect prevention techniques and analyses them critically. The scope of this study is restricted to the identification of the modern trends in defect prevention.