Requirements Engineering Requirements Traceability

CHAPTER TWO

LITERATURE REVIEW

2.1 Introduction

The idea of requirements traceability is to make high quality product by not changing requirements and ensure it meets the stakeholder viewpoint. This chapter highlights the importance of requirements engineering and its branches, requirements development and requirements management , as well as the focus of previous studies on requirements traceability.

2.2 Requirements Engineering

“Requirement Engineering (RE) as a field, plays an important part over the entire process of product development” (Pandey, Suman, & Ramani, 2010). “The method of integrating RE in the product development cycle is largely affected by the acceptance and performance of a product in a market” (PC & Prabhu, 2012). RE is

Whereas, others said that practice is a technique used to ensure that all the requirements that have been extracted, analyzed, and verified that have been included in the software and there is no ambiguity or loss of those requirements (Katta & Stålhane, 2014; Winkler & von Pilgrim, 2010). In this study, the researcher will use the term "Requirements Traceability Practice" will be used to refer all of practices terms. In the following paragraphs are the most important studies about requirements traceability practice will be discussed. Gotel and Finkelstein in (1994) describe the results of empirical studies into traceability, that was conducted in 1992 and lasted throughout the year. About one hundred software development practitioners with approximately 30 years of experience holding diverse position, in a large organization, were involved in the study. Five focus group sessions were held on attended by thirty-seven (37) practitioners for the consolidation of data and for independent observation of the process of gathering requirements (practically). Also, a comprehensive questionnaire was issued, and development workshops were held. Multiple perspectives were found by the authors on the expectations from traceability, problems encountered, and conflicts evident between parties in charge of producing traceability and the users of traceability. Although the rsearcher’s concern was to understand and expose the problem area scope, the main benefits of traceability to their subjects was not reported. The research by Ramesh and Jarke in (2001) was on a large practitioner study of traceability which took over three years for data collection in the 1990’s. Fifty-eight (58) students of masters in information technology were included in a pilot study to produce