As time continues to advance, the need for robust security threat mitigation has become increasingly vital in software. It is a constant struggle to maximize test coverage through optimal data generation. We conducted explanatory research to maximize test coverage of security requirements as modeled in the structured misuse case description (SMCD). The acceptance test case is designed through the structured misuse case description for mitigation of security threats. Mal activity is designed from SMCD upon which constraints are specified in object constraint language (OCL) in order to minimize human dependency and improve consistency in the optimal test case design. The study compared two state-of-the-art test coverage maximization approaches through optimal test data generation. It was evident through the results that MC/DC generated optimal test data, i.e., n + 1 test conditions in comparison to the decision coverage approach, i.e., 2n test conditions for security threats. Thus, MC/DC resulted in a significantly lower number of test cases yet maximized test coverage of security threats. We, therefore, conclude that MC/DC maximizes test coverage through optimal test data in comparison to decision coverage at the design level for security threat mitigation.
As time continues to advance, the need for robust security threat mitigation has become increasingly vital in software. However, ensuring early effective security threat mitigation requires optimal test data and consistent test case design. It is a constant struggle to maximize test coverage through test data optimization. We conducted explanatory research to maximize test coverage of security requirements as modeled in Structured Misuse Case Description (SMCD) i.e., structured specification of misuse case, so as to improve consistency in optimal test data generation. We specified constraints upon Mal activity in Object Constraint Language (OCL) in order to minimize human dependency and improve consistency in optimal test data generation. It was evident through results that MC/DC generated optimal test data of security threats through SMCD in comparison to the Decision Coverage method thus resulting in designing a significantly lower number of test cases and yet maximizing test coverage of security threats. MC/DC generated test data with n+1, while Decision Coverage generated test data with〖 2〗^n, we, therefore, conclude that MC/DC maximizes test coverage through optimal test data from SMCD in comparison to Decision Coverage.
The software industry is dynamic and constantly evolving, which offers challenging research opportunities. It is also moving toward innovation and changing its working styles to meet customer satisfaction, especially when customer requirements change frequently. Scrum is vital in this scenario for software industries since Scrum Master provides services to the scrum team as a servant leader by responding to change. However, in Software Industries, Scrum Masters still face obstacles in performing their responsibilities smoothly. The main objective of this research is to identify those challenges and their corresponding reasons, which are barriers for Scrum Masters in providing their services to the Scrum team. Quantitative and qualitative data collected through industrial surveys were analyzed through statistical techniques and thematic methods for qualitative data to reach the key facts. Our results reveal that 62 percent of organizations regularly apply Scrum to organizations. In addition, 61 percent of Scrum masters play their responsibilities smoothly in the industries. However, 39 percent face challenges; for instance, it was evident from survey results that Scrum Master plays an active role and faces big challenges in fulfilling his responsibilities since people are not willing to practice Scrum compared to traditional software models. Besides, Scrum Masters are constrained due to sociocultural issues. Software Industries and even the most experienced, i.e., 10-15 years experienced and Certified Scrum Masters, face the challenge of unavailability of or proxy product owners.