Thirteen Important Rules for Learning Embedded Design

Through practice, organization, and analysis, I have summarized some embedded rules learned during the embedded development process for your reference:

1 Law of Limited Resources

Embedded computing not only requires fast and consistent calculations over a network but also demands that the system orderly executes its code and data stored in a “common” and “narrow” space.

2 Law of Robustness

Embedded computing requires not only rapid and effective calculations but also insists that the system continues to operate normally even when certain computational units fail.

3 Law of Real-time

The calculation results of embedded systems depend not only on the correctness of logical operations but also on the computation time of these results.

4 Law of Redundancy

Once an embedded system has sufficient redundancy, the system’s “initial sensitivity” to its “final computation results” becomes negligible.

5 Law of Structure

For embedded systems, the trend of structural complexity indicates: a simpler system structure is more effective (The simplest is the best); b a more complex system structure is more stable (More complex is more stable).

6 Law of Simplicity

Simplifying an embedded system strengthens the interaction between the remaining functions; once the system’s functions are simplified, the probability of successful intrusion by external invaders increases.

7 Law of Conservation

If a certain function is to be retained in an embedded system, it is best to regard all other functions as “sacrosanct”; the removal (extinction) or generation (invasion) of system functions will significantly alter the overall (cluster) structure and its dynamic performance.

8 Law of Organization

The most important aspect of the embedded Internet is often not the characteristics of individual devices within the network but the overall order present in the network, i.e., network order. In a highly redundant network, the individual role of devices no longer significantly affects the overall system performance, but rather the characteristics of all nodes and their connections play the main role.

9 Law of Networking

A network composed of embedded Internet nodes interacting with each other often exhibits properties that are not significantly related to the properties of individual nodes.

10 Law of Messaging

Guaranteeing message searches: they have strict time sensitivity or basic normal operational requirements, and such messages require a time guarantee from the system. Once activities or tasks triggered by such messages are executed, their time constraints will be guaranteed by the system within a specified time interval. Optimal effect messages: they possess typical soft time constraints, meaning their time constraints are dictated by the time sequence of the activities or tasks themselves, and do not require system guarantees to meet their time constraints.

11 Law of Immunity

The immune system of the embedded Internet should emulate a living organism mechanism, where the immune function is a “feed-forward” system requiring the system to have foresight, allowing it to “attack (small) toxins with (large) toxins.”

12 Law of Integration

The embedded Internet is a complex network that can be analyzed by simple “components” to interpret the “whole” or express the “global” with “nodes.”

13 Law of Cost-Effectiveness

If system A is an embedded system of system B, i.e., B(a), then the cost of system A should not exceed 10% of the cost of system B, while the cost of system B(a) should be greater than the sum of the costs of systems A and B, and the cost-effectiveness of system B(a) should increase by 30%.

Scan the QR code below to follow!

Thirteen Important Rules for Learning Embedded DesignOn the electronic road, let’s walk together!

Leave a Comment

×