Research

Problem

Most authentication systems are built on the assumption that the network will be there when you need it. Some environments don’t allow that. They have to work fully connected, partially degraded, or completely offline. The question was whether those conditions call for different architectures, and whether all three can still meet the same Zero Trust requirements.

Approach

• Defined requirements for each connectivity tier, since latency, availability, and threat exposure change across all three
• Built a separate SysML architecture in MagicDraw/Cameo for each tier, including components, interfaces, and behavioral constraints
• Ran a trade study comparing all three against the same Zero Trust requirements
• Built a Raspberry Pi prototype to test the Tier 1 assumption, with Node-RED handling sensor flow and authentication sequencing
• Ran the prototype under simulated isolation; two interface assumptions in the model didn’t hold up and had to be revised

Findings

• Three SysML architecture models, each with documented design rationale
• A trade study showing that the same Zero Trust requirements can be satisfied in different ways across connectivity tiers
• A prototype that confirmed the architecture was buildable and exposed issues the model alone did not catch

Problem

The interesting part of a trading simulator isn’t the interface. It’s getting the underlying system right: auth flows, transaction integrity, consistent portfolio state.

Approach

• Designed the data model: users, positions, transaction history, market data
• Built authentication and session management with Django
• Implemented trade execution logic using live market data to enforce real transaction constraints

Outcome

• Full application handling auth, trade execution, and persistent portfolio state
• Built end-to-end — data model to deployed interface