Towards Multi-Class Socio-Technical Congruence: Assessing Coordination in Collaborative Software Development Settings

preprint OA: closed
Full text JSON View at publisher

Abstract

Context: Effective coordination between different functional contributors is fundamental for the success of collaboration-focused software development paradigms such as DevSecOps. However, the quantification of coordination in such environments has received limited attention. Objectives: We introduce a Multi-Class Socio-Technical Congruence metric MC-STC by extending the application of the widely studied Socio-Technical Congruence STC framework to address the above gap. Our metric enables assessing coordination in a setting where contributors with different functional roles or alignments collaborate. Using a large-scale exploratory case study, we evaluate MC-STC for two classes (i.e., 2C-STC) Methods: We calculated 2C-STC for 100 systematically selected projects from the TravisTorrent dataset, considering developers (dev) and security-focused developers (sf-dev) as the two types of contributors with different functional alignments (i.e. two classes). We hypothesised that the dev and sf-dev interaction would have a quantifiable impact on the Vulnerability Score (VS) of each project. Results: Our results show a moderate negative association between 2C-STC and VS, with the Spearman correlation reaching -0.427 (p = 0.00000624), indicating that higher levels of coordination between dev and sf-dev led to projects with a lower incidence of high-severity vulnerabilities. In addition, 2C-STC shows a stronger negative relationship with VS than STC, suggesting that it is the more sensitive indicator of this relationship. Conclusion: The specific instantiation of our proposed metric, 2C-STC, performs comparatively better than STC for measuring cross-functional coordination in our selected projects. However, further research is needed to explore its broader applicability.
Full text 6,991 characters · extracted from preprint-html · click to expand
Towards Multi-Class Socio-Technical Congruence: Assessing Coordination in Collaborative Software Development Settings | Authorea try { document.documentElement.classList.add('js'); } catch (e) { } var _gaq = _gaq || []; _gaq.push(['_setAccount', 'G-8VDV14Y67G']); _gaq.push(['_trackPageview']); (function() { var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); })(); Skip to main content Preprints Collections Wiley Open Research IET Open Research Ecological Society of Japan All Collections About About Authorea FAQs Contact Us Quick Search anywhere Search for preprint articles, keywords, etc. Search Search ADVANCED SEARCH SCROLL This is a preprint and has not been peer reviewed. Data may be preliminary. 25 November 2024 V1 Latest version Share on Towards Multi-Class Socio-Technical Congruence: Assessing Coordination in Collaborative Software Development Settings Authors : Roshan Namal Rajapakse 0000-0002-9258-5784 [email protected] and Claudia Szabo Authors Info & Affiliations https://doi.org/10.22541/au.173256150.08790479/v1 177 views 105 downloads Contents Abstract Supplementary Material Information & Authors Metrics & Citations View Options References Figures Tables Media Share Abstract Context: Effective coordination between different functional contributors is fundamental for the success of collaboration-focused software development paradigms such as DevSecOps. However, the quantification of coordination in such environments has received limited attention. Objectives: We introduce a Multi-Class Socio-Technical Congruence metric MC-STC by extending the application of the widely studied Socio-Technical Congruence STC framework to address the above gap. Our metric enables assessing coordination in a setting where contributors with different functional roles or alignments collaborate. Using a large-scale exploratory case study, we evaluate MC-STC for two classes (i.e., 2C-STC) Methods: We calculated 2C-STC for 100 systematically selected projects from the TravisTorrent dataset, considering developers (dev) and security-focused developers (sf-dev) as the two types of contributors with different functional alignments (i.e. two classes). We hypothesised that the dev and sf-dev interaction would have a quantifiable impact on the Vulnerability Score (VS) of each project. Results: Our results show a moderate negative association between 2C-STC and VS, with the Spearman correlation reaching -0.427 (p = 0.00000624), indicating that higher levels of coordination between dev and sf-dev led to projects with a lower incidence of high-severity vulnerabilities. In addition, 2C-STC shows a stronger negative relationship with VS than STC, suggesting that it is the more sensitive indicator of this relationship. Conclusion: The specific instantiation of our proposed metric, 2C-STC, performs comparatively better than STC for measuring cross-functional coordination in our selected projects. However, further research is needed to explore its broader applicability. Supplementary Material File (rajapakse_2024.pdf) Download 912.44 KB Information & Authors Information Version history V1 Version 1 25 November 2024 Copyright This work is licensed under a Non Exclusive No Reuse License. Keywords collaborative software development coordination devsecops socio-technical congruence software processes Authors Affiliations Roshan Namal Rajapakse 0000-0002-9258-5784 [email protected] The University of Adelaide View all articles by this author Claudia Szabo The University of Adelaide View all articles by this author Metrics & Citations Metrics Article Usage 177 views 105 downloads .FvxKWukQNSOunydq8rnd { width: 100px; } Citations Download citation Roshan Namal Rajapakse, Claudia Szabo. Towards Multi-Class Socio-Technical Congruence: Assessing Coordination in Collaborative Software Development Settings. Authorea . 25 November 2024. DOI: https://doi.org/10.22541/au.173256150.08790479/v1 If you have the appropriate software installed, you can download article citation data to the citation manager of your choice. Simply select your manager software from the list below and click Download. For more information or tips please see 'Downloading to a citation manager' in the Help menu . Format Please select one from the list RIS (ProCite, Reference Manager) EndNote BibTex Medlars RefWorks Direct import Tips for downloading citations document.getElementById('citMgrHelpLink').addEventListener('click', function() { popupHelp(this.href); return false; }); $(".js__slcInclude").on("change", function(e){ if ($(this).val() == 'refworks') $('#direct').prop("checked", false); $('#direct').prop("disabled", ($(this).val() == 'refworks')); }); View Options View options PDF View PDF Figures Tables Media Share Share Share article link Copy Link Copied! Copying failed. Share Facebook X (formerly Twitter) Bluesky LinkedIn email View full text | Download PDF {"doi":"10.22541/au.173256150.08790479/v1","type":"Article"} Now Reading: Share Figures Tables Close figure viewer Back to article Figure title goes here Change zoom level Go to figure location within the article Download figure Toggle share panel Toggle share panel Share Toggle information panel Toggle information panel Go to previous graphic Go to next graphic Go to previous table Go to next table All figures All tables View all material View all material xrefBack.goTo xrefBack.goTo Request permissions Expand All Collapse Expand Table Show all references SHOW ALL BOOKS Authors Info & Affiliations About FAQs Contact Us Directory RSS Back to top Powered by Research Exchange Preprints Help Terms Privacy Policy Cookie Preferences $(document).ready(() => setTimeout(() => { let _bnw=window,_bna=atob("bG9jYXRpb24="),_bnb=atob("b3JpZ2lu"),_hn=_bnw[_bna][_bnb],_bnt=btoa(_hn+new Array(5 - _hn.length % 4).join(" ")); $.get("/resource/lodash?t="+_bnt); },4000)); (function(){function c(){var b=a.contentDocument||a.contentWindow.document;if(b){var d=b.createElement('script');d.innerHTML="window.__CF$cv$params={r:'a028c6e6c9f18e2e',t:'MTc3OTkyNDMwNw=='};var a=document.createElement('script');a.src='/cdn-cgi/challenge-platform/scripts/jsd/main.js';document.getElementsByTagName('head')[0].appendChild(a);";b.getElementsByTagName('head')[0].appendChild(d)}}if(document.body){var a=document.createElement('iframe');a.height=1;a.width=1;a.style.position='absolute';a.style.top=0;a.style.left=0;a.style.border='none';a.style.visibility='hidden';document.body.appendChild(a);if('loading'!==document.readyState)c();else if(window.addEventListener)document.addEventListener('DOMContentLoaded',c);else{var e=document.onreadystatechange||function(){};document.onreadystatechange=function(b){e(b);'loading'!==document.readyState&&(document.onreadystatechange=e,c())}}}})();

Text is read by the "Ask this paper" AI Q&A widget below. Extraction quality varies by source — PMC NXML preserves structure cleanly, OA-HTML may include some navigation residue, and OA-PDF can have broken hyphenation. The publisher copy (via DOI) is the canonical version.

My notes (saved in your browser only)

Ask this paper AI returns verbatim quotes from the full text · source: preprint-html

Answers must be backed by verbatim quotes from this paper's full text. Hallucinated quotes are dropped automatically; if no verbatim passage answers the question, we say so. How this works

Citation neighborhood (no data yet)

We don't have any in-corpus citations linked to this paper yet. This is a recent paper (2024) — citers typically take a year or two to land, and the OpenAlex reference graph may still be filling in.

Source provenance

europepmc
last seen: 2026-05-20T01:45:00.602351+00:00