Detecting Software Security Vulnerability during an Agile Development by Testing the Changes to the Security Posture of Software Systems

PurposeThe purpose of this study is to reflect upon the feasibility of agile methodologies, Scrum in particular, to supplement the procedural design and implementation of performance measurement systems (PMS).Design/methodology/approachThe study is an interventionist case study that applied agile methodologies in the PMS development. Researchers actively participated in the PMS development, e.g. researchers designed some of the performance measurement prototypes in order to facilitate the agile development.FindingsThe study outlines an agile approach suitable for PMS development. The paper answers the topical needs for adaptability and agility in management accounting, by applying agile methodologies into PMS development. PMS development does not take place only as a project or process that systematically progresses from the measure selection to measure implementation. Instead, as the requirements for the PMS change during the development project, management may reject some measures and new measures emerge as the understanding about changing situations increase. Agile methodologies are a methodological way to respond to the inevitable change and to enhance management accounting adaptability.Research limitations/implicationsThis study contributes to the PMS literature by proposing that agile development methodologies can advance organizational features that increase management accounting adaptability. As a result, the study proposes a new approach for PMS development to supplement existing ones. Agile methodologies are especially suitable for extending the PMS in new, yet relatively immature areas of performance measurement. The new approach applies Scrum principles in PMS development. By drawing from the theories of performance measurement (system) development and enabling PMS, the paper furthers academic understanding about agile development of accounting information systems.Practical implicationsCompanies can use the proposed approach in PMS development, particularly after the initial system implementation in redesigning the system. The approach may increase the PMS impact in organizations and prevent PMS implementation failures.Originality/valueThe paper identifies the potential of using agile methodologies to enhance PMS adaptability and provides preliminary evidence of the potential of such approach in supplementing processual PMS development frameworks.

The Agile development methodology is soaring in popularity in the business world. Companies are turning to Agile to develop products quickly and to achieve digital transformation of their organization. Because of this push, companies need employees who understand Agile. Therefore, higher education is obligated to provide an understanding of Agile to students as they enter the workplace. Providing Agile experience to students who are new to programming is difficult because they are so worried about the coding aspects of the assignment, they cannot take time to think about the methodology they are using. The coding crowds out the time needed to get an understanding of how Agile actually works. One remedy for this is to use a low or no-code development platform. With this type of platform students spend less time learning to create apps, freeing them to experience the rituals and roles of Agile. This study examines using the Agile methodology along with the Microsoft Power Apps platform to provide an Agile experience to students. Two course sections were surveyed to learn if students perceived that they acquired a better understanding of Agile and to learn their perceptions of a no-code platform experience. The students completed surveys to ascertain their comfort with the Agile methodology and whether the no-code environment increased their comfort level. The results showed students perceived the no-code platform increased their comfort with using the Agile methodology. The implication is that no-code platforms can be used broadly to help students to gain experience with Agile.

The Internet economy has altered the rules of software engineering. Traditional development methodologies are too cumbersome to meet the rapidly changing requirements and short product cycles demanded by business. To meet these changing requirements, software developers have developed agile software development methodologies (SDMs) utilizing iterative development, prototyping, and templates. This research project investigated agile SDM implementation using an online survey sent to practitioners worldwide. This survey data were used to identify factors related to agile SDM implementation. Factors that included training, management involvement, access to external resources, and corporate size were found to impact implementation of an agile software development methodology. Factors such as using models, having an implementation plan, collocating the development team, and developing software for Internet or intranet use did not impact the implementation of an agile software development methodology. Several of the factors that impact the implementation of an agile development methodology are under the control of management. Organizations considering the implementation of an agile methodology may wish to manipulate some of these factors to increase the opportunities for success of their methodology.

The emergence of software offshore outsourcing phenomena hits every country positively and one of the offshore client/vendor attractng factor is CMM certification. CMM is a well recognized and globally accepted standard in software development to process control, quality improvement, and measurement of software firm's capability. Therefore, Pakistani software firms (SMEs) are striving to achieve the CMM certifications to earn profit from offshore clients. In fact, CMM certification is not easy to adopt for all level of firms. Pakistan software industry is at its initial stage, so it is not recommendable to jump for CMM by software firms (SMEs) directly. The present research paper suggests that these software firms (SMEs) should go for adaptation of agile development methodology for excellent performance on the foot steps of CMM. In this way, software firms (SMEs) can leads toward CMM after agile maturity. The authors used the eXtreme Programming (XP) as an example that proves Agile Development Methodology can well fit the CMM framework and software development firms (SMEs) can achieve their objectives to participate in offshore outsourcing phenonmena.

