Contemporary Software Development Research Articles

Transforming Hydrology Python Packages into Web Application Programming Interfaces: A Comprehensive Workflow Using Modern Web Technologies

The accessibility and deployment of complex hydrological models remain significant challenges in water resource management and research. This study presents a comprehensive workflow for converting Python-based hydrological models into web APIs, addressing the need for more accessible and interoperable modeling tools. The workflow leverages modern web technologies and containerization to streamline the deployment process. The workflow was applied to three distinct models: a GRACE downscaling model, a synthetic time series generator, and a MODFLOW groundwater model. The implementation process for each model was completed in approximately 15 min with a reliable internet connection, demonstrating the efficiency of the approach. The resulting APIs provide standardized interfaces for model execution, progress tracking, and result retrieval, facilitating integration with various applications. This workflow significantly reduces barriers to model deployment and usage, potentially broadening the user base for sophisticated hydrological tools. The approach aligns hydrological modeling with contemporary software development practices, opening new avenues for collaboration and innovation. While challenges such as performance scaling and security considerations remain, this work provides a blueprint for making complex hydrological models more accessible and operational, paving the way for enhanced research and practical applications in hydrology.

Bug Tracker User Guide

ABSTRACT___ The Bug Tracking Tool project addresses the pressing need for efficient bug tracking and management in contemporary software development. By leveraging modern web technologies and agile methodologies, the project aims to develop a comprehensive solution that streamlines bug identification, tracking, and resolution processes. Through a literature survey, key observations and shortcomings in existing bug tracking tools were identified, guiding the proposed work. The project’s methodology encompasses requirements gathering, design, implementation, testing, and deployment, focusing on user-centric design and functionality. Preliminary results demonstrate progress towards achieving project objectives, highlighting the tool’s potential to enhance software quality assurance practices and user satisfaction. Despite encountering challenges such as technical complexity and resource constraints, the project lays a solid foundation for future enhancements and optimizations. Overall, the Bug Tracking Tool project represents a significant step towards improving bug tracking practices and delivering higher-quality software products to end-users INDEX TEARMS – HTML, CSS , JavaScript, Python, Django Framework, SQLlite.

Impermanent identifiers: Enhanced source code comprehension and refactoring

In response to the prevailing challenges in contemporary software development, this article introduces an innovative approach to code augmentation centered around Impermanent Identifiers. The primary goal is to enhance the software development experience by introducing dynamic identifiers that adapt to changing contexts, facilitating more efficient interactions between developers and source code, ultimately advancing comprehension, maintenance, and collaboration in software development. Additionally, this study rigorously evaluates the adoption and acceptance of Impermanent Identifiers within the software development landscape. Through a comprehensive empirical examination, we investigate how developers perceive and integrate this approach into their daily programming practices, exploring perceived benefits, potential barriers, and factors influencing its adoption. In summary, this article charts a new course for code augmentation, proposing Impermanent Identifiers as its cornerstone while assessing their feasibility and acceptance among developers. This interdisciplinary research seeks to contribute to the continuous improvement of software development practices and the progress of code augmentation technology.

Mindfulness and Emotional Intelligence: A Study on Millennials on Hospitality

In software development, dependability and quality are critical. A Bug Tracking System (BTS) designed specifically for large-scale software projects is introduced in this significant project with the goal of streamlining bug tracking, reporting, detection, and resolution. The system provides secure authentication, a backend database that is reliable, and an easy-to-use web interface. Using cutting-edge web technologies, it offers critical features including automated notifications, progress tracking, severity assignment, and thorough bug reporting together with user-friendly interfaces for a range of user roles. Tools for data visualization help identify defect patterns and monitor projects. The project follows best practices recommended by the industry for requirements analysis, design, implementation, testing, and deployment, and it solicits ongoing input. The result is a thorough BTS that addresses defect management difficulties. Thorough testing and assessment in comparison to standards confirms its efficacy. This approach could have a big impact on software development, improving user satisfaction and quality. Furthermore, issues with bug tracking are covered, including distributed team communication, scalability, and automation balancing. Proposals for strategies to address these issues are grounded in scholarly research and professional opinions. This summary highlights the critical role that bug tracking systems play in contemporary software development, making it an invaluable tool for researchers, practitioners, and teams looking to improve bug tracking procedures and raise the caliber and effectiveness of the software development lifecycle. Keywords— Bug Tracking System, Software Development, Defect Management, Quality Assurance, Automation, Collaboration, Large-scale Projects.

