At the level of system system analysis, the variables and data types should be defined with the focus on the meaning and kind of information they represent and not affected by implementation details or non-functional aspects like memory or CPU usage.
The reason is that such implementation details unneccessarily tend to increase complexity and impede understandibility and clarity. (Later during design, implementation and optimization, implementation aspects will become relevant, but not yet.)
This applies to the following principles listed in the document:
"The data structure shall minimize the reanalysis of data if other data is received. i.e. not shift data, avoid changing data for all stored locations if a new LRBG is detected, etc."
"All data in the data structure shall be accessible without searching, i.e. pointer structure shall make searching superfluous"
Memory is not dynamically allocated. For each type the maximum number of instances shall be determined. This number can be created at start-up."
Review comments to Chapter "2 Principles":
At the level of system system analysis, the variables and data types should be defined with the focus on the meaning and kind of information they represent and not affected by implementation details or non-functional aspects like memory or CPU usage.
The reason is that such implementation details unneccessarily tend to increase complexity and impede understandibility and clarity. (Later during design, implementation and optimization, implementation aspects will become relevant, but not yet.)
This applies to the following principles listed in the document: