Software Development Approach Research Articles

OntoSuSD: Software engineering approaches integration ontology for sustainable software development

AbstractDifferent software development approaches (SDAs) are developed with broad portfolios of development processes. Each of the approaches has certain exclusive principles, practices, thinking, and values, which are informally represented, implemented, and improperly institutionalized. Ontologies are developed for the representation, assessment, and adaptation of SDAs separately without having a shared terminology which may lead to terminological conflict and confusion affecting the simultaneous representation and implementation in software development industry and academia. The software engineering approaches does not consider and support sustainability as priority concern. However, the approaches have capabilities of supporting sustainable software development in different sustainability aspects. This research article aims for the designing and development of an integrated ontology of software engineering approaches (i.e., agile, lean, and green) named OntoSuSD (ontology for sustainable software development) to support sustainable software development knowledge, awareness, and implementation. The goal of OntoSuSD is to propose, design and develop a formal, generic, consistent, and shared knowledge base containing semantic terminology and description of concepts and relationships generated around the representation and implementation of lean, agile, and green approaches in software development processes, which will facilitate their simultaneous implementation and assessment for sustainable software development. The OntoSuSD is developed using practical ontology engineering methodology by reusing relevant ontologies and explicit concepts and properties are defined to fulfill knowledge requirements and representations of the domain. The OntoSuSD is evaluated, and results infer OntoSuSD has high ontological design, good domain coverage, potential applications and achieves purpose of the ontology development.

A Paradigm Shift in Automating Software Engineering Tasks: Bots

Increasing developer productivity and improving software quality are enduring challenges in software engineering. Addressing these challenges has influenced research toward improved automation and formalisms to realize software development tasks, along the way seeking for disruptive ways to support software developers. The past 55 years of software engineering has seen a number of paradigm shifts, fundamental changes in our underlying assumptions which led to making some progress in developing better quality software and disruptive improvements. For example, agile and lean software development approaches challenged our assumptions about the way software development tasks are orchestrated and communicated. Agile and lean software development philosophies advocate elimination of waste by emphasizing value-added tasks and encouraging improved understanding of what tasks stay in inventory.1 Embracing agile and lean software development approaches with discipline led software engineers to prioritize software engineering activities with a bias towards visible delivery, most often leading to improved software quality and developer well being when done right.

Large-Scale Agile Transformations for Software Quality Assurance: An Empirical Case Study from Pakistan

Software quality plays an important role in the easy and quick adoption of a software product by the end users. Agile methods have proven to play an effective role in ensuring software quality; however, the public sector is hesitant in its adoption. This study evaluates the adoption of agile methods in the public sector in-house software development and capitalization of potential benefits. A quantitative approach is used with 28 survey questionnaires based on budget, time, quick debugging and correction, maintenance, easy testing, and installation as software quality components to assess the employability of agile methods. The questionnaire was served to 216 information technology (IT) professionals (project managers: 6%, developers: 61%, quality assurance (QA) leads: 8%, and testers: 25%) from the public sector companies having experience in software development using agile and waterfall methods. The quality components and hypotheses are evaluated using the T-test and chi-square test, respectively, with a 95% confidence interval. The results highlight the benefits of using agile methodologies for software quality components in the public sector. Additionally, the findings demonstrate how agile software development approaches significantly affect the quality of software products and successful delivery within budget and deadline.

The Impact of Agile Development Practices on Project Outcomes

Agile software development methods were introduced to minimize problems faced using traditional software development approaches. There are several Agile approaches used in developing software projects, these include Scrum, Extreme programming and Kanban. An Agile approach focuses on collaboration between customers and developers and encourages development teams to be self-organizing. To achieve this there are different Agile practices teams choose to use in their projects. Some teams only use one practice whilst others use a combination of practices. The most common practices used are stand-ups, user stories, Burndown chart/Burnup chart, pair programming, Epic and User stories. This paper reports on the analysis of the data collected from people involved in Agile software development teams and identifies that the combination of practices in Agile software development have an impact on the communication in the team, project requirements and project priorities, with more practices being adopted correlating with better project outcomes.

Yazılım yerelleştirmede kitle kaynaklı çeviri etkinliği

