Models in Engineering
MIT xPRO | Architecture and Systems Engineering: Models and Methods of Complex Systems
Course Project Sequence | April 2026 - May 2026
The Models in Engineering course focused on how engineering models are used to support system understanding, decision-making, verification, validation, and cross-domain analysis. The coursework emphasized model taxonomy, credibility, fidelity, decision support, federated modeling, model integration, and the role of models in reducing uncertainty across complex engineering systems.
Across the course, I applied these concepts through a combination of accident analysis, organizational modeling, multi-domain model integration, and verification and validation planning. The coursework connected historical engineering model use, such as the STS-107 Columbia accident analysis, with practical modeling challenges in complex electromechanical systems.
Week 1: What is a Model? — STS-107 Model Taxonomy and Decision Analysis
This project analyzed how models were used during and after the STS-107 Columbia accident. The work categorized image analysis, transport analysis, CART3D computational fluid dynamics modeling, and ballistic coefficient analysis according to model taxonomy, credibility, and fidelity.
The project also evaluated how the available models affected engineering decision-making. The analysis emphasized that models may provide useful decision support while still being limited by uncertainty, incomplete data, poor image quality, assumptions, or insufficient fidelity for operational decisions.
Concepts demonstrated:
Model taxonomy
Mathematical and simulation models
Physical evidence as model input
Model credibility and fidelity
Decision-making under uncertainty
Safety-critical model interpretation
Week 2: Model Review and Peer Commentary — In-Course Activity
This course activity involved reviewing and commenting on pre-existing project submissions within the course platform. Because the work was completed directly inside the course system as a commentary and peer-review activity, there was no standalone document or artifact to display publicly.
Although it is not presented as a portfolio artifact, this activity supported the broader course objective of evaluating how engineering models are communicated, interpreted, and critiqued by others.
Concepts demonstrated:
Model critique
Peer review
Engineering communication
Model interpretation
Evaluation of model clarity and usefulness
Week 3: Joining Several Models Together — Federated Change-Impact Modeling
This project explored how several models from different engineering domains can be connected to support subsystem change-impact analysis. The selected use case focused on a mechanical/electrical subsystem installation, where a single design change can affect arrangement models, electrical interface drawings, cable routing, procurement specifications, installation documentation, requirements, and verification planning.
The proposed approach used separate but connected models instead of one fully combined model. This federated modeling strategy allows each discipline to maintain its own model while linking information through common interface IDs, requirements, configuration baselines, and verification records.
Concepts demonstrated:
Federated modeling
Multi-domain model integration
Change-impact analysis
Cross-domain traceability
Interface IDs and configuration baselines
Model maintainability and ownership
Qualities of great models
Week 4: Models in Verification and Validation — Manned Research Submersible
This project developed a verification and validation framework for an integrated mechanical/electrical subsystem installation package for a Manned Research Submersible. The work considered product and process V&V across system, subsystem/function, part, and feature levels.
The project identified model, prototype, production-intent, and post-production V&V options. It also elaborated on a subsystem interface verification model that connects requirements, subsystem functions, physical components, interface definitions, installation documentation, and acceptance test steps.
The model was evaluated as highly useful for identifying missing interfaces, incomplete requirements traceability, unclear ownership, missing test coverage, and documentation gaps before physical installation begins.
Concepts demonstrated:
Verification and validation planning
Product and process V&V
System, subsystem, part, and feature-level analysis
Interface verification
Requirements-to-test traceability
Production-intent testing
Post-production evidence
Integration-risk reduction