Omar Ochoa

Dr. Omar Ochoa

orcid

Research Focus & Metrics

Academic Career Length

15Years (2012-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
19 November 2022 in Engineering Applications of Artificial Intelligence
Verified
Journal Article
Closed access
LHLynn Vonder Haar
Lynn Vonder Haar
TETimothy Elvira
Timothy Elvira
OOOmar Ochoa
Omar Ochoa

1 January 2012 in International Journal of Reliability and Safety
Verified
Journal Article
Closed access
OOOmar Ochoa
Omar Ochoa
AVAaron A. Velasco
Aaron A. Velasco
CSChristian Servin
Christian Servin
VKVladik Kreinovich
Vladik Kreinovich
One of the most important studies of the earth sciences is that of the Earth’s interior structure. There are many sources of data for the construction of tomographic models of earth structure. These include the time of the first arriving waves from earthquakes and from man-made sources, measurements of the earth’s gravity field and measurements of the dispersion of surface waves generated from earthquakes. Formally integrating the information derived from multiple types of data sources is an important theoretical and practical challenge. While such combination methods are being developed, as a first step, we propose a practical solution: to fuse the Earth models coming from different data sets. The models used in this paper contain measurements that have not only different accuracy and coverage but also different spatial resolution. We describe how to fuse such models under interval and probabilistic uncertainty. The resulting techniques can be used in other situations when we need to merge models of different accuracy and spatial resolution.

14 February 2026 in Software
Verified
Journal Article
Open access
PDF file
LVLynn Vonderhaar
Lynn Vonderhaar
JCJuan Ortiz Couder
Juan Ortiz Couder
TPTyler Procko
Tyler Procko
ELEva Lueddeke
Eva Lueddeke
DCDaryela Cisneros
Daryela Cisneros
OOOmar Ochoa
Omar Ochoa
Machine learning (ML) engineering increasingly incorporates principles from software and requirements engineering to improve development rigor; however, key non-functional requirements (NFRs) such as interpretability and explainability remain difficult to specify and verify using traditional requirements practices. Although prior work defines these qualities conceptually, their lack of measurable criteria prevents systematic verification. This paper presents a novel provenance-driven approach that decomposes ML interpretability and explainability NFRs into verifiable functional requirements (FRs) by leveraging model and data provenance to make model behavior transparent. The approach identifies the specific provenance artifacts required to validate each FR and demonstrates how their verification collectively establishes compliance with interpretability and explainability NFRs. The results show that ML provenance can operationalize otherwise abstract NFRs, transforming interpretability and explainability into quantifiable, testable properties and enabling more rigorous, requirements-based ML engineering.

27 October 2025 in IEEE Access
Verified
Journal Article
Open access
LNLuke Newcomb
Luke Newcomb
ANAlexandra Newcomb
Alexandra Newcomb
OOOmar Ochoa
Omar Ochoa
ADAlexanda Davidoff
Alexanda Davidoff
Large Language Models (LLMs) have significantly advanced automated code generation, but current methods predominantly rely on natural language descriptions during prompting. This approach encounters challenges when handling complex, class-level software generation tasks due to inherent ambiguity and under-specification. On the other hand, few studies have investigated how formal software engineering constraints, such as explicit preconditions and postconditions as part of the Design-by-Contract paradigm, influence class-level generation tasks. This work addresses this gap through a structured evaluation of six state-of-the-art LLMs generating complete software implementations of a medium complexity system from systematically designed class-level specifications. Results demonstrate that incorporating explicit design constraints during prompting significantly boosts initial generation accuracy (measured via the pass@k metric), particularly in Python but also in C++. Models with fewer parameters saw especially pronounced benefits. These findings suggest integrating structured software engineering constraints and design principles into LLM-based code generation workflows to enhance accuracy and maintainability in automated software projects.

26 February 2026 in International Journal on Artificial Intelligence Tools
Verified
Journal Article
Closed access
LVLynn Vonderhaar
Lynn Vonderhaar
TETimothy Elvira
Timothy Elvira
OOOmar Ochoa
Omar Ochoa

13 October 2024
Verified
Conference Paper
Closed access
JCJuan Ortiz Couder
Juan Ortiz Couder
WPWilliam C. Pate
William C. Pate
DMDaniel A. Machado
Daniel A. Machado
OOOmar Ochoa
Omar Ochoa
During the Software Development Lifecycle (SDLC), the first stage entails the Requirement Engineering phase. In this phase, engineers gather, analyze, and specify the requirements for a software system. Requirements playa crucial role in the SDLC as they establish the foundation for the entire system by defining the expected behaviors of the software system to be built. The resulting specifications are captured in a Software Requirement Specification (SRS) document. As part of the validation process, requirement specifications are traced. Requirement tracing involves linking the requirement to the artifacts where the customer requested the high-level requirement. Teaching proper requirements tracing can be challenging in a traditional classroom setting. It is essential to educate future software engineers on the proper process of developing an SRS document and of tracing requirements back to the originating artifact, which is also challenging due to the complexity and large scope of applying the complete requirements engineering process. Understanding how changes in customer needs can impact requirements is an imperative learning opportunity. In this work, we aim to incorporate the use of AI in the teaching of requirements tracing using Large Language Models. In this experiment, both GPT -3.5 and GPT -4 are provided the transcript of an interview between the customer and the engineering team, as well as the subsequent requirements elicited from that meeting and other customer provided artifacts. The GPTs are then instructed to determine which requirements can be traced back to the interview transcript. At the same time, the students (the requirements engineering team) conduct their own effort to trace requirements back to the original interview. The experiment was taken one step further to assess students' and the GPTs abilities to address requirements modifications. After another interview with the customer, where some needs were changed, some requirements were modified, and students, and GPTs were asked to trace the modified requirements to the new interview. The results proved that students are better than both GPT versions at tracing modified requirements, yet GPTs again identified requirements that students didn't trace back. The findings, illustrate that AI can help in the teaching of requirement tracing; these results suggest that while no AI model is currently capable of replacing real requirement engineers as they don't outperform students, it can be used as a tool to test the completeness of the requirement tracing process. We posit that GPT can be a tool for students to self-assess the degree to which their own requirements tracing is exhaustive.