Full-text resources of CEJSH and other databases are now available in the new Library of Science.
Visit https://bibliotekanauki.pl

Results found: 7

first rewind previous Page / 1 next fast forward last

Search results

Search:
in the keywords:  software development
help Sort By:

help Limit search:
first rewind previous Page / 1 next fast forward last
1

Intercultural Communication and Management Factors and Their Impact to the Process of Global Software Development for Virtual and Non-Virtual Teams

100%
Isern G.
Journal of Intercultural Management
|
2014
|
vol. 6
|
issue 1
5-16
EN
This position paper presents the factors involved in the successful software development and what is the impact of some methodologies like Agile in this process. Global software development projects may be a total success or an anticipated disaster for simple reasons that usually have nothing to do with the technology involved, with the time differences, or the product being built, but because of subtle intercultural factors. How do the language, the race, the gender, the religion, and the location affects the software development process from analysis and design to implementation, testing and maintenance? Do all these factors impact in the same way if we are working with a local team, and offshore development team or even a global virtual team? Is any specific software development methodology better suited for your particular case? How could you decide what’s the better approach? What will be the results and what our goals? The issues at stake are not superficial matters of the ways how people dress, or how clear do they speak in our local language, or what they like to eat, or their small daily behaviors, but are based in the fundamental differences in the systems of values that govern our lives. So institutions, corporations and global companies have to raise the level of awareness of their employees worldwide on the cultural differences, through various programs for intercultural or diversity training. But this poor model of cultural awareness is not enough to overcome some of the obstacles that intercultural differences bring to the table. So this paper will list and describe this important intercultural factors that directly impact in the software development process and how certain software development methodologies could be used in order to have a more systematic look or set of guidelines that would allow the team managers to evaluate and to decide how theuse of each one of these software development methodologies for local teams, non local teams and virtual teams will affect positively or negatively the outcomes of software development practices.
2
Publication available in full text mode
Content available

An Intelligent Market: Possibilities of a Revolution in Supermarkets Organization Using Agent Based Systems

100%
Cipi E., Durmishi V.
Academicus. International Scientific Journal
|
2010
|
issue 01
90-99
EN
This work is focused on studying the possibilities of a new model in business management, integrating the best solutions of IT in the supermarket enterprises. We aim to show how an agent based system is used to manage successfully a market and why it is considered an efficient method to support the challenges of the supermarket enterprises. In a highly competitive environment, the impact of this phenomenon is visible, noting the increase of the interest for electronic systems which offer intelligent services in some activities as administration, marketing, business services, etc. We think agent based systems are the best choice as tools that can automate the analysis of the database information and locate the real useful things.
3

Teaching Scrum in Cooperation with a Software Development Company

88%
Mahnič V., Georgiev S., Jarc T.
Organizacija
|
2010
|
vol. 43
|
issue 1
40-48
EN
The increasing use of agile methods for software development creates the need for these methods to become part of the education of future computer and information science engineers. On the other hand, teaching these methods gives us an opportunity to verify individual agile concepts and their effectiveness. For that reason, project work is an appropriate and frequently used form of teaching that enables students to get acquainted with agile methods and, at the same time, provides case studies for evaluating individual agile concepts. We describe our approach to teaching the Scrum agile method, within the software technology course, in cooperation with a software development company. Students were taught through work on a real project for which a list of requirements was submitted by the company. A co-worker of this company participated throughout the teaching period playing the role of customer's representative. During their work, students consistently used the Scrum method and at the end of each iteration they evaluated their experience by means of a questionnaire. In the article, the Scrum method is presented first, then a description of work on the project is given and finally the results of the survey are described.
4
Publication available in full text mode
Content available

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.
Informatyka Ekonomiczna
|
2015
|
issue 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.
5
Publication available in full text mode
Content available

Kiedy warto stosować metodyki zwinne (agile methodologies) w zarządzaniu projektami wytwarzania oprogramowania?

88%
Lasek M., Adamus A.
Informatyka Ekonomiczna
|
2014
|
issue 1(31)
157-172
EN
The article presents increasingly popular agile methodologies that are more and more often used for projects management of software development. The aim of this article is to analyze the concept of agility and agile methodologies, as well as to find an answer to the question when it is worth to use such methodologies which require organizational effort associated with their use, acquisition of the necessary skills and covering the necessary costs. We consider agile methodologies as the specific project management methodologies in software development. Therefore the article describes their role in the development of agile IT infrastructure, agile organizational culture, and issues related to the possibility of assessing the level of methodologies' agility, as well as the possibility of evaluation the purposefulness and benefits of using them in software development practice.
6
Publication available in full text mode
Content available

Trudności w implementacji wzorców projektowych w małych zespołach programistycznych

63%
Wojszczyk R., Ratuszniak P.
Przedsiębiorstwo we współczesnej gospodarce - teoria i praktyka
|
2017
|
vol. 2
|
issue 21
189-201
PL
Na rynku IT występuje wiele małych przedsiębiorstw tworzących własne, autorskie oprogramowanie lub wykonujące usługi dla firm trzecich. Małe zespoły często pracują według tzw. zwinnych metodyk wytwórczych, w których ograniczona jest ilość dokumentacji projektowej, a większość procedur znacznie uproszczona. Jednakże małe zespoły nie rezygnują ze stosowania dobrych praktyk, w tym wzorców projektowych. Celem artykułu jest przybliżenie wybranych trudności, z którymi borykają się małe zespoły programistyczne przy implementacji wzorców projektowych, oraz przedstawienie autorskiej metody wspomagającej wzrost jakości implementacji wzorców projektowych.
EN
There are many small businesses create their own, original software or performing services for third parties, in IT market. Small teams often work by the so-called. agile methodologies, which are limited by the amount of project documentation, and most of the procedures considerably simplified. However, small teams not reject good practice, including design patterns. The aim of the article is to present some difficulties faced by small development teams in the implementation of design patterns, and to present the author’s method of supporting an increase in the quality of implementation of design patterns.
7
Publication available in full text mode
Content available

Synergia zwinnego i szczupłego rozwoju oprogramowania na bazie Scrumban

63%
Knapik I., Werewka J., Grabiński T., Luty Z., Surowiec A.
Zeszyty Naukowe Wyższej Szkoły Ekonomii i Informatyki w Krakowie
|
2022
|
issue 18
99-121
EN
IT companies are constantly looking for effective methods of software development. Typically, these approaches are tailored to the type of software development work. The most popular are the agile, lean and proactive (classic) approaches. The study will assess the methodology that synergistically combines the agile and lean approaches. Representatives of these approaches are Scrum and Kanban. As a result of this assessment, optimal solutions for software development teams will be proposed. A case study of using a solution combining agile and lean approaches will be presented.
PL
W firmach informatycznych cały czas poszukiwane są efektywne metody rozwoju oprogramowania. Zwykle te podejścia dostosowywane są do rodzaju prac związanych z rozwojem oprogramowania. Do najbardziej popularnych należą podejście zwinne (agile), szczupłe (lean) i proaktywne (klasyczne). W opracowaniu poddana zostanie ocenie metodyka łącząca w sposób synergetyczny podejście zwinne (agile) i podejście szczupłe (lean). Reprezentantami tych podejść są Scrum i Kanban. W wyniku tej oceny zostaną zaproponowane optymalne rozwiązania dla zespołów rozwijających oprogramowanie. Przedstawiony zostanie przykład studialny (case study) użycia rozwiązania łączącego podejście zwinne i szczupłe.
first rewind previous Page / 1 next fast forward last
JavaScript is turned off in your web browser. Turn it on to take full advantage of this site, then refresh the page.