liveBook · Manning

Subject

A subject is an entity designated as the focus of representation, data modeling, or an authorization policy.

How 2 Manning books explain it

Grokking Relational Database Design

A subject is a person, place, thing, event, or other real-world item identified as relevant to a database design.

How it is used
Identifies real-world items during requirements gathering so designers can capture characteristics and relationships.
How deep it goes
Defines subjects and maps them to entities, stopping short of detailed database implementation.
Examples
Uses people, places, things, events, and an employee-to-entity conversion as examples.
What you can do after
Understand how to identify relevant subjects and translate them into entities with attributes.

Read how Grokking Relational Database Design explains subject →

Authorization in Action

A subject is the entity referred to in an account, policy, or authorization decision, potentially referring to a principal or resource.

How it is used
Clarifies who an account, policy, or authorization decision refers to, especially when requester and affected entity differ.
How deep it goes
Defines subject, contrasts it with principal, and shows attribute-based treatment in XACML without developing a typed subject model.
Examples
Uses parent-on-behalf-of-child access and XACML attributes such as username, department, and clearance.
What you can do after
Evaluate authorization terminology and distinguish the requester from the entity represented in a policy or access decision.

Read how Authorization in Action explains subject →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.