JAVA BASED FIRST-PERSON SHOOTER (FPS) GAME WITH REMASTERED GRAPHICS

Our project aims to accurately examine an old game's assembly source, comprehend its usefulness, and convert it into efficient Java code. Using Java's object-oriented characteristics, the emphasis is on restructuring and organizing code to make it more maintainable and comprehensible. The successful conversion of this game to Java demonstrates how knowledge of low-level assembly programming can supplement skill in high-level Java programming, resulting in a smooth integration of traditional gameplay with current technology. This integration not only heightens perceptions but also makes the game more accessible to modern audiences, providing an immersive gaming experience that combines the game's original character with contemporary software development standards. The enhanced graphics will also include upgrading game elements including textures, models, and special effects. The enhanced graphics will include improved game assets like textures, models, and special effects, as well as advanced lighting and shading effects. In addition, the game's user interface will be updated to increase use and appearance. The project's goal is to demonstrate the integration of classic FPS gameplay with contemporary graphics technology, providing players with an enhanced gaming experience that combines the recollections of old FPS games with the visual quality of modern gaming. Key Words: - Java programming, game development , FPS game, graphics.

Advancements in GitHub Automation and Workflow: A Comprehensive Exploration

The landscape of software development has been significantly transformed by the integration of automation and streamlined workflows, with GitHub emerging as a pivotal platform in this evolution. This research paper delves into the multifaceted realm of GitHub automation and workflow, investigating key aspects that contribute to enhanced efficiency, collaboration, and code quality in modern development practices. The paper begins by exploring the utilization of GitHub Actions for establishing robust Continuous Integration and Continuous Deployment (CI/CD) pipelines. Best practices for designing reliable workflows are discussed, along with insights into customizing workflows to suit diverse project requirements through the use of custom actions and templates. The automation of code reviews is scrutinized, with a focus on tools and practices that facilitate objective and efficient evaluation of code quality. The paper also investigates GitHub's role in security automation, covering strategies for vulnerability detection and integration of security checks into the development lifecycle. Collaborative workflows on GitHub, including branch management, pull requests, and code reviews, are explored as pivotal components fostering teamwork. The integration of GitHub into DevOps practices is analyzed, showcasing its synergy with popular DevOps tools and platforms. As a forward-looking endeavor, the research paper concludes by examining emerging trends and technologies in GitHub automation. By encapsulating a comprehensive overview of the current state and future trajectories of GitHub automation and workflow, this paper aims to contribute to the collective understanding of best practices, challenges, and opportunities in contemporary software development.

Team Size Dynamics: A Study on Factors Influencing Pull Request Acceptance in Open-Source Software Repositories

In contemporary software development, Pull-Based Development has become the prevalent methodology, prompting extensive research into the factors influencing the success of contributions. Our study delves into numerous factors while specifically investigating the pivotal role of team size in the evaluation and acceptance of pull requests. The significance of team size is underscored by its historical importance in guiding the choice of software methodologies. Our findings reveal that team size impacts the decision-making process concerning pull requests. The factors influencing these decisions are affected by team size, emphasizing the necessity of considering this variable in modern software projects. Our research illuminates the complex dynamics of pull-based development, providing valuable insights for project owners and developers alike.

A CASE environment for Project-based Course to learn a sustainable software development

In the context of contemporary software development education, project-based courses have gained prominence as effective pedagogical tools. This methodology empowers students to cultivate practical skills by engaging in real-world projects. However, integrating sustainable software development practices into such courses often remains a challenge such as the need to set up new technologies for each semester, making it hard to ensure consistent and disciplined development. To address this gap, this research introduces Agilearn, the conception of a Computer-Aided Software Engineering (CASE) environment tailored explicitly for project-based courses with a strong focus on promoting sustainability. It is expected to enhance the learning experience by offering a collaborative platform that automates tasks and establishes a standardized agile environment for students. This paper presents the requirements analysis, the course design to implement Agilearn, the architecture of Agilearn, and a case study to implement Agilearn.

Investigating the Role of Exploratory Testing in Agile Software Development: A Case Study Analysis

