Module 19 Cheat Sheet

FIELD MAPPING IS NOT ENOUGH

Need:
meaning
ownership
null semantics
identity
lifecycle
timing
failure semantics


ASK BUSINESS QUESTIONS
======================

"When X happens,
what should happen to Y?"


KEY QUESTIONS
=============

source of truth?
unique key?
who wins conflicts?
missing vs null?
delete vs deactivate?
sync timing?
partial success?
outage behavior?
replay?
audit?


ARTIFACTS
=========

data-flow diagram
API/event contract
mapping matrix
business rules
acceptance scenarios


TRACEABILITY
============

BR-001
→ mapping/code
→ automated tests

The sentence I'd use in an interview:

“I don't treat a field-mapping spreadsheet as the full integration requirement. I use it together with explicit business rules around identity, field ownership, null semantics, lifecycle, timing, partial failures and recovery, and I turn concrete input-to-expected-state examples into acceptance tests before implementation.”