M. ENGINEERING SYSTEMS
PORTFOLIO / 2026
INITIALIZING 00%
M.
A LITTLE SPACE TO BUILD BIG THINGS

WELCOME.

TO MOMNA'S ENGINEERING WORLD

CLOUD✳ DEVOPS✳ AUTOMATION✳ RELIABILITY✳ KUBERNETES✳ CLOUD✳ DEVOPS✳ AUTOMATION✳ RELIABILITY✳ KUBERNETES✳
SYSTEMS WITH PURPOSE
01 — 06
CASE STUDY 02 / MLOPS ENGINEERING
REPRODUCIBLE MACHINE LEARNING

From data
to model.

End-to-End MLOps Pipeline with DVC, MLflow & DagsHub

Building a reproducible machine learning workflow with data preprocessing, Random Forest training, evaluation and experiment tracking.

PYTHON SCIKIT-LEARN DVC MLFLOW DAGSHUB PANDAS NUMPY
ML PIPELINE / DATA FLOW 01 — 06
01
Raw dataset Pima Indians Diabetes Dataset
↓
02
Data preprocessing Transform raw data into processed data
↓
03
Model training Random Forest with parameter tuning
↓
04
Model evaluation Evaluate the saved model and calculate accuracy
↓
05
MLflow tracking Experiment parameters, metrics and artifacts
↘
06
DVC + DagsHub Pipeline versioning and remote collaboration
TRACK
REPRODUCIBLE WORKFLOW DATA → MODEL → TRACKING
PROJECT TYPE MLOps Pipeline
MODEL Random Forest
EXPERIMENT TRACKING MLflow
VERSIONING DVC / DagsHub
ENGINEERING SPECIFICATION MLOPS-02
R01

Pipeline orchestration

Separate preprocessing, model training and evaluation into defined stages managed through a DVC pipeline.

DVC PIPELINE
R02

Experiment tracking

Track training parameters, evaluation metrics and related artifacts with MLflow to make experiments easier to inspect.

MLFLOW
R03

Data & model versioning

Use DVC to manage pipeline definitions, dependencies and versioned project artifacts for repeatable execution.

VERSION CONTROL
R04

Remote collaboration

Use DagsHub with the project workflow to support remote data and artifact storage and experiment collaboration.

DAGSHUB
PIPELINE REQUIREMENTS R01 — R04
02 / PROBLEM & REQUIREMENTS
THE MLOPS CHALLENGE

A model is only one part. Reproducibility is the system.

A machine learning workflow involves more than fitting a model. Data preparation, experiment configuration, artifacts and evaluation must be organized into a repeatable process. This project structures those steps into a pipeline using DVC, MLflow and DagsHub.

01 PROJECT OBJECTIVE

Build a reproducible machine learning pipeline that connects data preprocessing, Random Forest model training and evaluation, while tracking experiments and managing versioned artifacts.

PROJECT SCOPE
01 Raw data → Preprocessing
02 Training → Experiment tracking
03 Evaluation → Versioned artifacts

03 / ARCHITECTURE & SYSTEM DESIGN

A reproducible pipeline from data to model.

The project organizes machine learning into three defined DVC stages: preprocessing, training and evaluation. DVC manages pipeline execution and versioned artifacts, while MLflow records experiment information. DagsHub supports the project's remote workflow.

CORE TECHNOLOGIES
Python Scikit-learn DVC MLflow DagsHub Pandas NumPy

ML pipeline architecture

Workflow flow
01

Dataset & configuration

Raw dataset, project parameters and pipeline definitions.

INPUT
02

Data preprocessing

The preprocessing stage prepares data for model training.

PREPROCESS
03

Model training

Train a Random Forest classifier and perform configured hyperparameter tuning.

TRAIN
04

Model evaluation

Load the saved model and calculate evaluation accuracy.

EVALUATE

Experiment & artifact management

DVC + MLFLOW

DVC defines the preprocessing, training and evaluation stages and manages versioned pipeline artifacts. MLflow tracks experiment parameters, metrics and artifacts. DagsHub provides the project's remote collaboration and storage environment.

↳ This diagram represents the repository's documented workflow. Experiment tracking and versioning are supporting capabilities, not additional sequential training stages. It does not imply a deployed prediction API or production model-serving layer.

04 / IMPLEMENTATION & CORE COMPONENTS

Every stage has a purpose.

This project separates data preprocessing, model training and evaluation into defined stages. DVC organizes the pipeline and its dependencies, MLflow records experiment information, and DagsHub supports remote collaboration around the workflow.

ENGINEERING PRINCIPLE

Keep preprocessing, training and evaluation independently identifiable, with pipeline dependencies and parameters defined in configuration. Track experiment results separately from the pipeline's stage order. This project demonstrates a reproducible training workflow—not a deployed production prediction service.

COMPONENT / 01 Data preparation

Preprocessing

The preprocessing stage prepares the dataset for the model-training workflow and produces the processed data used by later stages.

Source: src/preprocess.py
COMPONENT / 02 Model training

Random Forest training

Trains the classifier using the project's training workflow and includes GridSearchCV hyperparameter tuning.

