The Utilization of Automated Tools in the Automated Continuous Integration Practice Case Study: Medical Record Application

Authors

  • Eka Trisno Samosir Del Institute of Technology, Sitoluama, Laguboti, Toba Samosir, North Sumatera – Indonesia. 22381.
  • Hernawati Samosir Del Institute of Technology, Sitoluama, Laguboti, Toba Samosir, North Sumatera – Indonesia. 22381.
  • Inggriani Liem Del Institute of Technology, Sitoluama, Laguboti, Toba Samosir, North Sumatera – Indonesia. 22381.
  • Yudistira Dwi Bandung Institute of Technology, Jl. Ganesha 10, Bandung, West Java – Indonesia. 40132.

Keywords:

Build Tools, Build, Automated CI Tools, Continues Integration,

Abstract

Continuous integration (CI) is a software development practice that is carried out in a team by dividing modules among the team members and integrate team’s work regularly. Developers who are using CI practice manually will require more effort for the whole work integration compared to those who work in a team and integrate their work regularly. The application of toolset in CI practice will enable the developer to work easily. The CI practice that uses toolset is known as automated CI. The automated CI practice consists of version management using version control system tools, code program testing using testing tools, build execution using build tools and module integration practices using CI tools. From all of the automated CI practices, the focus of this research is the execution of build and the integration of modules manually and using automated tools. The significant differences from using automated tools in automated CI practice are the decrease of unnecessary effort spent by developers on the execution of the build using the build tools and the elimination of the integrator role by using CI tools that finally results in a more efficient performance of the developers.

References

Glenford J. Myers, 2004, The Art of Software Testing Second Edition, Hoboken, John Wiley & Sons.

Pilone Dan dan Russ Miles, 2007, Head First Software Development, USA.

Kaner, Falk, Nguyen, 1999, Testing Computer Software, Second Edition (Wiley Series), USA.

Humble, Jez dan David Farley, 2010, Continuous Delivery: Reliable Software Releases through Build, Test and Deployment Automation (Addison-Wesley Signature Series), USA.

Hijriyah, Yuanita Annisatul, 2014, Penggunaan VCS tools dalam praktik automated Continuous Integration pada studi kasus aplikasi rekam medis, Program Alih Jenjang D3 ke D4 Teknologi Informasi Kesehatan, Institut Teknologi Bandung, Bandung.

Muhamad, Fachrul Pralienka Bani, 2014, Penggunaan testing tools dalam praktik automated Continuous Integration pada studi kasus aplikasi rekam medis, Program Alih Jenjang D3 ke D4 Teknologi Informasi Kesehatan, Institut Teknologi Bandung, Bandung.

Meet Jenkins. (Online). URL: https://wiki.jenkinsci.org/display/JENKINS/Meet+Jenkins. Accessed in 10 October2013.

Fowler Martin, 2006, Continuous Integration. (Online). URL:http://martinfowler.com/articles/continuousIntegration.html. Accessed in 10 October 2013.

Duvall, Paul M., Steve Matyas and Andrew Glover, 2007, Continuous Integration: Improving software quality and reducing risk(AddisonWesley Signature Series), USA.

Somasundaram. Ravishankar, 2013, Git: Version Control for Everyone, Birmingham B3 2PB, Packt Publishing Ltd.

Glenford J. Myers, Tom Badgett, Corey Sandler, 2012, The Art of Software Testing 3rd Edition, Hoboken, JohnWiley & Sons.

Pressman. Roger S, 2001, Software Engineering: A Practitioner’s Approach Fifth Edition, New York, The McGraw Hill.

Peter A. Vogel, An Integrated General Purpose Automated Test Environment, ftp://192.67.63.1/pub/cite/vogel-cite.pdf. Accessed 3 May 2014.

Downloads

Published

2017-06-01

How to Cite

Samosir, E. T., Samosir, H., Liem, I., & Dwi, Y. (2017). The Utilization of Automated Tools in the Automated Continuous Integration Practice Case Study: Medical Record Application. Journal of Telecommunication, Electronic and Computer Engineering (JTEC), 9(2-5), 123–127. Retrieved from https://jtec.utem.edu.my/jtec/article/view/2411

Issue

Vol. 9 No. 2-5: Circuit and System Advancement in Modern World IV

Section

Articles

License

TRANSFER OF COPYRIGHT AGREEMENT

The manuscript is herewith submitted for publication in the Journal of Telecommunication, Electronic and Computer Engineering (JTEC). It has not been published before, and it is not under consideration for publication in any other journals. It contains no material that is scandalous, obscene, libelous or otherwise contrary to law. When the manuscript is accepted for publication, I, as the author, hereby agree to transfer to JTEC, all rights including those pertaining to electronic forms and transmissions, under existing copyright laws, except for the following, which the author(s) specifically retain(s):

  1. All proprietary right other than copyright, such as patent rights
  2. The right to make further copies of all or part of the published article for my use in classroom teaching
  3. The right to reuse all or part of this manuscript in a compilation of my own works or in a textbook of which I am the author; and
  4. The right to make copies of the published work for internal distribution within the institution that employs me

I agree that copies made under these circumstances will continue to carry the copyright notice that appears in the original published work. I agree to inform my co-authors, if any, of the above terms. I certify that I have obtained written permission for the use of text, tables, and/or illustrations from any copyrighted source(s), and I agree to supply such written permission(s) to JTEC upon request.