How Much Undocumented Knowledge is there in Agile Software Development?: Case Study on Industrial Project Using Issue Tracking System and Version Control System

2017 ◽  
Author(s):  
Shinobu Saito ◽  
Yukako Iimura ◽  
Aaron K. Massey ◽  
Annie I. Anton
Keyword(s):  
Control System ◽  
Software Development ◽  
Tracking System ◽  
Agile Software Development ◽  
Version Control ◽  
Industrial Project ◽  
Version Control System ◽  
Agile Software ◽  
Issue Tracking System

scholarly journals Software Upgradation Model Based on Agile Methodology

2017 ◽  
Vol 10 (2) ◽  
pp. 352-358
Author(s):  
Manvender Rathore ◽  
Deepa Jose
Keyword(s):  
Control System ◽  
Software Development ◽  
Vital Role ◽  
Interdisciplinary Teams ◽  
Version Control ◽  
Agile Methodology ◽  
Model Based ◽  
Proposed Model ◽  
Version Control System ◽  
Agile Software

Agile software development work on twelve principle for software development which implies requirements and solutions evolved through the combined teamwork of disciplined and interdisciplinary teams. The objective of this paper is to connect agile methodology with Version Control System for more efficient and effective utilization of resources. In this proposed model based on agile methodology, the Version Control System plays a vital role to make work done faster as compared to SCRUM. This paper compares various existing agile methodologies. The efficiency of the proposed model is proved through comparative analysis with existing agile methods and using ANOVA mathematical model. Bitbucket as Version Control System is used as web based hosting service and the proposed model is compared by maintaining similar sprints in SCRUM and VSprint model. VCS and previous SRS documents are the important components of this proposed model which helps in increasing the work speed at different phases of software development which the existing models does not consider.

Git4Voc: Collaborative Vocabulary Development Based on Git

2016 ◽  
Vol 10 (02) ◽  
pp. 167-191 ◽  
Author(s):  
Lavdim Halilaj ◽  
Irlán Grangel-González ◽  
Gökhan Coskun ◽  
Steffen Lohmann ◽  
Sören Auer
Keyword(s):  
Control System ◽  
Data Integration ◽  
Software Development ◽  
Domain Knowledge ◽  
Vocabulary Development ◽  
Version Control ◽  
Version Control System

Collaborative vocabulary development in the context of data integration is the process of finding consensus between experts with different backgrounds, system understanding and domain knowledge. The complexity of this process increases with the number of people involved, the variety of the systems to be integrated and the dynamics of their domain. In this paper, we advocate that the usage of a powerful version control system is one of the keys to address this problem. Driven by this idea and the success of the version control system Git in the context of software development, we investigate the applicability of Git for collaborative vocabulary development. Even though vocabulary development and software development have much more similarities than differences, there are still important challenges. These need to be considered in the development of a successful versioning and collaboration system for vocabulary development. Therefore, this paper starts by presenting the challenges we are faced with during the collaborative creation of vocabularies and discusses its distinction to software development. Drawing from these findings, we present Git4Voc which comprises guidelines on how Git can be adopted to vocabulary development. Finally, we demonstrate how Git hooks can be implemented to go beyond the plain functionality of Git by realizing vocabulary-specific features like syntactic validation and semantic diffs.

Agile Software Development

2012 ◽  
pp. 1-15
Author(s):  
Torstein Nicolaysen ◽  
Richard Sassoon ◽  
Maria B. Line ◽  
Martin Gilje Jaatun
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Implementation Team ◽  
Agile Methodologies ◽  
Development Organizations ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Agile Software

In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.

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.

Teaching Agile Software Development: A Case Study

2011 ◽  
Vol 54 (2) ◽  
pp. 273-278 ◽  
Author(s):  
Vladan Devedžić ◽  
Saša R Milenković
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Software
Sign in / Sign up

Export Citation Format

Share Document