Wyniki wyszukiwania - Biblioteka Nauki

1

Software Change Prediction: A Systematic Review and Future Guidelines

100%

Malhotra R. , Khanna M.

|

tom Vol. 13, nr 1

227--259

EN

Background: The importance of Software Change Prediction (SCP) has been emphasized by several studies. Numerous prediction models in literature claim to effectively predict change-prone classes in software products. These models help software managers in optimizing resource usage and in developing good quality, easily maintainable products. Aim: There is an urgent need to compare and assess these numerous SCP models in order to evaluate their effectiveness. Moreover, one also needs to assess the advancements and pitfalls in the domain of SCP to guide researchers and practitioners. Method: In order to fulfill the above stated aims, we conduct an extensive literature review of 38 primary SCP studies from January 2000 to June 2019. Results: The review analyzes the different set of predictors, experimental settings, data analysis techniques, statistical tests and the threats involved in the studies, which develop SCP models. Conclusion: Besides, the review also provides future guidelines to researchers in the SCP domain, some of which include exploring methods for dealing with imbalanced training data, evaluation of search-based algorithms and ensemble of algorithms for SCP amongst others.

2

Analiza przyczyn problemów jakości oprogramowania na podstawie ankiet osób uczestniczących w procesie wytwarzania systemów informatycznych

88%

Pieszczyk E. , Werewka J.

|

nr 3(37)

85-102

EN

The level of failure of IT projects is high and has not changed over many years despite improvement in software development processes. One of the obvious reasons for this is shortening the delivery time of information systems in the projects and rapidly changing technology. Quality assurance in software development process is a key issue in ensuring the proper operation of an IT system. In order to know the causes of the problems, it is important to know viewpoints of members of the teams developing software. These views were obtained by carrying out the survey. At the beginning categories of reasons are identified using Ishikawa diagram, a tool for quality management. In the next step an analysis was performed using the Pareto principle. The analysis allowed the identification of the most important causes of errors in the software development process. A detailed analysis of the observed results and appropriate conclusions of this analysis will help improve the processes of software development and collaboration between project management and software development processes.

3

Badanie satysfakcji jako atrybutu jakości systemów e-usługowych

75%

Łopaciński K. , Maciaszek L. A.

|

nr 2/2015 (52), t.1

37-50

EN

Due to the growing demand for different types of e-services there are more and more systems that allow for e-services provision and management on the market. The quality of such solutions should be improved in cooperation with customers on the basis of information about the level of their satisfaction with the usage. This can be possible owing to regular user satisfaction research. The article presents the concept of estimating satisfaction with e-service software which is based on the achievements of marketing research and software quality studies.

PL

W związku z rosnącym zapotrzebowaniem na różnego typu e-usługi na rynku pojawia się coraz więcej systemów pozwalających na świadczenie tego typu usług i zarządzanie nimi. Doskonalenie jakości takich narzędzi powinno być dokonywane przy współudziale klientów, na podstawie informacji o poziomie ich zadowolenia z użytkowania. Jest to możliwe dzięki prowadzeniu przez przedsiębiorstwa regularnych badań satysfakcji użytkowników. W artykule zaprezentowano koncepcję szacowania satysfakcji z użytkowania oprogramowania e-usługowego, która opiera się na dorobku badań marketingowych oraz badań nad jakością oprogramowania.

4

A design and experiment of automation management system for platform as a service

63%

Tashkandi A.

|

2019

|

tom Vol. 18

711--715

EN

Security [11] and quality [4] of cloud computing services represent significant factors that affect the adoption by consumers. Platform as a Service (PaaS) is one of cloud computing service models [14]. Management of database systems, middleware and application runtime environments is automated in PaaS [2]. PaaS automation management issues and requirements were collected in three rounds from information technology experts using Delphi technique. In this paper, PaaS automation quality and security management system is proposed and evaluated. Evaluation of the management system was based on experiment in a private cloud for an organization undergoing a transformation toward PaaS computing.

5

Wybrane Zagadnienia odpowiedzialności cywilnoprawnej w kontekście zastosowań sztucznej inteligencji

63%

Hulicki M.

|

tom 28

|

nr 4

885-918

EN

The article comprises an analysis of legal implications linked with the application of artificial intelligence (AI) in the economy. The current rules of civil law are often inadequate to address the consequences of actions taken by AI systems, as they fail to determine who is liable and on what legal basis. The essence of the problem is that AI’s decisions are autonomous. Vesting AI with legal personality would not suffice to solve the problems at issue. The combination of AI and blockchain technology in the form of smart contracts entails a situation where algorithms impact contract terms. Security of smart contract transactions depends on the quality of underlying algorithms. Relevant legislative modifications needed to provide for the liability of algorithms, especially in the context of AI, seem imminent. In fact, directives 2019/770 and 2019/771, which have only recently been adopted by the EU, are notable examples of a new regulatory approach to the issue of software liability. The author of this article suggests that in order to provide enhanced legal certainty, the quality of AI program code should be standardised. This would set a benchmark of algorithm quality that could be used to determine the liability of computer programs for their autonomous decisions.

