Software developers’ engagement in open-source software projects lies in different levels of participation, e.g., core or peripheral developers. Recent studies have investigated the role of developers’ contributions and their influence on software quality. However, few studies investigate the relationship between the developers’ experience and test code quality in software projects. In this study, we aim to investigate the relationship between the developers’ experience and the test code quality from the perspective of test smells. We performed an empirical study to analyze the insertion and removal of test smells in four open-source Java projects. We collected 18 test smells and calculated their authorship through the projects’ Tags. The four software projects, we analyze 386 test classes and 5,178 test smells. We found out that the insertion of 67.28% of test smells occurs during the test class creation, and the removal of 20.88% of test smells occurs during the evolution of projects. In addition, core developers are responsible for inserting 88.91% and removing 89.82% test smells. Core developers insert and remove more test smells than the peripheral developers. Most test smell removal is due to test code deletion, which may indicate that both core and peripheral developers are unaware of test smells in test code.
{"title":"An empirical study on the influence of developers’ experience on software test code quality","authors":"Denivan Campos, L. Martins, Ivan Machado","doi":"10.1145/3571473.3571481","DOIUrl":"https://doi.org/10.1145/3571473.3571481","url":null,"abstract":"Software developers’ engagement in open-source software projects lies in different levels of participation, e.g., core or peripheral developers. Recent studies have investigated the role of developers’ contributions and their influence on software quality. However, few studies investigate the relationship between the developers’ experience and test code quality in software projects. In this study, we aim to investigate the relationship between the developers’ experience and the test code quality from the perspective of test smells. We performed an empirical study to analyze the insertion and removal of test smells in four open-source Java projects. We collected 18 test smells and calculated their authorship through the projects’ Tags. The four software projects, we analyze 386 test classes and 5,178 test smells. We found out that the insertion of 67.28% of test smells occurs during the test class creation, and the removal of 20.88% of test smells occurs during the evolution of projects. In addition, core developers are responsible for inserting 88.91% and removing 89.82% test smells. Core developers insert and remove more test smells than the peripheral developers. Most test smell removal is due to test code deletion, which may indicate that both core and peripheral developers are unaware of test smells in test code.","PeriodicalId":440784,"journal":{"name":"Proceedings of the XXI Brazilian Symposium on Software Quality","volume":"42 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-11-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123880186","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
User Interface Prototyping is a resource for exploring and communicating ideas, which is largely used in software development in activities like requirements elicitation or product discovery. Existing works indicate that the use of prototyping can be related to the improvement of software quality. Therefore, we conducted a survey with practitioners from the software industry to investigate how prototyping has been used in quality assurance activities. As a result, we identified different development process models that adopt prototyping to support various activities, such as the identification of new technologies to be adopted, the definition of user stories, planning activities, identification of business rules and navigation flows, front-end and back-end implementation, reviews, and tests. However, we also identified prototyping-related problems, such as teams from the same company using prototyping in a non-standard way, or the use of outdated prototypes during tests, approval, and training phases. In this way, we verified that the adoption of prototyping as a tool to support the software development process must follow usage rules explicitly defined in the development process and clearly communicated to developers, so they can positively influence the improvement of the quality of software.
{"title":"Prototyping in Software Quality Assurance: A Survey With Software Practitioners","authors":"G. T. De Macedo, A. Fontão, B. Gadelha","doi":"10.1145/3571473.3571477","DOIUrl":"https://doi.org/10.1145/3571473.3571477","url":null,"abstract":"User Interface Prototyping is a resource for exploring and communicating ideas, which is largely used in software development in activities like requirements elicitation or product discovery. Existing works indicate that the use of prototyping can be related to the improvement of software quality. Therefore, we conducted a survey with practitioners from the software industry to investigate how prototyping has been used in quality assurance activities. As a result, we identified different development process models that adopt prototyping to support various activities, such as the identification of new technologies to be adopted, the definition of user stories, planning activities, identification of business rules and navigation flows, front-end and back-end implementation, reviews, and tests. However, we also identified prototyping-related problems, such as teams from the same company using prototyping in a non-standard way, or the use of outdated prototypes during tests, approval, and training phases. In this way, we verified that the adoption of prototyping as a tool to support the software development process must follow usage rules explicitly defined in the development process and clearly communicated to developers, so they can positively influence the improvement of the quality of software.","PeriodicalId":440784,"journal":{"name":"Proceedings of the XXI Brazilian Symposium on Software Quality","volume":"2010 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-11-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127353033","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
The human aspects of software development have received attention in recent years, especially with studies related to Developer Experience (DX). Activities related to development have a cognitive processing character. There is a link between affectivity (emotions, moods and feelings), cognitive processing and individual productivity. The objective of this study is to evaluate the DX in the development teams in the public service, in the environment of the Municipality. To achieve this objective, we used the correlation between the affective dimensions of valence, arousal and dominance with self-assessed productivity (sPR). This correlation measures the impact of affectivity effects on the productivity of development activities. The study was carried out with 11 municipal public service software development professionals in their daily activities through the use of interviews, questionnaires and the Self-Assessment Manikin (SAM) technique. The results demonstrate the importance of DX assessment in individual productivity, valuing human aspects and their influence on software development.
{"title":"Assessing DX through the correlation between affectivity and self-assessed productivity in a public institution","authors":"F. Lopes, A. Oran, B. Gadelha","doi":"10.1145/3571473.3571494","DOIUrl":"https://doi.org/10.1145/3571473.3571494","url":null,"abstract":"The human aspects of software development have received attention in recent years, especially with studies related to Developer Experience (DX). Activities related to development have a cognitive processing character. There is a link between affectivity (emotions, moods and feelings), cognitive processing and individual productivity. The objective of this study is to evaluate the DX in the development teams in the public service, in the environment of the Municipality. To achieve this objective, we used the correlation between the affective dimensions of valence, arousal and dominance with self-assessed productivity (sPR). This correlation measures the impact of affectivity effects on the productivity of development activities. The study was carried out with 11 municipal public service software development professionals in their daily activities through the use of interviews, questionnaires and the Self-Assessment Manikin (SAM) technique. The results demonstrate the importance of DX assessment in individual productivity, valuing human aspects and their influence on software development.","PeriodicalId":440784,"journal":{"name":"Proceedings of the XXI Brazilian Symposium on Software Quality","volume":"153 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-11-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126952604","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Developing interactive systems is a challenging task that involves concerns related to the human-computer interaction (HCI), such as usability and user experience. Therefore, HCI design is a core issue to the quality of such systems. HCI design often involves people with different backgrounds (e.g., Arts, Software Engineering, Design). This makes knowledge transfer a challenging issue due to the lack of a common conceptualization about HCI design, leading to semantic interoperability problems, such as ambiguity and imprecision when interpreting shared information. Ontologies have been acknowledged as a successful approach to represent domain knowledge and support knowledge-based solutions. Hence, in this work, we propose to explore the use of ontologies to represent structured knowledge of HCI design and improve knowledge sharing in this context. We developed the Human-Computer Interaction Design Ontology (HCIDO), which is part of the Human-Computer Interaction Ontology Network (HCI-ON) and is connected to the Software Engineering Ontology Network (SEON). By making knowledge related to the HCI design domain explicit and structured, HCIDO helped us to develop KTID, a tool that aims to support capturing and sharing knowledge to aid in HCI design by allowing HCI designers to annotate information about design choices in design artifacts shared with HCI design stakeholders. Preliminary results indicate that the tool can be particularly useful for novice HCI designers.
{"title":"An Ontology to support Knowledge Management Solutions for Human-Computer Interaction Design","authors":"Murillo V. H. B. Castro, M. Barcellos","doi":"10.1145/3571473.3571502","DOIUrl":"https://doi.org/10.1145/3571473.3571502","url":null,"abstract":"Developing interactive systems is a challenging task that involves concerns related to the human-computer interaction (HCI), such as usability and user experience. Therefore, HCI design is a core issue to the quality of such systems. HCI design often involves people with different backgrounds (e.g., Arts, Software Engineering, Design). This makes knowledge transfer a challenging issue due to the lack of a common conceptualization about HCI design, leading to semantic interoperability problems, such as ambiguity and imprecision when interpreting shared information. Ontologies have been acknowledged as a successful approach to represent domain knowledge and support knowledge-based solutions. Hence, in this work, we propose to explore the use of ontologies to represent structured knowledge of HCI design and improve knowledge sharing in this context. We developed the Human-Computer Interaction Design Ontology (HCIDO), which is part of the Human-Computer Interaction Ontology Network (HCI-ON) and is connected to the Software Engineering Ontology Network (SEON). By making knowledge related to the HCI design domain explicit and structured, HCIDO helped us to develop KTID, a tool that aims to support capturing and sharing knowledge to aid in HCI design by allowing HCI designers to annotate information about design choices in design artifacts shared with HCI design stakeholders. Preliminary results indicate that the tool can be particularly useful for novice HCI designers.","PeriodicalId":440784,"journal":{"name":"Proceedings of the XXI Brazilian Symposium on Software Quality","volume":"86 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-11-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"117283065","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Everton Luis Luz De Quadros, A. Lisboa, Marilaine Quadros Becker Souza, R. Prikladnicki, M. Chaves
Context: many tech companies have had to adapt their software development processes to the reality of forced remote work due to COVID-19. Later, many of these companies transitioned to hybrid work, interspersing remote work with face-to-face work. Goal: this article aims to understand the challenges and impacts of this transition to software quality and to create hybrid software development teams. Method: an empirical study was carried out in the technology department of a Brazilian multinational company, using a multivocal literature review combined with a field study with semi-structured interviews and discursive textual analysis. Results: this study identified three main dimensions of the impact of the transition from remote to hybrid model: people, processes, and organization. In each of them, specific items were identified and will be detailed in this article. Conclusions: permanent or hybrid remote work models have enormous challenges and require studies in the specific scenarios of each company. It is necessary to understand these challenges to propose solutions that simultaneously facilitate the work of teams and guarantee the quality of the projects.
{"title":"The migration from forced remote work to hybrid work and its impacts on software quality: the case of a multinational company","authors":"Everton Luis Luz De Quadros, A. Lisboa, Marilaine Quadros Becker Souza, R. Prikladnicki, M. Chaves","doi":"10.1145/3571473.3571498","DOIUrl":"https://doi.org/10.1145/3571473.3571498","url":null,"abstract":"Context: many tech companies have had to adapt their software development processes to the reality of forced remote work due to COVID-19. Later, many of these companies transitioned to hybrid work, interspersing remote work with face-to-face work. Goal: this article aims to understand the challenges and impacts of this transition to software quality and to create hybrid software development teams. Method: an empirical study was carried out in the technology department of a Brazilian multinational company, using a multivocal literature review combined with a field study with semi-structured interviews and discursive textual analysis. Results: this study identified three main dimensions of the impact of the transition from remote to hybrid model: people, processes, and organization. In each of them, specific items were identified and will be detailed in this article. Conclusions: permanent or hybrid remote work models have enormous challenges and require studies in the specific scenarios of each company. It is necessary to understand these challenges to propose solutions that simultaneously facilitate the work of teams and guarantee the quality of the projects.","PeriodicalId":440784,"journal":{"name":"Proceedings of the XXI Brazilian Symposium on Software Quality","volume":"79 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-11-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124174941","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Sara Mendes Oliveira Lima, Denivan Campos, I. Machado
In software testing, employing regression techniques is a viable strategy to deal with the complexity and the constant evolution of applications since its primary goal is to ensure that changes made between versions do not change the system’s behavior. Although the literature has dedicated efforts to developing new regression testing techniques suitable for the Android mobile platform, studies are limited concerning demonstrating which techniques software developers employ in practice. This study aims to report on a thematic synthesis of adopting regression testing techniques in Android projects. The research encompassed four stages: (i) conducting a structured literature review on regression testing techniques for the Android platform, (ii) carrying out an expert survey, (iii) conducting interviews with industry professionals, and (iv) building a thematic synthesis. The thematic synthesis presented a model from analyzing the results obtained in this multimethod study on regression testing techniques. With such a study, we could present empirical evidence on how professionals perform regression testing in Android projects, identify the commonly used regression testing techniques, and leverage the requirements for automating Android applications through regression testing.
{"title":"A thematic synthesis on the adoption of regression testing techniques in Android projects","authors":"Sara Mendes Oliveira Lima, Denivan Campos, I. Machado","doi":"10.1145/3571473.3571485","DOIUrl":"https://doi.org/10.1145/3571473.3571485","url":null,"abstract":"In software testing, employing regression techniques is a viable strategy to deal with the complexity and the constant evolution of applications since its primary goal is to ensure that changes made between versions do not change the system’s behavior. Although the literature has dedicated efforts to developing new regression testing techniques suitable for the Android mobile platform, studies are limited concerning demonstrating which techniques software developers employ in practice. This study aims to report on a thematic synthesis of adopting regression testing techniques in Android projects. The research encompassed four stages: (i) conducting a structured literature review on regression testing techniques for the Android platform, (ii) carrying out an expert survey, (iii) conducting interviews with industry professionals, and (iv) building a thematic synthesis. The thematic synthesis presented a model from analyzing the results obtained in this multimethod study on regression testing techniques. With such a study, we could present empirical evidence on how professionals perform regression testing in Android projects, identify the commonly used regression testing techniques, and leverage the requirements for automating Android applications through regression testing.","PeriodicalId":440784,"journal":{"name":"Proceedings of the XXI Brazilian Symposium on Software Quality","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-11-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128999584","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Eder Pereira Santos, Felipe G. S. Gomes, Sávio Freire, Manoel G. Mendonça, T. Mendes, R. Spínola
Context: The literature has proposed different approaches for Agile software development technical debt (ASD-TD) management, they are usually based on the point of view of software developers. Little is known about how project management practitioners actually perceive ASD-TD. Goal: To investigate how managers commonly discuss, experience, and manage ASD-TD, as well as roles, artifacts, and practices affected by ASD-TD extracted from Stack Exchange Project Management (SEPM). Method: We compiled 79 ASD-TD discussions from SEPM, and analyzed them quantitatively and qualitatively. Results: We identified 51 indicators used by managers to recognize ASD-TD items. The most commonly discussed types of TD are process and people debt. In addition, the Product Owner and Development Team are the most important roles with respect to ASD-TD. Sprint Backlog and Sprint Planning are the agile elements most affected by ASD-TD. We organized the TD indicators, roles involved, and agile elements affected by ASD-TD into a Mind Map. Conclusion: The perspective considered by project management practitioners to analyze the ASD-TD phenomenon is different from the one considered by other roles in agile software development.
{"title":"Technical Debt on Agile Projects: Managers’ point of view at Stack Exchange","authors":"Eder Pereira Santos, Felipe G. S. Gomes, Sávio Freire, Manoel G. Mendonça, T. Mendes, R. Spínola","doi":"10.1145/3571473.3571500","DOIUrl":"https://doi.org/10.1145/3571473.3571500","url":null,"abstract":"Context: The literature has proposed different approaches for Agile software development technical debt (ASD-TD) management, they are usually based on the point of view of software developers. Little is known about how project management practitioners actually perceive ASD-TD. Goal: To investigate how managers commonly discuss, experience, and manage ASD-TD, as well as roles, artifacts, and practices affected by ASD-TD extracted from Stack Exchange Project Management (SEPM). Method: We compiled 79 ASD-TD discussions from SEPM, and analyzed them quantitatively and qualitatively. Results: We identified 51 indicators used by managers to recognize ASD-TD items. The most commonly discussed types of TD are process and people debt. In addition, the Product Owner and Development Team are the most important roles with respect to ASD-TD. Sprint Backlog and Sprint Planning are the agile elements most affected by ASD-TD. We organized the TD indicators, roles involved, and agile elements affected by ASD-TD into a Mind Map. Conclusion: The perspective considered by project management practitioners to analyze the ASD-TD phenomenon is different from the one considered by other roles in agile software development.","PeriodicalId":440784,"journal":{"name":"Proceedings of the XXI Brazilian Symposium on Software Quality","volume":"114 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-11-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127325337","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Agile Software Development Methods (ASDMs) have addressed the complexity of managing software development processes through small increments, continuous and frequent delivery, openness to change, and work visibility. These practices have been complemented by the use metrics adapted to ASDMs context, generating a large number and types of metrics. Thus, this secondary study presents a Systematic Literature Mapping to understand how agile organizations use metrics. Seven research questions were defined, and 33 primary studies related to the use of agile metrics were selected. The results indicate that most organizations that use agile metrics use Scrum, develop large size general-purpose software products, desktop, or web applications, in small teams. The metrics are selected by primary studies based on literature search, interviews with the team members or expert groups. The majority of the organizations use Product Quality, Resource and Cost, and Process performance metrics, focusing in the agile team, management and customer. The primary studies results indicate that using agile metrics can positively impact the quality of processes, products, and services.
{"title":"How Agile Organizations Use Metrics: A Systematic Literature Mapping","authors":"S. Leal, J. Hauck, Monique Bertan, Gustavo Vieira","doi":"10.1145/3571473.3571479","DOIUrl":"https://doi.org/10.1145/3571473.3571479","url":null,"abstract":"Agile Software Development Methods (ASDMs) have addressed the complexity of managing software development processes through small increments, continuous and frequent delivery, openness to change, and work visibility. These practices have been complemented by the use metrics adapted to ASDMs context, generating a large number and types of metrics. Thus, this secondary study presents a Systematic Literature Mapping to understand how agile organizations use metrics. Seven research questions were defined, and 33 primary studies related to the use of agile metrics were selected. The results indicate that most organizations that use agile metrics use Scrum, develop large size general-purpose software products, desktop, or web applications, in small teams. The metrics are selected by primary studies based on literature search, interviews with the team members or expert groups. The majority of the organizations use Product Quality, Resource and Cost, and Process performance metrics, focusing in the agile team, management and customer. The primary studies results indicate that using agile metrics can positively impact the quality of processes, products, and services.","PeriodicalId":440784,"journal":{"name":"Proceedings of the XXI Brazilian Symposium on Software Quality","volume":"28 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-11-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115575157","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Teaching software requirements specifications can be challenging since students must learn the notations and representation of the problem domain in different software development contexts. So, one of the factors that impact the quality of requirements specifications can be the type of training received by software engineers. Given this context, In this paper, we present an exploratory study about the application of three different approaches for requirements specifications: in a traditional software context, applying UML Use Cases; in an agile context with User Stories; and a new technique proposed in Design Thinking (DT) context. We analyzed undergraduate students’ perceptions about the application of each one, including the ease, difficulty, usefulness, and adoption in future projects. The results present the participants’ perceptions about the techniques, and point out that the User Story is the easiest, and the most limited and most appropriate for the initial phases of a software process. The Use Case and the UJB shared a good part of the difficulties and facilities. But, the latter offers a wider range in relation to its use. The article shows SE teachers the benefits that each approach can offer not only for the specification of requirements, but for the entire software development process. Our research benefits instructors interested in understanding the students’ perceptions about software requirements specifications in such contexts, contributing to software quality teaching of them.
{"title":"What do students prefer - Use Cases, User Story or Design Thinking Techniques?","authors":"J. C. Duarte, Adriana Lopes Damian, T. Conte","doi":"10.1145/3571473.3571475","DOIUrl":"https://doi.org/10.1145/3571473.3571475","url":null,"abstract":"Teaching software requirements specifications can be challenging since students must learn the notations and representation of the problem domain in different software development contexts. So, one of the factors that impact the quality of requirements specifications can be the type of training received by software engineers. Given this context, In this paper, we present an exploratory study about the application of three different approaches for requirements specifications: in a traditional software context, applying UML Use Cases; in an agile context with User Stories; and a new technique proposed in Design Thinking (DT) context. We analyzed undergraduate students’ perceptions about the application of each one, including the ease, difficulty, usefulness, and adoption in future projects. The results present the participants’ perceptions about the techniques, and point out that the User Story is the easiest, and the most limited and most appropriate for the initial phases of a software process. The Use Case and the UJB shared a good part of the difficulties and facilities. But, the latter offers a wider range in relation to its use. The article shows SE teachers the benefits that each approach can offer not only for the specification of requirements, but for the entire software development process. Our research benefits instructors interested in understanding the students’ perceptions about software requirements specifications in such contexts, contributing to software quality teaching of them.","PeriodicalId":440784,"journal":{"name":"Proceedings of the XXI Brazilian Symposium on Software Quality","volume":"104 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-11-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132499500","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
André Ximenes, C. Alves, Jéssyka Vilela, Iveruska Jatobá
Context: In recent years, public organizations are adopting new technologies and innovating processes to improve the quality of services provided to society. In the context of digital transformation, in addition to the use of new technologies, organizations need to transform their culture and acquire new competencies so that teams can change their mindset and adopt innovative work practices. Problem: Digital transformation requires changes in internal processes, as well as in the technical and behavioral skills of teams, involving new ways of evaluating and directing the professional development of employees. Method: We conducted a case study at a public organization where a competency management model was developed based on the analysis of internal documentation and discussions with the organization’s stakeholders. The evaluation of the proposed model was carried out through a focus group with 11 professionals. Results: The article describes a competency management model to support digital transformation and business process improvement projects. The competency management model includes 4 roles and 37 competencies for teams. The model includes a competency matrix to map and assess the competencies needed for each role and actions to develop new competencies. Lessons Learned: Our experience suggests that developing competencies to support digital transformation initiatives requires establishing a shared alignment and a long-term vision to ensure effective organizational learning.
{"title":"A Competency Management Model to Support Digital Transformation Initiatives in a Public Organization","authors":"André Ximenes, C. Alves, Jéssyka Vilela, Iveruska Jatobá","doi":"10.1145/3571473.3571490","DOIUrl":"https://doi.org/10.1145/3571473.3571490","url":null,"abstract":"Context: In recent years, public organizations are adopting new technologies and innovating processes to improve the quality of services provided to society. In the context of digital transformation, in addition to the use of new technologies, organizations need to transform their culture and acquire new competencies so that teams can change their mindset and adopt innovative work practices. Problem: Digital transformation requires changes in internal processes, as well as in the technical and behavioral skills of teams, involving new ways of evaluating and directing the professional development of employees. Method: We conducted a case study at a public organization where a competency management model was developed based on the analysis of internal documentation and discussions with the organization’s stakeholders. The evaluation of the proposed model was carried out through a focus group with 11 professionals. Results: The article describes a competency management model to support digital transformation and business process improvement projects. The competency management model includes 4 roles and 37 competencies for teams. The model includes a competency matrix to map and assess the competencies needed for each role and actions to develop new competencies. Lessons Learned: Our experience suggests that developing competencies to support digital transformation initiatives requires establishing a shared alignment and a long-term vision to ensure effective organizational learning.","PeriodicalId":440784,"journal":{"name":"Proceedings of the XXI Brazilian Symposium on Software Quality","volume":"129 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-11-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132045069","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：