Early detection of faults in Software Development Life Cycle (SDLC) can significantly reduce the cost and shorten the time to deliver a certain product to market. Requirement based testing involves using requirement as the basis for generating test cases. This paper present a systematic review of requirement based testing exploring the hidden capabilities and challenges of the research that has been accomplished over the years. The study attempts to reveal the facts about Requirement based test case generation and presents critical evaluation of the proposed methods by researchers.
In current practice, requirements are the source of from which test cases are derived manually, but this is so laborious and costly process . With such drawbacks in mind, it is imperative to develop automatic testing technique, as manual deriving methods are laborious and fallacious. Testing process includes test case generation, test execution, and test evaluation . As customers demand more reliable, high efficient and low cost software products, the success of product engineering in the software industry is based upon good quality assurance .
Two modes are applied in generation of software products. In conventional way of Software Development Life Cycle (SDLC), testing software is carried out at later stage; however, it is very expensive, as high cost is incurred upon correction of errors. In second mode, i.e. Object Oriented Software Development (OOSD), testing is carried out at an early stage, soon after system requirements are available. It would surely eliminate the unwanted delay, confronted in the former mode. Along with this it would keep the errors to the minimum level and cost of fixing errors as well . Huge expenses in software development are drastically brought to lower level in requirement based test case generation. Software testing is crucial in developing a system, as about 30-50 % of the total cost of the system, is incurred upon testing process . In requirement based test case generation, the stakeholders can rightly claim that requirements they confirmed, are tested in right manner. Their claims necessitate the requirement based testing. Two categories of requirements are functional and Non-Functional Requirements (NFR), which are obtained during analysis phase. Functional requirements deal with the work, which the new system has to carry out, while non-functional requirements handle all the constraints of the system .
This paper discusses software testing where testing activities reveals the presence of faults and proposes an automatic testing tool to generate test cases automatically. The remainder of the paper is organized as follows. Section II discusses the system’s literature review. Section III presents critical evaluation of the discussed literature. Finally, we conclude our paper in Section IV and give some suggestions for future work.
The section describes the...