Engineering
Requirements analysis
Requirements describe outcomes, rules, and constraints.
REFERENCE CATEGORY
14 practical topics
Engineering
Requirements describe outcomes, rules, and constraints.
Engineering
Domain models name business concepts and their behavior.
Engineering
Entities have stable identity through changing attributes.
Engineering
Schema design makes relationships and integrity explicit.
Engineering
Architecture organizes responsibilities and dependencies.
Engineering
Separate HTTP, business rules, storage, and presentation responsibilities.
Engineering
SOLID encourages cohesive responsibilities and replaceable collaborators.
Engineering
Error handling distinguishes invalid input, conflicts, and unexpected failure.
Engineering
Logs explain execution and failure in operational terms.
Engineering
Tests prove requirements, invariants, and failure behavior.
Engineering
Concurrency means operations overlap and can act on stale state.
Engineering
A transaction boundary defines which database changes succeed together.
Engineering
Reliability means preserving correct outcomes despite expected failures.
Engineering
Observability uses logs, metrics, and traces to explain system behavior.