Overview of Open Source Tools for Agile Development

Author(s):  
Barbara Russo ◽  
Marco Scotto ◽  
Alberto Sillitti ◽  
Giancarlo Succi

Tools support is extremely important in Agile development. As described in the previous chapters, the Agile development is based on the identification and the subsequent reduction of activities that do not provide value to the customer and the ability to change the code without including new and undetected bugs in the code.

2022 ◽  
Author(s):  
Georges Labrèche ◽  
David Evans ◽  
Dominik Marszk ◽  
Tom Mladenov ◽  
Vasundhara Shiradhonkar ◽  
...  

Author(s):  
Sofiane Sahraoui

Open source software (OSS) development has been a trend parallel to that of agile software development, which is the highly iterative development model following conventional software engineering principles. Striking similarities exist between the two development processes as they seem to follow the same generic phases of software development. Both modes of development have less emphasis on planning and design and a more prominent role for implementation during the software engineering process. This chapter expounds on this connection by adopting an agile perspective on OSS development to emphasize the similarities and dissimilarities between the two models. An attempt is first made to show how OSS development fits into the generic agile development framework. Then, the chapter demonstrates how the development process of Mozilla and Apache as two of the most famous OSS projects can be recast within this framework. The similarity discussed and illustrated between agile and OSS development modes is rather limited to the mechanics of the development processes and do not include the philosophies and motivations behind development.


Author(s):  
Tom Butler ◽  
Joseph Feller ◽  
Andrew Pope ◽  
Ciaran Murphy

This chapter presents an action research-based case study of the development of pKADS (portable knowledge asset development system), an open source, desktop-based knowledge management (KM) tool, implemented in Java and targeted at government and nongovernment organizations. pKADS was a collaborative project involving Business Information Systems, University College Cork, Ireland and the United Nations Population Fund (UNFPA), and was funded by the government of Ireland. Development of the application took just three months, using an agile development approach and some reuse of existing open source code. The chapter discusses the background to the pKADS project and prior UNFPA KM efforts, the technical and conceptual architectures of the pKADS application, the roles played by open source components and open data standards, the rationale for releasing pKADS as open source software, and the subsequent results. Future research, in the form of developing open source, Intranet/Internet-based KM tools for the Government of Ireland—eGovernment Knowledge Platform (eGovKP) is also briefly discussed.


2014 ◽  
Vol 32 (3) ◽  
pp. 546-559 ◽  
Author(s):  
Alexandria Payne ◽  
John Curtis

Purpose – The purpose of this paper is to detail a Library open source software (OSS) development project resulting in the launch of StatBase, a statistical gathering and data visualization tool, so that organizations can adopt a locally managed alternative to costly data aggregation tools. Design/methodology/approach – This case study is based on a literature review, Agile development framework, and user experience modeling. The software solution features a Joomla framework with contributed modules and open source architecture. Findings – This case study demonstrates the creation and practical implementation of a scalable OSS platform for data management and analysis. Practical implications – Provides a frame of reference and methodology for libraries, both public and academic, seeking to implement a web-based resource to gather, organize, and interpret statistical metrics via a centralized, lightweight, open source architecture. Originality/value – This case study provides a detailed scope and step-by-step technology process description by which an organization can adopt or model the StatBase solution for business metrics.


Author(s):  
Falko Glöckler ◽  
James Macklin ◽  
David Shorthouse ◽  
Christian Bölling ◽  
Satpal Bilkhu ◽  
...  