Source: src/train.py
COMPONENT / 03 Evaluation

Model evaluation

Loads the saved model and calculates accuracy as part of the evaluation stage.

Source: src/evaluate.py
COMPONENT / 04 Orchestration

DVC pipeline

Defines preprocessing, training and evaluation stages, their dependencies and the pipeline configuration used for reproduction.

Source: dvc.yaml
COMPONENT / 05 Experiment tracking

MLflow

Records experiment parameters, evaluation metrics and associated artifacts so model-training runs can be inspected.

Role: Experiment records
COMPONENT / 06 Remote workflow

DagsHub

Provides the project's remote collaboration and storage environment alongside its DVC and MLflow workflow.

Role: Remote collaboration
05 / WORKFLOW & EXECUTION
ML PIPELINE LIFECYCLE

From raw data to evaluated model.

The MLOps workflow separates data preparation, model training and evaluation into defined stages. DVC coordinates pipeline execution, while MLflow records experiment information and DagsHub supports the project's remote workflow.

EXECUTION PRINCIPLE

A reproducible pipeline depends on explicit stages, configuration and tracked artifacts. Run the defined workflow, inspect each stage's output, and use the recorded evaluation rather than assuming model quality from successful execution alone.

PIPELINE EXECUTION SEQUENCE 01 — 04
01

Dataset & configuration

INPUT

Begin with the raw dataset and the project configuration. Parameters are defined separately so pipeline settings can be inspected and adjusted.

data/raw/ · params.yaml
02

Data preprocessing

PREPROCESS

The preprocessing script prepares the input data and produces the processed dataset used by the subsequent training stage.

src/preprocess.py
03

Model training & experiment logging

TRAIN

The training script fits a Random Forest classifier and performs GridSearchCV hyperparameter tuning. The workflow logs experiment parameters, metrics and related artifacts with MLflow.

src/train.py
04

Model evaluation

EVALUATE

The evaluation script loads the saved model and calculates accuracy. The resulting metric should be read from the actual run output rather than assumed in advance.

src/evaluate.py
PIPELINE COMMAND

dvc repro

Versioning & experiment records

DVC + MLFLOW + DAGSHUB

DVC defines and runs the pipeline stages and manages versioned data and model artifacts. MLflow records experiment parameters, metrics and artifacts. DagsHub provides the remote collaboration and storage environment used by the project.

↳ This timeline represents the repository's documented training and evaluation workflow. Experiment tracking and versioning support the stages; they are not extra sequential model-training steps. Successful pipeline execution alone does not establish a particular accuracy score or production deployment.
06 / VALIDATION & TECHNICAL EVIDENCE VERIFY BEFORE CLAIMING

Reproducibility needs evidence.

An MLOps pipeline should make its stages, training configuration and evaluation process inspectable. This section connects the implementation to the evidence needed to verify how the workflow behaves.

01

Verify pipeline execution

Run dvc repro in the configured project environment and inspect the actual command output. Do not label a run successful without observing its result.

02

Inspect experiment records

Check the MLflow tracking interface for recorded parameters, metrics and artifacts associated with an actual training run.

03

Confirm evaluation results

Use the evaluation output to report the real metric and its value. Explain what was measured instead of presenting a decorative metric as a result.

04

Check reproducibility

Review the tracked configuration, dependencies and outputs, then verify whether the workflow can be reproduced in the intended environment.

What counts as proof? A genuine execution log, experiment record or evaluation output that can be traced back to this repository.

07 / SECURITY, RELIABILITY & FAILURE HANDLING ENGINEERING RESPONSIBLY

Reliable workflows. Honest boundaries.

A reproducible ML workflow depends on more than training code. Credentials, pipeline dependencies, experiment records and evaluation outputs all need to be handled carefully. This review distinguishes documented project capabilities from operational safeguards that still require verification.

↳
CORE PRINCIPLE

Versioned artifacts and tracked experiments improve traceability, but do not automatically guarantee security, model quality or production reliability.

TECHNICAL REVIEW 04 FOCUS AREAS
01 / ACCESS
01
CREDENTIAL HYGIENE

Remote-service access

The project source contains tracking credential assignments. Do not treat source-code credentials as a secure secret management strategy. Use appropriately configured environment variables or a secrets manager, and rotate any exposed token.

SECURE CREDENTIALS
02 / PIPELINE
02
DEPENDENCIES & STATE

Track pipeline changes

DVC configuration and lock-file metadata help describe pipeline stages, dependencies and outputs. Inspect these files when investigating unexpected results or changes between runs.

REVIEW PIPELINE STATE
03 / TRACKING
03
EXPERIMENT TRACEABILITY

Review runs and artifacts

MLflow records configured experiment information such as parameters, metrics and artifacts. These records support investigation, but their completeness depends on what the implementation logs.

INSPECT EXPERIMENT RECORDS
04 / FAILURE
04
EXECUTION & VALIDATION

Investigate failed stages

Inspect command output, dependencies, parameters and the relevant pipeline stage before rerunning. Check evaluation output separately; do not infer model quality from a successful command alone.

