How deeply does Automating API Delivery cover domain model?

Explains the model’s role and inputs, but stops short of low-level API delivery process details.

Domain model

A domain model is a structured representation of business concepts, relationships, and workflows as interconnected software objects with behavior and data.

A domain model represents the business operations and data models behind an API, giving design work a shared view of the problem before requirements become API definitions. section 5.1 section 1.3

Use the model to:

Translate user stories or job stories into API requirements and definitions. section 5.1 section 1.3
Give API designers and reviewers shared context for discussing design decisions and consistency. section 5.1
Support API-first planning before backend implementation, testing, deployment, and publication. section 1.3

The model belongs in the plan-and-design stage. It simplifies surrounding complexity to emphasize selected points rather than documenting every low-level delivery process, and it can be refined as API design proceeds. section 1.3 section 5.1

How Automating API Delivery covers it

liveBook manning.com

Read Automating API Delivery on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

AI-Powered Developer: Build software with ChatGPT and CopilotA domain model is the representation of an application’s core business logic, including domain entities, value objects, and domain services.
liveBook manning.com

Architecture Modernization: Socio-technical alignment of software, strategy, and structureA domain model is a representation of the concepts, relationships, and rules that constitute a business domain.
liveBook manning.com

Java Persistence with Spring Data and Hibernate epubA domain model is an object-oriented representation of application-domain concepts, their state, and their relationships.
liveBook manning.com

Functional Design and Architecture: Examples in HaskellA domain model is a structured representation of the concepts, properties, relationships, and behavior of a problem domain.
liveBook manning.com

F# in Action: A Revised Edition of Get Programming with F#A domain model is a software representation of the entities, relationships, rules, and behavior of a problem domain.
liveBook manning.com

Go in Action, Second EditionA domain model is a representation of the concepts and relationships in a problem domain that software components conform to.
liveBook manning.com

Unit Testing Principles, Practices, and PatternsA software model representing the concepts, rules, and behavior of an application domain.

Compare how 8 books explain domain model →

Related concepts

domain-driven designused by · Domain-driven design is a software design approach that centers models, structure, and terminology on the concepts, behavior, and boundaries of a problem domain.
MVC modelequivalent to · An MVC model is the application component that represents application data and associated domain logic, making relevant state and behavior available to other components such as views.
shared kernelhas part · The shared kernel is a Domain-Driven Design pattern in which bounded contexts share a deliberately coordinated subset of their domain model, code, or data design.
api modelproduced by · An API-accessible model is a machine-learning model whose capabilities are made available to software through an application programming interface.
collaborative discovery and modelingequivalent to · Collaborative discovery and modeling is a group technique in which stakeholders jointly create and refine representations to establish shared understanding of a domain or system.

This explainer was generated by Manning's knowledge graph from the text of Automating API Delivery. The section links point to the parts of the book it draws on.