Software Testing Process Models Benefits&Drawbacks: a Systematic Literature Review <s> Which are the phases/practices of testing models for different domains? (RQ4) <s> Existing test process assessment and improvement models intend to raise maturity of an organization with reference to testing activities. Such process assessments are based on ldquowhatrdquo testing activities are being carried out, and thus implicitly evaluate process quality. Other test process measurement techniques attempt to directly assess some partial quality attribute such as efficiency or effectiveness some test metrics. There is a need for a formalized method of test process quality evaluation that addresses both implicitly and partially of these current evaluations. This paper describes a conceptual framework to specify and explicitly evaluate test process quality aspects. The framework enables provision of evaluation results in the form of objective assessments, and problem-area identification to improve the software testing processes. <s> BIB001 </s> Software Testing Process Models Benefits&Drawbacks: a Systematic Literature Review <s> Which are the phases/practices of testing models for different domains? (RQ4) <s> It is well known that most of mission critical systems like defense systems demand higher quality than general software systems. In order to assure the high quality of the systems, those software systems must be thoroughly tested with well defined testing processes. As software systems evolve, software testing should also be improved with continual-base. Even if there are some previous researches on test process model, those models have some limitations and problems to be applied for software testing process improvement in a specific domain like military weapon systems. In this paper, we propose a new testing maturity model, called MND-TMM (Ministry Of National Defense-Testing Maturity Model), which can be adopted effectively for the weapon software system development. We also present OWL ontology for the MND-TMM, called MTO(MND-TMM ontology) to help software organizations set up their effective testing strategies and improve their testing processes, which can lead to high quality product developments. <s> BIB002 </s> Software Testing Process Models Benefits&Drawbacks: a Systematic Literature Review <s> Which are the phases/practices of testing models for different domains? (RQ4) <s> Embedded software requires high quality to meet customer requirements and to achieve product competitiveness. Testability Maturity Model (TMM)and Test Process Improvement (TPI) are recommended to improve test activities, which are important for product quality. However, TMM and TPI in themselves are not appropriate for embedded software since they are lack of consideration on embedded software. This paper deals with the properties of embedded software and industrial challenges based on existing model and we suggest Embedded Test Process Improvement Model (Emb-TPI). Emb-TPI considers practical improvement strategies for the quality of embedded software and focuses on evaluation procedures that achieve cost-effectiveness and valid evaluation results.We present the results of applying Emb-TPI to product development division (PDD) to prove that the model is valid. Emb-TPI provides methods to evaluate test activities in embedded software development and helps to reveal insufficient areas of test activities, which ultimately improves test capabilities. <s> BIB003 </s> Software Testing Process Models Benefits&Drawbacks: a Systematic Literature Review <s> Which are the phases/practices of testing models for different domains? (RQ4) <s> Context: Testing is one of the most important phases of software development. However, in industry this phase is usually compromised by the lack of planning and resources. Due to it, the adoption of a streamlined testing process can lead to the construction of software products with desirable quality levels. Objective: Presenting the results of a survey conducted to identify a set of key practices to support the definition of a generic, streamlined software testing process, based on the practices described in the TMMi (Test Maturity Model integration). Method: Based on the TMMi, we have performed a survey among software testing professionals who work in both academia and industry. Their responses were analyzed quantitatively and qualitatively in order to identify priority practices to build the intended generic process. Results: The analysis enabled us to identify practices that were ranked as mandatory, those that are essential and should be implemented in all cases. This set of practices (33 in total) represents only 40% of the TMMis full set of practices, which sums up to 81 items related to the steps of a testing process. Conclusion: The results show that there is a consensus on a subset of practices that can guide the definition of a lean testing process when compared to a process that includes all TMMi practices. It is expected that such a process encourages a wider adoption of testing activities within the software industry. <s> BIB004
Models also define practices which are important for a testing process (Tables 11, 12, 13, 14 and 15) . We collect the practices based on models' phases ( i. Planning, ii. Test Case Design, iii. Setup of test environment and data, iv. Execution and Evaluation, and v. Monitoring and Control) and map them to specific domains. The embedded software domain is not included in the tables, because no paper discusses the practices of the Emb-TPI model. General. We collect practices of three models. The research of Camargo et al. BIB004 identifies practices of the TMMi model [TM2] based on a survey. The authors define three profiles to analyze the results regarding the level of importance. They created a reduced set of practices (31 items), which are important for all three profiles BIB004 . The first phase is Planning, which defines how testing will be executed and what will be tested. The Planning phase includes practices such as Identify product risks and Analyze product risks, with outputs necessary for test prioritization. Other practices Identify items and features to be tested, Establish the test schedule and Plan for test staffing are also marked as mandatory because they are included in the test plan and thus related to the practice Establish the test plan. The phase Test Case Design include only two mandatory practices: Identify and prioritize test cases and Identify necessary specific test data. During the Setup of Test Environment and Data phase the tests and requirements are prioritized and implemented. The order is defined based on the product risks. There are practices such as Develop and prioritize test procedures, Develop test execution schedule, Implement the test environment and Perform test environment intake test. During the Execution and Evaluation phase test are performed and possible defects are reported. Moreover, results and the achievement of test goals are evaluated. Status checking and, if necessary, corrective actions are parts of the Monitoring and Control phase BIB004 . The study of Farooq et al. BIB001 describes practices of the Meta-measurement approach [TM11]. The first step includes establishing evaluation requirements which represent the evaluator's needs and objectives. The second step is Lack of applicability  TM1,TM3,TM9 : Not applicable for small-to medium-sized enterprises (SME)  . TM1,TM3,TM9: Several limitations in the implementation for specific domain. Too complex and difficult to adapt for a specific case, requires the experts' process evaluation, difficult to apply without CMM or combine with other models and lack of important key areas BIB002 . Lack of support for specific areas TM1: No support for test basic elementary factors (e.g. test organization, human resource management and test bed BIB003 .