The role of the Contract Data Requirements List [CDRL] in the DoD acquisition process is to provide the authoritative list of required artifacts for a given procurement. It forms an appendix to the acquisition contract, and includes delivery information and a schedule for each, typically mapped to milestone events such as the Preliminary Design Review [PDR] or the Critical Design Review [CDR] in the DoD Acquisition Waterfall Lifecycle. A number of CDRLs were proposed for the Joint Mission Planning Systems [JMPS] Framework, including a number of artifacts specific to the architecture and design of the application. Alignment with the DoD Acquisition Waterfall Lifecycle milestone events posed significant challenges to the program, given the contractor's proposed Agile development methodology. Many of these architectural and design documents carried a delivery-schedule expectation that placed them in conflict with the best practices and anticipated benefits of Agile, including the principle of “design only as much as is necessary to build features”. Using the Enterprise Architect tool, the contractor was able to produce a “living design” used daily by the development team, including architects, designers, developers, integrators, and testers. The tool provided capabilities that facilitated templates for various CDRLs, including the Systems Architecture Description [SAD], the Software Design Description [SDD], and the Interface Design Description [IDD], allowing on-demand generation of snapshots of the architecture and detailed design as it evolved, providing the appropriate level of documentation of the as-built system. The result better addressed the contractual intent of the CDRLs, to provide subsequent platform developers an accurate and up-to-date understanding of the architecture and design of the JMPS Framework, while better preserving the integrity of the development of the Enterprise Architecture within the selected Zachman Framework, and in the context of the contractor's Agile methodology.

The quality of the software is greatly determined by the testing phase, which involves various test cases that can be conducted through manual testing and automation testing. Manual testing is performed manually without using automation scripts, whereas automation testing is conducted using automation scripts. ABC is a company that operates globally in the field of access control, with the Card Printer being one of the menus used in access control. In the development process of this software, both manual and automation testing phases are carried out. The automation testing process employs the Selenium tool, which has proven to be time-consuming and poses challenges when running numerous test cases. This research aims to develop automation testing using Playwright to address the long execution time issue encountered with Selenium. The research utilizes the Card Printer project in the development of automation testing and adopts the Agile methodology. The result of developing automation testing using Playwright was successfully applied to 12 test cases. Additionally, the time analysis between Playwright and Selenium showed that Playwright has a total execution time of 4.9 minutes, which is faster compared to Selenium's total execution time of 8.3 minutes. With faster execution times, Playwright can be considered a tool in the development of automation testing.

Unified modelling language (UML) 2.0 introduced in 2002 has been developing and influencing object-oriented software engineering and has become a standard and reference for information system analysis and design modelling. There are many concepts and theories to model the information system or software application with UML 2.0, which can make ambiguities and inconsistencies for a novice to learn to how to model the system with UML especially with UML 2.0. This article will discuss how to model the simple software application by using some of the diagrams of UML 2.0 and not by using the whole diagrams as suggested by agile methodology. Agile methodology is considered as convenient for novices because it can deliver the information technology environment to the end-user quickly and adaptively with minimal documentation. It also has the ability to deliver best performance software application according to the customer's needs. Agile methodology will make simple model with simple documentation, simple team and simple tools.

Software Development Life Cycle models are used as the basis to design software applications. In these models, there exists some tribulations and to overcome these defects, agile models are presented. The mature software applications of agile development utilize both iterative and incremental style. It can be viewed as a response against conventional procedural activity. It is viewed not as to meet the volatility and varying situations but as the modern business ethics for software development. By examining and exploring the agile models, it has been found that efficiency of agile models can be improved. This research investigates the agile frameworks (DSDM and LSD) in terms of testing. It also examines that the effectiveness of dynamic systems development model (DSDM) from testing perspective. The results show the performance of DSDM agile framework and the estimated efficiency of this framework.

