Traditional Software Development Methodologies Research Articles

Building Trust in AI -A Simplified Guide to Ensure Software Quality

In recent years, Artificial Intelligence (AI) has emerged as an innovative technology in a variety of areas, including software development. The demand for high-quality software has grown in tandem with the increasing complexity of applications and user expectations.AI-driven approaches are revolutionizing traditional software development methodologies by automating and augmenting various stages of the development life cycle, leading to improved efficiency, reduced costs, and enhanced software quality. This research explores the crucial role of AI in developing high-quality software and its impact on the software development process. Firstly, it discusses how AI technologies like machine learning, natural language processing, and deep learning can facilitate requirements gathering, analysis, and validation, leading to better understanding and refinement of user needs. Next, it delves into the significance of AI in automating the coding process, such as generating code snippets, fixing bugs, and optimizing performance, thus accelerating development and reducing human errors. Moreover, the paper highlights the pivotal role of AI in software testing and quality assurance. AI-powered testing tools can execute comprehensive tests more efficiently, detect defects, and predict potential software vulnerabilities, thereby enhancing the overall reliability and robustness of the software product. Additionally, AI techniques can enable real-time monitoring and analytics, allowing developers to identify and address issues promptly during the software's operational phase. Furthermore, the paper addresses the ethical considerations and challenges associated with AI in software development, including bias in training data, interpretability of AI-driven decisions, and potential job displacement for software developers.

Performance Assessment of Traditional Software Development Methodologies and DevOps Automation Culture

Successful implementations of Software Development Methodologies significantly improve software efficiency, collaboration and security. Most companies are moving away from traditional development methodologies towards DevOps for faster and better software delivery. DevOps, which is a primary need of the IT industry, brings development and operation teams together to overcome communication gaps responsible for software failures. It relies on different sets of automation tools to robotize the tasks of software development from continuous integration, to testing, delivery, and deployment. The existence of several automation tools in each development phase raises the need for an integrated set of tools to reduce development time. For this purpose, we used the DevOps-based hybrid model Integrated Tool Chain (ITC), along with three sample java-based projects or code repositories to quantify the results. This paper evaluates and compares measurement metrics of java projects using traditional development methodologies and DevOps, and the results are shown in tabular and graphical format. The latest Google and Stack Overflow Trends have also been included to retrieve the best performer development methodology. This comparative and evaluative performance analysis will be beneficial to young researchers that study the metrics of software development, while also they will be introduced to the automotive environment of DevOps, the latest emerging buzzword in software development.

The Concept of Automatic Creation Tool for Computer Game Scenario Prototype

The experience of game studios shows that classical methodologies of software development are poorly implemented in video game development because of the interactive component of this area, related to the correct creation of feedback between the game and the user. In addition, video game development involves a large number of developers from different areas, whose activities must be coordinated in the project.
 Despite these differences, video games, like any other developed software, need a development team organization process. In this article we reviewed traditional software development methodologies, as well as modifications specializing specifically in video game development. The most popular methodologies were compared and the quality of their implementation in video game development studios was determined.

The impact of general data protection regulation on software engineering practices

PurposeThis paper aims to explore the changes imposed by the general data protection regulation (GDPR) on software engineering practices. The fundamental objective is to have a perception of the practices and phases that have experienced the greatest changes. Additionally, it aims to identify a set of good practices that can be adopted by software engineering companies.Design/methodology/approachThis study uses a qualitative methodology through four case studies involving Portuguese software engineering companies. Two of these companies are small and medium enterprises (SMEs) while the other remaining two are micro-companies. The thematic analysis is adopted to identify patterns in the performed interviews.FindingsThe findings indicate that significant changes have occurred at all stages of software development. In particular, the initial stages of identifying requirements and modeling processes were the stages that experienced the greatest changes. On the opposite, the technical development phase has not noticeably changed but, nevertheless, it is necessary to look at the importance of training software developers for GDPR rules and practices.Research limitations/implicationsTwo relevant limitations were identified as follows: only four case studies involving micro-companies and SMEs were considered, and only the traditional software development methodology was considered. The use of agile methodologies was not explored in this study and the findings can only be mainly applied to the waterfall model.Originality/valueThis study offers mainly practical contributions by identifying a set of challenges that are posed to software engineering companies by the implementation of GDPR. Through their knowledge, it is expected to help these companies to better prepare themselves and anticipate the challenges they will necessarily face.

AGILE SOFTWARE DEVELOPMENT

