liveBook · Manning

Model architecture

As explained in Delivering Machine Learning Projects: From design to deployment

A model architecture is the structural arrangement of components and connections that defines how a machine learning model processes inputs and produces outputs.

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

How Delivering Machine Learning Projects: From design to deployment covers it

How deep it goes
Develops a high-level system-component feasibility check, but defers detailed interactions and does not specify an internal model topology.
Examples
Uses a smart-building system with sensors, a database, model execution, actuators, and user-facing information to identify required components.
What it assumes
Assumes familiarity with ML models while prompting investigation of the client’s existing systems and deployment constraints.
What you can do after
Practice/perform a high-level feasibility check of model execution, data flow, and available production components.
How it connects
Links model properties to business requirements, nonfunctional requirements, development infrastructure, and production architecture.

Also explained in

Compare how 13 books explain model architecture →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Delivering Machine Learning Projects: From design to deployment. The section links point to the parts of the book it draws on.