{"id":{"repo_id":"ets-quebec","oai_identifier":"oai:espace.etsmtl.ca:3035"},"canonical_url":"https://search.ndltd.org/etd/ets-quebec/oai:espace.etsmtl.ca:3035","repository":{"repo_id":"ets-quebec","name":"ETS (Quebec)","base_url":"https://espace.etsmtl.ca/cgi/oai2"},"display":{"title":"Extraction and analysis of behavior practices based on GitLab MR information","abstract":"The constantly evolving nature of technology in software, IT, and telecommunication is no doubt associated with emerging challenges regarding the ability to deliver software faster and with higher quality. The adoption of DevOps by many companies, in different application domains, in the last decade has resulted in major progress regarding both aspects. However, to reach the objectives of DevOps, a systematic approach to the continuous improvement of the different phases of the software delivery process needs to be established. This thesis focuses on the improvement of the code review phase of the process based on an industrial case study provided by Kaloom. The overall objective is to investigate different statistical and machine learning techniques that can be used to extract and analyze behavior practices from the data recorded by GitLab during the Merge Request (MR) peer-review phase. For this purpose, we focus on three main research questions: RQ1) How does the Lead Time of MRs change over the 21 days of a sprint, RQ2) What are the behavior practices of software engineers during the sprint days, and RQ3) What are exceptions and outliers in MR data. Our main findings include that there is no correlation between the Lead Time and Size of MRs in the studied groups, that the groups with hardware tests have higher average Lead Time, and that there is a very weak Spearman correlation between the Lead Time of an MR and the day on which an MR was created or closed. Furthermore, through manual analysis of exception MRs, we observed that some MRs are commented after the merge and that these MRs are often associated with errors discovered later during the different product testing phases.","abstract_html":"The constantly evolving nature of technology in software, IT, and telecommunication is no doubt associated with emerging challenges regarding the ability to deliver software faster and with higher quality. The adoption of DevOps by many companies, in different application domains, in the last decade has resulted in major progress regarding both aspects. However, to reach the objectives of DevOps, a systematic approach to the continuous improvement of the different phases of the software delivery process needs to be established. This thesis focuses on the improvement of the code review phase of the process based on an industrial case study provided by Kaloom. The overall objective is to investigate different statistical and machine learning techniques that can be used to extract and analyze behavior practices from the data recorded by GitLab during the Merge Request (MR) peer-review phase. For this purpose, we focus on three main research questions: RQ1) How does the Lead Time of MRs change over the 21 days of a sprint, RQ2) What are the behavior practices of software engineers during the sprint days, and RQ3) What are exceptions and outliers in MR data. Our main findings include that there is no correlation between the Lead Time and Size of MRs in the studied groups, that the groups with hardware tests have higher average Lead Time, and that there is a very weak Spearman correlation between the Lead Time of an MR and the day on which an MR was created or closed. Furthermore, through manual analysis of exception MRs, we observed that some MRs are commented after the merge and that these MRs are often associated with errors discovered later during the different product testing phases.","abstract_has_math":false,"creators":["Mashari, Seyedbehnam"],"institution":"École de technologie supérieure","degree_name":"Mémoire de maîtrise électronique","degree_level":"masters","degree_discipline":null,"degree_department":null,"school":null,"contributors":[],"advisors":[],"committee_chairs":[],"committee_members":[],"year":2022,"date_issued":"2022-04-25","date_published":"2022-04-25","updated_at":"2026-11-18T22:09:26Z","subjects":["DevOps, revue de code, la demande de fusion, techniques statistiques, d'apprentissage automatique, les comportements"],"languages":["en"],"rights":[],"rights_urls":[],"identifier_entries":[{"key":"dc:identifier","label":"Identifier","values":["INSERT-YOUR-LIBRARY-ID-HERE3035"],"render_values":[{"text":"INSERT-YOUR-LIBRARY-ID-HERE3035","href":null,"code":true}]}],"person_identifier_entries":[]},"links":{"outbound_url":null,"outbound_label":null,"outbound_source":null,"record_url":null,"record_label":null,"record_kind":null,"record_source":null,"download_url":"https://espace.etsmtl.ca/id/eprint/3035/1/MASHARI_Seyedbehnam.pdf","download_label":"Download PDF","download_source":"dc:identifier","access_status":null,"embargo_until":null,"access_note":null},"source_record":{"url":"https://espace.etsmtl.ca/cgi/oai2?verb=GetRecord&metadataPrefix=oai_etdms&identifier=oai%3Aespace.etsmtl.ca%3A3035","prefix":"oai_etdms"},"metadata_groups":[{"id":"people","label":"People","entries":[{"key":"dc:creator","label":"Author","values":["Mashari, Seyedbehnam"]}]},{"id":"academic_context","label":"Academic Context","entries":[{"key":"dc:date","label":"Dc Date","values":["2022-04-25"]},{"key":"dc:publisher","label":"Institution","values":["École de technologie supérieure"]},{"key":"dc:type","label":"Dc Type","values":["Electronic Thesis or Dissertation"]},{"key":"thesis:degree_level","label":"Degree Level","values":["masters"]},{"key":"thesis:degree_name","label":"Degree Name","values":["Mémoire de maîtrise électronique"]},{"key":"thesis:institution_name","label":"Thesis Institution Name","values":["École de technologie supérieure"]}]},{"id":"subjects_keywords","label":"Subjects and Keywords","entries":[{"key":"dc:subject","label":"Dc Subject","values":["DevOps, revue de code, la demande de fusion, techniques statistiques, d'apprentissage automatique, les comportements"]}]},{"id":"language_rights","label":"Language and Rights","entries":[{"key":"dc:language","label":"Dc Language","values":["en"]}]},{"id":"identifiers","label":"Identifiers","entries":[{"key":"dc:identifier","label":"Identifier","values":["INSERT-YOUR-LIBRARY-ID-HERE3035","https://espace.etsmtl.ca/id/eprint/3035/1/MASHARI_Seyedbehnam.pdf"]}]},{"id":"additional","label":"Additional Metadata","entries":[{"key":"dc:description","label":"Description","values":["The constantly evolving nature of technology in software, IT, and telecommunication is no doubt associated with emerging challenges regarding the ability to deliver software faster and with higher quality. The adoption of DevOps by many companies, in different application domains, in the last decade has resulted in major progress regarding both aspects. However, to reach the objectives of DevOps, a systematic approach to the continuous improvement of the different phases of the software delivery process needs to be established. This thesis focuses on the improvement of the code review phase of the process based on an industrial case study provided by Kaloom. The overall objective is to investigate different statistical and machine learning techniques that can be used to extract and analyze behavior practices from the data recorded by GitLab during the Merge Request (MR) peer-review phase. For this purpose, we focus on three main research questions: RQ1) How does the Lead Time of MRs change over the 21 days of a sprint, RQ2) What are the behavior practices of software engineers during the sprint days, and RQ3) What are exceptions and outliers in MR data. Our main findings include that there is no correlation between the Lead Time and Size of MRs in the studied groups, that the groups with hardware tests have higher average Lead Time, and that there is a very weak Spearman correlation between the Lead Time of an MR and the day on which an MR was created or closed. Furthermore, through manual analysis of exception MRs, we observed that some MRs are commented after the merge and that these MRs are often associated with errors discovered later during the different product testing phases."]},{"key":"dc:format","label":"Dc Format","values":["application/pdf"]},{"key":"dc:title","label":"Title","values":["Extraction and analysis of behavior practices based on GitLab MR information"]}]}],"canonical_facts":{"dc:creator":["Mashari, Seyedbehnam"],"dc:date":["2022-04-25"],"dc:description":["The constantly evolving nature of technology in software, IT, and telecommunication is no doubt associated with emerging challenges regarding the ability to deliver software faster and with higher quality. The adoption of DevOps by many companies, in different application domains, in the last decade has resulted in major progress regarding both aspects. However, to reach the objectives of DevOps, a systematic approach to the continuous improvement of the different phases of the software delivery process needs to be established. This thesis focuses on the improvement of the code review phase of the process based on an industrial case study provided by Kaloom. The overall objective is to investigate different statistical and machine learning techniques that can be used to extract and analyze behavior practices from the data recorded by GitLab during the Merge Request (MR) peer-review phase. For this purpose, we focus on three main research questions: RQ1) How does the Lead Time of MRs change over the 21 days of a sprint, RQ2) What are the behavior practices of software engineers during the sprint days, and RQ3) What are exceptions and outliers in MR data. Our main findings include that there is no correlation between the Lead Time and Size of MRs in the studied groups, that the groups with hardware tests have higher average Lead Time, and that there is a very weak Spearman correlation between the Lead Time of an MR and the day on which an MR was created or closed. Furthermore, through manual analysis of exception MRs, we observed that some MRs are commented after the merge and that these MRs are often associated with errors discovered later during the different product testing phases."],"dc:format":["application/pdf"],"dc:identifier":["INSERT-YOUR-LIBRARY-ID-HERE3035","https://espace.etsmtl.ca/id/eprint/3035/1/MASHARI_Seyedbehnam.pdf"],"dc:language":["en"],"dc:publisher":["École de technologie supérieure"],"dc:subject":["DevOps, revue de code, la demande de fusion, techniques statistiques, d'apprentissage automatique, les comportements"],"dc:title":["Extraction and analysis of behavior practices based on GitLab MR information"],"dc:type":["Electronic Thesis or Dissertation"],"thesis:degree_level":["masters"],"thesis:degree_name":["Mémoire de maîtrise électronique"],"thesis:institution_name":["École de technologie supérieure"]},"updated_at":"2026-11-18T22:09:26Z"}