Kitle kaynaklı çeviri, bir hizmet ya da ürünle ilgili içeriğin aynı anda birçok dile çevrilmesi amacıyla, gönüllü olarak bir araya gelmiş insanların gerçekleştirdiği bir yerelleştirme uygulaması olarak tanımlanabilir. Çevrimiçi platformlar aracılığıyla gerçekleştirilen kitle kaynaklı çeviri işlerinde yer alan gönüllüler, çevirmen ve/veya düzeltmen olarak projeye katkı sağlayabilirler. Kitle kaynaklı projelerde çok sayıda dile eş zamanlı olarak hızlı bir şekilde çeviri yapılabilmesi ve çeviri etkinliğinin gönüllülük esasına dayanması ya da düşük ücretlerle gerçekleştirilmesinin sonucu olarak maliyetten tasarruf edilir. Bu nedenle, bir çeviri projesinin kitle kaynaklı yapıda yürütülmesi şirketlere avantaj sağlar. Geleneksel yerelleştirme projelerinde “şelale modeli” adı verilen bir yöntem kullanılmaktaydı. Bu yöntemde, yazılım ya da uygulama geliştirildikten sonra yerelleştirme aşamasına geçiliyor; tüm metin unsurlarının bir araya getirilmesi ve çeviri işlemlerinin başlaması, ürünün piyasaya sunulmasından hemen önce gerçekleştiriliyordu. Günümüzde ise, yerelleştirme çalışmaları çoğunlukla yinelemeli ve iş birliğine dayalı yöntemlerin öne çıktığı çevik yazılım geliştirme yaklaşımlarıyla yürütülmektedir. Çevik yerelleştirme döngüsü içerisinde yer alan çevirmenler, ürün geliştirme çalışmaları devam ettikçe iş akışı içinde sürekli olarak görev alır. Geleneksel şelale modelinin aksine, çevik yerelleştirme sürecinde, çeviriler, erek kitlenin/son kullanıcıların beklenti ve gereksinimlerine yanıt verebilecek şekilde, yenilikçi çözümler üretilerek ve yazılım güncellemeleri dikkate alınarak gerçekleştirilir. Mozilla Firefox gibi açık kaynaklı yazılımlar, içerik çevirilerinde makine çevirisi sistemleri ve kendi çeviri bellekleri yanında, kitle kaynaklı çeviri olanaklarını da kullanmaktadır. Sistemde, farklı dil ve lehçelere çeviri yapan 200’ü aşkın ekip yer almakta, gün içinde binlerce metin dizgisi birçok dile çevrilmekte ve gerekli düzeltiler gerçekleştirilmektedir. Bu çalışma kapsamında, ilk olarak yazılım yerelleştirme sürecinde çevirmenin konumu sorgulanacak; ardından, kitle kaynaklı yerelleştirme çalışmalarında çevirmenin ne gibi görevler üstlenebildiği Mozilla Pontoon yerelleştirme yönetim sistemi özelinde örneklerle açıklanmaya çalışılacaktır.

Understanding Agile Practices for Job Satisfaction through Job Characteristics

Usage of Agile Practices draws the attention to the adoption of these agile methods because of their significant contributions to high software quality and job benefits. Therefore, the purpose of this research was to look at the role of job characteristics in mediating the relations between agile practices; project management (PM), and software development approaches (SDA) and job satisfaction. Sample was 486 professionals working in the companies incorporating agile practices, to whom an online survey was administered during period of September 2021 using the Google Forms platform. Findings affirmed the claims that agile PM and SDA practices made professionals more satisfied with their jobs and this impact has been found further mediated by job characteristics. Results indicated that job characteristics like job autonomy and feedback mediated the agile PM practices and job satisfaction. While agile SDA practices and job satisfaction were explained significantly by all job characteristics i.e., feedback, task significance, skill variety, autonomy, and task identity. This study offers insights into agile approaches in project management and software development. This research reveals beneficial aspects of agile practices that influence job satisfaction in work environment.

Building Software Applications Securely with DevSecOps: A Socio-Technical Perspective

