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

Slides:



Advertisements
Similar presentations
Visual Studio Online. What it Provides Visual Studio Online, based on the capabilities of Team Foundation Server with additional cloud services, is the.
Advertisements

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.
Update on Version Control Systems: GitLab, SVN, Git, Trac, CERNforge
Andy Nicholls – Head of Consultancy DevelopR – formalising R Development.
Continuous Integration Demonstration. Agenda 1.Continuous Integration Basics 2.Live Demonstration 3.Bamboo Concepts 4.Advantages 5.Version 2.0 Features.
CWG2 Tools, Guidelines and Procedures 16 December 2014 ALICE O 2 Asian Workshop
Version control Using Git 1Version control, using Git.
Achieving Agility with WSO2 App Factory S. Uthaiyashankar Director, Cloud Solutions WSO2 Inc. Dimuthu Leelarathne Software Architect WSO2 Inc.
Tools and software process for the FLP prototype B. von Haller 9. June 2015 CERN.
DevOps Jesse Pai Robert Monical 8/14/2015. Agile Software Development 8/14/2015© 2015 SGT Inc.2.
Copyright BSPIN Agile Practices Benchmarking Case Study by Mazataz – Tesco.
Agile and XP Development Dan Fleck 2008 Dan Fleck 2008.
Talent Development Suite Geared up for the „War for Talents“
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.
KNOVADA – CUSTOMERSOFT SOLUTIONS Maximizing The Business Value Of Your Employees.
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.
Perforce Software Version Everything.. Visual Studio Industry Partner Perforce Software NEXT STEPS Contact us at: Perforce products.
U.S. Department of Agriculture eGovernment Program eGovernment Working Group Meeting February 11, 2004.
Optimal Pipeline Using Perforce, Jenkins & Puppet Nitin Pathak Works on
Open GSBPM compliant data processing system in Statistics Estonia (VAIS) 2011 MSIS Conference Maia Ennok Head of Data Warehouse Service Data Processing.
©2009 ifanos c&p / Hoffmann&Reif. All rights reserved for InWEnt Capacity Building International 20 September 2010 | | Slide: 1 The iDRM Management Platform.
Software Engineering Overview DTI International Technology Service-Global Watch Mission “Mission to CERN in Distributed IT Applications” June 2004.
RCE Platform Technology (RPT) Mark Arndt User Support.
(1) Introduction to Continuous Integration Philip Johnson Collaborative Software Development Laboratory Information and Computer Sciences University of.
Personal Training Assistant – Sprint#1 Group Gamma.
Build and Deployment Process Understand NCI’s DevOps and continuous integration requirements Understand NCI’s build and distribution requirements.
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.
WP2 : Collaborative tools Leandro Fernandez ICS Division November 26, 2014.
Software collaboration tools as a stack of services Borja Aparicio Cotarelo IT-PES-IS 2HEPiX Fall 2015 Workshop.
ERPsim Overview EIN 6133 Enterprise Engineering Fall, 2015.
DECTRIS Ltd Baden-Daettwil Switzerland Continuous Integration and Automatic Testing for the FLUKA release using Jenkins (and Docker)
(Atlassian) Software Development tools used in BE/CO Jira, Bamboo, Fisheye+Crucible, Clover
Test all the things! Improving code quality at the OU with Continuous Integration MoodleMoot Ireland UK 2016 Mark Johnson Tony Lin.
HPE ALM Octane.
Build and Test system for FairRoot
TOP project – STATUS UPDATE & Workflow demo
Parts Management Plan Builder 26 July 07
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
L – Modeling and Simulating Social Systems with MATLAB
L – Modeling and Simulating Social Systems with MATLAB
Enterprise Quality Roadmap
Software Documentation
Simulation use cases for T2 in ALICE
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
One tool to rule them all? Integration or survival of the fittest
Helping a friend out Guidelines for better software
GitHub A Tool for software collaboration James Skon
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

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 Version Control System Team planning quality checks changes Build Run Test feedback Integration-Server Issue Tracker

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“? Survey Expert Interviews Brainstorming 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 Version control system Code collaboration Merge support Issue tracking Documentation IDE integration Access control (external users) Easy and fast setup Easy to use Planning possibilities (roadmap, backlog, sprints) Automatization (Continuous Integration, Deployment) Integration of issues, documentation, code

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 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

Questions?