A data source is the origin of data consumed by systems: databases, files, sensors, applications or APIs that produce or expose data. It specifies format, semantics, update frequency and trust level, and is essential for integration, data quality and governance. Understanding data sources informs architecture, privacy and operational decisions.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
A data source is an origin from which data is generated, collected, or provided, such as a sensor, system, file, or service.
The term belongs to data processing and was formalized through distributed systems, catalogs, and the web. The sources name no inventor.
Follow data from origin through interface and metadata to consumer. Structure, freshness, quality, and ownership remain traceable.
The topic has a specific mechanism and boundary that guide its use.
Its value depends on applying it to an observable problem and checking the result.
A source model supports integration, governance, lineage, and troubleshooting. A source alone guarantees neither quality nor lawful use.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.