While continuous real-time software delivery practices induced by agile software development approaches create new business opportunities for organizations, these practices also present new security challenges in the DevOps environment. DevSecOps attempts to incorporate advanced automated security practices for agility in the DevOps environment. Mainstream perspectives of DevSecOps tend to overlook the collaborative role played by social actors and their relations with technologies in securing software applications in organizations. The first perspective emphasises the use of technologies such as containers, microservices, cryptographic protocols and origin authentication to secure the continuous deployment pipeline. The other dominant perspective focuses almost exclusively on the social aspects such as organizational silos, culture, and team collaboration. Such one-sided perspectives neglect the socio-technical argument that secure software applications from continuous deployment emerges when developers, quality assurers, operators and security experts combine their collective expertise together with DevSecOps technologies. The article presents a socio-technical framework of DevSecOps based on a systematic literature review. The review focused primarily, but not exclusively, on the computing and information systems literature and identified 26 peer reviewed articles from 2016 to 2020 which met the quality criteria and contributed to the analysis. The authors used a critical appraisal checklist and member checking to assess the quality of the articles. The authors then used thematic analysis to develop a comprehensive framework for DevSecOps based on the insights from these articles and a socio-technical lens. The socio-technical framework can be used by practitioners to perform a more holistic analysis of their DevSecOps practices. It highlights the key social and technical themes that underpin the effectiveness of DevSecOps and how insights about these themes can be used by practitioners to improve the instrumental and humanistic goals of DevSecOps. An interdisciplinary approach is proposed to adequately address challenging socio-technical relationships in DevSecOps. Future research can empirically test the importance of the interplay between technology and human activities to improve the overall performance of DevSecOps and other domains in cyber warfare and security.

The Importance of Agile Technique in Comparison to Sequential Design Models

Software development procedures are constantly evolving to monitor and evaluate the quality and to save money and time. Numerous organizations are migrating away from traditional business models and toward agile methodologies. The purpose of this paper is to illustrate both traditional and agile software development approaches and the numerous techniques associated with them. This analysis conducted identical investigations into two radically different ways of thinking about product development: traditional methods and agile approaches. The paper is supported by several studies commissioned by various organizations to determine the transition from the traditional to the agile paradigm. The follow-up and data analysis explore and reveal changes and emerging trends that arose announcement of the agile technique which is mentioned in this paper, and also has gained increasing prominence in agile in product development over the last couple of years.

A SURVEY REPORT ON PROJECTOMATE

The Agile Development approach to systems development is the new fundamental for developers. Twelve Principles supporting the Agile Manifesto were elaborated in support. Hence the team always has to look towards identifying and proposing appropriate reference disciplines which are manifest in the Agile Development Universe of Discourse. The Manifesto evokes some reference disciplines to support its various aspects. Why is it desirable and necessary to search for such reference disciplines? The answer is Alternative Software Development and Project Management approaches, such as Software Prototyping and Rapid Development and now including Agile Development, all seemed based on pragmatic experience and have been designed mostly by consultants and practitioners. While this is not in any way to denigrate or deprecate them, it is felt that support for these approaches needs to also come from other disciplines, such as management studies, leadership studies, and the like to give Agile Development a more solid theoretical and intellectual basis.

Software development process evolution and paradigm shift - a case study of Malaysian companies

Due to the consequences of global software development (GSD), the traditional approaches of software development evolved into lightweight agile methods. The agile methods got overwhelming response from software development companies due to their obvious support to GSD. In this regard, limited research work has been presented on software process evolution and process paradigm shift in context of GSD. Most of the work presented on GSD mainly focus on the companies in Europe, America, Australia and other western countries. Existing research work highlight the standard benefits and challenges of GSD but do not investigate its effect on software development processes and associated reasons causing the affect particularly in Malaysian software development companies. The research work presented in this paper addresses this issue and investigates the effects of GSD on software processes, software process evolution and paradigm shift and finds the current software processes being used in Malaysian companies. Also, it further determines the GSD factors and reasons behind the change and selection of a software development process. GSD factors affecting the software processes have been termed as challenges. Structured interviews have been conducted to collect qualitative data from industry professionals involved in GSD. General inductive approach has been used for qualitative data analysis and findings. The results show that after GSD, Malaysian companies are mostly following agile methods. The traditional and ad-hoc approaches used before GSD have been replaced by the lightweight agile methodologies. Few of the companies are still following ad-hoc approaches mainly due to size of the project and company as most of the Malaysian companies are small and medium size. The research is significant that it provides clear insight into software process paradigm in Malaysian companies. The outcome of the research provides foundations for the standardization of software processes, process improvement, selection and quality enhancement approaches in Malaysian companies.

Stakeholder identification for a structured release planning approach in the automotive domain

