Skip to content

Rapid Battle Cards 13–24

13. Centralized vs Distributed Architecture

Centralized = harvested Metadata persists in one common repository.
Distributed = common access, but queries live sources and keeps no persistent central store.

14. Centralized vs Hybrid

Centralized = selected scope is copied centrally.
Hybrid = some enterprise Metadata persists centrally while other detail stays source-held.

15. Distributed vs Hybrid

Distributed = no central persistent repository.
Hybrid = some Metadata persists centrally.

16. Hybrid vs Bi-Directional

Hybrid = mixed persistence/retrieval.
Bi-Directional = controlled Metadata changes can flow back to source repositories.

17. Strategy vs Requirements

Strategy = enterprise direction/current-to-future approach.
Requirements = specific content, function, access, quality, history, and control needs.

18. Requirements vs Architecture

Requirements = what consumers/content need.
Architecture = how Metadata will be sourced, stored, integrated, refreshed, and delivered.

19. Architecture vs Metamodel

Architecture = environment pattern.
Metamodel = model of Metadata repository objects and relationships.

20. Apply Standards vs Manage Stores

Standards = define/enforce Metadata conventions, naming, attributes, visibility, exchange rules.
Manage Stores = operate harvests, movement, updates, warnings, interfaces, jobs, and issues.

21. Integrate vs Deliver Metadata

Integrate = reconcile/standardize/assemble Metadata from sources.
Deliver = make managed Metadata accessible and usable to consumers/systems.

22. Metadata Source vs Metadata Repository

Source = local producer/repository for a tool or process.
Enterprise repository/environment = integrating, governing, relating, and delivering across sources.

23. Harvest vs Manual Enrichment

Harvest = automated extraction from source tools.
Manual enrichment = Steward/user-added enterprise context such as ownership, definitions, classifications, or notes.

24. Lineage vs Impact Analysis

Lineage = trace origin/movement/transformation.
Impact = identify consequences/dependencies of a proposed change.

Source: pp. 403–419.

← Cards 01–12 · Cards 25–36 →