Software Requirement Registration and Traceability Model in the Context of Organizational Development

Abstract

Requirement engineering is the first and crucial phase in the development of software. It involves set of activities like system feasibility study, elicitation analysis, specification and management of the requirements. Poor and uncontrolled requirement engineering processes yield low quality, highly expensive software products. Obviously, organizations are highly dissatisfied with such systems. One of the most critical requirement engineering processes that grossly contribute to this inaccuracy is lack of proper implementation and measuring requirement engineering process, project management. Most software companies do not have formal registration and management of requirement hence it is difficult to trace and update the requirement whenever change requests come. Every requirement change by itself have an impact in the project therefore the impact of the change must be analyzed before accept and implement it because every requirement change required additional budget and time from initially stated. In order to overcome such problem, we design a new model that show how to integrate requirement engineering practice with organizational context, project management and practice gap in the requirement engineering. The new model may be useful for organization in order to improve the requirement engineering practice and it may be used as an input for the researcher for future requirement engineering process improvement. It is designed for requirement engineering process evolution in the organization and the implementation part of this research is important for registration and tracing of the requirement in the software project and the key result is design model that used to evaluate requirement engineering process in the software firm