Ow and Yaacob conducted a survey on software Quality Assurance in Malaysia. The survey investigated the trends in SQA investments with respect to development purposes. In their work, the QA problems encountered have been addressed from three main sources: people, management and technology. They found that there is a significant increase in awareness of the importance of software quality even by those companies which developed software systems for internal applications.
To develop high-quality software, Lee et. Yasuda and Yamada discuss the concept and practice of software quality assurance in Japan. Survey methodology The survey was carried out by filling an Electronic form. The form had a total of 50 questions about performing quality assurance and applying software practice that affect the quality.
Two experts from the Faculty of Information Technology at the Islamic University of Gaza were asked to validate the questionnaire. Some modifications and additions were considered to the questions and the final questionnaire was constructed.
The questionnaire was available for 20 days. It was announced to software development groups by means of discussion lists and direct email messages sent to professionals and institutions. The parsed contents of answer were analyzed statistically using excel The size of these Participants varied from low size organization to large size organizations.
Figure 1 shows the percentage of participants in each size. It was found that Figure 2 shows the distribution of the job responsibilities in the sample. Since the participants may have more than one role, it is clear that most of them were programmers. The questionnaire found that Table 1 shows that most of them works in less than five years. Some of them work on more than one type of these applications as shown in table 2.
Also, it is noticeable that some of these units are not fully dedicated to the quality assurance. About the nature of the project that developed locally in Gaza. The survey indicates that most of software developers In addition, most of the respondents Regarding the question of whether they have defined metrics to measure the software quality, most developers The research tried to investigate the problem of late submission of the developed projects by the local organization in Gaza since it affects the quality of the produced software.
As in figure 3 , This means that the quality will be low according to time limitations and unplanned actions. And the second reason was "repeated modification in the requirements". This means, as the participants believe, that the main reason for late submission is the customer understanding of the system.
The Reasons for the late submission About the productivity of our organizations in Gaza, the survey indicated that About the average number of users for the developed projects, Accordingly, it can be concluded that systems built in Gaza Strip are mostly small. Therefore, we designed a set of questions to examine the usage of some requirements analysis activates in software development life cycle. The process began from validating the requirements elicitation and towards producing software requirements specification document.
The questions measured the usage of these activities, and the results varied among the participants. We asked the participants about doing analysis for the developed system before coding and we found that Hence, it can be concluded that the one reason many systems failed is because of the lack of analysis. About using IEEE standards for making software requirements specification report, it was found that The most important question was about using requirements elicitation techniques; we found that most of developers Figure 5 summarizes these results.
This course covers all quality assurance methods and techniques that aim at achieving this goal of building quality into the software. The course is a must for every project manager, QA manager and test manger.
Contact Us. Concepts Many software organizations try to achieve software quality by focusing on testing activities that are normally done after the product has been put together by the development team. Omri , C. Sinz Published 29 April Computer Science ArXiv Over the last years, machine learning techniques have been applied to more and more application domains, including software engineering and, especially, software quality assurance.
Important application domains have been, e. The ability to predict which components in a large software system are most likely to contain the largest numbers of faults in the next release helps to better manage projects, including early… Expand. View PDF on arXiv. Save to Library Save. Create Alert Alert. Share This Paper. Figures and Tables from this paper. Tree-based software quality estimation models for fault prediction.
0コメント