One tool to rule them all? Integration or survival of the fittest

Slides:



Advertisements
Similar presentations
Software Configuration Management: Under the Hood of Two Leading Tools Presented by: Andrew Wheeler & Shane Marcus.
Advertisements

Visual Studio Online. What it Provides Visual Studio Online, based on the capabilities of Team Foundation Server with additional cloud services, is the.
Version Control What it is and why you want it. What is Version Control? A system that manages changes to documents, files, or any other stored information.
VisIt Software Engineering Infrastructure and Release Process LLNL-PRES Lawrence Livermore National Laboratory, P. O. Box 808, Livermore,
New Collaboration Technologies for Implementing Problem-based Learning Mark A. Serva Assistant Professor of MIS University of Delaware Institute for Transforming.
CS 501 : An Introduction to SCM & GForge An Introduction to SCM & GForge Lin Guo
Update on Version Control Systems: GitLab, SVN, Git, Trac, CERNforge
Andy Nicholls – Head of Consultancy DevelopR – formalising R Development.
Features and Functions of Information Systems. What are information systems?  Information systems consist of software, hardware and communication networks.
Improving Software Quality with Continuous Integration
Continuous Integration Demonstration. Agenda 1.Continuous Integration Basics 2.Live Demonstration 3.Bamboo Concepts 4.Advantages 5.Version 2.0 Features.
Shop 9000 Product Review 2007 Visual User Group Nov 21 st 2007.
CONTINUOUS INTEGRATION, DELIVERY & DEPLOYMENT ONE CLICK DELIVERY.
Project Proposal: Academic Job Market and Application Tracker Website Project designed by: Cengiz Gunay Client: Cengiz Gunay Audience: PhD candidates and.
Version control Using Git 1Version control, using Git.
1 Topics for this Lecture Software maintenance in general Source control systems (intro to svn)
© 2012 IBM Corporation Rational Insight | Back to Basis Series SCM introduction Chu Shu June 2012.
DevOps Jesse Pai Robert Monical 8/14/2015. Agile Software Development 8/14/2015© 2015 SGT Inc.2.
Bboogle: Updates and Experience Patricia Goldweic, Sr. Software Engineer, Northwestern University Brian Nielsen, Project Manager, Faculty Initiatives,
What is SMEcollaborate Primarily developed for Small and Medium Companies who wish to collaborate together. It is a:- A resource center for collaborating.
Introduction to Git and GitHub
Version control Using Git Version control, using Git1.
Priit Collaboration infrastructure.
GIT and JUnit Dr. Andrew Wallace PhD BEng(hons) EurIng
KMS Products By Justin Saunders. Overview This presentation will discuss the following: –A list of KMS products selected for review –The typical components.
Introduction to Version Control SE-2030 Dr. Rob Hasker 1 Based on material at and slides written.
Continuous Integration and Code Review: how IT can help Alex Lossent – IT/PES – Version Control Systems 29-Sep st Forum1.
The Role of Experience in Software Testing Practice Zahra Molaei Soheil Hedayatitezengi Comp 587 Prof. Lingard 1 of 21.
The Harvard ABCD Forge Project Management and Software Development Best Practices January 2007  Norton Allen
Software Development A Proposed Process and Methodology.
Optimal Pipeline Using Perforce, Jenkins & Puppet Nitin Pathak Works on
Mindcraft is a registered trademark of Mindcraft, Inc. October 26, 1998Copyright 1998 Mindcraft, Inc. A Strategy for Buying Directory Servers Bruce Weiner.
©2009 ifanos c&p / Hoffmann&Reif. All rights reserved for InWEnt Capacity Building International 20 September 2010 | | Slide: 1 The iDRM Management Platform.
RCE Platform Technology (RPT) Mark Arndt User Support.
Build and Deployment Process Understand NCI’s DevOps and continuous integration requirements Understand NCI’s build and distribution requirements.
The Claromentis Digital Workplace An Introduction
ATS code development workflow Group Name: TST WG Source: Mahdi Ben Alaya, TST WG vice chair, SENSINOV, Miguel.
ATS code development workflow Group Name: TST WG Source: Mahdi Ben Alaya, TST WG vice chair, SENSINOV, Meeting Date: TST #21 Document.
Who is Gregg? 1 Mile
Geoff Davis Software Development Leader Software Development at eWater.
ATS code development workflow Group Name: TST WG Source: Mahdi Ben Alaya, TST WG vice chair, SENSINOV, Miguel.
Virtual Lab Overview 5/21/2015 xxxxxxxxxx NWS/MDL/CIRA.
Software collaboration tools as a stack of services Borja Aparicio Cotarelo IT-PES-IS 2HEPiX Fall 2015 Workshop.
Test all the things! Improving code quality at the OU with Continuous Integration MoodleMoot Ireland UK 2016 Mark Johnson Tony Lin.
Building Enterprise Applications Using Visual Studio®
Build and Test system for FairRoot
Agenda:- DevOps Tools Chef Jenkins Puppet Apache Ant Apache Maven Logstash Docker New Relic Gradle Git.
TOP project – STATUS UPDATE & Workflow demo
Open-O Integration Project Introduction
Continuous Integration (CI)
Version Control with Subversion
HCM Connector for JIRA – Plugin for Atlassian Marketplace
External Web Services Quick Start Guide
Infrastructure Orchestration to Optimize Testing
Supervision Miniworkshop JCOP Workshop 2015
Trends like agile development and continuous integration speak to the modern enterprise’s need to build software hyper-efficiently Jenkins:  a highly.
Version control, using Git
One tool to rule them all? Integration or survival of the fittest
API Documentation Guidelines
Empirical Project Monitor and Results from 100 OSS Development Projects Masao Ohira Empirical Software Engineering Research Laboratory, Nara Institute.
Scrum Experience Group Team Foundation Server (TFS)
100 LEGACY SYSTEMS vs 30 AGILE DEVELOPERS
X in [Integration, Delivery, Deployment]
Automated Testing and Integration with CI Tool
Helping a friend out Guidelines for better software
VIRBank Kristina Naudžiūnaitė Rita Birgelytė
CI/CD Workflow and Event Pages
Market Trends. Extracted slides from a presentation given at CID by Wolf-Michael Mehl Amsterdam, May 22nd, 2014.
Bots and integrations.
WeBWork and Open Educational Resources (OER)
Presentation transcript:

