2 Ordinary Differential Equations

Total Page:16

File Type:pdf, Size:1020Kb

2 Ordinary Differential Equations Technical University of Munich Department of Informatics Bachelor’s Thesis in Informatics Robust Development with Continuous Integration in TIDOWA Robuste Entwicklung mit Kontinuierlicher Integration in TIDOWA Author: Hoang-Trieu Tong Supervisor: Prof. Dr. rer. nat. Martin Schulz Advisor: Dr. rer. nat. Martin Schreiber Submission Date: 15.04.2021 I confirm that this bachelor’s thesis is my own work and I have documented all sources and material used. Place, Date Hoang-Trieu Tong Abstract As software projects grow, the respective source code will become more complex and the number of developers that work simultaneously on the project will increase. Unfortunately, the same applies for the probability of errors occurring during the period of developing such a software. Thus, some countermeasures are required to minimize the probability of major errors and to detect software bugs in the project. Continuous integration (CI) and CI environments represent possible countermeasures. This thesis reports on CI and various implementations of CI applied to TIDOWA, a recently developed software program that is able to compute the approximate solution of initial value problems by means of time integration methods. In addition, a test framework is developed and implemented to verify the validity of TIDOWA’s implementations especially the validity regarding the convergence behavior of the implemented time integration methods. The CI environment in combination with the test framework represents a step towards creating a software development environment that allows better cooperation of developers and improves the quality of the software. i Contents Contents 1 Motivation 1 2 Ordinary Differential Equations 3 2.1 Introduction . 3 2.2 Initial Value Problems . 4 2.3 Examples . 7 2.3.1 System of Linear Oscillating Equations . 7 2.3.2 Model of the Circadian Clock . 7 2.4 Numerical Solution of IVPs . 8 2.4.1 Introduction . 8 2.4.2 Explicit Euler Method . 9 2.4.3 Heun Method . 9 2.4.4 Runge-Kutta Method of Order 4 . 10 2.4.5 Implicit Time Integration Method . 12 2.5 Concept of Convergence . 12 3 TIDOWA 15 4 Continuous Integration (CI) 17 4.1 Definition and Examination of CI . 17 4.2 Common Practices . 19 4.3 Overview of CI Implementations . 20 5 CI-Oriented Changes and Extensions in TIDOWA 27 5.1 Preliminaries . 27 5.2 Restructuring of TIDOWA . 27 5.3 Integration of Python Setuptools and Virtual Environment . 30 5.4 Test Framework . 31 5.5 Further Extensions . 31 ii 6 Continuous Integration in TIDOWA 32 6.1 Introduction . 32 6.2 Implementation of the Test Framework . 32 6.2.1 System Design: Essential Requirements and Design of the Test Framework 32 6.2.2 Implementation: Introduction . 38 6.2.3 Implementation: Preliminaries . 40 6.2.4 Implementation: Modules - The Core Four . 42 6.2.5 Implementation: Connectors - Data Transfer between Modules . 47 6.2.6 Implementation: Administrative Structure - Unification into One Program 49 6.3 Integration of CI Environment . 54 6.3.1 System Design: Selection and Essential Requirements of the CI Environment 54 6.3.2 Implementation: Preliminaries . 55 6.3.3 Implementation: Integration of Test Framework . 56 7 Case Study: Usage of Test Framework 59 7.1 Structure of Tests . 59 7.2 Interaction with Tests . 60 7.3 Test Execution in Local Environment . 60 8 Conclusion and Outlook 61 Bibliography 63 iii 1 Motivation Ordinary differential equations are often used in the field of physics, biology, medicine or even warfare to model complex correlations, e.g. the behavior of a pendulum or the ratio of two species over a certain period of time. What is more interesting than creating a model to certain problems is to find a way to solve them and thus predict events that may occur. One possible approach with which one may solve ordinary differential equations is the numeric approach that applies numerical methods onto these equations to derive an approximation of the solution. As some of the methods were developed by mathematicians who lived back then before the digital age, it is possible to use these procedures manually without any computational assistance. However, using this approach for models and problems that contain hundreds or thousands of equations takes a fair amount of time. Fortunately, with the digital revolution it is possible to hand such tasks over to computers with suitable programs. A program that is capable of this is TIDOWA. TIDOWA, developed at the Technical University Munich (TUM), provides implementations of different numerical methods that can be used to approximate the solution of ordinary differential equations. The software already offers a variety of numerical methods, nonetheless the project still is in its early stages. As the program grows and new functionalities are added, it is essential that the parts implemented so far are correct. This is important as future extensions might be based on old functionality. If older parts are erroneous, future developers will encounter lots of trouble and require much effort to fix parts of the software for which they are not responsible for and with which they are not familiar with. As this should not be the fate of every successive developer, it is time to take TIDOWA to the next level and introduce an environment that continuously tests the software and detects incorrect implementations, thus allowing developers to fix them in a timely manner. This thesis reports on the introduction of an environment to TIDOWA that continuously reviews the state of the software to detect possible errors as early as possible. In this context, it also covers the implementation of a test framework for TIDOWA that allows developers to 1 1 Motivation verify certain attributes concerning the behavior of implemented numerical methods. Chapter 2 discusses the fundamental concepts of ordinary differential equations that are used in TIDOWA. It introduces the theory and terminology necessary to further develop the software. Chapter 3 summarizes the history and the current state of the program. It also depicts the way how TIDOWA works and the interaction of the individual modules and stages within the software. Chapter 4 examines the subject of continuous integration from a theoretical standpoint. Additionally the chapter presents and compares various existing implementations of continu- ous integration environments. Chapter 5 presents the changes that were introduced to the software to integrate it into a continuous integration environment and to simplify its development for future developers. Chapter 6 discusses the two components that were newly introduced with the work of this thesis, them being the continuous integration environment and the test framework. First, the theory behind both is examined, which includes the selection process of the continuous integration environment and the design of the test framework. Afterwards, the details con- cerning both implementations are described. Chapter 7 describes the usage of the test framework. The chapter displays how tests are structured, added, removed and further executed inside a local environment. 2 2 Ordinary Differential Equations This chapter discusses the fundamentals regarding ordinary differential equations (ODEs), initial value problems (IVPs), time integration (TI) methods and convergence. It briefly introduces important concepts and terms that are included in TIDOWA. The following explanations and descriptions in Chapter 2.1 are based on [1, 2, 3, 4]. 2.1 Introduction Ordinary differential equations (ODEs) are equations that connect: • y(t), an unknown function with t being a variable, often used to identify the varying aspect time and • derivatives of this unknown function that are displayed with e.g. y0(t), y0, y(1)(t) or y(1) for the first derivative of y(t). In this context, y is referred to as dependent variable and t as independent variable. There are two important terms regarding ODEs: order and degree. The order of an ODE is equal to the “order of the highest derivative that appears in the”[1] ODE. Furthermore, the degree of an ODE is identical to the exponent of the highest derivative. If we consider the following exemplary ODE, it has an order of 4 and a degree of 1. y0(t)6 + 5y00(t)2 − 3y000(t)5 − 2y0000(t) = 0 One way of presenting ODEs is the so called standard form or normal form of the ODE. The standard form or normal form of a general ODE of order n is as follows: y(n)(t) = f(t, y(t), y(2)(t), ..., y(n−1)(t)) where f depicts a given functional relationship of y and t. The function s(t) is a solution of the ODE, defined in the interval I ⊆ R, if the follow- ing conditions apply: 3 2 Ordinary Differential Equations • the function s(t) is differentiable in I • functional identity: If y(t) and its derivatives y(i)(t) can be replaced by s(t) and its derivatives s(i)(t), with ∀t ∈ I, so that the equation is still satisfied, it is called functional identity We consider the following ODE as an example: 0 + y (t) = 4y(t) t ∈ R The solution of this example is the function s(t) = e4t. When y(t) and y0(t) are replaced with s(t) and s0(t) = 4e4t, the equation is still satisfied with: 4e4t = 4e4t. Thus, the functional + identity is fulfilled. In addition, s(t) is differentiable in R . It should be noted that in general an ODE has not only one but infinite solutions. The whole set of solutions is referred to as general solution or complete solution. In general we deal with systems of ODEs that consist of multiple ordinary differential equa- tions rather than individual equations. Examples for such systems are examined in Chapter 2.3. For the sake of completeness it should be mentioned that other types of differential equations such as partial differential equations exist as well.
Recommended publications
  • Continuous Integration
    Continuous Integration Mark C. Miller Lawrence Livermore National Laboratory Software Productivity Track, ATPESC 2020 See slide 2 for license details exascaleproject.org License, Citation and Acknowledgements License and Citation • This work is licensed under a Creative Commons Attribution 4.0 International License (CC BY 4.0). • The requested citation the overall tutorial is: David E. Bernholdt, Anshu Dubey, Mark C. Miller, Katherine M. Riley, and James M. Willenbring, Software Productivity Track, in Argonne Training Program for Extreme Scale Computing (ATPESC), August 2020, online. DOI: 10.6084/m9.figshare.12719834 • Individual modules may be cited as Speaker, Module Title, in Software Productivity Track… Acknowledgements • Additional contributors include: Patricia Grubel, Rinku Gupta, Mike Heroux, Alicia Klinvex, Jared O’Neal, David Rogers, Deborah Stevens • This work was supported by the U.S. Department of Energy Office of Science, Office of Advanced Scientific Computing Research (ASCR), and by the Exascale Computing Project (17-SC-20-SC), a collaborative effort of the U.S. Department of Energy Office of Science and the National Nuclear Security Administration. • This work was performed in part at the Argonne National Laboratory, which is managed by UChicago Argonne, LLC for the U.S. Department of Energy under Contract No. DE-AC02-06CH11357. • This work was performed in part at the Oak Ridge National Laboratory, which is managed by UT-Battelle, LLC for the U.S. Department of Energy under Contract No. DE-AC05-00OR22725. • This work was performed in part at the Lawrence Livermore National Laboratory, which is managed by Lawrence Livermore National Security, LLC for the U.S. Department of Energy under Contract No.
    [Show full text]
  • Seisio: a Fast, Efficient Geophysical Data Architecture for the Julia
    1 SeisIO: a fast, efficient geophysical data architecture for 2 the Julia language 1∗ 2 2 2 3 Joshua P. Jones , Kurama Okubo , Tim Clements , and Marine A. Denolle 1 4 4509 NE Sumner St., Portland, OR, USA 2 5 Department of Earth and Planetary Sciences, Harvard University, MA, USA ∗ 6 Corresponding author: Joshua P. Jones ([email protected]) 1 7 Abstract 8 SeisIO for the Julia language is a new geophysical data framework that combines the intuitive 9 syntax of a high-level language with performance comparable to FORTRAN or C. Benchmark 10 comparisons with recent versions of popular programs for seismic data download and analysis 11 demonstrate significant improvements in file read speed and orders-of-magnitude improvements 12 in memory overhead. Because the Julia language natively supports parallel computing with an 13 intuitive syntax, we benchmark test parallel download and processing of multi-week segments of 14 contiguous data from two sets of 10 broadband seismic stations, and find that SeisIO outperforms 15 two popular Python-based tools for data downloads. The current capabilities of SeisIO include file 16 read support for several geophysical data formats, online data access using FDSN web services, 17 IRIS web services, and SeisComP SeedLink, with optimized versions of several common data 18 processing operations. Tutorial notebooks and extensive documentation are available to improve 19 the user experience (UX). As an accessible example of performant scientific computing for the 20 next generation of researchers, SeisIO offers ease of use and rapid learning without sacrificing 21 computational performance. 2 22 1 Introduction 23 The dramatic growth in the volume of collected geophysical data has the potential to lead to 24 tremendous advances in the science (https://ds.iris.edu/data/distribution/).
    [Show full text]
  • Empirical Study of Restarted and Flaky Builds on Travis CI
    Empirical Study of Restarted and Flaky Builds on Travis CI Thomas Durieux Claire Le Goues INESC-ID and IST, University of Lisbon, Portugal Carnegie Mellon University [email protected] [email protected] Michael Hilton Rui Abreu Carnegie Mellon University INESC-ID and IST, University of Lisbon, Portugal [email protected] [email protected] ABSTRACT Continuous integration is an automatic process that typically Continuous Integration (CI) is a development practice where devel- executes the test suite, may further analyze code quality using static opers frequently integrate code into a common codebase. After the analyzers, and can automatically deploy new software versions. code is integrated, the CI server runs a test suite and other tools to It is generally triggered for each new software change, or at a produce a set of reports (e.g., the output of linters and tests). If the regular interval, such as daily. When a CI build fails, the developer is result of a CI test run is unexpected, developers have the option notified, and they typically debug the failing build. Once the reason to manually restart the build, re-running the same test suite on for failure is identified, the developer can address the problem, the same code; this can reveal build flakiness, if the restarted build generally by modifying or revoking the code changes that triggered outcome differs from the original build. the CI process in the first place. In this study, we analyze restarted builds, flaky builds, and their However, there are situations in which the CI outcome is unex- impact on the development workflow.
    [Show full text]
  • Usage, Costs, and Benefits of Continuous Integration in Open
    Usage, Costs, and Benefits of Continuous Integration in Open-Source Projects Michael Hilton Timothy Tunnell Kai Huang Oregon State University University of Illinois at University of Illinois at [email protected] Urbana-Champaign Urbana-Champaign [email protected] [email protected] Darko Marinov Danny Dig University of Illinois at Oregon State University Urbana-Champaign [email protected] [email protected] ABSTRACT CI using several quality metrics. However, the study does Continuous integration (CI) systems automate the compi- not present any detailed information about the use of CI. lation, building, and testing of software. Despite CI rising In fact, despite some folkloric evidence about the use of CI, as a big success story in automated software engineering, it there is no systematic study about CI systems. has received almost no attention from the research commu- Not only do we lack basic knowledge about the extent nity. For example, how widely is CI used in practice, and to which open-source projects are adopting CI, but also what are some costs and benefits associated with CI? With- we have no answers to many other important questions re- out answering such questions, developers, tool builders, and lated to CI. What are the costs of CI? Does CI deliver researchers make decisions based on folklore instead of data. on the promised benefits, such as releasing more often, or In this paper, we use three complementary methods to helping make changes (e.g., to merge pull requests) faster? study in-depth the usage of CI in open-source projects. To Are developers maximizing the usage of CI? Despite the understand what CI systems developers use, we analyzed widespread popularity of CI, we have very little quantita- 34,544 open-source projects from GitHub.
    [Show full text]
  • Spice Program Open Source 2015 Learnings
    Spice Program Open Source 2015 learnings Please see this Futurice Spice Program blog post to learn the context for this list. ​ ​ Learned even more about practical problems in measuring time. Direct uploads from browser to AWS S3. Basics of Polymer. React + Redux (lots of it). Basic info about Google Cloud Services. Practical usage of Google Cloud Storage (the Google's S3 equivalent). Heroku Pipelines. Improved & more modular Angular application structure formation. Webpack, JSON Web Token implementation on the backend, and ES6. Actually learning how Promises should be used in JavaScript. Some knowledge about Dokku, the host­it­yourself­Heroku. Got practical experience and more understanding about Node.js, npm, and bacon.js. How the Azure Web App continuous deployment works. A bit on how Travis CI operates under the hood. How to make Joomla templates. Learned about Let's Encrypt on Apache with vhosts. Learned more about Web MIDI API and RxJS. Also more about ES6 and setting up a compact development environment for that. Learned basics of RxJS. Learned a lot about creating a reusable library with JS/browserify. Learned some Cycle.js. Learned a little about Node.js testing. Learned the EMV chip card specification on very detailed level by implementing large part of the specification. I'm using the EMV knowledge on daily basis in my current client project. Improved my Clojure language skills. Learned to work with the Go programming language. Wrote an OSS tool that I later then used in a customer project. I learned better ways to use Dagger 2 in Android and trial and evaluate other app architectural patterns based around this.
    [Show full text]
  • Open Source Best Practices: from Continuous Integration to Static Linters
    THE MOLECULAR SCIENCES SOFTWARE INSTITUTE - LOGO CONCEPTS ROUND 2 Open Source Best Practices: From Continuous Integration to Static Linters Daniel G. A. Smith and Ben Pritchard The Molecular Sciences Software Institute !1 @dga_smith / @molssi_nsf 1. 3 The Molecular Sciences Software Institute (MolSSI) •Designed to serve and enhance the software development efforts of the broad field of computational molecular science (CMS). •Funded at the institute level under the Software Infrastructure for Sustained Innovation (SI2) initiative by the National Science Foundation. •Launched August 1st, 2016 •Collaborative effort by: •Virginia Tech •U.C. Berkeley •U. Southern •Rice U. •Stanford U. California •Stony Brook U. •Rutgers U. •Iowa State U. !2 The Molecular Sciences Software Institute (MolSSI) •Software Infrastructure •Build open-source frameworks and packages for the entire CMS community •Education and training •Online materials and training guides •Host a number of targeted workshops, summer schools, and other training programs •Community Engagement and Leadership •Interoperability standards and best practices !3 •Data and API standardization targets Talk Motivation •Many terms thrown around: •Best Practice •Manage Code •DevOps •Build and Package •Open Source •“Just get the physics •Software Sustainability working” •“Incorrect Software” “Best” is subjective and depends on your own community. Lets discuss practical applications and how to make our lives easier! !4 Open Source Open Source software is software that can be freely accessed, used,
    [Show full text]
  • Conan Documentation Release 1.25.2
    Conan Documentation Release 1.25.2 The Conan team Sep 24, 2021 CONTENTS 1 Introduction 3 1.1 Open Source...............................................3 1.2 Decentralized package manager.....................................3 1.3 Binary management...........................................4 1.4 All platforms, all build systems and compilers.............................5 1.5 Stable...................................................5 1.6 Community................................................6 2 Install 7 2.1 Install with pip (recommended).....................................7 2.2 Install from brew (OSX).........................................8 2.3 Install from AUR (Arch Linux).....................................8 2.4 Install the binaries............................................8 2.5 Initial configuration...........................................9 2.6 Install from source............................................9 2.7 Update..................................................9 2.8 Python 2 Deprecation Notice....................................... 10 3 Getting Started 11 3.1 An MD5 hash calculator using the Poco Libraries............................ 11 3.2 Installing Dependencies......................................... 14 3.3 Inspecting Dependencies......................................... 15 3.4 Searching Packages........................................... 18 3.5 Building with Other Configurations................................... 18 4 Using packages 21 4.1 Installing dependencies......................................... 21 4.2 Using
    [Show full text]
  • Datadeps.Jl: Repeatable Data Setup Journal of for Reproducible Data Science
    White, L, et al. 2019 DataDeps.jl: Repeatable Data Setup Journal of for Reproducible Data Science. Journal of Open Research open research software Software, 7: 33. DOI: https://doi.org/10.5334/jors.244 SOFTWARE METAPAPER DataDeps.jl: Repeatable Data Setup for Reproducible Data Science Lyndon White, Roberto Togneri, Wei Liu and Mohammed Bennamoun The University of Western Australia, Crawley, Western Australia, AU Corresponding author: Lyndon White ([email protected]) We present DataDeps.jl: a julia package for the reproducible handling of static datasets to enhance the repeatability of scripts used in the data and computational sciences. It is used to automate the data setup part of running software which accompanies a paper to replicate a result. This step is commonly done manually, which expends time and allows for confusion. This functionality is also useful for other packages which require data to function (e.g. a trained machine learning based model). DataDeps.jl simplifies extending research software by automatically managing the dependencies and makes it easier to run another author’s code, thus enhancing the reproducibility of data science research. Keywords: data management; reproducible science; continuous integration; software practices; dependency management; open source software; JuliaLang 1 Introduction In the movement for reproducible sciences there have These tasks are automatable and therefore should be been two key requests upon authors: 1. Make your automated, as per the practice “Let the computer do the research code public, 2. Make your data public [3]. In work” [7]. practice this alone is not enough to ensure that results can DataDeps.jl handles the data dependencies, while Pkg1 be replicated.
    [Show full text]
  • Code Coverage & Continuous Integration
    Code Coverage & Continuous Integration ATPESC 2019 Jared O’Neal Mathematics and Computer Science Division Argonne National Laboratory Q Center, St. Charles, IL (USA) July 28 – August 9, 2019 exascaleproject.org License, citation, and acknowledgments License and Citation • This work is licensed under A CreAtive Commons Attribution 4.0 InternAtionAl License (CC BY 4.0). • Requested citAtion: Jared O’NeAl, Code CoverAge & Continuous IntegrAtion, in Better Scientific SoftwAre TutoriAl, Argonne TrAining ProgrAm on Extreme-Scale Computing (ATPESC), St. ChArles, IL, 2019. DOI: 10.6084/m9.figshAre.9272813. Acknowledgements • This work wAs supported by the U.S. DepArtment of Energy Office of Science, Office of Advanced Scientific Computing ReseArch (ASCR), And by the Exascale Computing Project (17-SC-20-SC), A collAborAtive effort of the U.S. DepArtment of Energy Office of Science And the NAtionAl NucleAr Security AdministrAtion. • This work wAs performed in pArt At the Argonne NAtionAl LAborAtory, which is mAnAged by UChicago Argonne, LLC for the U.S. DepArtment of Energy under ContrAct No. DE-AC02-06CH11357 • AliciA Klinvex 2 ATPESC 2019, July 28 – August 9, 2019 CODE COVERAGE How do we determine what other tests are needed? Code coverage tools • Expose parts of the code that aren’t being tested • gcov o standard utility with the GNU compiler collection suite o Compile/link with –coverage & turn off optimization o counts the number of times each statement is executed • lcov o a graphical front-end for gcov o available at http://ltp.sourceforge.net/coverage/lcov.php
    [Show full text]
  • Continuous Testing & Integration
    Continuous Testing & Integration Philippe Collet (avec beaucoup de M1 PROJET - 2019-2020 (images: pixabay) 1 slides de Guilhem. Molines) Delivering Software P. C o l l e t 2 Delivering software… • In 1995, MS released Windows 95 – Major breakthrough for consumers – Real multi-tasking with background apps • How many service packs were released? 3 Delivering software… • In 1995, MS released Windows 95 – Major breakthrough for consumers – Real multi-tasking with background apps • How many service packs were released? à 2 (yes, two) (6 months and 1 year after release) 4 Delivering software… • In 2015, MS released Windows 10 – 4 editions – Continuous, forced updates • How many service packs were released? 5 Delivering software… • In 2015, MS released Windows 10 – 4 editions – Continuous, forced updates • How many service packs were released? à couldn’t count… (1 GB on first day) 6 What is the most important thing you need to deliver software continuously? Trust 7 How do you get trust in your software delivery? • Good architecture • Development guidelines • Project management • Controlled processes • Traceability of requirements • Automation • Repeatable pipeline • Testing • Testing • And… Testing 8 Software Delivery Life Cycle (SDLC) In a nutshell P. C o l l e t 9 Single student, simple project • Ant • Maven? • SCM? • Code and click 10 Group of students, simple project • Ant / Maven • Github • Code and click • Build on local machine • Ticket management ? 11 Industrial complex project • 20 – 200 contributors • One release / year • One patch / month • > 20M LOCs • Deployment complexity • à What do you need? 12 Industrial complex project • Componentization • Independence of builds • Each component tested • Clear quality indicators • Requirement traceability • Fast builds • Each contributor only builds what they code • Deployment automation 13 Software quality • What is it? • No Defects? • Or….
    [Show full text]
  • I'm Leaving You, Travis: a Continuous Integration Breakup Story
    I’m Leaving You, Travis: A Continuous Integration Breakup Story David Gray Widder, Michael Hilton, Christian Kästner, Bogdan Vasilescu Carnegie Mellon University, USA ABSTRACT it’s natural for different projects to have different needs, as wellas Continuous Integration (CI) services, which can automatically build, for a project’s CI needs to change over time, as developers navigate test, and deploy software projects, are an invaluable asset in dis- these tradeoffs [2, 27]. Simply stated, one size does not fitall. tributed teams, increasing productivity and helping to maintain As a realization of the diversity of CI needs, the marketplace of code quality. Prior work has shown that CI pipelines can be sophisti- available CI tools in open-source software (OSS) is booming. While cated, and choosing and configuring a CI system involves tradeoffs. not long ago Jenkins and Travis CI were the only broadly used As CI technology matures, new CI tool offerings arise to meet the client-side and cloud-based CI services, respectively, there are now 1 distinct wants and needs of software teams, as they negotiate a 17 CI services that integrate with GitHub directly, and online 2 path through these tradeoffs, depending on their context. In this discussions are explicit about the need for tailored CI solutions. paper, we begin to uncover these nuances, and tell the story of To better support developers looking for bespoke CI solutions as open-source projects falling out of love with Travis, the earliest well as designers and builders of CI tools, in this paper we begin to and most popular cloud-based CI system.
    [Show full text]
  • Download Download
    p-ISSN : 2443-2210 Jurnal Teknik Informatika dan Sistem Informasi e-ISSN : 2443-2229 Volume 7 Nomor 1 April 2021 Continuous Integration and Continuous Delivery Platform Development of Software Engineering and Software Project Management in Higher Education http://dx.doi.org/10.28932/jutisi.v7i1.3254 Riwayat Artikel Received: 5 Januari 2021 | Final Revision: 15 Maret 2021 | Accepted: 24 Maret 2021 Sendy Ferdian#1, Tjatur Kandaga#2, Andreas Widjaja#3, Hapnes Toba#4, Ronaldo Joshua#5, Julio Narabel#6 Faculty of Information Technology, Universitas Kristen Maranatha, Bandung, Indonesia [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] Abstract — We present a report of the development phase of a likely to be very diverse and composed of various tools, platform that aims to enhance the efficiency of software commercially or open-source technologies, therefore project management in higher education. The platform managing application delivery lifecycle is difficult because accommodates a strategy known as Continuous Integration and Continuous Delivery (CI/CD). The phase consists of of those complexities. Dealing with those daunting and several stages, followed by testing of the system and its complex tasks, one solution is using the DevOps [3] [4] deployment. For starters, the CI/CD platform will be deployed approach. for software projects of students in the Faculty of Information The relatively new emerging DevOps is a culture where Technology, Universitas Kristen Maranatha. The goal of this development, testing, and operations teams join together paper is to show a design of an effective platform for collaborating to deliver outcome results in a continuous and continuous integration and continuous delivery pipeline to accommodate source code compilation, code analysis, code effective way [2] [5].
    [Show full text]