Compare Domains

Compare Domains

For a first class task, compare just two cases. Use a home leak alarm and a park soil sensor. Both may sense water. The home alarm may wake a resident in one minute. The park sensor may guide work the next day. This one change in time can change power, link, and alert choices.

Add the wrong-action test. A false home alarm may wake a family and call a plumber. A false park alert may waste water and staff time. Write both costs. Set a rule that keeps weak data from making the costly action.

Add the lost-service test. Let the home unit sound a local alarm when the cloud is down. Let the park unit keep readings until the path returns. The same fault can need two safe results. Record each result beside its domain card.

Last, swap the sites. Ask whether the home design can run across a large park and whether the park design can guard a fast leak. The gaps show why a shared part does not erase domain needs. Keep that lesson when more cases are added.

Write the two results side by side. Use the same short fields for job, time, harm, place, power, data, owner, and safe fault. Circle the fields that differ. Those circles explain the design split in words that a new reader can test.

Keep one shared fact too. Both devices still need a sound measure and a support path. Shared facts can guide common parts, while the circled facts guide each setup. This is a safer use of a domain map than copying one full design into every case.

Back to the chapter