Chapter 15. Domain Interactions

The motivation for domain interactions is that decisions made locally in one domain can have impacts on system-level requirements and other domain-specific requirements. For example, heat dissipation is typically not thought of as a constraint that is impacted by the choice of a software algorithm. Unfortunately, software execution can dramatically impact heat dissipation through its interaction with the CPU it runs on, and indirectly through interfaces to other system components. Other examples include impacts of local power consumption on system-level power constraints, impacts of component function on system security, and impacts of electromagnetic interference among chips on a board. In each case, local decisions ...

Get System-Level Design with Rosetta now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.