Software Testing Process Models Benefits&Drawbacks: a Systematic Literature Review <s> TM2: <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> BIB001 </s> Software Testing Process Models Benefits&Drawbacks: a Systematic Literature Review <s> TM2: <s> One of the latest additions in defining the test process is the upcoming ISO/IEC 29119 standard, which aims to define a universally applicable generic test process model. However, currently the standard does not offer any support for the adoption process of the model. In this paper, we present our framework, which aims to combine a maturity level-based approach with the standard process. Our objective was to create an easy-to-use framework for organizations to assess how closely their existing test process follows the standard, and give feedback on improvement objectives. Our results indicate that combining maturity levels with the standard is a viable approach to assess the implementation of the standard in practice. <s> BIB002 </s> Software Testing Process Models Benefits&Drawbacks: a Systematic Literature Review <s> TM2: <s> Testing is an essential part of the software development lifecycle for gaining trust in the quality of the delivered product. Concerns have been raised over the maturity of existing test processes and techniques, and the desire to improve has been acknowledged. Even though there are test process improvement models available on the market, the guidelines on how to use them are unsatisfactory. This paper describes the empirical analysis of Test Maturity Model integration (TMMi) through a single-object case study of test process assessment and improvement planning conducted in Playtech Estonia’s Casino unit. An evaluation on the performance of TMMi is presented, raising also some concerns over its applicability in agile environments. Improvement possibilities for TMMi are described, which contribute to the potential enhancement of the framework. <s> BIB003 </s> Software Testing Process Models Benefits&Drawbacks: a Systematic Literature Review <s> TM2: <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 </s> Software Testing Process Models Benefits&Drawbacks: a Systematic Literature Review <s> TM2: <s> The software testing phase, despite its importance, is usually compromised by the lack of planning and resources in industry. This can risk the quality of the derived products. The identification of mandatory testing-related practices may lead to the definition of feasible processes for varied sizes of software companies. In this context, this work aims at identifying a set of key practices to support the definition of a generic, streamlined software testing process, based on practices that are described in the TMMi (Test Maturity Model integration), and verify the alignment of the devised process with the TMMi levels. We have performed a survey amongst Brazilian software testing professionals who work in both academia and industry, in order to identify priority practices to build the intended, streamlined process; additionally, we applied a diagnosis tool in order to measure the level of TMMi which is fulfilled with the devised process. A set of 33 (out of 81) practices were ranked as mandatory by most of participants, which represents 40 % of the TMMi’s full set of practices; on the downside, a testing process that relies on this subset of TMMi practices does not fully fulfil level 2 (Managed) of the maturity model. The identified subset of practices 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 in software development; even though the streamlined process does not encompass many practices that are spread across TMMi levels, a substantial subset of level 2 practices (Managed) should be accomplished with its adoption. <s> BIB005 </s> Software Testing Process Models Benefits&Drawbacks: a Systematic Literature Review <s> TM2: <s> Model-based testing (MBT) provides a systematic and automated way to facilitate rigorous testing of software systems. MBT has been an intense area of research and a large number of MBT techniques have been developed in the literature and in the practice. However, all of the techniques have been developed using their own concepts and terminology of MBT, which are very often different than other techniques and at times have conflicting semantics. Moreover, while working on MBT projects with our industrial partners in the last several years, we were unable to find a unified way of defining MBT techniques based on standard terminology. To precisely define MBT concepts with the aim of providing common understanding of MBT terminology across techniques, we formalize a small subset of the recently released ISO/IEC/IEEE 29119 Software Testing Standard as a conceptual model (UML class diagrams) together with OCL constraints. The conceptual model captures all the necessary concepts based on the standard terminology that are mandatory or optional in the context of MBT techniques and can be used to define new MBT tools and techniques. To validate the conceptual model, we instantiated its concepts for various MBT techniques previously developed in the context of our industrial partners. Such instantiation automatically enforces the specified OCL constraints. This type of validation provided us feedback to further refine the conceptual model. Finally, we also provide our experiences and lessons learnt for such formalization and validation. <s> BIB006
No comprehensive documentation about agile practices in comparison with CMMI and application of best practices BIB003 . TM3: No practical and realistic improvements on embedded software BIB001 . TM6: Priorities are not defined in the case of lack of time or resources BIB005 . Model complexity TM2: Very detailed practices and distribution across the specific goals and process areas make the model complex and difficult to understand BIB004 . TM8: A high level of abstraction introduces ambiguity in understanding the concepts BIB006 . Practical limitations TM2: Practical limitations in real cases, for example the implementation of the idea to move all processes to one level before proceeding to the next is not possible and the level requirements are not intuitive BIB002 . TM17: It requires continuous adaptation of the practices  . Other TM12: The organization should construct and strengthen the knowledge-oriented culture and the team enthusiasm. TM12: The organization should understand the model fully when planning and adapting the testing processes.