Review Checklist

Review Checklist

Review Checklist

Use this checklist before accepting a pattern design:

Is the pattern solving a reviewed problem rather than adding vocabulary? Is the component boundary small enough to test and replace? Is the interface contract explicit? Is state authority visible? Are command acceptance and rejection visible? Are event meanings and subscribers visible? Is stale, duplicate, offline, and degraded behavior documented? Is the tradeoff recorded? Does a named owner maintain the interface and pattern decision? Is there a change condition for new devices, new states, new subscribers, new commands, or new product promises?

Back to the chapter