6

A Systematic Reuse Process for Automated Acceptance Tests: Construction and Elementary Evaluation

63%

Irshad M. , Petersen K.

|

tom Vol. 15, nr 1

133--162

EN

Context: Automated acceptance testing validates a product’s functionality from the customer’s perspective. Text-based automated acceptance tests (AATs) have gained popularity because they link requirements and testing. Objective: To propose and evaluate a cost-effective systematic reuse process for automated acceptance tests. Method: A systematic approach, method engineering, is used to construct a systematic reuse process for automated acceptance tests. The techniques to support searching, assessing, adapting the reusable tests are proposed and evaluated. The constructed process is evaluated using (i) qualitative feedback from software practitioners and (ii) a demonstration of the process in an industry setting. The process was evaluated for three constraints: performance expectancy, effort expectancy, and facilitating conditions. Results: The process consists of eleven activities that support development for reuse, development with reuse, and assessment of the costs and benefits of reuse. During the evaluation, practitioners found the process a useful method to support reuse. In the industrial demonstration, it was noted that the activities in the solution helped in developing an automated acceptance test with reuse faster than creating a test from scratch i.e., searching, assessment and adaptation parts. Conclusion: The process is found to be useful and relevant to the industry during the preliminary investigation.

7

Zarządzanie jakością i niezawodnością oprogramowania w systemach związanych z bezpieczeństwem

63%

Porzeziński M.

|

tom Vol. 2, No. 3

45--52

EN

This article is concerned with the methods of ensuring the required quality and reliability of software in safetyrelated systems. The basic types of software reliability models and their specific properties are presented. The principles of managing the process of software development, based on the "Model V" life cycle, with particular emphasis on the role of inspection and testing processes are discussed. Also the methodology of quality management and reliability of the software recommended by the PN-EN 61508-3 are outlined. At the end the concept of application to support the process of assessing the quality and integrity of the safety-related software is described.

8

Jakość oprogramowania w zwinnym podejściu do zarządzania projektami informatycznymi

63%

Brodnicki K.

|

tom R. 53, nr 9-10

15--21

PL

Cel: Celem artykułu jest ocena, czy wykorzystanie podejścia zwinnego Scrum w organizacji podnosi jakość wytwarzanego oprogramowania oraz próba uzyskania odpowiedzi na pytanie, jak nowelizacja Przewodnika po Scrumie (Scrum Guide) z listopada 2020 roku wpłynęła na proces wytwarzania oprogramowania. Projekt badania/metodyka badawcza/koncepcja: Przyjętą metodyką badawczą jest przegląd literatury przedmiotu oraz badania własne autora. Wyniki/wnioski: Wnioskiem z przeprowadzonych badań jest fakt, że zastosowanie podejścia zwinnego Scrum pozytywnie wpływa na jakość wytwarzanego oprogramowania. Postępowanie zgodnie z wytycznymi zawartymi w Przewodniku oraz podnoszenie kompetencji w zespołach wytwórczych powoduje, że wzrasta świadomość dotycząca wytwarzanych produktów, co ma bezpośredni wpływ na jakość. Ograniczenia: Do ograniczeń w prowadzonych badaniach zaliczyć można stosunkowo niewielką liczbę przeprowadzonych wywiadów. Liczba ta wynika z trudności w uzyskaniu obecnie rzetelnych danych, ale zdaniem autora badania takie są znacznie bardziej wiarygodne i niosą większą wartość poznawczą aniżeli badania ilościowe. Zastosowanie praktyczne: Uzyskane wyniki niewątpliwie przyczynią się do poprawy obszarów w organizacji i ciągłego ich doskonalenia, a organizacjom zamierzającym dokonać transformacji z podejścia klasycznego do zwinnego – uniknąć powielania potencjalnych błędów. Oryginalność/wartość poznawcza: Dotychczas w literaturze przedmiotu brak jest badań skupiających się na porównaniu bieżącej wersji Przewodnika po Scrumie z jego poprzednią wersją i wpływu tychże różnic na funkcjonowanie organizacji.

EN

Purpose: The aim of the article is to verify whether the use of agile testing improves the software quality and to try to answer the question how an updated version of the Scrum Guide (November 2020) influenced the software development process.. Design/methodology/approach: The adopted research methodology is a review of the literature on the subject and the author's own research. Findings/conclusions: The conclusion of the research is the fact that the use of the Scrum agile approach positively affects the quality of the software produced. Following the guidelines contained in the Guide and increasing competences in production teams increases the awareness of the manufactured products, which has a direct impact on quality. Research limitations: The limitations in the conducted research include a relatively small number of conducted interviews. This number results from the difficulties in obtaining reliable data at present, but according to the author, such studies are much more reliable and carry more cognitive value than quantitative studies. Practical implications: The obtained results will undoubtedly contribute to the improvement of areas in the organization and their continuous improvement, and for organizations intending to transform from a classic to an agile approach – avoid duplicating potential mistakes. Originality/value: So far, the literature on the subject lacks research focusing on comparing the current version of Scrum Guide with its previous version and the impact of these differences on the functioning of the organization.