ترجمه مقاله بهینه سازی تست نرم افزار - نشریه الزویر

The goal of any business is to satisfy the needs of its target customers, and IT industry is not an exception from that rule. Thus, the upgraded version of the V-model testing is supposed to deal with the weaknesses of the original version in question by combining it with the method known as agile testing. At the beginning of the report, hypothesis such as the strengths and weaknesses of the existing V-model testing via literature review and interviews with respective specialists in the sphere were analysed. Successively, the possible advantages of agile method of testing were then considered. Moreover, the report comes up with the ways in which the two models could be naturally combined to produce a much more effective one. Once the new model was presented, its strengths and weaknesses were assessed by the means of a case study analysis using metric and a data analysis through a survey were conducted to evaluate the credibility of the futurist model. Promptly, the research found that the suggested testing model provides better results than the common version of V-model testing. Firstly, a real case scenarios under metric evaluation of the models have indicated that the proposed model is better than the V-model, since it can handle the following aspects; reduced testing time, debugging, prioritization of requirements, easy mapping of roles and improved visibility of project resources. Secondly, a survey data analysis highlighted various advantages of the future model. The top priorities of the new model from the respondent’s perception were; the new model manages rapidly changing priorities, it accelerates time to market, it increases productivity and it improves quality.

1. Introduction

With There are a myriad of Software development processes and methods available that can be used in the development of software, some of which are traditional and are termed as “old-fashioned” by proponents of newer and more “classy” processes and methodologies such as Agile methodologies. The more traditional approaches to software development include the waterfall and V-model methods which have been in use in software development cycles for decades, but are regularly the point of critics. The focus of this paper will primarily be on the V-model of software development combined with the testing process of more modern approach of software development known as agile development. The V-model of software development is regarded as an extension of the waterfall model and in this type of methodology; software development execution of processes happens in a sequential approach with a V shape that involves a sequence of processes and is also regarded as the verification and validation model. The V model is regarded as a high level design of Test Driven Development (TDD), and each development phase of the software is directly associated with a corresponding testing phase. This means that each corresponding phase of testing is planned in parallel with the development phase hence test cases are developed in the development phase in order to be implemented in the corresponding testing phase, but typically testing is conducted once the software is completed. As mentioned above it consists of two aspects, verification and validation. Verification is an internal process as compared to validation and typically involves checking if the software complies with its technical specifications as defined and guided by a system analyst. Validation, on the other hand, involves the compliance of the software to the requirements, needs or specification of the customer. In this case, the left side of the V model describes the various business and technical details while the right side is more concerned about the testing.

6. Conclusion and Recommendations

Software development and integration is a multifaceted form of computing. The availability of functional and efficient software tool for review of trends and activities can result in business success. The V model is one of the software development processes, however, the proposed software development process is more efficient than the V model. The case studies under review have indicated that the proposed model is better than the V-model, since it can handle reduced Testing Time, debugging, prioritization of requirements, easy mapping of roles, and improved visibility of project resources. Additionally, the validation checks are better implemented in the proposed systems.