In this research, an improved framework for requirement change management in global software development (RCM_GSD) has been presented. The objective is to manage the change in requirement specifically in global software development in an appropriate manner. The proposed framework RCM_GSD follows the required processes of RCM and reduces the concerns of GSD. Systematic Literature Review (SLR) was conducted for exploration of relevant research. During literature study, it is analyzed that the existing techniques of change management were not suitable for global software development (GSD). The change in requirements becomes more complicated in distributed environment due to the lack of communication and collaboration among globally dispersed stakeholders. The proposed model is compared with other models proposed in recent literature and analysis is made between them; feedback was obtained from the domain experts as well. The feedback and comparison results show that the proposed model provides an appropriate solution for requirement change management in GSD.

Regression testing is a means to assure that a change in the software, or its execution environment, does not introduce new defects. It involves the expensive undertaking of rerunning test cases. Several techniques have been proposed to reduce the number of test cases to execute in regression testing, however, there is no research on how to assess industrial relevance and applicability of such techniques. We conducted a systematic literature review with the following two goals: firstly, to enable researchers to design and present regression testing research with a focus on industrial relevance and applicability and secondly, to facilitate the industrial adoption of such research by addressing the attributes of concern from the practitioners' perspective. Using a reference-based search approach, we identified 1068 papers on regression testing. We then reduced the scope to only include papers with explicit discussions about relevance and applicability (i.e. mainly studies involving industrial stakeholders). Uniquely in this literature review, practitioners were consulted at several steps to increase the likelihood of achieving our aim of identifying factors important for relevance and applicability. We have summarised the results of these consultations and an analysis of the literature in three taxonomies, which capture aspects of industrial-relevance regarding the regression testing techniques. Based on these taxonomies, we mapped 38 papers reporting the evaluation of 26 regression testing techniques in industrial settings.

Context. A majority of the regression testing techniques proposed by the research have not been adopted in industry. To increase adoption rates, we need to better understand the practitioners' perspectives on regression testing. Objective. This study aims at exploring the regression testing state of practice in the large-scale embedded software development. The study has two objectives, 1) to highlight the potential challenges in practice, and 2) to identify the industry-relevant research areas regarding regression testing. Method. We conducted a qualitative study in two large-scale embedded software development companies, where we carried out semi-structured interviews with representatives from five software testing teams. We did conduct the detailed review of the process documentation of the companies to complement/validate the findings of the interviews. Results. Mostly, the practitioners run regression testing with a selected scope, the selection of scope depends upon the size, complexity, and location of the change. Test cases are prioritized on the basis of risk and critical functionality. The practitioners rely on their knowledge and experience for the decision making regarding selection and prioritization of test cases. The companies are using both automated and manual regression testing, and mainly they rely on inhouse developed tools for test automation. The challenges identified in the companies are: time to test, information management, test suite maintenance, lack of communication, test selection/prioritization, lack of assessment, etc. The proposed improvements are in line with the identified challenges. Regression testing goals identified in this study are customer satisfaction, critical defect detection, confidence, effectiveness, efficiency, and controlled slip through of faults. Conclusions. Considering the current state of practice and identified challenges we conclude that there is a need to reconsider the regression test strategy in the Preprint submitted to Information and Software Technology November 29, 2018 companies. Researchers need to analyze the industry perspective while proposing new regression testing techniques. The industry-academia collaboration projects would be a good platform in this regard.

Context: Regression testing is a well-researched area. However, the majority regression testing techniques proposed by the researchers are not getting the attention of the practitioners. Communication gaps between industry and academia, and disparity in the regression testing goals are the main reasons. Close collaboration can help in bridging the communication gaps and resolving the disparities. Objective: The study aims at exploring the views of academics and practitioners about the goals of regression testing. The purpose is to investigate the commonalities and differences in their viewpoints and defining some common goals for the success of regression testing. Method: We conducted a focus group study, with 7 testing experts from industry and academia. 4 testing practitioners from 2 companies and 3 researchers from 2 universities participated in the study. We followed GQM approach, to elicit the regression testing goals, information needs, and measures. Results: 43 regression testing goals were identified by the participants, which were reduced to 10 on the basis of similarity among the identified goals. Later during the priority assignment process, 5 goals were discarded, because the priority assigned to these goals was very low. Participants identified 47 information needs/questions required to evaluate the success of regression testing with reference to goal G5 (confidence). Which were then reduced to 10 on the basis of similarity. Finally, we identified measures to gauge those information needs/questions, which were corresponding to the goal (G5). Conclusions: We observed that participation level of practitioners and researchers during the elicitation of goals and questions was same. We found a certain level of agreement between the participants regarding the regression testing definitions and goals. But there was some level of disagreement regarding the priorities of the goals. We also identified the need to implement a regression testing evaluation framework in the participating companies.

Fungi are considered good producers of industrially valuable enzymes with higher enzymatic activities. Among these cellulases are group of extracellular enzymes commonly employed in many industries for the hydrolysis of cellulolytic material. Aspergillus fumigatus produced exoglucanase having high enzymatic activity (83 U/gds) during the solid-state fermentation of wheat straw under optimum physical and nutritional conditions. Maximum production was obtained after 72 h of fermentation, at 55 °C temperature, pH 5.5, 80 % moisture level, and 2 mL fungal inoculum. Production was further increased by the addition of fructose (0.3 %) as additional carbon source, peptone (0.4 %) as nitrogen source, Tween-80 (0.3 %) as surfactant, and ammonium sulfate (0.2 %) in media. Exoglucanase was 2.30-folds purified by adding 40 % ammonium sulfate with volumetric activity 95.4 U/gds and specific activity 14.74 U/mg. Further, it was 5.18-folds purified by gel filtration chromatography with volumetric activity 115.2 U/gds and specific activity 33.10 U/mg. Purified exoglucanase has maximum activity at 55 °C and pH 4.8 using 1 % Avicel aqueous solution as substrate. The K(m) and V(max) were 4.34 mM and 7.29 μM/min, respectively. Calcium, magnesium, and zinc ions have positive effect on exoglucanase activity.

Formal Method (FM) is an emergent feature that uses mathematical notations to mark accurate and explicit specifications that error and discrepancies are identified during early phases of the software development process. By using the Z specification, system specification, design and verification can improve the quality effectively. In this paper, we present the formal specification for the e-Health system by using Z schema. This paper will be motivation to Formal Methods that FM not only beneficial for mission critical systems but also in the commercial and business oriented applications, because the development time, verification and maintenance cost will drastically reduce.

No abstract

Formal methods can be used at any stage of product development process to improve the software quality and efficiency using mathematical models for analysis and verification. From last decade, researchers and practitioners are trying to establish successful transfer of practices of formal methods into industrial process development. In the last couple of years, numerous analysis approaches and formal methods have been applied in different settings to improve software quality. In today's highly competitive software development industry, companies are striving to deliver fast with low cost and improve quality solutions and agile methodologies have proved their efficiency in acquiring these. Here, we will present an integration of formal methods, specifications and verification practices in the most renowned process development methodology of agile i.e. extreme programming with a conceptual solution. That leads towards the development of a complete formalized XP process in future. This will help the practitioners to understand the effectiveness of formal methods using in agile methods that can be helpful in utilizing the benefits of formal methods in industry.