Agile Software Development plays a quintessential part in modern day software development. The term Agile refers to frequent reassessment and adaptation of plans and techniques and dividing tasks into shorter tasks for efficiency. Agile Software Development differs considerably from Traditional Software Development Methodology. Agile methodology aims to deliver features of a software project in small steps within a short duration of time (i.e., iterations). Hence, it becomes necessary to use agile software development methodology in todays’ fast-paced revolutionizing software industry. This paper discusses the important subtopics of Agile Software Development which gathered by reviewing/surveying of research papers. First, is the Agile Planning Life Cycle which consists of various stages such as pre-planning, planning, release planning and product backlog management. In the next section, principles such as Scrum, Extreme Programming, Kanban and Lean are discussed. The last section comprises the impact of Agile principles on software quality.

Investigating Crucial Factors of Agile Software Development Through Composite Approach

The major emphasis of Software Engineering (SE) discipline is to produce successful software systems. The success of software projects is estimated through quadruple measures including budget, cost, scope, and quality. To meet this aim of SE, several software development processes are presented in the literature. Such processes are categorized into two different methodologies which are known as traditional and agile software development methodologies. The issue with traditional software development methodologies is that they had not shown any remarkable progress towards the fundamental goal of SE. Consequently, software development organizations have started to adopt agile methodologies in the pursuit of successful software development. However, agile adoption does not come without challenges that vary from one context to another. Therefore, it is necessary to figure out the key factors of agile software development for successful project outcomes. In the wake of such need, this study investigated the Critical Success Factors (CSFs), categorized and prioritized them through a mixed-method approach. Such an approach was based on the detailed literature review and Delphi method accompanied with Multi-Criteria Decision Analysis (MCDA) technique. Twelve CSFs were revealed and categorized into people, organization and technical dimensions. Among these factors, ‘team capability’ was found the most significant factor where ‘culture’ was revealed as the least significant factor. The findings of the study would be promising for agile software development that is carried on in the local software industry.

A Comparison between Agile and Traditional Software Development Methodologies

Agile and Traditional software development methodologies, both are being used in different projects of software development industry. Agile software development technology is an incremental software development process. On the other hand, Traditional software development methodologies or plan-driven software can be explained as a more formal approach to software development. These methodologies come with a fully completed set of systems requirements followed by an architectural and high level design development and inspiration. This research focuses on the software development life cycle, role and responsibilities of agile and traditional software development methodologies and their technical practices. It performs a comparison between both the software development methodologies. Here a questionnaire is used to collect data from the various experts of different IT related organizations of Bangladesh. In the questionnaire, there are three sections to bring out the individual knowledge from different organization, methodology knowledge of the respondents and software development experience of the respondents. The respondents are mainly software engineer, system analyst, software developer etc. A comparison is also performed between this survey result and a survey done by Ambler.

COMPARISON OF TRADITIONAL AND AGILE SOFTWARE DEVELOPMENT METHODOLOGY: A SHORT SURVEY

This paper explains comparison between traditional and agile software development methodologies. Due to the significant use of software development processes, in product development this discussion is quite important. For discussion, their definitions, development life cycles, critical practices, advantages, disadvantages used as evaluative parameters including six different modes, three from each. This research also summarizes limitations and factors used to control the cost of both methodologies. The discussion continued with the conclusion that what are the core steps while selecting desired software development methodology either traditional or agile and what will be the impact of the end product.

PROSPECTS OF AGILE MANAGEMENT METHODOLOGY APPLICATION IN IT-PROJECT MANAGEMENT

The paper proposes a modern scientific and practical approach to improving the performance of enterprises through the use of Agile management. The purpose of the article is to improve the process of managing web projects through the use of agile management mechanisms in the planning and development phase of an IT project. One of the possible promising methods for solving modern management problems is the application of the principles of flexible development methodology. (Agile development). The prerequisites for the emergence of the Agile management concept were identified and a comparative analysis of project management approaches was conducted. The peculiarities of application of different project management methodologies in IT companies are investigated. The characteristics of the positive and negative aspects of the application of alternative approaches to software development are given. The main difference between traditional software development methodology and flexible development methodology is outlined. The basic characteristics of the most used model of agile management - the Scrum model are given. It is determined that within the framework of the Scrum model, the factors of minimizing the risk of failure of individual projects and the entire project portfolio of an organization are: ensuring the balance of the portfolio in its formation; regular monitoring of the portfolio implementation and preventive measures; agreed decision-making on changes to projects, taking into account the interrelation of content, timing and resources with other projects. Changes were recorded in the functional responsibilities of investors, executives, and customers of the software when implementing the flexible methodology. The factors of increase of efficiency of realization of IT-projects are revealed and advantages of correct use of flexible methodology for projects in the field of IT are stated. A further area of research in the field of lean / agile management methodology will be to apply the benefits of these methodological approaches to other areas of the economy.

