Loading...
Publication
CONTINUOUS INTEGRATION METHODOLOGY IMPLEMENTATION AND COMPARISON
| Name: | Description: | Size: | Format: | |
|---|---|---|---|---|
| 8.83 MB | Adobe PDF |
Authors
Abstract(s)
In order to know the impact and results of a Continuous Integration (CI) Methodology an
implementation of CI was made on a software company. Saviasoft is a company that
produces custom software. Implementing CI over an existing agile methodology that has
not been changed for a while, is not easy, mainly because the developers are unaware of the
benefits of using CI tools. In order to accomplish the objective of implementing a CI
methodology, developers should have enough knowledge about CI concepts and know how
to use the adequate tools properly, and, how to implement them on their projects.
The aims of the project are to improve the quality of the software that Saviasoft produces;
analyze the impact of the CI methodology implementation; and improve the reliability of the
software that is developed, by having a better way of testing. Jenkins is the tool that will
serve as the base for the CI methodology implementation.
The project implementation has the following steps: (1) Analysis of the actual situation of
the company; (2) Selection of specific metrics to measure before implementing CI; (3)
Implementation of CI over the existing agile methodology; and (4) Measure the same metrics
after the CI implementation and compare the results.
The results of the CI implementation were the expected: currently, the company produces
software with an enhanced quality.
The CI implementation mainly improved the software quality, test phase, and deployment
phase. In the future, Saviasoft will propose CI courses to the clients that have in-house
developers.
Description
Keywords
Continuous Integration Implementation Quality Assurance Continuous Integration Comparison Impact of Continuous Integration Measure Continuous Integration