In regulated domains like automotive, release planning is a complex process. This complex process consists of an agreement between product development processes for hardware as well as mechanic systems and approaches for software development. Particularly in automotive, the creation and synchronization of release plans for hardware as well as software is a challenge. Within the whole complex system development, it is challenging to consider the relevant stakeholders in the initial creation of a release plan. Depending on the context that a release plan shall be created for, there are different stakeholders that have to be considered from the beginning. There are numerous publications in the area of release planning, but there is no detailed research that shows which stakeholders have to be addressed in the automotive context. The aim of this work is to identify stakeholders of a release plan as an appropriate approach to create transparency in release planning in the automotive domain. Action research to elaborate relevant stakeholders for release planning was conducted at Dr. Ing. h. c. F. Porsche AG. We present a detailed overview of identified stakeholders as well as their required content and added value regarding two pilot projects. With this contribution, identified stakeholders of release planning from the hardware and software points of view are introduced. We discuss, based on the results, why there are common stakeholders for the two projects and why there are individual stakeholders for each project. With this work, we present a more complete stakeholder identification and a more detailed understanding of their needs.

Risk Assessment Approach for Software Development using Cause and Effect Analysis

In the industry of software development, the risk is the most effective competitor who tries to flop the project at any stage of development. Risk is a critical factor that is obscure and has the potential to wreak massive loss of the project in terms of money, time, and resources. It is also harmful to the credibility of the organization. Most of the organizations don’t focus on this factor, and as a result, might witness the project failing. Lack of risk assessment is very common in most of organizations. This paper introduces risk assessment factors and analyzes the various situations to tackle them. We investigate the most effective key risk variables cost, strategy, technique, operation, and some unknown/unpredictable factors. Based on these variables, survey and interviews are conducted and examined them. We applied empirical studies on these variables and map them on the cause and effect analysis technique. The proposed technique elaborates the factors behind these risk variables. After that, results and analysis of these variables have been incorporated to scale down the impact of risk.

Non-functional Requirements Elicitation in Agile Base Models

The elicitation of non-functional and functional needs is one of the most critical jobs of a requirement engineer. This scenario involves the imposition of limits on non-functional needs, whereas functional requirements call for the operation of a system in order to carry out functionality. Over the last few years, agile software development approaches have gained widespread acceptance in the software industry as a problem-solving paradigm. Non-functional requirements (NFRs) are frequently cited as a point of contention in non-functional requirements (NFR) approaches. As well as functional requirements like speed and efficiency, security is desired, amongst a host of other things. Aspects like usability, security, and privacy must all be taken into account. Functional needs must be treated as though they were first-class under the current industry standard of practice. Functional requirements are distinguished from non-functional requirements by the fact that only implemented requirements can be evaluated. To give an example, this method attracts the attention of the system's end users to a critical defect in its architecture. Projects of this type frequently fail because to dissatisfaction among the target audience. If you'd like a great demonstration, consider the London Ambulance System. When dealing with non-compliance to the necessary degree of detail, it is feasible to raise the likelihood of software success this is the first study of its kind in its sector to bring attention to the most critical NFR issues. The problems that arise during the elicitation stage of requirement engineering in agile base models. It also outlines the techniques and strategies that are being considered. Proposed in the literature as a means of dealing with these problems.

Modelling in low-code development: a multi-vocal systematic review

In 2014, a new software development approach started to get a foothold: low-code development. Already from its early days, practitioners in software engineering have been showing a rapidly growing interest in low-code development. In 2021 only, the revenue of low-code development technologies reached 13.8 billion USD. Moreover, the business success of low-code development has been sided by a growing interest from the software engineering research community. The model-driven engineering community has shown a particular interest in low-code development due to certain similarities between the two. In this article, we report on the planning, execution, and results of a multi-vocal systematic review on low-code development, with special focus to its relation to model-driven engineering. The review is intended to provide a structured and comprehensive snapshot of low-code development in its peak of inflated expectations technology adoption phase. From an initial set of potentially relevant 720 peer-reviewed publications and 199 grey literature sources, we selected 58 primary studies, which we analysed according to a meticulous data extraction, analysis, and synthesis process. Based on our results, we tend to frame low-code development as a set of methods and/or tools in the context of a broader methodology, often being identified as model-driven engineering.

Analysing the Obstacles in Agile Software Development Approach: A Review

The development of reusable and extensible software for business purposes has been the hallmark of the day. More developers are taking advantage of numerous approaches towards reaching their goals. One such approach is the agile approach in the development of extensible applications which has become so popular since its introduction over a decade ago. Using an agile approach that has a defined value in developing applications portray numerous benefits which have been identified by various scholars pointing out their outcomes as motivating factors of its adoption. With all such outline benefits, there exist some potential obstacles to agile developmental approach which has not been fully addressed. Hence, this article is aimed at analysing the obstacles which software developers face during agile development through a database search and also to guide them on ways to overcome such obstacles.