This abstract provides a thorough examination of the critical function of exploratory testing in the framework of Agile software development approaches, drawing conclusions from a careful examination of case studies. Agile approaches have become a top framework for encouraging adaptability, cooperation, and continuous improvement in response to the software development processes' ever-increasing complexity and quick evolution. In such a dynamic environment, exploratory testing is a vital tool that helps teams discover bugs, iteratively explore software features, and improve testing methods. This paper clarifies the complex interactions between exploratory testing and Agile principles, illuminating their effects on project outcomes, team dynamics, and product quality through a thorough analysis of several case studies taken from various industry contexts. This study offers useful insights and suggestions for improving testing procedures and streamlining software development processes by combining empirical data and theoretical frameworks to better understand how exploratory testing can be successfully integrated into Agile environments. Finally, this study emphasises the importance of exploratory testing as a fundamental component of Agile approaches and argues for the deliberate application of this practice to promote innovation, flexibility, and quality control in contemporary software development projects.

The platformisation of software development: Connective coding and platform vernaculars on GitHub

This article contributes to recent scholarship on platform, software and media studies by critically engaging with the ‘social coding’ platform GitHub, one of the most prominent actors in the online proprietary and F/OSS (free and/or open-source software) code hosting space. It examines the platformisation of software and project development on GitHub by combining institutional and cultural analysis. The institutional analysis focuses on critically examining the platform from a material-economic perspective to understand how it configures contemporary software and project development work. It proposes the concept of ‘connective coding’ to characterise how software intermediaries such as GitHub configure, valorise and capitalise on public repositories, developer and organisation profiles. This institutional perspective is complemented by a case study analysing cultural practices mediated by the platform. The case study examines the platform vernaculars of news media and journalism initiatives highlighted by Source, a key publication in the newsroom software development space, and how GitHub modulates visibility in this space. It finds that the high-visibility platform vernacular of this news media and journalism space is dominated by a mix of established actors such as the New York Times, the Guardian and Bloomberg, as well as more recent actors and initiatives such as ProPublica and Document Cloud. This high-visibility news media and journalism platform vernacular is characterised by multiple F/OSS and F/OSS-inspired practices and styles. Finally, by contrast, low-visibility public repositories in this space may be seen as indicative of GitHub’s role in facilitating various kinds of ‘post-F/OSS’ software development cultures.

Python API Misuse Mining and Classification Based on Hybrid Analysis and Attention Mechanism

APIs play a crucial role in contemporary software development, streamlining implementation and maintenance processes. However, improper API usage can result in significant issues such as unexpected outcomes, security vulnerabilities and system crashes. To detect API misuses, current methods primarily rely on comparing established API usage patterns with target points for automated detection, mainly based on pre-validated datasets. Nonetheless, there is a scarcity of publicly available datasets on API misuses and their corresponding fixes, which hinders data-driven research. Moreover, most existing techniques concentrate on statically typed languages, such as Java and C, with only a few addressing dynamic languages like Python effectively, due to difficulties in handling dynamic features. Therefore, it is essential to identify Python API misuses and their fixes automatically and promptly. In this paper, we introduce HatPAM, a Hybrid Analysis and Attention-based Python API-Misuse Miner, which (a) provides a method for automatically mining true-positive commits related to Python API-misuse fixes from GitHub and (b) presents the subsequent processing for classifying Python API misuses in true-positive cases. Particularly, HatPAM applies hybrid static analysis and introduces a structure-based attention mechanism to examine syntax, semantics and structural features in Python code context, and considers the consistency between code and developers’ natural intent to significantly reduce false-positive cases. Evaluation on six popular Python projects reveals that HatPAM outperforms various state-of-the-art baselines, achieving up to 92.2% Precision, 86.7% Recall and 89.3% F1-score, indicating its capability to identify and classify Python API-misuse commits.

The Impact of the Web Data Access Object (WebDAO) Design Pattern on Productivity

