Systems Architect · South Korea

Hwang

Lead Architect & Product Planner · 26 years in software delivery

I design structure before writing code.
My work bridges the gap between business requirements and engineering reality — through asset-based architecture, requirement traceability, and the SOM framework I developed over two decades of practice.

Read the SOM Paper → Theory Series
26
Years in Practice
8+
Shipped Products
1
DOI on Zenodo
Research

The SOM Framework

A practitioner's answer to the semantic gap in software quality management — inspired by manufacturing's Bill of Materials.

Preprint Zenodo · DOI Registered
SOM: A BOM-Inspired Program-Centric Traceability Framework
for Software Quality Management

Modern software projects suffer from a persistent "semantic gap" — requirements written in natural language, code artifacts in formal structures, and quality documentation spread across disconnected tools. This paper proposes SOM (Software Object Model/Material), a framework that assigns a persistent identifier (SOM ID) to each functional unit (Program) at the planning stage, connecting requirements, code, test cases, and documentation under a single traceable anchor — analogous to a part number in manufacturing's Bill of Materials.

DOI: 10.5281/zenodo.19638263
Read on Zenodo → Theory Series (KR) Series Overview (EN)
Theory Series

SOM — Building a Bill of Materials for Software

A serialized essay explaining the SOM framework from first principles. Written in Korean with English subtitles — 5 episodes published, 10 planned.

EP. 01
Why QA is Always the Developer's Language
Three structural fractures in software quality — and their common root.
EP. 02
What the Factory Taught Us — The BOM Idea
How manufacturing unified its language with BOM, and why software still hasn't.
EP. 03
The Declaration — Software Needs Its Own Bill of Materials
The moment the SOM framework was conceived, and the three fractures it resolves.
EP. 04
The Five-Layer Architecture of SOM
Project · Module · Program · Component · Action — layers that absorb change.
EP. 05
SOM ID — The Key That Makes Programs into Assets
One number connecting planning, development, testing, and documentation.
EP. 06
SOM vs Existing Methods
SOM doesn't care about domain — web, public sector, embedded, safety-critical. Why existing methods fall short.
Coming Soon
EP. 07
First Steps with SOM — Building a Program List
Where to start: defining your Program units before anything else. The practical entry point for SOM adoption.
Coming Soon
EP. 08
Designing Test Scenarios with SOM
How SOM IDs become the backbone of test scenario design — connecting planning intent to test coverage.
Coming Soon
EP. 09
SOM Quality Metrics — Coverage, Integrity, Impact
Coverage, defect density, change impact — quality metrics that everyone on the team can finally read.
Coming Soon
EP. 10
The Future of SOM — Software Digital Twin
When SOM is complete, a living digital twin of your software emerges. Real-time quality dashboards, AI-powered defect prediction.
Coming Soon
BONUS 1
SOM × Embedded — A BOM for Safety-Critical Software
Where SOM meets functional safety standards — DO-178C, ISO 26262, IEC 61508. Traceability for the stakes that matter most.
Coming Soon
BONUS 2
What Sima Qian Knew — Annals, Biographies, and SOM ID
The historian who organized all of history by identity — 2,000 years before software traceability became a field.
Coming Soon
BONUS 3
Code Is Equal — Organizations Are Not
Why SOM didn't exist before. Not a technology problem — an organizational one. 26 years of watching the food chain up close.
BONUS 4
The Moment You Name It, It Becomes Real
Laozi warned against naming. But 26 years in software taught the opposite — things that couldn't exist because they had no name.
BONUS 5
SOM Tree — A Living Portrait of Your Software
Newton asked why the apple falls. SOM Tree doesn't judge the fruit — it shows you the gravity behind it.
About

Practitioner turned Researcher

Hwang
Hwang
Systems Architect
Product Planner
SOM Framework Creator
South Korea

26 years. One recurring problem.

Across hundreds of software delivery projects — from government systems to commercial products — I kept encountering the same failure pattern: planners, developers, and QA teams could not share a common language for the same software unit.

SOM is my answer. Not a tool, not a process — a framework for assigning identity to software units from the planning stage, so that every artifact across the project lifecycle can be traced back to a single, stable anchor.

The intellectual lineage of SOM draws from manufacturing (BOM), information architecture, and — perhaps unexpectedly — the biographical-annals style (Jijeonche) of Sima Qian's Shiji, in which a subject-centric structure enables cross-referencing across domains.

Requirements Traceability Software Quality Asset-based Architecture BOM-inspired Design ALM Digital Twin
Products

Independently Built Engines

Each product is independently planned, architected, and shipped — not a demo, a deployable engine.

📜
WiseMo
Classical Recitation Engine
Handwrite Eastern & Western classics with karaoke-synced TTS in the original language. MBTI-personalized interpretations, RPG-style progression. 9 books, 240+ passages.
Live
JellyMo
JellyMo
Emotion-based Asset System
An asset-based design system that modularizes emotion for scalable expansion. Not simple images — composable asset structures enable MBTI-based character customization.
Live
⚡
BA-QA
AI-Era Quality Assurance Engine
Real-time synchronization between planning artifacts and source code. Shift-Left beyond Shift-Left — the traceability engine that closes the RTM gap automatically.
2026.06 Launch
Contact

Get in Touch

Collaboration · Feedback · Research

If you are working on requirements traceability, software quality, or ALM —
I would be glad to hear from you.

Zenodo Preprint Korean Site