Functional Implementation Domains
Currently, FEAST defines several functional implementation domains to organize its architecture and development. These domains include:
-
Broadly Expandable and Reconfigurable Data Acquisition and Automation Device Standard or “breads” encompasses the hardware domain. It defines the electromechanical specifications for compatible hardware. Implementations include: SLICE function cards CRUST interface bridges, and LOAF controllers & backplanes.
-
Firmware for Resilient, (Function-)Oriented Operation of Things Specification or “fruits” encompasses the firmware domain. It defines standardized logic, interfaces and modules for hardware operation.
-
Programmable Runtime Orchestration and Transport Interfaces for Node Supervision or “proteins” encompasses the middleware domain. It provides runtime orchestration, device management, and modular drivers to bridge the gap between device firmware and user-defined software.
-
System User Graphical Interface and Remote Scheduling or “sugars” encompasses the software/interface domain. It’s purpose is enabling user interaction, system monitoring, control interfaces, and remote scheduling.
Future Domains
-
Versatile External Gear, Interfaces, and Experimental Subsystems or “vegies” is a conceptual framework for user-fabricated hardware that can integrate with BREADS-compatible systems. This includes DIY sensors, actuators, and tools made through various fabrication methods like 3D printing, digital manufacturing, and component modification. Conceptually, these are used by the BREADS hardware domain and would be considered as “below” BREADS in the hierarchy (VEGIES -> BREADS -> FROOTS -> PROTINS -> SUGIRS).