Informacja

Drogi użytkowniku, aplikacja do prawidłowego działania wymaga obsługi JavaScript. Proszę włącz obsługę JavaScript w Twojej przeglądarce.

English (EN)·Polski (PL)·Yкраїнський (UK)
Przejdź do strony domowej biblioteki Centralna Biblioteka Wojskowa Link otwiera się w nowym oknie Logo biblioteki Prolib Integro - strona głównaCentralna Biblioteka Wojskowa

Wyszukujesz frazę "Software development" wg kryterium: Wszystkie pola

  Lista filtrów
Wyrównaj
Wyświetlanie 1-10 z 133
Tytuł:
Modern methods of software development
Autorzy:
Zima, D.
Powiązania:
https://bibliotekanauki.pl/articles/1941640.pdf
Data publikacji:
2015
Wydawca:
Politechnika Gdańska
Tematy:
Software development method
agile
open source
testing
maintenance
waterfall
Scrum
Opis:
Software development methods consist of such activities like analysis, planning, development, testing, deployment, maintenance and retirement. All of them can be divided into two main categories – traditional and agile. The objective of this paper is to review some of the most popular traditional, agile and open source development methods. Special attention was paid to the common stages of all methods – testing and maintenance.
Źródło:
TASK Quarterly. Scientific Bulletin of Academic Computer Centre in Gdansk; 2015, 19, 4; 481-493
1428-6394
Pojawia się w:
TASK Quarterly. Scientific Bulletin of Academic Computer Centre in Gdansk
Dostawca treści:
Biblioteka Nauki
Artykuł
Tytuł:
Software reliability growth modeling for agile software development
Autorzy:
Rawat, S.
Goyal, N.
Ram, M.
Powiązania:
https://bibliotekanauki.pl/articles/329876.pdf
Data publikacji:
2017
Wydawca:
Uniwersytet Zielonogórski. Oficyna Wydawnicza
Tematy:
software reliability
nonhomogeneous poison process
transient faults
permanent faults
Musa model
niezawodność oprogramowania
błąd przejściowy
zwarcie trwałe
Opis:
The frequent incremental release of software in agile development impacts the overall reliability of the product. In this paper, we propose a generic software reliability model for the agile process, taking permanent and transient faults into consideration. The proposed model is implemented using the NHPP (non-homogenous Poisson process) and the Musa model. The comparison of the two implementations yields an effective, empirical and reliable model for agile software development.
Źródło:
International Journal of Applied Mathematics and Computer Science; 2017, 27, 4; 777-783
1641-876X
2083-8492
Pojawia się w:
International Journal of Applied Mathematics and Computer Science
Dostawca treści:
Biblioteka Nauki
Artykuł
Tytuł:
The Implementation of 3TZ Model of Software Development
Autorzy:
Chaczko, Z.
Aslanzadeh, S.
Jiang, F.
Klempous, R.
Powiązania:
https://bibliotekanauki.pl/articles/226332.pdf
Data publikacji:
2012
Wydawca:
Polska Akademia Nauk. Czytelnia Czasopism PAN
Tematy:
software development
cloud computing
distributed software services
3TZ environment
Opis:
This paper presents the concepts and explores issues related to the 3 Time Zones (3TZ) model of software development in global workspace environment. The 3TZ model itself seeks to take advantages of differences in time zones between places around the world. By engaging software development teams in different regions separated by 8 hours each, it is possible for their combined working hours to cover the whole 24 hours period. Thus, while they each work their normal 8 hour days, together they are able to achieve in 1 day what a single team would achieve in 3 days. They are able to achieve this by passing on their work from one team to the next as one finishes their workday and the next team starts their workday. The 3TZ model of software development revolves around the employment of a software development team distributed in at least 3 different locations around the world in 3 different time zones. If work was passed on from one team to the next and adjacent teams were separated by 8 hours, then 24 hours continuous collaborative software development could be achieved. Though this poses many challenges, when dealt with there is great potential for software to be developed much faster than is possible for a single, collocated development team. In the global economy, we have seen a decrease in the barriers towards communication across the globe along with an increase of service availability to support this communication. Software development is one of the disciplines that is capable of effectively utilizing and benefiting from global collaboration prospect lent by ever increasing capability of information and communication technology. 24 hours continuous development is ideal for application towards tasks that have hard deadlines or require work completed as soon as possible. This article will mainly focus on introducing 24/7 global models that can be applied in cloud environment used in three different time zones.
Źródło:
International Journal of Electronics and Telecommunications; 2012, 58, 4; 433-439
2300-1933
Pojawia się w:
International Journal of Electronics and Telecommunications
Dostawca treści:
Biblioteka Nauki
Artykuł
Tytuł:
An Empirical Study on the Factors Affecting Software Development Productivity
Autorzy:
Lavazza, L.
Morasca, S.
Tosi, D.
Powiązania:
https://bibliotekanauki.pl/articles/384131.pdf
Data publikacji:
2018
Wydawca:
Politechnika Wrocławska. Oficyna Wydawnicza Politechniki Wrocławskiej
Tematy:
effort
function point
empirical study
ISBSG dataset
factors
development
productivity
Opis:
Background : Software development productivity is widely investigated in the Software Engineering literature. However, continuously updated evidence on productivity is constantly needed, due to the rapid evolution of software development techniques and methods, and also the regular improvement in the use of the existing ones. Objectives : The main goal of this paper is to investigate which factors affect productivity. It was also investigated whether economies or diseconomies of scale exist and whether they may be influenced by productivity factors. Method : An empirical investigation was carried out using a dataset available at the software project repository ISBSG. The major focus was on factors that may affect productivity from a functional point of view. The the conducted analysis was compared with the productivity data provided by Capers Jones in 1996 and 2013 and with an investigation on open-source software by Delorey et al. Results : This empirical study led to the discovery of interesting models that show how the different factors do (or do not) affect productivity. It was also found out that some factors appear to allow for economies of scale, while others appear to cause diseconomies of scale. Conclusions : This paper provides some more evidence about how four factors, i.e., programming languages, business areas, architectural types, and the usage of CASE tools, influence productivity and highlights some interesting divergences in comparison with the results reported by Capers Jones and Delorey et al.
Źródło:
e-Informatica Software Engineering Journal; 2018, 12, 1; 27-49
1897-7979
Pojawia się w:
e-Informatica Software Engineering Journal
Dostawca treści:
Biblioteka Nauki
Artykuł
Tytuł:
Inżynieria wymagań w metodach Agile
Requirements Engineering in Agile Software Development
Autorzy:
Lipski, A.
Powiązania:
https://bibliotekanauki.pl/articles/1396866.pdf
Data publikacji:
2010
Wydawca:
Wojskowa Akademia Techniczna im. Jarosława Dąbrowskiego
Tematy:
Agile
inżynieria wymagań
inżynieria oprogramowania
agile
requirements engineering
software engineering
Opis:
"Zwinne" wytwarzanie oprogramowania (Agile Software Development) stało się bardzo popularne na przestrzeni kilku ostatnich lat. Metody Agile zostały wymyślone w celu szybszego dostarczenia działającego oprogramowania do klienta oraz dostosowania się oprogramowania do zmiennych potrzeb klienta. Można zauważyć, że istnieje wiele technik i praktyk wymyślonych oraz opracowanych w kontekście tradycyjnej inżynierii wymagań, które obecnie wykorzystywane są z dobrym rezultatem przez metody Agile. Celem tego artykułu jest pokazanie, w jaki sposób techniki inżynierii wymagań są wykorzystywane przez metody Agile oraz w jaki sposób metody te mogą być udoskonalone za pomocą tych technik.
Agile Software Development approaches have become increasingly popular during the last few years. Agile practises have been developed with the aim to deliyer software faster and to ensure that the software meets changing needs of customers. We can find out that there are a lot of practices and approaches which are created and developed in context of traditional Requirements Engineering and which are used by Agile methods with a good result. The goal of this article is to show how the Requirements Engineering technics are used by Agile methods and how this methods can be improved by them.
Źródło:
Biuletyn Instytutu Systemów Informatycznych; 2010, 5; 47-53
1508-4183
Pojawia się w:
Biuletyn Instytutu Systemów Informatycznych
Dostawca treści:
Biblioteka Nauki
Artykuł
Tytuł:
Statistical models to accelerate software development by means of iterative compilation
Autorzy:
Kamińska, A.
Bielecki, W.
Powiązania:
https://bibliotekanauki.pl/articles/305535.pdf
Data publikacji:
2016
Wydawca:
Akademia Górniczo-Hutnicza im. Stanisława Staszica w Krakowie. Wydawnictwo AGH
Tematy:
program execution time
optimizing compilation
iterative compilation
statistical models
rocessor cache
Opis:
Minimization of data-processing time and reduction of software-development time are important practical problems to be tackled by modern computer science. This paper presents the authors’ proposal of a family of statistical models for the estimation of program execution time, which is an approach focused on both of the above problems at the same time. The family consists of a general model and specific models and has been elaborated based on empirical data collected for pattern-program loops representing some arbitrarily selected features related to the program structure and the specificity of a program-execution environment. The paper presents steps to elaborate the aforementioned family as well as the results of the carried-out experimental research. The paper demonstrates how the elaborated models can be applied in iterative compilation for optimization purposes, allowing us to reduce the time of software development and produce code with minimal execution time.
Źródło:
Computer Science; 2016, 17 (3); 407-435
1508-2806
2300-7036
Pojawia się w:
Computer Science
Dostawca treści:
Biblioteka Nauki
Artykuł
Tytuł:
A hardware/software development environment for SoC-based time interval counters
Autorzy:
Grzęda, G.
Szplet, R.
Powiązania:
https://bibliotekanauki.pl/articles/114349.pdf
Data publikacji:
2015
Wydawca:
Stowarzyszenie Inżynierów i Techników Mechaników Polskich
Tematy:
system on chip
precise time counter
AXI Stream protocol
Opis:
The paper describes a design environment for development of precise time counters. The design was implemented in a System-on-Chip Zynq from Xilinx as an embedded solution with a custom user interface. The paper presents the system design, a dedicated time counter interface, and software running on the processing part of the Zynq device. It also contains the results of all system performance tests. The tests reveal the design advantages over the traditional approach, involving an FPGA device connected to a PC that serves as a host with a dedicated user interface. The presented development environment allowed reducing the calibration and measurement times twofold and threefold, respectively. Furthermore, thanks to the bus interface designed for data transmission from the time counter to the control module, the 200 MB/s data throughput inside the SoC was achieved.
Źródło:
Measurement Automation Monitoring; 2015, 61, 7; 299-301
2450-2855
Pojawia się w:
Measurement Automation Monitoring
Dostawca treści:
Biblioteka Nauki
Artykuł
Tytuł:
Analysis of exploration testing approach and conclusions from implementation in software development
Autorzy:
Kędziora, Michał
Kałwak, Karolina
Jóźwiak, Ireneusz J.
Szczepanik, Michał
Powiązania:
https://bibliotekanauki.pl/articles/1877558.pdf
Data publikacji:
2020
Wydawca:
Politechnika Śląska. Wydawnictwo Politechniki Śląskiej
Tematy:
software testing
software quality
exploratory testing
software development
testowanie oprogramowania
jakość oprogramowania
testowanie eksploracyjne
rozwój oprogramowania
Opis:
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.
Źródło:
Zeszyty Naukowe. Organizacja i Zarządzanie / Politechnika Śląska; 2020, 144; 249-263
1641-3466
Pojawia się w:
Zeszyty Naukowe. Organizacja i Zarządzanie / Politechnika Śląska
Dostawca treści:
Biblioteka Nauki
Artykuł
Tytuł:
Software Development for the Detonation Product Analysis of High Energetic Materials - Part I
Autorzy:
Muthurajan, H.
Ghee, H.
Powiązania:
https://bibliotekanauki.pl/articles/358537.pdf
Data publikacji:
2008
Wydawca:
Sieć Badawcza Łukasiewicz - Instytut Przemysłu Organicznego
Tematy:
detonation products
explosives
energetic materials
volume of detonation products
oxygen balance
software
Opis:
The detonation of energetic materials will result in the formation of decomposition products. These may be carbon monoxide, carbon dioxide, carbon, water, etc. In order to clarify the problems of decomposition products, a software package is developed to solve the problems of decomposition products using four different concepts. Although each concept will provide a different answer for the decomposition products they can be used as a guide and give fairly good approximations. This paper describes the development of a software package to estimate the possible decomposition products and the results generated using the software package LION. An algorithm to compute the detonation products of energetic materials using four different concepts along with the computation of oxygen balance, elemental composition, and molecular weight has been developed and described in this paper. The concept or predicting possible detonation products is particularly useful as one of the guideline for screening the potential molecules, when formulating explosives to produce a minimum toxic fumes to reduce the toxic hazardous to the users.
Źródło:
Central European Journal of Energetic Materials; 2008, 5, 3-4; 19-35
1733-7178
Pojawia się w:
Central European Journal of Energetic Materials
Dostawca treści:
Biblioteka Nauki
Artykuł
Wyświetlanie 1-10 z 133

Ta witryna wykorzystuje pliki cookies do przechowywania informacji na Twoim komputerze. Pliki cookies stosujemy w celu świadczenia usług na najwyższym poziomie, w tym w sposób dostosowany do indywidualnych potrzeb. Korzystanie z witryny bez zmiany ustawień dotyczących cookies oznacza, że będą one zamieszczane w Twoim komputerze. W każdym momencie możesz dokonać zmiany ustawień dotyczących cookies