Samsung DRS

2016

A defect and code review tracker, recreated from Samsung’s printing division.

Links
Live demoSource
About

A recreation of the defect and code review tracker built at Samsung Electronics’ printing division in 2016–2017. Firmware, QA and code review teams in Suwon and Bangalore used it while moving from IBM Rational and Review Board to Perforce, Helix Swarm, Jira and Confluence.

The demo runs on mock data generated in the browser: 812 defects and 631 code reviews across 44 printer and copier models.

OriginalReact and Node.js, styled with Bootstrap
StackVinext, React 19, Base UI, Tailwind CSS, React Flow, Cloudflare Workers
NoteA recreation with mock data, not affiliated with or endorsed by Samsung Electronics

Seven systems

During the migration the same work was spread across seven systems. DRS synced with all of them, so every defect and review kept its records linked.

The DRS mark: one shape drawn three times in three violets, like sheets leaving a printer.
The migration diagram, drawn with React Flow, then defects by migration state.

Insights

Defects are measured against severity targets, and code reviews against a 48-hour turnaround, over 7 days to 6 months.

Switching the reporting period; the tiles and severity targets recompute.
Reported vs resolved, review outcomes, a product line heatmap and turnaround by change type.

Defects

The defect list filters by scope, status and search, keeps its state in the URL, and can be driven entirely from the keyboard.

Scope tabs, a status filter, a search for C3150 and a sort by severity.
J and K move, X selects, and the bulk edit bar appears (keys shown bottom right).
Defect D-17-0363: status, severity, the PS-C3150FR spec card and its records in five systems.
Close-up from the DRS demo: Engineering fields
Engineering fields
Close-up from the DRS demo: Europe, CIS, MEA
Europe, CIS, MEA
Close-up from the DRS demo: Korea, Japan, Europe
Korea, Japan, Europe
Close-up from the DRS demo: Americas, Europe
Americas, Europe
Engineering fields and three sales-region dot maps; Korea and Japan get a ring.
The relationship map: linked reviews, suggested defects and affected product lines.
Reporting a duplex jam: D-17-0363 appears as a possible duplicate.

Code reviews

Every change goes to the Code Review Team. Diffs show side by side or unified, and any line takes a comment.

CR-2225’s diff, unified and side by side, then a comment on one line.

Roles

There is no sign-in. Settings switches between the 34 people, and each role sees what it may do.

As a QA engineer a review waits; as the review team lead it gets a reviewer.
Insights, a defect search, D-17-0363, its relationship map, a review diff and duplicate detection.

And more

Daily and weekly email digests, team profiles, notifications, and Ctrl+K search across everything.

Two daily digests, then a weekly one filtered to major and critical defects.
The Teams page, searched for Bangalore.
Notifications filtered to unread and mentions, then marked as read.
Ctrl+K: a search for duplex, then for a person (keys shown bottom right).
Insights on a phone.
The defect list and a defect on a phone.

Mock data

Records are generated in the browser from a fixed seed, January 2016 to September 2017. Edits stay in localStorage, and the demo clock starts at 6 p.m. on 15 September 2017.