One tool to rule them all? Integration or survival of the fittest Carina Haupt German Aerospace Center (DLR) Department Intelligent and Distributed Systems Berlin / Braunschweig / Cologne Research Software Engineering Conference 2017

Software Development @ DLR Some numbers > RSE Conference 2017 > Haupt, Carina • One tool to rule them all? Integration or survival of the fittest > 08.09.2017 Software Development @ DLR Some numbers Some numbers More than 8000 employees More than 1500 employees develop software More than 150 Mio EUR personnel costs per year for software development → DLR is one of the biggest „software houses“ in Germany Characteristics „Developer“ often do not have any training in software development Variety of used software technologies i.E. over 30 programming languages 2005 Umfrage < 100 gelernte Informatiker

Where we started Software Engineering Tools @ DLR > RSE Conference 2017 > Haupt, Carina • One tool to rule them all? Integration or survival of the fittest > 08.09.2017 Where we started Software Engineering Tools @ DLR Team Version Control System planning quality checks changes Build Run Test feedback Issue Tracker Integration-Server

The Naive Approach Survival of the fittest > RSE Conference 2017 > Haupt, Carina • One tool to rule them all? Integration or survival of the fittest > 08.09.2017 The Naive Approach Survival of the fittest CVS Find the best tool for each task

But wait…perhaps lets ask the users first! The study > RSE Conference 2017 > Haupt, Carina • One tool to rule them all? Integration or survival of the fittest > 08.09.2017 But wait…perhaps lets ask the users first! The study Which ressources do we have to access „users“? Brainstorming Survey Expert Interviews DLR SE-Workshops: Yearly meeting of SE interested employees DLR SE-Network: Each institute has one point of contact for all SE needs Personal network

What the users said Characterisation of development > RSE Conference 2017 > Haupt, Carina • One tool to rule them all? Integration or survival of the fittest > 08.09.2017 What the users said Characterisation of development Aimed project quality ~ 50 % basic ~ 30 % medium ~ 20 % high Team sizes Mainly one person projects Similar amount of small (2-6 person) and medium sized teams (6-20 person) Few big teams (> 20 person) Currently used tools Mainly SVN & Mantis Self hosted alternatives (Git, Jira) Additional tooling (mainly Jenkins for CI)

What the users said Requirements (extract) > RSE Conference 2017 > Haupt, Carina • One tool to rule them all? Integration or survival of the fittest > 08.09.2017 What the users said Requirements (extract) High level overview of project Different views for different roles Planning possibilities (roadmap, backlog, sprints) Version control system Code collaboration Merge support Issue tracking Documentation Automatization (Continuous Integration, Deployment) Integration of issues, documentation, code IDE integration Access control (external users) Easy and fast setup Easy to use

What the users said Our results > RSE Conference 2017 > Haupt, Carina • One tool to rule them all? Integration or survival of the fittest > 08.09.2017 What the users said Our results Requirements Easy to setup Easy to use Easy to learn Highly integrated tools To be covered functionality Source code repository Issue tracking Documentation Continous Integration Reports (for project head) Target group Projects aiming for basic or medium quality → High quality projects set up their own tools One person and small sized teams → Have no resources for overhead

What the users said Our results > RSE Conference 2017 > Haupt, Carina • One tool to rule them all? Integration or survival of the fittest > 08.09.2017 What the users said Our results What we learned „Easy“ and integration beats missing functionality If it is not easy to set up, people will not use it If it is not easy to use, projects will not keep using it Our decision → We go with a simple integrated software engineering tool suite The facts Multiple tools mean more setup work Powerful tools mean more to learn Integrated tools have less features

The New Approach One tool to rule them all > RSE Conference 2017 > Haupt, Carina • One tool to rule them all? Integration or survival of the fittest > 08.09.2017 The New Approach One tool to rule them all Source Code Repository Issue Tracker Documentation CI +

The Feedback What our test group said > RSE Conference 2017 > Haupt, Carina • One tool to rule them all? Integration or survival of the fittest > 08.09.2017 The Feedback What our test group said Testversion at facility „Simulation and Software Technology“ Stats (04.09.2017) 117 active users 48 GitLab groups 388 GitLab projects 266 mile stones 2438 issues 19892 comments 3354 builds Users Everybody for everything Start 2014 pilot -> 08.2016 EE version GitLab Stats (12.12.2016) 73 active users 32 GitLab groups 218 GitLab projects 164 mile stones 864 issues 5590 comments 815 builds   GitLab Stats (04.09.2017) 117 active users 48 GitLab groups 388 GitLab projects 266 mile stones 2438 issues 19892 comments 3354 builds Everybody Researcher Students PHDs IT Head of departments Everything Software projects Scripts Code snippets Configurations Papers Thesis / Project reports They love Groups Private area Snippets They don’t love Viewing/Access restrictions between groups (configuration / company rules)

Questions? If it is not easy, people will not use it -> they are scientists, not coders