DIAGNOSE BEFORE RETRYING
!

Implementation boundary

This project documents an MLOps pipeline. Do not claim automated rollback, production monitoring, a completed security audit or verified access controls without separate implementation evidence.

ENGINEERING ANALYSIS / 08

MLOps decision matrix

04 COMPONENTS
01 DVC Pipeline stages
02 Preprocess Data preparation
03 Train Model training
04 Evaluate Model assessment
ML
EXPERIMENT TRACKING & CONFIGURATION

MLflow supports experiment tracking, while params.yaml keeps configurable pipeline values in a dedicated file. DagsHub provides the project's remote collaboration and tracking context.

COMPONENT ENGINEERING VALUE TRADE-OFF
01 DVC

Defines pipeline stages and tracks pipeline state.

Requires maintained stage definitions and dependencies.

02 params.yaml

Separates supported configuration values from source code.

Configuration changes still require careful validation.

03 MLflow

Organizes experiment-tracking information for model development.

Useful comparisons depend on consistent logging and run records.

04 DagsHub

Connects the project with remote data-versioning and tracking workflows.

Remote operations depend on correct configuration and access.

DESIGN IMPLICATION

Reproducibility is a workflow design goal, not an automatic guarantee. Data, parameters, dependencies and experiment records must remain aligned for results to be meaningfully reproduced and compared.

MLOPS SYSTEM DESIGN

Reproducibility is built through deliberate decisions.

This project combines pipeline orchestration, configurable execution and experiment tracking. Each component serves a distinct purpose in making the model-development workflow easier to organize, inspect and maintain.

A

Separation of concerns

DVC manages pipeline structure while MLflow focuses on experiment tracking. They complement each other rather than replacing one another.

B

Reproducibility vs. complexity

Versioned pipeline definitions and externalized parameters improve traceability, but add configuration and dependency management responsibilities.

C

Tracking vs. production readiness

Experiment tracking supports model-development analysis. Production serving, deployment automation and monitoring remain separate capabilities—not assumed deliverables.

RESULTS / LIMITATIONS / LEARNINGS

Better workflows begin with measurable thinking.

This project brings data versioning, pipeline orchestration, model training, evaluation and experiment tracking into one structured MLOps workflow. Its value lies in the foundations it establishes—not in unverified performance claims.

A

Make experiments traceable

Separate experiment tracking from pipeline orchestration so model-development activity is easier to inspect.

B

Reproducibility needs discipline

Versioned data references, consistent parameters and maintained dependencies all contribute to repeatable work.

C

Evaluation is not deployment

Assessing a model is a distinct step from serving it in production. Deployment and production monitoring remain future extensions of this project.

PROJECT OUTCOMES / 09

What the implementation establishes

SCOPE REVIEW
01 IMPLEMENTED FOUNDATION

Structured ML workflow

The repository defines DVC pipeline stages for preprocessing, training and evaluation, supported by pipeline configuration and tracked state files.

dvc.yaml dvc.lock params.yaml
02 TRACKING FOUNDATION

Experiment visibility

MLflow tracking and DagsHub integration form part of the project's approach to organizing model-development activity and remote project resources.

!
LIMITATIONS / NEXT ITERATION

What still needs validation or extension

  • — Record actual evaluation metrics from a verified model run.
  • — Verify full pipeline reproducibility in a clean environment.
  • — Extend the workflow with deployment automation and production monitoring if required.
↗

Evidence-first reporting No accuracy score, runtime improvement or successful end-to-end run is claimed here without verified execution evidence.

Review source and pipeline files ↗
PROJECT RESOURCES / 10

Explore the implementation

SOURCE INDEX
GH OPEN REPOSITORY ↗
GITHUB REPOSITORY

MLOps Pipeline with DVC, MLflow & DagsHub

Review the project source, pipeline definitions, configuration and supporting implementation files.

github.com/momna-shahid17/mlops-dvc-mlflow-pipeline
IMPLEMENTATION FILES 01 — 04
01 dvc.yaml Pipeline stages and dependencies ↗ 02 dvc.lock Recorded pipeline state ↗ 03 params.yaml Pipeline parameter configuration ↗ 04 src/ Preprocessing, training and evaluation code ↗
↗
POTENTIAL EXTENSIONS

Where the workflow could go next

01

Validate reproducibility with a clean end-to-end pipeline run.

02

Capture verified evaluation metrics and experiment comparisons.

03

Explore model serving, deployment automation and production monitoring.

FROM IMPLEMENTATION TO ITERATION

The repository documents the work. The next iteration builds on it.

The source repository is the starting point for reviewing this project’s pipeline structure, model-development code and configuration. The next stage is to validate the workflow through repeatable runs and extend it where the requirements demand.

A

Inspect the source

Start with the pipeline definition and configuration files to understand how the workflow is organized.

B

Validate with evidence

Use actual pipeline output, evaluation results and experiment records to support technical conclusions.

C

Extend deliberately

Treat deployment, automated delivery and production monitoring as future work unless implemented and verified.

Explore the GitHub repository ↗
Scroll to Top