Huss, Moe, authorHerber, Daniel R., advisorBorky, John M., advisorMiller, Erika, committee memberMallette, Paul, committee member2024-01-012024-01-012023https://hdl.handle.net/10217/237446Model-Based Systems Engineering (MBSE) is an architecture-based software development approach. Agile, on the other hand, is a light system development approach that originated in software development. To bring together the benefits of both approaches, this research is divided into two stages. The first stage proposes an integrated Agile MBSE approach that adopts a specific instance of the Agile approach (i.e., Scrum) in combination with a specific instance of an MBSE approach (i.e., Model-Based System Architecture Process — "MBSAP") to create an Agile MBSE approach called the integrated Scrum Model Based System Architecture Process (sMBSAP). The proposed approach was validated through an experimental study that developed a health technology system over one year, successfully producing the desired software product. This work focuses on determining whether the proposed sMBSAP approach can deliver the desired Product Increments with the support of an MBSE process. The interaction of the Product Development Team with the MBSE tool, the generation of the system model, and the delivery of the Product Increments were observed. The results showed that the proposed approach contributed to achieving the desired system development outcomes and, at the same time, generated complete system architecture artifacts that would not have been developed if Agile had been used alone. Therefore, the first contribution of this stage lies in introducing a practical and operational method for merging Agile and MBSE. In parallel, the results suggest that sMBSAP is a middle ground that is more aligned with federal and state regulations, as it addresses the technical debt concerns. The second stage of this research compares Reliability of Estimation, Productivity, and Defect Rate metrics for sprints driven by Scrum versus sMBSAP through the experimental study in stage 1. The quasi-experimental study conducted ten sprints using each approach. The approaches were then evaluated based on their effectiveness in helping the Product Development Team estimate the backlog items they can build during a time-boxed sprint and deliver more Product Backlog Items (PBI) with fewer defects. The Commitment Reliability (CR) was calculated to compare the Reliability of Estimation with a measured average Scrum-driven value of 0.81 versus a statistically different average sMBSAP-driven value of 0.94. Similarly, the average Sprint Velocity (SV ) for the Scrum-driven sprints was 26.8 versus 31.8 for the MBSAP-driven sprints. The average Defect Density (DD) for Scrum-driven sprints was 0.91, while that of sMBSAP-driven sprints was 0.63. The average Defect Leakage (DL) for Scrum-driven sprints was 0.20, while that of sMBSAP-driven sprints was 0.15. The t-test analysis concluded that the sMBSAP-driven sprints were associated with a statistically significant larger mean CR, SV , DD, and DL than that of the Scrum-driven sprints. The overall results demonstrate formal quantitative benefits of an Agile MBSE approach compared to Agile alone, strengthening the case for considering Agile MBSE methods within the software development community. Future work might include comparing Agile and Agile MBSE methods using alternative research designs and further software development objectives, techniques, and metrics. Future investigations may also test sMBSAP with non-software systems to validate the methodology across other disciplines.born digitaldoctoral dissertationsengCopyright and other restrictions may apply. User is responsible for compliance with all applicable laws. For information about copyright law, please see https://libguides.colostate.edu/copyright.model-based software engineering (MBSE)Scrumsystem architecturemodelingagilesoftware developmentText