Software industry is a growing sector in economy and in the present financial crisis, software firms are facing problems in providing necessary support for research and development activities. The objective of this paper is to find alternatives to the use of IT (information technology) solution of software firm development. Agile development methodologies are very promising in the software industry. Agile development techniques are such a way of developing environment such that it is very practical and viable in understanding the flow of business environment changes constantly. Agile development processes optimize the opportunity provided by cloud computing by doing software releases iteratively and getting user feedback more frequently. The research methodology depends on Cloud Computing as an alternative to IT provision, management and security. It also took into account the best practices for Cloud Computing usage within software firms and software developers experience in IT. The strategy includes five stages, with emphasis on the evaluation of data and processes/functions/applications from several major software firms based on some key criteria, while creating a correspondence between these aspects and the models/services/applications that exist on the Cloud market. The outcome of using Cloud solutions in software firms by improving knowledge is impressive.

A Literature Review on Agile Methodologies Quality, eXtreme Programming and SCRUM

The rapid adoption of DevOps practices has transformed the software development landscape by emphasizing continuous integration, continuous delivery (CI/CD), and agile methodologies. However, this rapid pace of development often introduces significant security challenges, as traditional security testing methods struggle to keep up with the accelerated release cycles. To address these challenges, the integration of Artificial Intelligence (AI) and Machine Learning (ML) into automated security testing has emerged as a promising solution. This paper explores the use of AI and ML to enhance automated security testing within DevOps environments, offering a comprehensive approach to identifying, predicting, and mitigating security vulnerabilities in real time. Automated security testing leverages AI and ML algorithms to analyze code, detect anomalies, and predict potential security threats. These technologies enable the continuous monitoring of codebases, allowing for the early identification of vulnerabilities before they are exploited. By incorporating AI-driven security testing into the CI/CD pipeline, organizations can ensure that security is not an afterthought but a continuous process integrated into every stage of the software development lifecycle. AI and ML models can be trained to recognize patterns associated with security risks, such as code injection, unauthorized access, and data leakage. These models continuously learn from new data, improving their accuracy over time and adapting to evolving threats. The dynamic nature of AI-driven security testing makes it particularly suited for DevOps environments, where frequent code changes and updates can introduce new vulnerabilities. Moreover, AI and ML can assist in automating complex tasks, such as threat modeling, risk assessment, and the prioritization of security issues, enabling security teams to focus on higher-order tasks that require human expertise.

This paper describes an agile development methodology which combines agile principles with organizational patterns and adapts them to build embedded real-time systems focusing on the system's constraints. The hardware/software partitioning and platform-based design are used in the proposed methodology to support the embedded system designer meet the system's constraints in an iterative and incremental way and to reduce substantially the design time and cost of the product. To discuss the strengths and weakness of this methodology, a case study involving a pulse oximeter is also presented

From the perspective of the main goal, the real use of agile project methodology was analyzed, and then the levels of knowledge and use of the mentioned methodology were evaluated. Areas for potential improvement were identified and proposals for measures were created to increase the efficiency of future project implementation. Most companies today focus on delivering quality and gaining customer satisfaction and in order to accomplish this, the challenge lies in choosing between traditional development methodologies and agile development methodologies. However, both these approaches have positives and negatives, making the right choice plays a crucial role while starting a new project.

In this paper, an application of Agile Devel-opment Methodologies (ADM) to university project ori-ented courses is presented. A multidisciplinary student team applies Waterfall and Agile (Scrum) project man-agement strategies over a period of 10 months to a pro-ject based capstone course. The study primarily focuses on evaluating the two methodologies across five catego-ries – student confidence, student awareness, stakeholder confidence, stakeholder awareness, and project success. Results suggest that overall Agile can be more effective than Waterfall. Due to practices such as daily standups and frequent sprint planning, the student team and stake-holders found they were not only able to stay up to date with the progress of the overall project but also found there was enough time allocated to address the ever-changing nature of requirements brought on by the pro-ject. The lessons learned and recommendations provided in this study are generalized such that they can be applied in other project based courses as well.

Agile software development is often seen as a product development strategy to design and develop new software products. One of the biggest mistakes that most software development teams make is to consider software re-engineering as a part of their maintenance activities rather than an integral part of the product development lifecycle, and therefore, they don’t consider a systematic development approach for re-engineering activities. Even the most popular agile development frameworks such as Scrum, Kanban, and SAFe don’t have any specific guidelines for re-engineering projects. It is also commonly observed that most of the teams that used agile development methodologies faced several challenges and accumulated a huge technical debt due to their short-focused goals and lack of systematic re-engineering plans (Raza and Majeed in Int J Sci Eng Res 3(8):1–5 (2012) [1]). This paper describes the importance of continuous software re-engineering and the usage of agile methodologies to effectively achieve the re-engineering goals.