Application of Principles From the Scrum Agile Method to a Prototype Vehicle Control Development Cycle

2014 ◽  
Author(s):  
Derek Bonderczuk ◽  
Patrick Currier ◽  
Matthew Nelson
Keyword(s):  
Control System ◽  
Software Development ◽  
Vehicle Control ◽  
Agile Method ◽  
Staffing Levels ◽  
Development Cycle ◽  
Experimental Vehicle ◽  
Agile Software ◽  
Development Methods

Traditional methods for organization of controls development tend not to facilitate the speedy completion of complex tasks such as development of an experimental vehicle control system, particularly when staffing levels are low. This paper proposes the use of Scrum Agile software development methods to streamline the control development cycle for a prototype vehicle. The EcoCAR 2 competition vehicle at Embry-Riddle Aeronautical University is used as a case study for this implementation. Specific protocols and workflows for development are outlined and examples of implementation on the EcoCAR 2 vehicle are provided. Implementation results indicate that the method allowed for an aggressive development schedule for the vehicle software without compromising reliability, maintainability, or upgradeability.

Fixed Priced Projects in Agile

2016 ◽  
pp. 222-236
Author(s):  
Anuradha Chaminda Gajanayaka
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Development Model ◽  
Software Development Model ◽  
Responding To Change ◽  
The One ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

Agile software development has established as a reliable alternative to waterfall software development model. Unfortunately the use of agile software development has been limited to time based contracts and not for time limited contracts. The main reason for this limitation is the “Agile manifesto” itself. The forth value of the manifesto states that agile believers find more value in “Responding to change over following a plan”. This is the one of the main reasons why agile software development methods are not preferred for a fixed priced contract or time limited contract. The following case study provides an example on how the agile software development can be used for fixed priced software development contracts even when operating in offshore context. The agile software development concepts were used throughout to plan, execute, monitor, report, etc. for the project documented in this case study.

Extending Security in Agile Software Development Methods

2007 ◽  
pp. 143-159 ◽  
Author(s):  
M. Siponen ◽  
R. Baskerville ◽  
R. Kuivalainen
Keyword(s):  
Information Systems ◽  
Software Development ◽  
Agile Software Development ◽  
Agile Methods ◽  
Agile Method ◽  
Management Standards ◽  
Secure Information ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

Software developers can use agile software development methods to build secure information systems. Current agile methods have few (if any) explicit security fea-tures. While several discrete security methods (such as checklists and management standards) can supplement agile methods, few of these integrate seamlessly into other software development methods. Because of the severe constraints imposed by agile methods, these discrete security techniques integrate very poorly into agile approaches. This chapter demonstrates how the security features can be integrated into an agile method called feature driven development.

Extending Security in Agile Software Development Methods

2008 ◽  
pp. 845-858
Author(s):  
M. Siponen ◽  
R. Baskerville ◽  
T. Kuivalainen
Keyword(s):  
Information Systems ◽  
Software Development ◽  
Agile Software Development ◽  
Agile Methods ◽  
Agile Method ◽  
Management Standards ◽  
Secure Information ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

Software developers can use agile software development methods to build secure information systems. Current agile methods have few (if any) explicit security fea-tures. While several discrete security methods (such as checklists and management standards) can supplement agile methods, few of these integrate seamlessly into other software development methods. Because of the severe constraints imposed by agile methods, these discrete security techniques integrate very poorly into agile approaches. This chapter demonstrates how the security features can be integrated into an agile method called feature driven development.

An Analysis of Process Characteristics for Developing Scientific Software

2011 ◽  
Vol 23 (4) ◽  
pp. 64-79 ◽  
Author(s):  
Diane Kelly
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Professional Training ◽  
Scientific Software ◽  
Development Environment ◽  
Engineering Development ◽  
Development Processes ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

The development of scientific software is usually carried out by a scientist who has little professional training as a software developer. Concerns exist that such development produces low-quality products, leading to low-quality science. These concerns have led to recommendations and the imposition of software engineering development processes and standards on the scientists. This paper utilizes different frameworks to investigate and map characteristics of the scientific software development environment to the assumptions made in plan-driven software development methods and agile software development methods. This mapping exposes a mismatch between the needs and goals of scientific software development and the assumptions and goals of well-known software engineering development processes.

scholarly journals A review on Continuous Integration, Delivery and Deployment using Jenkins

2021 ◽  
Vol 23 (06) ◽  
pp. 919-922
Author(s):  
Arpita S.K ◽  
◽  
Amrathesh Amrathesh ◽  
Dr. Govinda Raju M ◽  
◽  
...  
Keyword(s):  
Software Development ◽  
Software Tools ◽  
Integration Process ◽  
Continuous Integration ◽  
Software Deployment ◽  
Development Cycle ◽  
Continuous Delivery ◽  
Standard Practices ◽  
Development Methods ◽  
The Given

Continuous Integration (CI) is the technique of integrating small changes made to the code more often rather than waiting till the end of the development cycle for integration. The software practice wherein the software deployment can be done anytime to the market is called Continuous Delivery (CD). With continuous integration and continuous delivery, the problem of taking time to find and resolve the bug can be reduced to a large extent. As the time to find the bugs and fix them gets reduced, many releases adhering to the given timeline can be made by an organization. Various software tools have been developed for the continuous integration process which includes Jenkins, Bitbucket, TeamCity. In this paper, a review on the standard practices, approaches, challenges faced while using the continuous integration/delivery in the software development, methods of solving them, and using Jenkins for the implantation of continuous integration/delivery is done.

scholarly journals DevOPS Now and Then

2020 ◽  
Author(s):  
Raju Singh
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Continuous Improvement ◽  
Building Blocks ◽  
Extended Version ◽  
Agile Method ◽  
Development Cycle ◽  
Development Life Cycle ◽  
Continuous Delivery ◽  
Software Development Life Cycle

DevOps is an emerging practice to be followed in the Software Development life cycle. The name DevOps indicates that it’s an integration of the Development and Operation team. It is followed to integrate the various stages of the development cycle. DevOps is an extended version of the existing Agile method. DevOps aims at continuous integration, Continuous Delivery, Continuous Improvement, faster feedback and security. This paper reviews the building blocks of DevOps, challenges in adopting DevOps, Models to improve DevOps practices and Future works on DevOps

Sign in / Sign up

Export Citation Format

Share Document