A model’s architecture is the arrangement of components and connections that determines how it processes inputs and produces outputs. No particular internal model design is specified here. The immediate architectural decision is whether a model with the required properties can be built and run within a viable production system. section 2.7.2
Before committing to a design, complete a high-level feasibility check:
- Identify the client’s data and processing systems, cloud policies, and legacy components; record constraints on scale and speed. section 2.3.2
- Identify the system components needed to supply data, execute the model, and use its outputs. Check that those components are available and that the team can commission them. section 2.7.2
- Record missing components or skills as delivery risks now; leave detailed component interactions for later system design. section 2.7.2
Smart-building control
A proposed system takes building-sensor data into a database, runs a model to determine control signals, sends those signals to actuators, and presents events and decisions to users. This establishes the surrounding system components, not the model’s internal architecture. section 2.7.2
Capture the resulting decisions in a technical architecture deliverable so the team and client can review what is proposed and what remains unresolved. section 4.3.5