An iteration‐based interactive analysis method to design dynamic service‐oriented systems

SummaryService‐oriented paradigm presents numerous new software development patterns and idioms. Software systems are implemented by composing existing third‐party services deployed in the open environment, which is significantly different from traditional software development methodologies in which systems are built through developing modules after system design in a closed environment. Therefore, it is urgent to raise a new design method to adapt to this new circumstance. We concentrate on reusing as many deployed services as possible then introduce a new life cycle model named Taiji model to illustrate this development process. The iteration‐based interactive analysis method following the model is proposed to design service‐oriented systems based on the view of extracting non‐creative activities from a creative activity through defining new notations or applying new rules. The method includes the interactive analysis process that analyzes requirements with deployed services in a local point of view and the iterative analysis process that redesigns system with new knowledge in a global perspective. Meanwhile, the reusable service threshold value is defined to build the uncertain candidate service set (UCSS) of each module in analysis process. The reliability and flexibility of systems can be improved through the quantitative static structure analysis on the basis of the UCSS of systems. Meanwhile, a practical dynamic service binding method that selects services according to actual states of invoking them is presented on the basis of the UCSS containing them. Finally, we also give a case study to illustrate the feasibility of this method. Copyright © 2017 John Wiley & Sons, Ltd.

Survey and Comparative Study on Agile Methods in Software Engineering

Today‘s business environment is very much dynamic, and organisations are constantly changing their software requirements to adjust with new environment. They also demand for fast delivery of software products as well as for accepting changing requirements. In this aspect, traditional plan-driven developments fail to meet up these requirements. Though traditional software development methodologies, such as life cycle-based structured and object oriented approaches, continue to dominate the systems development few decades and much research has done in traditional methodologies, Agile software development brings its own set of novel challenges that must be addressed to satisfy the customer through early and continuous delivery of the valuable software. This article is located in the field of engineering Information Systems (IS) and in particular in the world of engineering process. In order, to produce information systems that the customer needs, many methods engineering were introduced. The first methods introduced are called sequential methods like Cascade method, V cycle or the Y cycle then there are iterative methods like RUP or Symphony and finally agile methods like Scrum and XP have emerged.

Controlling Change on Agile Software Development Projects

The importance of effective change control when developing software is well known throughout the Information Technology (IT) industry. Any software development project will deal with various forms of change throughout its lifetime, and without effective change control processes in place changes can lead to unforeseen, and often negative, consequences for an organization [8]. Yet despite this, change will almost always occur, and should therefore be anticipated. The change control processes in place on a software development project vary depending on the software development methodology being utilized [3]. Agile software development methodologies have become increasingly popular in recent years, with eighty-eight percent of respondents in a 2013 survey stating that their organization was practicing Agile [1]. According to Winter[1], Scrum is the most popular of the various Agile methodologies. A primary motivation for switching to Agile methodologies such as Scrum has been to better manage changes that were always inevitable, yet difficult to manage when utilizing traditional software development methodologies, such as the Waterfall methodology [4]. As more and more organizations transition to the Agile Scrum methodology, they must ensure processes are in place to properly control all forms of change. This includes changes that fall within the scope of a single project, as well as changes with a scope that extends across the enterprise. This paper explores various forms of change control and provides strategies and methods for effectively controlling and managing all forms of change on Agile software development projects.

Mejoramiento en la productividad de software por la adaptación de un marco de desarrollo ágil

(Recibido: 2015/02/20 - Aceptado: 2015/06/17)El presente trabajo de investigación plantea que el uso de las metodologías ágiles en conjunto con herramientas de software libre permite mejorar la productividad, reducir costos y optimizar recursos en la etapa de desarrollo informático, y contribuye a mejorar la satisfacción del usuario con la implementación de software de excelente calidad. A continuación se realiza un diagnóstico de las variables consideradas de importancia para el éxito en la ejecución o desarrollo de proyectos informáticos y que están asociadas al uso de las metodologías tradicionales y ágiles para el desarrollo de software.

Investigation of Adherence Degree of Agile Requirements Engineering Practices in Non-Agile Software Development Organizations

Requirements are critical for the success of software projects. Requirements are practically difficult to produce, as the hardest stage of building a software system is to decide what the system should do. Moreover, requirements errors are expensive to fix in the later phases of the software development life cycle. The rapidly changing business environment is highly challenging traditional Requirements Engineering (RE) practices. Most of the software development organizations are working in such dynamic environment, as a result, either by or without their awareness agile methodologies are adopted in various phases of their software development cycles. The aim of this paper is to investigate the adherence degree of agile RE practices in various software development organizations that are classifying themselves as adopting traditional (i.e. non-agile) software development methodologies. An approach is proposed for achieving this aim and it is applied on five different projects from four different organizations. The result shows that even the non-agile software development organizations are applying agile RE practices by different adherence degrees.