Preventing accessibility barriers: Guidelines for using user interface design patterns in mobile applications

Mobile applications play an important role in many aspects of life. It is essential to be aware of the software development approaches that can support the design of accessible applications. Their main goal is to ensure that the interactive applications are available to everyone, including people with disabilities, reduced skills, or momentarily induced impairments. This paper aims to identify the accessibility barriers that occur when using design patterns for building user interfaces of mobile apps and propose guidelines to prevent the problems most often encountered. We start by conducting a gray literature review in professional forums and blogs to reveal the difficulties developers face when using mobile user interface design patterns. We thus compiled a catalog which contains the descriptions of 9 user interface design patterns, the accessibility barriers linked to the use of each pattern and the guidelines that can be followed to prevent the problem of these barriers. We carried out an evaluation of the use of the catalog with 60 participants. Our results show that in most cases, the guidelines were correctly applied for the prototyping of mobile user interfaces. The findings also revealed the usefulness and ease-of-use of the guidelines from the perspective of the participants.

Advancing Static Code Analysis With Language-Agnostic Component Identification

Static code analysis of software systems has proven beneficial for a broad range of domains, including security assessments, coding practice, error detection, and others. However, as modern systems have grown in complexity and heterogeneity over the past few decades, advances in development frameworks have dominated. Rather than involving low-level language constructs, these frameworks typically focus on software components, including data entities, controllers, and endpoints. As a result, current code analysis approaches have become unsuitable for analyzing these modern systems due to their focus on low-level constructs in a single language. Thus, code analysis has become a far more complicated endeavor thanks to the plethora of languages, frameworks, and design approaches in modern software development. This paper presents a novel approach to solving the problem of being tied to a single language and its low-level constructs. The system’s source code is transformed into an intermediate representation called a language-agnostic abstract-syntax tree. This system representation is then assessed by generalized component parsers that extract relevant high-level information, such as components, from low-level structures. The design of the approach is presented here in detail, along with its evaluation in a case study involving two large, heterogeneous, cloud-native system benchmarks (Java and C++ microservices). The study demonstrates a unified identification approach to determine system data entities and endpoints. Utilizing higher-level constructs, such as components, can advance the current practice of system analysis to better face broader problems introduced by modern system development practices.

Исследование методов построения облачных платформенных сервисов и реализаций стандарта TOSCA

This paper overview and compares various tools for automating resource management in the cloud. Changes in software architecture and development approaches require automation of deployment management processes and further maintenance of software in different environments. Chapter 2 provides a detailed overview of the tools with sample configurations, as well as a breakdown of relevant articles that look at various automation tools and the effectiveness of their implementation. Chapter 3 presents a draft solution for combining orchestrators developed at ISP RAS to obtain a tool with functionality that competitors do not have.

Исследование методов построения облачных платформенных сервисов и реализаций стандарта TOSCA

This paper overview and compares various tools for automating resource management in the cloud. Changes in software architecture and development approaches require automation of deployment management processes and further maintenance of software in different environments. Chapter 2 provides a detailed overview of the tools with sample configurations, as well as a breakdown of relevant articles that look at various automation tools and the effectiveness of their implementation. Chapter 3 presents a draft solution for combining orchestrators developed at ISP RAS to obtain a tool with functionality that competitors do not have.

Systematic Literature Review: Causes of Rework in GSD

Global Software Development (GSD) involves multiple sites which comprise of different cultures and time zones apart from geographical locations. It is a common software development approach adopted to achieve competitiveness. However, due to multiple challenges it can result in misunderstandings and rework. Rework raises the chance of project failure by delaying the project and increasing the estimated budget. The aim of this study is to identify and categorize the rework causes to reduce its frequency in GSD. To identify the empirical literature related to causes of rework, we performed a Systematic Literature Review (SLR). A total of 23 studies are included as a result of final inclusion. The empirical literature from the year 2009 to 2020 is searched. The overall identified causes of rework in GSD are categorized into 6 major categories which are communication, Requirement Management (RM), roles of stakeholders, product development/integration issues, documentation issues, and differences among stakeholders. The most reported rework causes are related to the category of communication & coordination and RM. Moreover, an industrial survey is conducted to validate the identified rework causes and their mitigation practices from practitioners. This study will help practitioners and researchers in addressing the identified causes and therefore reduce the chances of rework.