Search

In software development, documentation is a continuous process that specifies what the system does, how it does it, and for whom it does it, describing all its characteristics from different perspectives in order to facilitate the understanding of all the interested parties. However, this is not always achieved due to poor documentation practices, leading to a type of technical debt known as documentation debt, which is related to missing, inconsistent, or incomplete documentation that degrades the understanding of the system, severely affecting its development, maintenance, and evolution. This phenomenon seems to be aggravated in agile approaches, either due to a misunderstanding of agile values and principles by focusing on the continuous delivery of functional software rather than comprehensive documentation, or a lack of good documentation practices. Although there are initiatives that generally describe the causes, effects, and good practices to mitigate documentation debt, it is still necessary to understand the impact of this type of debt on the software industry and to delve into a more complete definition in agile software development. In this sense, the results of a systematic mapping are presented, which provide a solid base of knowledge about documentation debt in agile software development and allow identifying gaps or research opportunities in this topic. [ABSTRACT FROM AUTHOR]

Knowledge transfer in software development teams allows their members' non-externalized knowledge to be collected, to form the organizational knowledge from a repository and share it among them. During this process, difficulties may arise in making this knowledge available, which may be associated with the lack of collaboration and motivation of the team, as well as poor communication and little support from the organization. Given these difficulties, the GamifiK strategy, supported by gamification, was proposed to foster collaboration in the transfer of knowledge in software development teams. This paper used an empirical research approach with a quasi-experimental design in an academic context to evaluate the collaboration of agile team members in sharing their knowledge and contributing to knowledge transfer. A statistically significant increase in team productivity was perceived, reflected in the ability to perform more user stories per sprint and complete incidents in less time. GamifiK is a promising strategy for fostering collaborative knowledge transfer across software development teams. [ABSTRACT FROM AUTHOR]

This study presents the design of a massive collaborative software development course by adapting web tools. The course integrates teaching software development and agile methodologies with project-based learning, allowing students to relate theory and practice. A case study is conducted with the participation of 475 students enrolled in a Node.JS and agile methodologies course. The results for the course and for the use of the tools applied are satisfactory, given the students' final products, their perception of learning, and their effective completion rate of the massive course. In conclusion, the massive course designed here enables web development teaching in collaborative work teams, emulating an authentic environment by using project management platforms and repositories mediated by a learning management system. [ABSTRACT FROM AUTHOR]

The aim of this study was to analyse the possible relationships between different aspects of exercise score in competition and anthropometric characteristics in a group of national elite AG adolescents according to two different categories. Descriptive and cross-sectional study. The sample consisted of 39 adolescents aged between 11 and 19 years (14,9± 2,39), from the junior and senior categories. An ad hoc questionnaire was administered asking for sociodemographic and sporting data, together with anthropometric measurements of weight, height, waist circumference and tricipital, bicipital, suprailiac, supraspinatus, supraspinatus and calf skinfolds. Significant associations were found between the % BF (sum of triceps and subscapularis skinfold) with the BAL and COMB exercise difficulty score and more moderately with the DYN exercise difficulty and end score. Similarly, the % of BF with the sum of the two tricipital and calf creases showed a moderate association with the final grade of the DYN exercise and the difficulty grade of the BAL exercise, as well as the difficulty grade of the DYN exercise. The bases present higher values in all anthropometric measures compared to the agile; in terms of performance, it is higher in the senior category, obtaining better scores in all the variables analysed and finally, there is a negative association between the % BF and the score in the difficulty grades of all the exercises, as well as in the final grade of the DYN exercise. [ABSTRACT FROM AUTHOR]