In contemporary software development, it is crucial to adhere to design patterns because well-organized and readily maintainable source code facilitates bug fixes and the development of new features. A carefully selected set of design patterns can have a significant impact on the productivity of software development. Data Access Object (DAO) is a frequently used design pattern that provides an abstraction layer between the application and the database and is present in the back-end. As serverless development arises, more and more applications are using the DAO design pattern, but it has been moved to the front-end. We refer to this pattern as WebDAO. It is evident that the DAO pattern improves development productivity, but it has never been demonstrated for WebDAO. Here, we evaluated the open source Angular projects to determine whether they use WebDAO. For automatic evaluation, we trained a Natural Language Processing (NLP) model that can recognize the WebDAO design pattern with 92% accuracy. On the basis of the results, we analyzed the entire history of the projects and presented how the WebDAO design pattern impacts productivity, taking into account the number of commits, changes, and issues.

Integrating Data Pipelines into Release Pipelines: A Comprehensive Examination

The integration of data pipelines within release pipelines has become essential in contemporary software development to ensure a smooth flow of data, boost operational efficiency, and maintain high standards of software delivery. This paper thoroughly examines the concept, architecture, implementation, and advantages of embedding data pipelines into release pipelines. It also addresses the challenges and best practices to optimize this integration.

Exploring Teams' Temporal Factors for Determining Process Tailoring that Promotes the Evolution of Agilebased Software Development

In contemporary software development, software process tailoring (SPT) refers to the continual planning and adjustment of the development process, which evolves to better accommodate dynamics and meet customer needs. SPT is a critical teamwork involving the differences in time-related perceptions among team members when tailoring to adjust and refine the development. This is particularly true in agile-based projects that promote iterative development over shorter cycle times for early release; thus, temporality is critical to efficiently and effectively determine a process solution for the next iteration of time-bound development. In this regard, this study theorizes a temporal model to explore how teams' temporal leadership, temporal reflexivity and shared temporal cognitions (STC) collectively determine SPT performance in agile environments. Based on an empirical examination, we suggest facilitating the role of temporal leadership in agile development, as the results demonstrate that it not only directly increases SPT performance but also stimulates both temporal reflexivity and STC in their collateral influences on effectual development planning. Notably, the results also show that team reflexivity does not exert the same favorable effect in SPT as in the distributed team environment. Theoretical implications are considered, and practical applications of the findings are provided.

Automation for CI/CD Pipeline for Code Delivery with Multiple Technologies

In contemporary software development, the use of diverse technologies is prevalent, introducing challenges in managing Continuous Integration and Continuous Delivery (CI/CD) pipelines. This white paper investigates the complexities associated with deploying code written in multiple technologies within a unified CI/CD pipeline. It proposes a comprehensive solution for effective automation to enhance agility, efficiency, and reliability in software delivery.

Search-based detection of code changes introducing performance regression

• Detecting code changes responsible for performance regression is time-consuming. • Dynamic analysis is a credible source in detection performance regression but expensive. • Detecting performance regression problem formulated as optimization problem. • Detection rules generated by using a multi-objective evolutionary algorithm. In contemporary software development, developers commonly conduct regression testing to ensure that code changes do not affect software quality. Conducting performance regression testing after every code change is known to be expensive which emigres the need to direct the performance regression testing efforts on code changes that are most likely introducing performance regression. In this paper, we exploit code change metrics to identify the group introducing the regression based on a pre-trained detection rule. We present PRICE approach as a new formulation of detecting code changes introducing performance regression as an optimization problem using multi-objective evolutionary algorithms. PRICE evaluated using a set of 8000 commits, extracted from the Git project. Results show the effectiveness of our approach in accurately detecting performance regression introducing code changes. The average regression detection PRICE provides is 77% which is 22% more than the state-of-the-art deterministic approach. This improvement didn’t compromise the detection of the contradicted code changes that are not introducing a regression. PRICE provides detection of code changes not introducing a regression averaged 63%, which is also an improvement of 14% than the comparative approach. Using PRICE, we were able to explore new search spaces and provide competing results.

An Exploration of npm Package Co-Usage Examples from Stack Overflow: A Case Study

Third-party package usage has become a common practice in contemporary software development. Developers often face different challenges, including choosing the right libraries, installing errors, discrepancies, setting up the environment, and building failures during software development. The risks of maintaining a third-party package are well known, but it is unclear how information from Stack Overflow (SO) can be useful. This paper performed an empirical study to explore npm package co-usage examples from SO. From over 30,000 SO question posts, we extracted 2,100 posts with package usage information and matched them against the 217,934 npm library package. We find that, popular and highly used libraries are not discussed as often in SO. However, we can see that the accepted answers may prove useful, as we believe that the usage examples and executable commands could be reused for tool support.

