Ograniczanie wyników
Czasopisma help
Autorzy help
Lata help
Preferencje help
Widoczny [Schowaj] Abstrakt
Liczba wyników

Znaleziono wyników: 38

Liczba wyników na stronie
first rewind previous Strona / 2 next fast forward last
Wyniki wyszukiwania
Wyszukiwano:
w słowach kluczowych:  software development
help Sortuj według:

help Ogranicz wyniki do:
first rewind previous Strona / 2 next fast forward last
EN
OntoUML is an ontologically well-founded conceptual modeling language that provides precise meaning to modeled elements. As a result, its usage is beneficial in the Model-Driven Development approach to software development. Relational databases are commonly used for storage of application data, and they offer support for the implementation of custom data constraints. In this paper, we discuss the realization of constraints that arise from OntoUML structural models in PostgreSQL, Microsoft SQL Server and MySQL, and provide a complete reference on how to implement these constraints so that only data conforming to the OntoUML model can be stored.
EN
Purpose: The aim of this article was to present the typology of information technology standards and to explore their importance for programmers. Design/methodology/approach: The research was exploratory in nature, and based on grounded theory and ethnography. The tool used to collect data were interviews. Findings: On the basis of the research it is concluded that standards were of utmost importance to the respondents, and were a thing that allowed them to work efficiently. Research limitations/implications: The conducted research was qualitative and inductive. For this reason, there is limited possibility of making generalizations about the results. Originality/value: The paper presents important findings that might increase the work efficiency of programmers. Additionally the research was conducted using a relatively uncommon approach in IT and management field (grounded theory, ethnography, qualitative methods, interviews).
EN
In machine learning, learning algorithms that learn from other algorithms are called meta-learning. New algorithms called Ensemble algorithms have surfaced as a viable method to improve defect prediction models' accuracy and dependability. In software development defect prediction of software engineering is still a big challenge, and leads to the failure of systems, increases the cost of maintenance, and makes the development process more difficult. Consequently, defect prediction systems have become more popular as a way to foresee possible flaws early on in the development process. Defect prediction is the process that specifies the possible defects in the code written newly or the existing modified code without the use of code testing.This paper introduces ensemble learning ideas, reviews the traditional defect prediction models, and investigates ensemble learning techniques for defect classification and prediction such as bagging, boosting, stacking, and random forests, Case studies and actualexperiments illustrate the important roleof ensemble algorithms in classifying five severity types of defects and predicting the severity code of defects to improve the software development process by reducing the time and effort needed to determine the type of defect.
PL
W uczeniu maszynowym algorytmy uczenia się, które uczą się na podstawie innych algorytmów, nazywane są metauczeniem. Pojawiłysię nowe algorytmy zwane algorytmami Ensemble jako realna metoda poprawy dokładności i niezawodności modeli przewidywania defektów. W rozwoju oprogramowania przewidywanie defektów w inżynierii oprogramowania jest nadal dużym wyzwaniem i prowadzi do awarii systemów, zwiększa koszty utrzymania i utrudnia proces tworzenia oprogramowania. W rezultacie systemy przewidywania defektów stały się coraz bardziej popularne jako sposób przewidywania możliwych wad na wczesnym etapie procesu rozwoju. Przewidywanie defektów to proces, który określa możliwe defekty w nowo napisanym kodzie lub istniejącym zmodyfikowanym kodzie bez użycia testowania kodu. W artykule przedstawiono koncepcje uczenia się zespołowego, dokonano przeglądu tradycyjnych modeli przewidywania defektów i zbadano techniki uczenia się zespołowego do klasyfikacji i przewidywania defektów, takiejak pakowanie, wzmacnianie, układanie w stosy i lasy losowe. Studia przypadków i rzeczywiste eksperymenty ilustrują ważną rolę algorytmów zespołowych w klasyfikacji pięć typów ważności defektów i przewidywanie kodu ważności defektów w celu usprawnienia procesu tworzenia oprogramowania poprzez skrócenie czasu i wysiłku potrzebnego do określenia rodzaju defektu.
4
Content available remote An Ontology to Understand Programming Cocktails
EN
An ever-growing landscape of programming technologies (tools, languages, libraries and frameworks) has rapidly become the norm in many domains of computer programming - Web Development being the most noticeable example. The concurrent use of many compartmentalised technologies has advantages: it allows for flexibility in implementation, while also improving reusability. On the other hand, this proliferation tends to create convoluted development workflows that must be (painstakingly) planned, managed and maintained. The combination of multiple languages, libraries, frameworks and tools (Ingredients) in a single project effectively forms a Programming Cocktail, that can rapidly become cognitive and financially onerous. Aiming at understanding these complex situations, an ontology was created to provide a formal and structured analysis of these cocktails. It emerged from a survey of technologies that several companies are currently using to develop their systems, and aims to provide support for better understanding, classifying and characterising Programming Cocktails. This paper presents not only the ontology itself, but also the consequent knowledge that was constructed and structured through its development.
5
Content available remote Fixations in Agile Software Development Teams
EN
Cognitive biases influence every human being, including the individuals that take part in the software development process. Fixation is a cognitive bias that occurs when one focuses too much on certain items, events, obstacles or activities. In this study, we examine whether agile team members fixate on any particular agile practices. Through a set of semi-structured interviews, we investigated the source of these fixations, their consequences, and then propose possible countermeasures. We found that practitioners tend to fixate on practices that give them a sense of being in control over the project (such as meetings or Scrum events), while neglecting the Agile Principles of self-organising teams and working at a sustainable pace. This resulted in a series of problems, such as futile attempts to control team members, oversharing information with the client, meetings becoming a form of interrogation, and others.
EN
Background: Python is a popular and easy-to-use programming language. It is constantly expanding, with new features and libraries being introduced daily for a broad range of applications. This dynamic expansion needs a robust support structure for developers to effectively utilise the language. Aim: In this study we conduct an in-depth analysis focusing on several research topics to understand the theme of Python questions and identify the challenges that developers encounter, using the questions posted on Stack Overflow. Method:We perform a quantitative and qualitative analysis of Python questions in Stack Overflow. Topic Modelling is also used to determine the most popular and difficult topics among developers. Results: The findings of this study revealed a recent surge in questions about scientific computing libraries pandas and TensorFlow. Also, we observed that the discussion of Data Structures and Formats is more popular in the Python community, whereas areas such as Installation, Deployment, and IDE are still challenging. Conclusion: This study can direct the research and development community to put more emphasis on tackling the actual issues that Python programmers are facing.
EN
Agile methods facilitate collaboration between multiple teams towards a shared objective. Nonetheless, working on large-scale projects with diverse teams can be challenging. It necessitates proactive approach to management, with a focus on team-building and creating psychologically safe work environment. This paper investigates the leadership role in creating a psychologically safe environment for Large Scale Agile (LSA) projects. We conducted semi-structured interviews with software professionals working on LSA project in a Scandinavian technology company, and thematic analysis was conducted to identify the parameters related to project leaders that enable psychological safety. The results shed light on the building blocks of a psychologically safe environment, and the reported cause and effect of psychological safety in the LSA industrial project. The findings suggest that a proactive management style is required to build a cohesive team in large projects with diverse teams and backgrounds.The paper also proposed future research directions.
EN
The practice of code review is crucial in software development to improve code quality and promote knowledge exchange among team members. It requires identifying qualified reviewers with the necessary expertise and experience to thoroughly examine modifications suggested in a pull request and improve the efficiency of the code review process. However, it can be costly and time-consuming for maintainers to manually assign suitable reviewers to each request for large-scale projects. To address this challenge, various techniques, including machine learning, heuristic-based algorithms, and social network analysis, have been employed to suggest reviewers for pull requests automatically.
EN
This paper focuses on application of technical debt prioritization technique to the telecommunication software managing the fleet of devices for a video surveillance system. Technical debt for this application was gathered, categorized and prioritized according to the approach named CoDVA. However, the implementation of technical debt reduction did not follow exactly the expected guidelines. The three main causes of this phenomenon were discovered: continuous refactoring approach, sizing of technical debt items, and the broadened scope of refactoring activities. Therefore, we propose to adopt a specific definition of technical debt and follow a few rules for defining its scope and granularity.
EN
Purpose: The main purpose of the research is to examine the suitability of exploratory tests in the software testing process. Design/methodology/approach: An experiment, carried out for the sake of this study, consisted of two parts. First, a test was performed, and in the second part a survey was conducted, which allowed for the comparison of exploratory and test-based tests. Findings: The results of the tests indicated a slightly lower effectiveness of the exploratory approach, which may have been caused by the conditions of the experiment: the choice of the tested software, short duration of test sessions, participants lacking knowledge about the investigated software and experience in performing exploratory tests. Originality/value: Despite the weaker results obtained, the exploratory tests proved useful, as evidenced by the detection of distinctive errors, not found during tests based on test cases. In the survey, 90% of respondents confirmed the use of formalized test approach, based on test cases, while just over a half (57%) indicated having experience in conducting exploratory tests. Testers considered both approaches useful, addressing greater need for conducting formalized tests using test cases. Results included in the research allowed to indicate the qualities and shortcomings of the exploratory approach to software testing.
EN
As the delivery of good quality software in time is a very important part of the software development process, it's a very important task to organize this process very accurately. For this, a new method of the searching associative rules were proposed. It is based on the classification of all tasks on three different groups, depending on their difficulty, and after this, searching associative rules among them, which will help to define the time necessary to perform a specific task by the specific developer.
EN
This article proposes the construction of autonomous mobile robots and designing of obstacle avoidance algorithms for them. Nowadays, mobile robots are gaining more and more popularity on the customer as well as industrial market, for example as automatic vacuum cleaners or lawnmowers. Obstacle avoidance algorithms play an important role in performance of this types of robots. The proposed algorithms were designed for builds with rather not expensive electronic components, especially sensors with limited precision and dynamics. The project began with the selection of needed parts and building materials as well as designing of the PCB and assembling the whole construction. The project included also designing and developing the software responsible for, among others, implementation of obstacle avoidance algorithms. After the project’s completion, a series of tests in a closed environment was conducted to verify the quality of vehicles’ performance. Results of tests were positive.
EN
Socio-economic changes and evolving IT environment led to the emergence of new mobility solutions, very popular in urban areas. New Mobility Services (NMS), including Mobility-as-a-Service (MaaS) are now an integral part of short- and longdistance transportation service portfolio in many countries and are offered both by companies (public or private) and individual bidders. The challenge for the service providers is now to adjust the business models of those solutions to the customers’ needs. The particular layers of designing MaaS solutions are crucial to meet the requirements of users, especially young adults (Y generation), considered as the primary target group for MaaS offer. Therefore, the study aims to examine the level of awareness of the MaaS market offer and, in addition, a range of use of those solutions.
14
Content available Preferable Ways of Decision-Making in IT Teams
EN
Software development team collaboration requires various decisions regarding essential aspects of a project’s progress. General and particular decision-making models are considered, and their main aspects such as team types, problem solving categories, and decision-making ways are analyzed. The research concerns representative groups of IT specialists and their preferences in decision-making are investigated. Four possible cases were tested: hierarchical choice (by leader) team members’ choice (team consensus or voting) and external expert impact. It allows one to show some differences in the behaviors of both traditional and virtual teams.
EN
Since the time when first CASE (Computer-Aided Software Engineering) methods and tools were developed, little has been done in the area of automated creation of code. CASE tools support a software engineer in creation the system structure, in defining interfaces and relationships between software modules and, after the code has been written, in performing testing tasks on different levels of detail. Writing code is still the task of a skilled human, which makes the whole software development a costly and error-prone process. It seems that recent advances in AI area, particularly in deep learning methods, may considerably improve the matters. The paper presents an extensive survey of recent work and achievements in this area reported in the literature, both from the theoretical branch of research and from engineer-oriented approaches. Then, some challenges for the future work are proposed, classified into Full AI, Assisted AI and Supplementary AI research fields.
PL
Od czasu pojawienia się pierwszych metod i narzędzi CASE niewiele zrobiono w zakresie automatycznego wytwarzania oprogramowania. Narzędzia CASE wspierają deweloperów w tworzeniu struktury systemu, definiowaniu interfejsów i relacji między modułami oprogramowania oraz, po powstaniu kodu, w wykonywaniu zadań testowych na różnych poziomach szczegółowości. Pisanie kodu jest jednak nadal zadaniem wykwalifikowanego specjalisty, co powoduje, że cały proces wytwarzania oprogramowania jest kosztowny i podatny na błędy. Ostatnie postępy w obszarze sztucznej inteligencji, szczególnie w zakresie metod głębokiego uczenia maszynowego, mogą i powinny znacznie poprawić tę sytuację. W artykule przedstawiono przegląd dotychczasowych osiągnięć w tej dziedzinie, znanych z literatury przedmiotu, szczególnie w zakresie czysto teoretycznym, gdyż efekty inżynierskie znajdujące zastosowanie praktyczne są jak dotąd bardzo ograniczone. Następnie zaproponowano i opisano kilka kierunków przyszłych prac w tej dziedzinie, które zaklasyfikowano jako Full AI, Assisted AI i Supplementary AI, w kolejności wynikającej z oczekiwanego stopnia zautomatyzowania procesów wytwarzania oprogramowania.
EN
The paper presents the main results of software development for a new robotic technology of microplasma spraying of powder coatings to protect surfaces of industrial parts. The numerical methods have been implemented for modeling temperature fields induced by the radiation treatment of coatings. The proprietary software products have been developed to perform calculations of temperature fields in two-layer heat absorbers under irradiation and to provide the desired trajectory of a plasma source. The laboratory samples with coatings have been obtained.
PL
W artykule przedstawiono główne wyniki opracowywania oprogramowania dla nowej zrobotyzowanej technologii mikroplazmatycznego natryskiwania powłok proszkowych w celu ochrony powierzchni części przemysłowych. Zastosowano metody numeryczne do modelowania pól temperatury indukowanych przez napromienianie powłok. Opracowano autorskie produkty do wykonywania obliczeń pól temperatur w dwuwarstwowych pochłaniaczach ciepła w warunkach napromieniowania i zapewnienia pożądanej trajektorii źródła plazmy. Uzyskano próbki laboratoryjne z powłokami.
EN
Global competition and increasingly complex networks of supply chains require new production philosophies, novel supply chain paradigms (Lean, Agile and Hybrid ones) and new organization and cooperation forms of companies in order to reduce cost, increase productivity and boost competitiveness. Therefore, members of an Agile supply chain form a virtual enterprise (VE) network, which stands for temporary cooperation of VE members (final assemblers, suppliers, service providers) in which the members share their skills, human and equipment resources as well as waste for more efficient operation. The goal of this study is VE optimization, which means forming optimum combinations of potential chain members. This innovative and original approach involves developing an optimization method and defining objective functions (total cost, total lead time) and design constraints (production and service capacities, inventories and members flexibility) for optimum formation of VEs. The focus of VE optimization is to manufacture and deliver final products to customers in the most time- and cost-effective manner, with the total cost and total lead time of the supply chain being minimized during the optimization. Unique optimization software has been developed based on this method. It can can be widely used for optimizing micro- and macro regional virtual networks.
EN
Changing market environment, global competition, rapidly fluctuating customer demands and more complex global network of supply chains require new production conceptions (Pull, Lean) and technologies. Novel supply chain paradigms (1. Lean-, 2. Agile-, 3. Leagile Supply Chain) are forms in order to increase and maintain competitiveness of companies. New organization and cooperation forms are formed. The members of an Agile Supply Chain form Virtual Enterprise (VE) network, which supports the fast and flexible fulfilment of changing customers’ demands. The goal of the study is the VE network optimization, which means the formation of optimal combination of ideal chain’s members (production companies, service providers and customers). This study is original and unique, since an optimization method, objective functions (total cost and lead time) and design constraints have been elaborated. Based on the elaborated method an optimization software has been developed which can be widely used for optimization of micro- and macro regional networks.
PL
Zmiana otoczenia rynkowego, globalna konkurencja, gwałtowne wahania zapotrzebowania klientów i bardziej złożona globalna sieć łańcuchów dostaw wymagają nowych koncepcji produkcji (Pull, Lean) i technologii. Paradygmaty łańcucha dostaw (1. Lean-, 2. Agile-, 3. Leagile Supply Chain) są formami powstałymi w celu zwiększenia i utrzymania konkurencyjności firm. Powstają nowe formy organizacji i współpracy. Członkowie Łańcucha Agile Supply Chain tworzą sieć wirtualnego przedsiębiorstwa (Virtual Enterprise, VE), która zapewnia szybkie i elastyczne spełnianie zmieniających się wymagań klientów. Celem badania jest optymalizacja sieci VE, co oznacza tworzenie optymalnej kombinacji idealnych członków łańcucha (firm produkcyjnych, dostawców usług i klientów). Przedstawione badania są oryginalne i unikalne, ponieważ opracowano metodę optymalizacji, funkcje celu (całkowity koszt i czas realizacji) oraz ograniczenia projektowe. Na podstawie opracowanej metody opracowano oprogramowanie optymalizacyjne, które można szeroko wykorzystać do optymalizacji sieci mikro- i makroregionalnych.
EN
In a modern urban organization, mobility is an important issue for society. Traffic congestion of urban roads undermines mobility is a real problem in major cities This article shows the development and implementation of a centralized traffic control system in the city of Cali Valle (Colombia) applied to control traffic lights located to the east of the city (Simon Bolivar and Ciudad de Cali highways), allowing the central operators directly influence the traffic flow, know and display the status of the lights and generate statistics about the events of the online equipment. Particular real benefits of proposed new system of traffic lights are reflected in green times at each intersection allocated in accordance with the present traffic volumes on the road network at any time of day and in every sector of the city in particular, which of course increases the efficiency of each light installed at each intersection. As demonstrated in this article case study, the congestion scheme has been improved, and the project has opened up vast opportunities for innovative network management strategies for the optimization of network performance. Many of these strategies are developed to give a coordinated high-level control across different traffic control platforms based on real time traffic condition and performance on site.
PL
W referacie przedstawiono elementy zarządzania konfiguracją występujące podczas wytwarzania oprogramowania. Omówiono wymagania dokumentu standaryzacyjnego NATO AQAP 2210 dedykowanego wytwarzaniu oprogramowania.
EN
This paper presented the elements of configuration management, which occur during software development. The requirements of Allied Quality Assurance Publication 2210 were discussed
first rewind previous Strona / 2 next fast forward last
JavaScript jest wyłączony w Twojej przeglądarce internetowej. Włącz go, a następnie odśwież stronę, aby móc w pełni z niej korzystać.