Investigating the Project Management Trends in IT Organizations in Saudi Arabia

This is a study to investigate the current status and future trends of IT project management in Saudi Arabia. The organization ability of transition from traditional software development methodology to agile methodologies is addressed as well. The study is based on online survey that was answered by 17 respondents who represent six big organizations from the private and the government sectors. The results are analyzed and discussed. The expected obstacles that organizations could face when changing to agile methodologies are discussed.

Analyzing the Harmful Effect of God Class Refactoring on Power Consumption

Energy efficiency and other sustainability issues are common concerns in the material production industries but rarely addressed in software development efforts. Instead, traditional software development life cycles and methodologies place an emphasis on maintainability and other intrinsic software quality features. One standard practice is to improve maintainability by detecting bad smells in a system's architecture and then applying refactoring transformations to deal with those smells. The refactoring research area is sufficiently mature for most techniques to achieve more maintainable system architectures, but the authors argue that they can also lead to both decreased sustainability and increased power consumption. Accordingly, this article analyzes the relationship between architecture sustainability and maintainability by providing empirical evidence of how power consumption increases after refactoring.

Building Secure Software Using XP

Security is an important and challenging aspect that needs to be considered at an early stage during software development. Traditional software development methodologies do not deal with security issues and so there is no structured guidance for security design and development; security is usually an afterthought activity. This paper discusses the integration of XP with security activities based on the CLASP (Comprehensive Lightweight Application Security Process) methodology. This integration will help developers using XP develop secure software by applying security measures in all phases and activities, thereby minimizing the security vulnerabilities exploited by attackers.

Layered Approach to Open Source Software Development Success

Open source has emerged as a widely accepted software development phenomenon which has tremendously brought about a significant paradigm shift from traditional software development methodologies such as top down design and stepwise refinement to an unconventional software development approach by means of collaborative software development method among a wide geographically dispersed interested developers and committed project participants while paying less attention to immediate “physical gains”. The open source approach focuses on highly diverse views of developer motivations; ranging from ego gratification, ideological satisfaction and gift culture for individual developers and open source motivations may be viewed from spreading the software development risks and associated maintenance costs at corporate organisational level. In this article, a five layered open onion model of open source was broadly examined. Analysis and evaluation were narrowed down to only the initiation layer of the open onion model. Results show that open source success largely depends on the quality associated with successful initiation of the project. Our findings also reveal that the most popular open source license is GPL and that license type has significant impact on project rank. The domain audience has negative impact on project rank and user interface has significantly negative impact on project’s domain audience. Open source project topics covered have a significant impact on the domain audience and a negative effect on the user interface. This research has also presented a conceptual framework of open source success tree.

Service design and inventory system — An object-oriented reusable software asset

Competition and the fast pace of technological evolution in today's global telecommunications industry are placing unique demands on the flexibility of operations support software systems. The industry must be capable of rapidly introducing new services, technologies, and organizational structures. Networks must be capable of being partitioned for various applications and administered based on complex ownership relationships among the various network components. User permissions must be readily adaptable to reflect various combinations of services, network partitions, and work functions. To meet the time constraints of the market, telecommunications providers require the ability to configure systems to meet their needs without relying on traditional software development intervals and external software development resources. Traditional software development methodologies generally do not provide the timeliness and flexibility required. The Service Design and Inventory (SDI) system — also known as the Attribute Design Database System (ADDS) — has achieved a high degree of reusability and customer-configurable adaptability through a unique application of object-oriented technology.

Small-team development in a competitive environment

The telecommunications industry is undergoing rapid and continuous change. To be successful in today's dynamic market, competitors must quickly identify and embrace new opportunities. Fortunately, companies have at their disposal enormous amounts of data and high-speed computers that can help them analyze opportunities and hasten their entry into new markets. Unfortunately, the software needed to support these efforts takes precious time to design and develop. Traditional software development methodologies might not suffice in such a fast-paced environment. Thus, alternatives are needed to shorten response time and provide greater flexibility to market-driven changes. This paper discusses AT&T's successes with a small-team approach to software development. Rather than maintaining separate functional organizations having well-defined roles and responsibilities, a single, closely knit team is established consisting of customers, systems engineers, and developers. The team's overarching goal is to help AT&T customers solve business problems as quickly as possible.