Secure software development: industrial practice - a review

The current state of application assets with respect to their development, functionality, scalability, user friendliness, and compatibility with legacy systems has witnessed an unprecedented degree of positive improvements. This induced increase in productivity and value has been a product of the technological innovations within and around the software development landscape. Owing to specific software development practices including software reusability, Object Oriented Programming (OOP), encapsulation, and portability, all sectors of the economy have come to embrace software products that have helped to drive business transactions. Nonetheless, the proliferation of software which has driven up the velocity, veracity and volume of data associated with transactions has become a goldmine for grabs. Hackers and adversaries alike have thus capitalized on this development to exploit the potential threats and vulnerabilities associated with software products. Insecure software is global issue, and one that impacts individuals, organizations and governments. Data loss is both a security and privacy issue, with compliance, regulatory and legal concerns, and bad actors are relentless in their efforts to steal, deface, alter/manipulate, destroy, and compromise software systems. Organizations should therefore embrace secure code principles, threat modeling, and institute a Secure Software Development Lifecycle (SSDLC) practice that will aid the embedment of security into the development phase, to contain the risks, threats, and vulnerabilities that are inherent in software development. This paper demonstrates an effort to provide and arm organizations with the necessary tools, processes, and mechanisms that can be leveraged to combat cyber-threats and enforce Information Assurance (IA) within and around enterprise application assets. Beginning with an overview of the contemporary software development practices witnessed in diverse organizations, including financial, energy, aviation, commerce, nuclear, defense, and several other Critical Infrastructure (CI) organizations, the tenets of a composite, structured and robust. SSDLC has been presented to promote a defense-in-depth security for enterprise organizations.

Constructing a software requirements specification and design for electronic IT news magazine system

Requirements engineering process intends to obtain software services and constraints. This process is essential to meet the customer's needs and expectations. This process includes three main activities in general. These are detecting requirements by interacting with software stakeholders, transferring these requirements into a standard document, and examining that the requirements really define the software that the client needs. Functional requirements are services that the software should deliver to the end-user. In addition, functional requirements describe how the software should respond to specific inputs, and how the software should behave in certain circumstances. This paper aims to develop a software requirements specification document of the electronic IT news magazine system. The electronic magazine provides users to post and view up-to-date IT news. Still, there is a lack in the literature of comprehensive studies about the construction of the electronic magazine software specification and design in conformance with the contemporary software development processes. Moreover, there is a need for a suitable research framework to support the requirements engineering process. The novelty of this paper is the construction of software specification and design of the electronic magazine by following the Al-Msie'deen research framework. All the documents of software requirements specification and design have been constructed to conform to the agile usage-centered design technique and the proposed research framework. A requirements specification and design are suggested and followed for the construction of the electronic magazine software. This study proved that involving users extensively in the process of software requirements specification and design will lead to the creation of dependable and acceptable software systems.

Exploring the effects of team coordination and power distance on effective software process tailoring: a theoretical perspective

PurposeSoftware process tailoring (SPT) plays a critical role in contemporary software development. Because SPT determines how a software project proceeds, its effectiveness should be investigated. Specifically, SPT is a collaborative yet highly conflictual process, and the existing literature has paid little or no attention to how team members coordinate and to how power distance (PD) influences coordination under this conflictual situation for the purpose of fostering SPT effectiveness.Design/methodology/approachA propositional research method is utilized by reviewing the extant literature regarding SPT, team coordination and PD. Accordingly, several propositions are developed to theorize the contributive and moderating effects of team coordinative capabilities and PD on SPT effectiveness.FindingsThis study advances the understanding of the underlying mechanisms of the four distinct coordination capabilities in performing SPT, which will help software firms comprehend the moderating effects of PD on the relationships among coordinative capabilities and SPT effectiveness.Originality/valueThis study extends coordination theory and reveals four coordination capabilities that nurture SPT effectiveness. Moreover, this study demonstrates how power plays a role in the coordination of a team through the collaborative yet divergent SPT decision process to yield an integrative tailoring solution. In particular, we take a fresh viewpoint of PD considering the member-member relationship in exploring its moderating effects in the SPT context.