Camilo Almendra
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Previous Organizations / Institutes
The organizations / institutes from the scholar's other articles in the past ten years
Camilo Almendra has a total of 21 co-authors. Here are the top co-authors by number of shared publications:
- Lincoln Rocha
Federal University of Ceará
3 shared publications - Carla Silva
Universidade Federal de Pernambuco
2 shared publications - Peter Hamfelt
Roxtec Group
2 shared publications - Ricardo Britto
Department of Software Engineering, Blekinge Institute of Technology, Karlskrona, Sweden and Ericsson, Stockholm, Sweden
2 shared publications - Cesar Lincoln Cavalcante Mattos
Universidade Federal do Ceará
1 shared publication - David Campelo
Aveiro University
1 shared publication
Latest Publications
- 4 November 2025
- Published by Sociedade Brasileira de Computação
- p. 204-214
An Ontology for Safety Assurance Information Management
Context: Diverse information needs to be traced and managed throughout the development lifecycle of safety-critical systems, such as requirements, design definitions, tests and code. A safety-critical system (SCS) undergoes certification procedures that require the presentation of arguments supporting the design and implementation decisions involved in the SCS construction. Nowadays, many regulations require elaborating assurance cases (ACs) to present such arguments. The integrated management of the diverse data required to produce the ACs can leverage the continuous traceability assessment and support the automated generation of ACs at any time in the SCS lifecycle. Objective: Ontologies can integrate metamodels to connect data from different domains. We designed and implemented a Safety Assurance Ontology (SAO) to integrate outputs of safety and software engineering activities. SAO encompasses an information model, rules and competency questions to support the work of software, safety and assurance engineers in the context of an SCS development that requires the production of ACs. Method: SAO was built based on knowledge extracted from safety datasets and argumentation patterns. This work presents the SAO’s design, implementation, and evaluation through an illustrative scenario with public datasets and an expert survey with industrial practitioners and researchers. Results: SAO comprises concepts, relationships, and formation rules integrating safety assurance and software project information. We implemented the ontology information model and its formation rules using semantic web technologies. Conclusions: SAO can trace relevant project information, infer implicit information, and highlight traceability gaps in the public datasets evaluated. Practitioners find SAO’s competency questions on traceability gaps useful in revealing direct and indirect relationships among project items. They also find that the basic competency questions facilitate the contextualisation of items traced in the project repositories. Also, they pointed out that adding specialisations for key concepts can enhance practitioners’ grasp of the metamodel scope, thus promoting its applicability.
- 4 November 2025
- Published by Sociedade Brasileira de Computação
- p. 204-214
An Ontology for Safety Assurance Information Management
Context: Diverse information needs to be traced and managed throughout the development lifecycle of safety-critical systems, such as requirements, design definitions, tests and code. A safety-critical system (SCS) undergoes certification procedures that require the presentation of arguments supporting the design and implementation decisions involved in the SCS construction. Nowadays, many regulations require elaborating assurance cases (ACs) to present such arguments. The integrated management of the diverse data required to produce the ACs can leverage the continuous traceability assessment and support the automated generation of ACs at any time in the SCS lifecycle. Objective: Ontologies can integrate metamodels to connect data from different domains. We designed and implemented a Safety Assurance Ontology (SAO) to integrate outputs of safety and software engineering activities. SAO encompasses an information model, rules and competency questions to support the work of software, safety and assurance engineers in the context of an SCS development that requires the production of ACs. Method: SAO was built based on knowledge extracted from safety datasets and argumentation patterns. This work presents the SAO’s design, implementation, and evaluation through an illustrative scenario with public datasets and an expert survey with industrial practitioners and researchers. Results: SAO comprises concepts, relationships, and formation rules integrating safety assurance and software project information. We implemented the ontology information model and its formation rules using semantic web technologies. Conclusions: SAO can trace relevant project information, infer implicit information, and highlight traceability gaps in the public datasets evaluated. Practitioners find SAO’s competency questions on traceability gaps useful in revealing direct and indirect relationships among project items. They also find that the basic competency questions facilitate the contextualisation of items traced in the project repositories. Also, they pointed out that adding specialisations for key concepts can enhance practitioners’ grasp of the metamodel scope, thus promoting its applicability.
- Open Access
- 22 September 2025
- Published by Sociedade Brasileira de Computação
- p. 337-347
Automatic Identification of Machine Learning-Specific Code Smells
Machine learning (ML) has rapidly grown in popularity, becoming vital to many industries. Currently, the research on code smells in ML applications lacks tools and studies that address the identification and validity of ML-specific code smells. This work investigates suitable methods and tools to design and develop a static code analysis tool (MLpylint) based on code smell criteria. This research employed the Design Science Methodology. In the problem identification phase, a literature review was conducted to identify ML-specific code smells. In solution design, a secondary literature review and consultations with experts were performed to select methods and tools for implementing the tool.We evaluated the tool on data from 160 open-source ML applications sourced from GitHub. We also conducted a static validation through an expert survey involving 15 ML professionals. The results indicate the effectiveness and usefulness of the MLpylint. We aim to extend our current approach by investigating ways to introduce MLpylint seamlessly into development workflows, fostering a more productive and innovative developer environment.
- 22 September 2025
- Published by Sociedade Brasileira de Computação
- p. 337-347
Open AccessAutomatic Identification of Machine Learning-Specific Code Smells
Machine learning (ML) has rapidly grown in popularity, becoming vital to many industries. Currently, the research on code smells in ML applications lacks tools and studies that address the identification and validity of ML-specific code smells. This work investigates suitable methods and tools to design and develop a static code analysis tool (MLpylint) based on code smell criteria. This research employed the Design Science Methodology. In the problem identification phase, a literature review was conducted to identify ML-specific code smells. In solution design, a secondary literature review and consultations with experts were performed to select methods and tools for implementing the tool.We evaluated the tool on data from 160 open-source ML applications sourced from GitHub. We also conducted a static validation through an expert survey involving 15 ML professionals. The results indicate the effectiveness and usefulness of the MLpylint. We aim to extend our current approach by investigating ways to introduce MLpylint seamlessly into development workflows, fostering a more productive and innovative developer environment.
- Open Access
- 22 September 2025
- Published by Sociedade Brasileira de Computação
- p. 1028-1030
Evolving Practices in Distributed R&D&I Projects: Bridging Academia and Industry Through Lightweight Collaboration
This presentation reports the best practices and methods adopted by the Alan Turing Lab (ATLab) research group in the past years, running distributed research, development, and innovation (R&D&I) projects with a global industry partner. This work highlights the software engineering processes thatwere iteratively refined through years of collaboration.We also share insights in two domains where our researchers stand out: Visualization and Artificial Intelligence. This report may be useful for research groups and organizations beginning to engage in innovation partnerships.
- 22 September 2025
- Published by Sociedade Brasileira de Computação
- p. 1028-1030
Open AccessEvolving Practices in Distributed R&D&I Projects: Bridging Academia and Industry Through Lightweight Collaboration
This presentation reports the best practices and methods adopted by the Alan Turing Lab (ATLab) research group in the past years, running distributed research, development, and innovation (R&D&I) projects with a global industry partner. This work highlights the software engineering processes thatwere iteratively refined through years of collaboration.We also share insights in two domains where our researchers stand out: Visualization and Artificial Intelligence. This report may be useful for research groups and organizations beginning to engage in innovation partnerships.
- Open Access
Automatic Identification of Machine Learning-Specific Code Smells
Machine learning (ML) has rapidly grown in popularity, becoming vital to many industries. Currently, the research on code smells in ML applications lacks tools and studies that address the identification and validity of ML-specific code smells. This work investigates suitable methods and tools to design and develop a static code analysis tool (MLpylint) based on code smell criteria. This research employed the Design Science Methodology. In the problem identification phase, a literature review was conducted to identify ML-specific code smells. In solution design, a secondary literature review and consultations with experts were performed to select methods and tools for implementing the tool. We evaluated the tool on data from 160 open-source ML applications sourced from GitHub. We also conducted a static validation through an expert survey involving 15 ML professionals. The results indicate the effectiveness and usefulness of the MLpylint. We aim to extend our current approach by investigating ways to introduce MLpylint seamlessly into development workflows, fostering a more productive and innovative developer environment.
Open AccessAutomatic Identification of Machine Learning-Specific Code Smells
Machine learning (ML) has rapidly grown in popularity, becoming vital to many industries. Currently, the research on code smells in ML applications lacks tools and studies that address the identification and validity of ML-specific code smells. This work investigates suitable methods and tools to design and develop a static code analysis tool (MLpylint) based on code smell criteria. This research employed the Design Science Methodology. In the problem identification phase, a literature review was conducted to identify ML-specific code smells. In solution design, a secondary literature review and consultations with experts were performed to select methods and tools for implementing the tool. We evaluated the tool on data from 160 open-source ML applications sourced from GitHub. We also conducted a static validation through an expert survey involving 15 ML professionals. The results indicate the effectiveness and usefulness of the MLpylint. We aim to extend our current approach by investigating ways to introduce MLpylint seamlessly into development workflows, fostering a more productive and innovative developer environment.
- 9 February 2022
- Published by Springer Nature in Requirements Engineering
- Vol. 27 (2) , 273-292
How assurance case development and requirements engineering interplay: a study with practitioners
- 9 February 2022
- Published by Springer Nature in Requirements Engineering
- Vol. 27 (2) , 273-292
How assurance case development and requirements engineering interplay: a study with practitioners
- 12 December 2019
- Published by Springer Nature in Software and Systems Modeling
- Vol. 19 (3) , 763-784
Using empirical studies to mitigate symbol overload in iStar extensions
- 12 December 2019
- Published by Springer Nature in Software and Systems Modeling
- Vol. 19 (3) , 763-784
Using empirical studies to mitigate symbol overload in iStar extensions