The DINA Consortium (DINA = “DIgital information system for NAtural history data”, https://dina-project.net) is a framework for like-minded practitioners of natural history collections to collaborate on the development of distributed, open source software that empowers and sustains collections management. Target collections include zoology, botany, mycology, geology, paleontology, and living collections. The DINA software will also permit the compilation of biodiversity inventories and will robustly support both observation and molecular data. The DINA Consortium focuses on an open source software philosophy and on community-driven open development. Contributors share their development resources and expertise for the benefit of all participants. The DINA System is explicitly designed as a loosely coupled set of web-enabled modules. At its core, this modular ecosystem includes strict guidelines for the structure of Web application programming interfaces (APIs), which guarantees the interoperability of all components (https://github.com/DINA-Web). Important to the DINA philosophy is that users (e.g., collection managers, curators) be actively engaged in an agile development process. This ensures that the product is pleasing for everyday use, includes efficient yet flexible workflows, and implements best practices in specimen data capture and management. There are three options for developing a DINA module: create a new module compliant with the specifications (Fig. 1), modify an existing code-base to attain compliance (Fig. 2), or wrap a compliant API around existing code that cannot be or may not be modified (e.g., infeasible, dependencies on other systems, closed code) (Fig. 3). create a new module compliant with the specifications (Fig. 1), modify an existing code-base to attain compliance (Fig. 2), or wrap a compliant API around existing code that cannot be or may not be modified (e.g., infeasible, dependencies on other systems, closed code) (Fig. 3). All three of these scenarios have been applied in the modules recently developed: a module for molecular data (SeqDB), modules for multimedia, documents and agents data and a service module for printing labels and reports: The SeqDB collection management and molecular tracking system (Bilkhu et al. 2017) has evolved through two of these scenarios. Originally, the required architectural changes were going to be added into the codebase, but after some time, the development team recognised that the technical debt inherent in the project wasn’t worth the effort of modification and refactoring. Instead a new codebase was created bringing forward the best parts of the system oriented around the molecular data model for Sanger Sequencing and Next Generation Sequencing (NGS) workflows. In the case of the Multimedia and Document Store module and the Agents module, a brand new codebase was established whose technology choices were aligned with the DINA vision. These two modules have been created from fundamental use cases for collection management and digitization workflows and will continue to evolve as more modules come online and broaden their scope. The DINA Labels & Reporting module is a generic service for transforming data in arbitrary printable layouts based on customizable templates. In order to use the module in combination with data managed in collection management software Specify (http://specifysoftware.org) for printing labels of collection objects, we wrapped the Specify 7 API with a DINA-compliant API layer called the “DINA Specify Broker”. This allows for using the easy-to-use web-based template engine within the DINA Labels & Reports module without changing Specify’s codebase. In our presentation we will explain the DINA development philosophy and will outline benefits for different stakeholders who directly or indirectly use collections data and related research data in their daily workflows. We will also highlight opportunities for joining the DINA Consortium and how to best engage with members of DINA who share their expertise in natural science, biodiversity informatics and geoinformatics.


Author(s):  
A. F. Tappenden ◽  
T. Huynh ◽  
J. Miller ◽  
A. Geras ◽  
M. Smith

This article outlines a four-point strategy for the development of secure Web-based applications within an agile development framework and introduces strategies to mitigate security risks that are commonly present in Web-based applications. The proposed strategy includes the representation of security requirements as test cases supported by the open source tool FIT, the deployment of a highly testable architecture allowing for security testing of the application at all levels, the outlining of an extensive security testing strategy supported by the open source unit-testing framework HTTPUnit, and the introduction of the novel technique of security refactoring that transforms insecure working code into a functionally-equivalent secure code. Today, many Web-based applications are not secure, and limited literature exists concerning the use of agile methods within this domain. It is the intention of this article to further discussions and research regarding the use of an agile methodology for the development of secure Web-based applications.


Author(s):  
John Alexander Soraca Higuera ◽  
Alexander Bustamante Martínez ◽  
Giovanni López Castillo ◽  
Ernesto Galvis Lista ◽  
Luis Gómez Flórez

Resumen El artículo presenta el diseño y construcción de una infraestructura para el desarrollo ágil de soluciones de inteligencia de negocios, donde se escogieron prácticas de dos metodologías ágiles, entre las existentes con mayor renombre y con enfoques diferentes, como Programación Extrema (XP), enfocada en la forma de programar, y Scrum, enfocada en la forma de organizar el proyecto. Las prácticas seleccionadas se implementaron mediante herramientas de software libre compatibles con el entorno de desarrollo Microsoft SQL Server 2008 r2 en una máquina virtual. Con esta infraestructura los desarrolladores tienen a la mano las herramientas necesarias para crear e implementar soluciones de inteligencia de negocios. Palabras Clave: Inteligencia de Negocios, Metodologías Ágiles, Programación Extrema, Scrum.   Abstract The paper presents the design and construction of an infrastructure for agile development of business intelligence solutions, where two selected practices among existing agile methodologies, where two were selected Agile practices among the most renowned existing and different approaches, as Extreme Programming (XP), focused in the form of programming, and Scrum, focusing on how to organize the project. Selected practices were implemented through open source tools compatible with the development environment Microsoft SQL Server 2008 R2 in a virtual machine. With this infrastructure developers have at hand the necessary tools to create and deploy business intelligence solutions. Keywords: Business Intelligence, Agile Methodologies, Extreme Programming, Scrum


Author(s):  
Paolo Ciancarini ◽  
Marcello Missiroli ◽  
Francesco Poggi ◽  
Daniel Russo

2005 ◽  
Author(s):  
Kevin Gary ◽  
Brian Blake ◽  
Stephen Aylward ◽  
Julien Jomier ◽  
David Gobbi ◽  
...  

Open source technologies are increasing in popularity for software development. Many open source projects rely on skilled development teams whose members are distributed throughout the world. Often, agile development methods are employed by these teams, as the focus is on concurrent development and fast production over requirements management and quality assurance. The image-guided surgery toolkit (IGSTK) is an open source development project that relies on the collaboration of a skilled and distributed development team, yet addresses a domain that demands managing requirements as well as implementing a high degree of robustness and addressing safety concerns. Due to this unique cross-section of open source technology and the surgical domain, the IGSTK team has developed a set of best practices and requirements techniques to augment commonly applied agile methods. This paper presents the lessons we have learned as we have engaged in the software development process.


2015 ◽  
Vol 23 (2) ◽  
pp. 324-332 ◽  
Author(s):  
Aaron Neinstein ◽  
Jenise Wong ◽  
Howard Look ◽  
Brandon Arbiter ◽  
Kent Quirk ◽  
...  

Abstract Objective Develop a device-agnostic cloud platform to host diabetes device data and catalyze an ecosystem of software innovation for type 1 diabetes (T1D) management. Materials and Methods An interdisciplinary team decided to establish a nonprofit company, Tidepool, and build open-source software. Results Through a user-centered design process, the authors created a software platform, the Tidepool Platform, to upload and host T1D device data in an integrated, device-agnostic fashion, as well as an application (“app”), Blip, to visualize the data. Tidepool’s software utilizes the principles of modular components, modern web design including REST APIs and JavaScript, cloud computing, agile development methodology, and robust privacy and security. Discussion By consolidating the currently scattered and siloed T1D device data ecosystem into one open platform, Tidepool can improve access to the data and enable new possibilities and efficiencies in T1D clinical care and research. The Tidepool Platform decouples diabetes apps from diabetes devices, allowing software developers to build innovative apps without requiring them to design a unique back-end (e.g., database and security) or unique ways of ingesting device data. It allows people with T1D to choose to use any preferred app regardless of which device(s) they use. Conclusion The authors believe that the Tidepool Platform can solve two current problems in the T1D device landscape: 1) limited access to T1D device data and 2) poor interoperability of data from different devices. If proven effective, Tidepool’s open source, cloud model for health data interoperability is applicable to other healthcare use cases.


Sign in / Sign up

Export Citation Format

Share Document