8.8 A Checklist for Multi-Board Software Development

When developing code that can be used in both single- and multi-processor environments, the design is more complex. State machines can be split, procedural interfaces need to be changed, pointer-based access is to be reexamined, and so on. The following provides a checklist for the development:

• Use messages as opposed to procedure calls between functional modules that can be split

• Split state machines and use messages for interaction between the state machines

• Use Message Abstractions and Name Services to handle both intra-board and inter- board communications

• Use Agent and Subagent methods for management