The benefits of agile frameworks applied to small projects have aroused interest in the large-scale software industry. However, applying them in scaled environments has meant facing multiple challenges, including communication, coordination, and cooperation. Scaled frameworks emerge in response to these challenges, describing the implementation guides to achieve the agile large-scale transformation. However, a lack of conceptual clarity regarding the elements prescribed by these frameworks was identified in the literature. This article introduces the Scaled Agile Model reference model, which integrates the experience reported in the literature and the fundamental attributes of scaled agile frameworks: SAFe, LeSS, Nexus, and DAD. A protocol was followed for the harmonization of multiple models, which allowed integrating and obtaining a reference model from the results of the harmonization of frameworks and the literature found. Additionally, SAM was evaluated for clarity, suitably, and completeness through a focus group. Thus, the proposed reference model defines sixteen roles, three levels of scale, and 34 practices grouped into 8 categories. The results suggest a good acceptance by the experts who evaluated the proposal. Likewise, the proposed model aims to be of great practical benefit for companies that want to scale, companies that are scaling, or companies that have already scaled and want to evaluate their implementation. [ABSTRACT FROM AUTHOR]

In this paper is presented a methodology for the design and implementation of automation products for technological processes from the Cuban pharmaceutical industry. The proposed methodology is based on a scrum approach, by using own software technologies which reduce the time of development and start up, provide great flexibility and efficiency in operations, significantly improve the traceability of processes and facilitate work based on user-friendly designs of the human-machine interface among its main advantages. The methodology developed is applicable to the automation of most of the pharmaceutical industry processes and guarantees to satisfy the demanding quality indicators of this industry and the requirements of the Drug Control Center (CECMED) of Cuba. The application of the methodology in the Cuban pharmaceutical industry has meant a saving to the country more of three and half million of euros in the last five years. [ABSTRACT FROM AUTHOR]

The main objective of the present study is to develop a mobile application that manages and controls the entry and exit of bike users (students, faculty, and administrative staff) at the Cooperative University of Colombia (UCC, in Spanish), Bogota campus. Unified modeling language (UML) models are applied to improve software quality by using appropriate metrics and software requirements to control the entry and exit of bike users through a mobile application with up to date technologies (Ionic and Angular). The agile Scrum process is used to obtain the software product to control access to the university through a web application and an app. It is concluded that the software developed here responds to the needs of the university by improving control over on campus bicycle parking. [ABSTRACT FROM AUTHOR]

This paper presents the review of three main existing agile approaches: Scrum, Lean Software Development and Kanban, which served as the basis for the development of a proposal for a new approach in Agile development. To achieve this, a description of each agile approach to software development and a comparison of their strengths and weaknesses are made. Then, the new proposal is established based on the integration of the three approaches, defining a set of metrics and developing a case study to evaluate the integration and obtain quantitative and qualitative data. The results obtained from the case study proved to be quite positive because it allowed us to comprehensively evaluate the new approach. These results represent a promising start to continue working in this line of research. [ABSTRACT FROM AUTHOR]

This paper presents a proposal for assigning priorities to test cases in agile development environments. Through mathematical methods, a function is obtained to calculate the priority of the test cases of the software projects and their relationship with the phases of the project development life cycle. The defined function is based on four indicators whose information is possible to obtain in each of the project's iterations. A case study is also presented that allows comparing the results of ordering of the test cases, according to the priority with their effectiveness for the detection of potential errors and get expected result. [ABSTRACT FROM AUTHOR]

At present, software companies are part of an important economic sector worldwide, because they are more lucrative and well-paid every day, generating significant transformations at a social and economic level, in the same way with the progress of the business and knowledge management; At present, software companies are part of an important economic sector worldwide, because they are more lucrative and well-paid every day, generating significant transformations at a social and economic level, in the same way with the progress of companies and knowledge management; in order to obtain quality software, it implies the use of agile methodologies, or international standardized models of ISO quality for the analysis, design, programming and testing of software that allow unifying the work philosophy, in order to achieve greater "reliability, maintainability and analysis ", while raising productivity, both for development work and for software quality control; In this research, a study of the latest scientific and bibliographic publications is carried out, such as: Standards, policies, methodologies or procedures for the analysis, design, development, programming and control tests of software established for its elaboration, as evidenced in this article; The policies established for its elaboration are related to the definition of standards, in order to develop competitive software at the regional and international level it is required to be connected to the ISO / IEC 12207,, ISO / IEC 15504 SPICE, ISO / IEC 14598 certification systems and ISO 25000, this to consider if a company is mature. As a result, Colombia could be one of the interpreters of the new digital economy, through coordinated actions, if the concept of software quality is consolidated to become an exporter of this service, in order to develop competitive software in the international arena it is required to be connected to the certification systems, this is because today it is considered a poorly mature industry that from some points of view looks like "a craft rather than an industry" [ABSTRACT FROM AUTHOR]

This article presents a methodology based on the agile XP process for the development of robot-oriented software in educational platforms using the ROS middleware. The final result was a set of evidences such as user stories, UML-based diagrams and lines of code in the Python language that demonstrate good code quality practices in software development with the use of the object-oriented paradigm. A modified agile methodology is obtained with an evolutionary and incremental design but with a rigorous documentation useful for educational and research projects. [ABSTRACT FROM AUTHOR]

Depending on the technique used in the capture of requirements, it is possible to obtain innovative and iterative processes that truly support the construction of applications that consume web services. In the present article the elicitation approaches of the agile and traditional software methodologies are analyzed and the aspects of the rules that guarantee the concordance with the characteristics of the applications that consume services are taken, with the purpose of proposing a framework of work for the elicitation of the information applied to the specific case of applications that use web services. At the end of the article, a validation will be carried out in two companies that provide software development services. [ABSTRACT FROM AUTHOR]

Agile development methods prioritize the requirements for incremental delivery functionality. So the elicitation of these requirements must select these main features and specify them efficiently. However, there are still no registers that drive practices in this way. This work aims to identify as many elicitation practices in agile developments of scientific literature and classify them according to the main focus of each guideline. For this, it carries out a systematic mapping over main databases in this area. The results obtained show insufficient reporting guidelines for agile developers. Primary studies are mainly theoretical, this means that the requirements for elicitation practices in agile methods still require further empirical validation to be accepted. The definition of ontology is absolutely necessary, regarding elicitation in agile developments, to facilitate the identification of useful practices for obtaining successful products. [ABSTRACT FROM AUTHOR]

This research work presents a novel hybrid agile method for software development on mobile devices. The evaluation of several aspects is presented to show the advantages of this method, including level of agility the method, if the method is suitable or not to develop applications on mobile devices and its applicability on a real example. This new method was created after a process of five steps, which consisted on the analysis of current software for mobile devices and existent agile development methods, the design of an evaluation methodology for agile methods, the application of the evaluation method, the development of a hybrid agile development method and the use of the method in a real example. Components of the novel method, such as resources, schemas and artefacts used are described, since those elements can be useful for developers and project managers of mobile devices' software. The theoretical and practical evaluation of this new method indicates it possess the necessary characteristics to be consider an agile methodology. The method incorporates the strengths and improvements discovered in current agile development methods. Also, the application on the real example of development for mobile devices showed its applicability and good performance. [ABSTRACT FROM AUTHOR]

El artículo discurre sobre el concepto y la implementación de metodologías ágiles, o el uso de servicios de software, en el entorno empresarial. El autor comenta sobre la prevalencia del fracaso de nuevas empresas y describe la importancia de la aplicación e incorporación de metodologías ágiles para ayudar a prevenir el fracaso.

The article provides information on the virtual learning environment in military health education including incorporation of new information technologies and communication, agile process based structures and learning management system. Topics include management of economic resources, computer systems and complementary teaching.

Se presenta una introducción en la que el autor comenta sobre los artículos en este número, incluyendo uno sobre la sucesión en las empresas familiares, uno sobre las metodologías ágiles en los emprendimientos y uno sobre cloud computing.