Data architecture (DAMA-DMBOK2)
https://knobit.org/id/register/data-architecture
Also as Turtle · JSON-LD · RDF/XML
| LCG purposes | Assessing the learner's knowledge or skill state |
|---|---|
| LCG purposes | Opening up a learning outcome |
| LCG purposes | Selecting an assessment task or learning activity |
| conforms to profile | https://oppekava.edu.ee/a/Knobitite_kirjeldamise_ja_seostamise_reeglid#LCG-KNOBIT-0.1 |
| dcterms:description | Recognising and repairing defects in enterprise data architecture deliverables, from concerns and principles to the roadmap: the competence the data-architecture skill applies in its five stages, and that skill-tests assesses. en |
| dcterms:identifier | SCOPE-1 |
| dcterms:license | https://creativecommons.org/licenses/by/4.0/ |
| dcterms:title | Data architecture (DAMA-DMBOK2) en |
| owl:sameAs | https://bitbucket.org/reffa/ontology/skills/data-architecture |
| skos:note | audience: Data architects, and AI models assessed by skill-tests en |
| skos:note | domain: Data management, data architecture (DAMA-DMBOK2 chapter 4) en |
| skos:note | level: CDMP Associate: the data architecture questions of the Data Management Fundamentals exam (DAMA International); CDMP has no data architecture specialist exam en |
Items and references
Business drivers edu:LearningOutcome
https://knobit.org/id/register/data-architecture#AV-1
| dcterms:description | Why organisations practise data architecture. en |
|---|---|
| dcterms:identifier | AV-1 |
| dcterms:source | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture, 1.1 en |
| includes knobit | Explains the business drivers of data architecture |
| rdfs:label | Business drivers en |
| schema:isPartOf | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture |
| skos:notation | 1.1 |
Integrate with enterprise architecture edu:LearningOutcome
https://knobit.org/id/register/data-architecture#AV-10
| dcterms:description | Aligning data architecture with strategy and the other architecture domains. en |
|---|---|
| dcterms:identifier | AV-10 |
| dcterms:source | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture, 2.2 en |
| includes knobit | Explains the alignment of architecture with the data strategy |
| rdfs:label | Integrate with enterprise architecture en |
| schema:isPartOf | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture |
| skos:notation | 2.2 |
Tools edu:LearningOutcome
https://knobit.org/id/register/data-architecture#AV-11
| dcterms:description | Data modelling tools, asset management software, graphical design applications. en |
|---|---|
| dcterms:identifier | AV-11 |
| dcterms:source | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture, 3 en |
| includes knobit | Explains data architecture tools |
| rdfs:label | Tools en |
| schema:isPartOf | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture |
| skos:notation | 3 |
Lifecycle projections edu:LearningOutcome
https://knobit.org/id/register/data-architecture#AV-12
| dcterms:description | Planning the lifecycle of architecture standards and platforms. en |
|---|---|
| dcterms:identifier | AV-12 |
| dcterms:source | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture, 4.1 en |
| includes knobit | Explains lifecycle projections |
| rdfs:label | Lifecycle projections en |
| schema:isPartOf | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture |
| skos:notation | 4.1 |
Diagramming clarity edu:LearningOutcome
https://knobit.org/id/register/data-architecture#AV-13
| dcterms:description | Diagrams readers can follow. en |
|---|---|
| dcterms:identifier | AV-13 |
| dcterms:source | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture, 4.2 en |
| includes knobit | Explains clear architecture diagrams |
| rdfs:label | Diagramming clarity en |
| schema:isPartOf | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture |
| skos:notation | 4.2 |
Readiness and risk assessment edu:LearningOutcome
https://knobit.org/id/register/data-architecture#AV-14
| dcterms:description | Risks and readiness of architecture work. en |
|---|---|
| dcterms:identifier | AV-14 |
| dcterms:source | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture, 5.1 en |
| includes knobit | Explains data architecture readiness and risk assessment |
| rdfs:label | Readiness and risk assessment en |
| schema:isPartOf | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture |
| skos:notation | 5.1 |
Organisation and cultural change edu:LearningOutcome
https://knobit.org/id/register/data-architecture#AV-15
| dcterms:description | Embedding the architecture practice. en |
|---|---|
| dcterms:identifier | AV-15 |
| dcterms:source | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture, 5.2 en |
| includes knobit | Explains organisational change for data architecture |
| rdfs:label | Organisation and cultural change en |
| schema:isPartOf | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture |
| skos:notation | 5.2 |
Data architecture governance and metrics edu:LearningOutcome
https://knobit.org/id/register/data-architecture#AV-16
| dcterms:description | Architecture review, principle exceptions and metrics. en |
|---|---|
| dcterms:identifier | AV-16 |
| dcterms:source | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture, 6 en |
| includes knobit | Explains principle exceptions |
| includes knobit | Explains data architecture governance and metrics |
| rdfs:label | Data architecture governance and metrics en |
| schema:isPartOf | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture |
| skos:notation | 6 |
Data architecture outcomes and practices edu:LearningOutcome
https://knobit.org/id/register/data-architecture#AV-2
| dcterms:description | Artefacts (specifications), activities (forming, consuming) and behaviours. en |
|---|---|
| dcterms:identifier | AV-2 |
| dcterms:source | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture, 1.2 en |
| includes knobit | Explains stakeholders, concerns and viewpoints |
| includes knobit | Explains the enterprise data model and its subject areas |
| rdfs:label | Data architecture outcomes and practices en |
| schema:isPartOf | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture |
| skos:notation | 1.2 |
Enterprise architecture domains edu:LearningOutcome
https://knobit.org/id/register/data-architecture#AV-3
| dcterms:description | Business, data, application and technology architecture. en |
|---|---|
| dcterms:identifier | AV-3 |
| dcterms:source | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture, 1.3.1 en |
| includes knobit | Explains the enterprise architecture domains |
| rdfs:label | Enterprise architecture domains en |
| schema:isPartOf | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture |
| skos:notation | 1.3.1 |
Enterprise architecture frameworks edu:LearningOutcome
https://knobit.org/id/register/data-architecture#AV-4
| dcterms:description | Zachman and TOGAF. en |
|---|---|
| dcterms:identifier | AV-4 |
| dcterms:source | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture, 1.3.2 en |
| includes knobit | Explains the architecture principle template |
| includes knobit | Explains reading a CRUD matrix by entity |
| includes knobit | Explains enterprise architecture frameworks |
| rdfs:label | Enterprise architecture frameworks en |
| schema:isPartOf | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture |
| skos:notation | 1.3.2 |
Enterprise data model edu:LearningOutcome
https://knobit.org/id/register/data-architecture#AV-5
| dcterms:description | Subject areas, entities and their relationships across the enterprise. en |
|---|---|
| dcterms:identifier | AV-5 |
| dcterms:source | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture, 1.3.3 en |
| includes knobit | Redistributes an application-named subject area |
| includes knobit | Explains the enterprise data model and its subject areas |
| includes knobit | Explains the system of record |
| includes knobit | Explains the BIAN service landscape |
| includes knobit | Explains definitions distinguishing a concept |
| rdfs:label | Enterprise data model en |
| schema:isPartOf | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture |
| skos:notation | 1.3.3 |
Data flow design edu:LearningOutcome
https://knobit.org/id/register/data-architecture#AV-6
| dcterms:description | Data lineage between processes, applications and stores; the data value chain. en |
|---|---|
| dcterms:identifier | AV-6 |
| dcterms:source | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture, 1.3.3 en |
| includes knobit | Raises a double creation as a business decision |
| includes knobit | Explains reading a CRUD matrix by entity |
| includes knobit | Explains data flows and the data value chain |
| rdfs:label | Data flow design en |
| schema:isPartOf | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture |
| skos:notation | 1.3.3 |
Evaluate existing data architecture specifications edu:LearningOutcome
https://knobit.org/id/register/data-architecture#AV-7
| dcterms:description | Reviewing the current specifications against needs. en |
|---|---|
| dcterms:identifier | AV-7 |
| dcterms:source | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture, 2.1.1 en |
| includes knobit | Resolves colliding architecture principles for their owners |
| includes knobit | Rewrites a solution as the concern behind it |
| includes knobit | Explains stakeholders, concerns and viewpoints |
| rdfs:label | Evaluate existing data architecture specifications en |
| schema:isPartOf | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture |
| skos:notation | 2.1.1 |
Develop a roadmap edu:LearningOutcome
https://knobit.org/id/register/data-architecture#AV-8
| dcterms:description | Transition steps from the current to the target architecture. en |
|---|---|
| dcterms:identifier | AV-8 |
| dcterms:source | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture, 2.1.2 en |
| includes knobit | Resequences decommissioning after the consumers move |
| includes knobit | Explains transition architectures and work packages |
| includes knobit | Explains roadmap dependency and decommissioning order |
| rdfs:label | Develop a roadmap en |
| schema:isPartOf | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture |
| skos:notation | 2.1.2 |
Manage enterprise requirements within projects edu:LearningOutcome
https://knobit.org/id/register/data-architecture#AV-9
| dcterms:description | Architecture decisions and their traceability in projects. en |
|---|---|
| dcterms:identifier | AV-9 |
| dcterms:source | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture, 2.1.3 en |
| includes knobit | Links a reversing decision to the one it reverses |
| includes knobit | Explains architecture decision records |
| includes knobit | Explains the traceability of target placements |
| rdfs:label | Manage enterprise requirements within projects en |
| schema:isPartOf | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture |
| skos:notation | 2.1.3 |
da-concerns-principles C1: AP-001 and AP-007 collide edu:Question
https://knobit.org/id/register/data-architecture#DA-101
| dcterms:identifier | DA-101 |
|---|---|
| rdfs:label | da-concerns-principles C1: AP-001 and AP-007 collide en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (2 points) |
| solvable with | set of Recognises colliding architecture principles with no precedence |
da-concerns-principles C1: the collision is sent to the owners edu:Question
https://knobit.org/id/register/data-architecture#DA-102
| dcterms:identifier | DA-102 |
|---|---|
| rdfs:label | da-concerns-principles C1: the collision is sent to the owners en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (2 points) |
| solvable with | set of Recognises colliding architecture principles with no precedence, Resolves colliding architecture principles for their owners |
da-concerns-principles C2: AP-004 is a product choice edu:Question
https://knobit.org/id/register/data-architecture#DA-103
| dcterms:identifier | DA-103 |
|---|---|
| rdfs:label | da-concerns-principles C2: AP-004 is a product choice en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C2 (2 points) |
| solvable with | set of Recognises a technology choice filed as a principle |
da-concerns-principles C2: CN-004 is a solution, rewritten as a question edu:Question
https://knobit.org/id/register/data-architecture#DA-104
| dcterms:identifier | DA-104 |
|---|---|
| rdfs:label | da-concerns-principles C2: CN-004 is a solution, rewritten as a question en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C2 (2 points) |
| solvable with | set of Recognises a solution stated as a concern, Rewrites a solution as the concern behind it |
da-concerns-principles I1: SH-002 has no concern edu:Question
https://knobit.org/id/register/data-architecture#DA-105
| dcterms:identifier | DA-105 |
|---|---|
| rdfs:label | da-concerns-principles I1: SH-002 has no concern en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises a stakeholder with no concern |
da-concerns-principles I1: CN-002 is raised by nobody edu:Question
https://knobit.org/id/register/data-architecture#DA-106
| dcterms:identifier | DA-106 |
|---|---|
| rdfs:label | da-concerns-principles I1: CN-002 is raised by nobody en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises a concern raised by no stakeholder |
da-concerns-principles I1: CN-003 has no viewpoint edu:Question
https://knobit.org/id/register/data-architecture#DA-107
| dcterms:identifier | DA-107 |
|---|---|
| rdfs:label | da-concerns-principles I1: CN-003 has no viewpoint en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises a concern no viewpoint frames |
da-concerns-principles I1: VP-003 frames nothing edu:Question
https://knobit.org/id/register/data-architecture#DA-108
| dcterms:identifier | DA-108 |
|---|---|
| rdfs:label | da-concerns-principles I1: VP-003 frames nothing en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises a viewpoint framing no concern |
da-concerns-principles I1: VP-004 has no model kinds edu:Question
https://knobit.org/id/register/data-architecture#DA-109
| dcterms:identifier | DA-109 |
|---|---|
| rdfs:label | da-concerns-principles I1: VP-004 has no model kinds en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises a viewpoint with no model kinds |
da-concerns-principles I1: AP-005 has no rationale edu:Question
https://knobit.org/id/register/data-architecture#DA-110
| dcterms:identifier | DA-110 |
|---|---|
| rdfs:label | da-concerns-principles I1: AP-005 has no rationale en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises an architecture principle with no rationale or implications |
da-concerns-principles I2: no payment stakeholder edu:Question
https://knobit.org/id/register/data-architecture#DA-111
| dcterms:identifier | DA-111 |
|---|---|
| rdfs:label | da-concerns-principles I2: no payment stakeholder en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I2 (1 points) |
| solvable with | set of Recognises a missing architecture stakeholder |
da-concerns-principles I2: AP-006 has no owner edu:Question
https://knobit.org/id/register/data-architecture#DA-112
| dcterms:identifier | DA-112 |
|---|---|
| rdfs:label | da-concerns-principles I2: AP-006 has no owner en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I2 (1 points) |
| solvable with | set of Recognises an architecture principle with no owner |
da-principles-subject-areas C1: AP-102 reported against data principle DP-001 edu:Question
https://knobit.org/id/register/data-architecture#DA-150
| dcterms:identifier | DA-150 |
|---|---|
| rdfs:label | da-principles-subject-areas C1: AP-102 reported against data principle DP-001 en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (2 points) |
| solvable with | set of Recognises an architecture principle contradicting the data strategy |
da-principles-subject-areas C1: board-approved AP-102 taken to the data strategy owner for a ruling edu:Question
https://knobit.org/id/register/data-architecture#DA-151
| dcterms:identifier | DA-151 |
|---|---|
| rdfs:label | da-principles-subject-areas C1: board-approved AP-102 taken to the data strategy owner for a ruling en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (2 points) |
| solvable with | set of Explains the alignment of architecture with the data strategy |
da-principles-subject-areas I1: workshop notes classified as stakeholders, concerns, viewpoints and views edu:Question
https://knobit.org/id/register/data-architecture#DA-152
| dcterms:identifier | DA-152 |
|---|---|
| rdfs:label | da-principles-subject-areas I1: workshop notes classified as stakeholders, concerns, viewpoints and views en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (2 points) |
| solvable with | set of Explains stakeholders, concerns and viewpoints |
da-principles-subject-areas I1: notes linked (raised by, framed by, conforms to, addresses) edu:Question
https://knobit.org/id/register/data-architecture#DA-153
| dcterms:identifier | DA-153 |
|---|---|
| rdfs:label | da-principles-subject-areas I1: notes linked (raised by, framed by, conforms to, addresses) en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (2 points) |
| solvable with | set of Explains stakeholders, concerns and viewpoints |
da-principles-subject-areas I4: Kafka request recorded as a decision, not a principle edu:Question
https://knobit.org/id/register/data-architecture#DA-154
| dcterms:identifier | DA-154 |
|---|---|
| rdfs:label | da-principles-subject-areas I4: Kafka request recorded as a decision, not a principle en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I4 (2 points) |
| solvable with | set of Recognises a technology choice filed as a principle |
da-principles-subject-areas I4: written principles carry the full template edu:Question
https://knobit.org/id/register/data-architecture#DA-155
| dcterms:identifier | DA-155 |
|---|---|
| rdfs:label | da-principles-subject-areas I4: written principles carry the full template en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I4 (2 points) |
| solvable with | set of Explains the architecture principle template |
da-principles-subject-areas I5: Q-1 answered - data strategy prevails, its owner rules edu:Question
https://knobit.org/id/register/data-architecture#DA-156
| dcterms:identifier | DA-156 |
|---|---|
| rdfs:label | da-principles-subject-areas I5: Q-1 answered - data strategy prevails, its owner rules en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I5 (2 points) |
| solvable with | set of Explains the alignment of architecture with the data strategy |
da-principles-subject-areas I5: Q-4 answered - concerns framed by viewpoints, answered by views edu:Question
https://knobit.org/id/register/data-architecture#DA-157
| dcterms:identifier | DA-157 |
|---|---|
| rdfs:label | da-principles-subject-areas I5: Q-4 answered - concerns framed by viewpoints, answered by views en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I5 (2 points) |
| solvable with | set of Explains stakeholders, concerns and viewpoints |
Rules of definition edu:Question
https://knobit.org/id/register/data-architecture#DA-1801
| dcterms:identifier | DA-1801 |
|---|---|
| rdfs:label | Rules of definition en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:learningResourceType | multiple_choice |
| schema:text | Which description consists of the main parts of a definition? (a) the nearest superordinate concept and the distinguishing characteristic; (b) only the name of the concept; (c) repeating the concept; (d) only an example en |
| solvable with | set of Explains the rules for defining a concept |
da-enterprise-data-model C1: Core Banking retired and Balance moved edu:Question
https://knobit.org/id/register/data-architecture#DA-201
| dcterms:identifier | DA-201 |
|---|---|
| rdfs:label | da-enterprise-data-model C1: Core Banking retired and Balance moved en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (2 points) |
| solvable with | set of Recognises an application-named subject area, Redistributes an application-named subject area |
da-enterprise-data-model C1: Party and Customer overlap edu:Question
https://knobit.org/id/register/data-architecture#DA-202
| dcterms:identifier | DA-202 |
|---|---|
| rdfs:label | da-enterprise-data-model C1: Party and Customer overlap en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (2 points) |
| solvable with | set of Recognises overlapping subject areas |
da-enterprise-data-model C2: Account has two systems of record edu:Question
https://knobit.org/id/register/data-architecture#DA-203
| dcterms:identifier | DA-203 |
|---|---|
| rdfs:label | da-enterprise-data-model C2: Account has two systems of record en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C2 (2 points) |
| solvable with | set of Recognises a subject area with two systems of record |
da-enterprise-data-model C2: the warehouse is the record for Payment edu:Question
https://knobit.org/id/register/data-architecture#DA-204
| dcterms:identifier | DA-204 |
|---|---|
| rdfs:label | da-enterprise-data-model C2: the warehouse is the record for Payment en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C2 (2 points) |
| solvable with | set of Recognises a reporting store as system of record |
da-enterprise-data-model I1: EN-003 is in two subject areas edu:Question
https://knobit.org/id/register/data-architecture#DA-205
| dcterms:identifier | DA-205 |
|---|---|
| rdfs:label | da-enterprise-data-model I1: EN-003 is in two subject areas en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises an entity in two subject areas |
da-enterprise-data-model I1: Loan has no system of record edu:Question
https://knobit.org/id/register/data-architecture#DA-206
| dcterms:identifier | DA-206 |
|---|---|
| rdfs:label | da-enterprise-data-model I1: Loan has no system of record en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises a subject area with no system of record |
da-enterprise-data-model I1: Card has no domain edu:Question
https://knobit.org/id/register/data-architecture#DA-207
| dcterms:identifier | DA-207 |
|---|---|
| rdfs:label | da-enterprise-data-model I1: Card has no domain en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises a subject area with no owning domain |
da-enterprise-data-model I1: Product is not defined edu:Question
https://knobit.org/id/register/data-architecture#DA-208
| dcterms:identifier | DA-208 |
|---|---|
| rdfs:label | da-enterprise-data-model I1: Product is not defined en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises a subject-area definition defining nothing |
da-enterprise-data-model I1: Chargeback has no term edu:Question
https://knobit.org/id/register/data-architecture#DA-209
| dcterms:identifier | DA-209 |
|---|---|
| rdfs:label | da-enterprise-data-model I1: Chargeback has no term en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises an enterprise entity with no glossary term |
da-enterprise-data-model I1: Repayment Schedule has no entity edu:Question
https://knobit.org/id/register/data-architecture#DA-210
| dcterms:identifier | DA-210 |
|---|---|
| rdfs:label | da-enterprise-data-model I1: Repayment Schedule has no entity en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises an enterprise term with no entity |
da-enterprise-data-model I2: Loan is aligned to Payments edu:Question
https://knobit.org/id/register/data-architecture#DA-211
| dcterms:identifier | DA-211 |
|---|---|
| rdfs:label | da-enterprise-data-model I2: Loan is aligned to Payments en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I2 (1 points) |
| solvable with | set of Recognises a wrong business-area alignment |
da-enterprise-data-model I2: customers are created in CRM edu:Question
https://knobit.org/id/register/data-architecture#DA-212
| dcterms:identifier | DA-212 |
|---|---|
| rdfs:label | da-enterprise-data-model I2: customers are created in CRM en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I2 (1 points) |
| solvable with | set of Recognises a system of record not creating its data |
da-principles-subject-areas C2: LeaseOne, not the BI copy or the channel, as system of record for leases edu:Question
https://knobit.org/id/register/data-architecture#DA-250
| dcterms:identifier | DA-250 |
|---|---|
| rdfs:label | da-principles-subject-areas C2: LeaseOne, not the BI copy or the channel, as system of record for leases en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C2 (2 points) |
| solvable with | set of Explains the system of record |
da-principles-subject-areas C2: lease definition that distinguishes leases from loans edu:Question
https://knobit.org/id/register/data-architecture#DA-251
| dcterms:identifier | DA-251 |
|---|---|
| rdfs:label | da-principles-subject-areas C2: lease definition that distinguishes leases from loans en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C2 (2 points) |
| solvable with | set of Explains definitions distinguishing a concept |
da-principles-subject-areas I2: business-named leasing subject area with its one owning domain edu:Question
https://knobit.org/id/register/data-architecture#DA-252
| dcterms:identifier | DA-252 |
|---|---|
| rdfs:label | da-principles-subject-areas I2: business-named leasing subject area with its one owning domain en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I2 (2 points) |
| solvable with | set of Explains the enterprise data model and its subject areas |
da-principles-subject-areas I2: leasing entities citing their terms, lessee and dealer as party roles edu:Question
https://knobit.org/id/register/data-architecture#DA-253
| dcterms:identifier | DA-253 |
|---|---|
| rdfs:label | da-principles-subject-areas I2: leasing entities citing their terms, lessee and dealer as party roles en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I2 (2 points) |
| solvable with | set of Explains the enterprise data model and its subject areas |
da-principles-subject-areas I3: leasing subject area aligned to BIAN Loans and Deposits edu:Question
https://knobit.org/id/register/data-architecture#DA-254
| dcterms:identifier | DA-254 |
|---|---|
| rdfs:label | da-principles-subject-areas I3: leasing subject area aligned to BIAN Loans and Deposits en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I3 (1 points) |
| solvable with | set of Explains the BIAN service landscape |
da-principles-subject-areas I5: Q-2 answered - system of record creates, reporting store consumes edu:Question
https://knobit.org/id/register/data-architecture#DA-255
| dcterms:identifier | DA-255 |
|---|---|
| rdfs:label | da-principles-subject-areas I5: Q-2 answered - system of record creates, reporting store consumes en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I5 (2 points) |
| solvable with | set of Explains the system of record |
da-principles-subject-areas I5: Q-3 answered - BIAN service landscape as shared vocabulary edu:Question
https://knobit.org/id/register/data-architecture#DA-256
| dcterms:identifier | DA-256 |
|---|---|
| rdfs:label | da-principles-subject-areas I5: Q-3 answered - BIAN service landscape as shared vocabulary en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I5 (2 points) |
| solvable with | set of Explains the BIAN service landscape |
da-data-flows C1: the address is created twice edu:Question
https://knobit.org/id/register/data-architecture#DA-301
| dcterms:identifier | DA-301 |
|---|---|
| rdfs:label | da-data-flows C1: the address is created twice en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (3 points) |
| solvable with | set of Recognises an entity created in two applications |
da-data-flows C1: the double creation is raised to the owners edu:Question
https://knobit.org/id/register/data-architecture#DA-302
| dcterms:identifier | DA-302 |
|---|---|
| rdfs:label | da-data-flows C1: the double creation is raised to the owners en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (3 points) |
| solvable with | set of Recognises an entity created in two applications, Raises a double creation as a business decision |
da-data-flows C1: the address flows into CRM and loops edu:Question
https://knobit.org/id/register/data-architecture#DA-303
| dcterms:identifier | DA-303 |
|---|---|
| rdfs:label | da-data-flows C1: the address flows into CRM and loops en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (3 points) |
| solvable with | set of Recognises a data flow into the system of record, Recognises a circular data flow |
da-data-flows C2: core banking updates card limits edu:Question
https://knobit.org/id/register/data-architecture#DA-304
| dcterms:identifier | DA-304 |
|---|---|
| rdfs:label | da-data-flows C2: core banking updates card limits en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C2 (2 points) |
| solvable with | set of Recognises an update outside the system of record |
da-data-flows C2: the warehouse creates balances edu:Question
https://knobit.org/id/register/data-architecture#DA-305
| dcterms:identifier | DA-305 |
|---|---|
| rdfs:label | da-data-flows C2: the warehouse creates balances en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C2 (2 points) |
| solvable with | set of Recognises a creator outside the system of record |
da-data-flows I1: arrears are created nowhere edu:Question
https://knobit.org/id/register/data-architecture#DA-306
| dcterms:identifier | DA-306 |
|---|---|
| rdfs:label | da-data-flows I1: arrears are created nowhere en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises an entity read with no creator |
da-data-flows I1: FL-005 has no consumer edu:Question
https://knobit.org/id/register/data-architecture#DA-307
| dcterms:identifier | DA-307 |
|---|---|
| rdfs:label | da-data-flows I1: FL-005 has no consumer en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises a data flow with no consumer |
da-data-flows I1: FL-008 sends cards from the payments hub edu:Question
https://knobit.org/id/register/data-architecture#DA-308
| dcterms:identifier | DA-308 |
|---|---|
| rdfs:label | da-data-flows I1: FL-008 sends cards from the payments hub en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises a flow of data its source does not hold |
da-data-flows I1: AS-009 is unknown edu:Question
https://knobit.org/id/register/data-architecture#DA-309
| dcterms:identifier | DA-309 |
|---|---|
| rdfs:label | da-data-flows I1: AS-009 is unknown en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises an unknown application in the matrix |
da-data-flows I1: FL-011 has no frequency edu:Question
https://knobit.org/id/register/data-architecture#DA-310
| dcterms:identifier | DA-310 |
|---|---|
| rdfs:label | da-data-flows I1: FL-011 has no frequency en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises a data flow with no frequency or pattern |
da-data-flows I1: nothing feeds the risk platform edu:Question
https://knobit.org/id/register/data-architecture#DA-311
| dcterms:identifier | DA-311 |
|---|---|
| rdfs:label | da-data-flows I1: nothing feeds the risk platform en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises a broken data value chain |
da-data-flows I2: deletions stay in the warehouse edu:Question
https://knobit.org/id/register/data-architecture#DA-312
| dcterms:identifier | DA-312 |
|---|---|
| rdfs:label | da-data-flows I2: deletions stay in the warehouse en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I2 (1 points) |
| solvable with | set of Recognises a deletion not reaching the copies |
da-flows-roadmap-dependencies C1: core banking's card-limit chain breaks at the switch-off edu:Question
https://knobit.org/id/register/data-architecture#DA-351
| dcterms:identifier | DA-351 |
|---|---|
| rdfs:label | da-flows-roadmap-dependencies C1: core banking's card-limit chain breaks at the switch-off en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (3 points) |
| solvable with | set of Recognises a broken data value chain |
da-flows-roadmap-dependencies C1: every card reader traced to the record after the last state edu:Question
https://knobit.org/id/register/data-architecture#DA-352
| dcterms:identifier | DA-352 |
|---|---|
| rdfs:label | da-flows-roadmap-dependencies C1: every card reader traced to the record after the last state en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (3 points) |
| solvable with | set of Explains data flows and the data value chain |
da-flows-roadmap-dependencies I1: card limits created twice within a transition state edu:Question
https://knobit.org/id/register/data-architecture#DA-353
| dcterms:identifier | DA-353 |
|---|---|
| rdfs:label | da-flows-roadmap-dependencies I1: card limits created twice within a transition state en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises an entity created in two applications, Explains transition architectures and work packages |
da-flows-roadmap-dependencies I1: one creator per card entity at the end of each state edu:Question
https://knobit.org/id/register/data-architecture#DA-354
| dcterms:identifier | DA-354 |
|---|---|
| rdfs:label | da-flows-roadmap-dependencies I1: one creator per card entity at the end of each state en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Explains reading a CRUD matrix by entity, Explains transition architectures and work packages |
da-flows-roadmap-dependencies I2: the replacement warehouse flow drops deletions edu:Question
https://knobit.org/id/register/data-architecture#DA-355
| dcterms:identifier | DA-355 |
|---|---|
| rdfs:label | da-flows-roadmap-dependencies I2: the replacement warehouse flow drops deletions en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I2 (2 points) |
| solvable with | set of Recognises a deletion not reaching the copies |
da-flows-roadmap-dependencies I2: the new fraud feed has no frequency or pattern edu:Question
https://knobit.org/id/register/data-architecture#DA-356
| dcterms:identifier | DA-356 |
|---|---|
| rdfs:label | da-flows-roadmap-dependencies I2: the new fraud feed has no frequency or pattern en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I2 (2 points) |
| solvable with | set of Recognises a data flow with no frequency or pattern |
da-architecture-decisions C1: AD-004 silently reverses AD-005 edu:Question
https://knobit.org/id/register/data-architecture#DA-401
| dcterms:identifier | DA-401 |
|---|---|
| rdfs:label | da-architecture-decisions C1: AD-004 silently reverses AD-005 en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (2 points) |
| solvable with | set of Recognises a silent reversal of a decision |
da-architecture-decisions C1: the reversal is linked or narrowed edu:Question
https://knobit.org/id/register/data-architecture#DA-402
| dcterms:identifier | DA-402 |
|---|---|
| rdfs:label | da-architecture-decisions C1: the reversal is linked or narrowed en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (2 points) |
| solvable with | set of Recognises a silent reversal of a decision, Links a reversing decision to the one it reverses |
da-architecture-decisions C2: AD-008 breaks AP-001 with no exception edu:Question
https://knobit.org/id/register/data-architecture#DA-403
| dcterms:identifier | DA-403 |
|---|---|
| rdfs:label | da-architecture-decisions C2: AD-008 breaks AP-001 with no exception en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C2 (2 points) |
| solvable with | set of Recognises a principle violated without exception |
da-architecture-decisions C2: AD-008 is raised rather than accepted edu:Question
https://knobit.org/id/register/data-architecture#DA-404
| dcterms:identifier | DA-404 |
|---|---|
| rdfs:label | da-architecture-decisions C2: AD-008 is raised rather than accepted en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C2 (2 points) |
| solvable with | set of Recognises a principle violated without exception |
da-architecture-decisions I1: AD-004 has one option edu:Question
https://knobit.org/id/register/data-architecture#DA-405
| dcterms:identifier | DA-405 |
|---|---|
| rdfs:label | da-architecture-decisions I1: AD-004 has one option en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (2 points) |
| solvable with | set of Recognises a decision with no alternatives |
da-architecture-decisions I1: AD-007 lists only benefits edu:Question
https://knobit.org/id/register/data-architecture#DA-406
| dcterms:identifier | DA-406 |
|---|---|
| rdfs:label | da-architecture-decisions I1: AD-007 lists only benefits en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (2 points) |
| solvable with | set of Recognises a decision with only positive consequences |
da-architecture-decisions I1: AD-006 is accepted with an open question edu:Question
https://knobit.org/id/register/data-architecture#DA-407
| dcterms:identifier | DA-407 |
|---|---|
| rdfs:label | da-architecture-decisions I1: AD-006 is accepted with an open question en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (2 points) |
| solvable with | set of Recognises an accepted decision with open questions |
da-architecture-decisions I1: AD-011 chose an option not considered edu:Question
https://knobit.org/id/register/data-architecture#DA-408
| dcterms:identifier | DA-408 |
|---|---|
| rdfs:label | da-architecture-decisions I1: AD-011 chose an option not considered en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (2 points) |
| solvable with | set of Recognises a decision outside its options |
da-architecture-decision-records C1: TP-003 names a system of record no decision gives it edu:Question
https://knobit.org/id/register/data-architecture#DA-450
| dcterms:identifier | DA-450 |
|---|---|
| rdfs:label | da-architecture-decision-records C1: TP-003 names a system of record no decision gives it en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (4 points) |
| solvable with | set of Recognises a placement contradicting the system of record |
da-architecture-decision-records C1: TP-005 cites the superseded AD-003 edu:Question
https://knobit.org/id/register/data-architecture#DA-451
| dcterms:identifier | DA-451 |
|---|---|
| rdfs:label | da-architecture-decision-records C1: TP-005 cites the superseded AD-003 en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (4 points) |
| solvable with | set of Recognises a placement citing a superseded decision |
da-architecture-decision-records C1: TP-004 is accepted with no decision edu:Question
https://knobit.org/id/register/data-architecture#DA-452
| dcterms:identifier | DA-452 |
|---|---|
| rdfs:label | da-architecture-decision-records C1: TP-004 is accepted with no decision en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (4 points) |
| solvable with | set of Recognises a placement with no decision |
da-architecture-decision-records C1: SA-008 Product has no target placement edu:Question
https://knobit.org/id/register/data-architecture#DA-453
| dcterms:identifier | DA-453 |
|---|---|
| rdfs:label | da-architecture-decision-records C1: SA-008 Product has no target placement en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (4 points) |
| solvable with | set of Recognises a subject area with no target placement |
da-architecture-decision-records C2: AD-009 records no context edu:Question
https://knobit.org/id/register/data-architecture#DA-454
| dcterms:identifier | DA-454 |
|---|---|
| rdfs:label | da-architecture-decision-records C2: AD-009 records no context en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C2 (2 points) |
| solvable with | set of Recognises a decision record with no context |
da-architecture-decision-records C2: AD-010 is accepted with no decider or date edu:Question
https://knobit.org/id/register/data-architecture#DA-455
| dcterms:identifier | DA-455 |
|---|---|
| rdfs:label | da-architecture-decision-records C2: AD-010 is accepted with no decider or date en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C2 (2 points) |
| solvable with | set of Recognises an accepted decision with no decider |
da-architecture-decision-records I1: the AD-014 exception lacks the principle owner's approval edu:Question
https://knobit.org/id/register/data-architecture#DA-456
| dcterms:identifier | DA-456 |
|---|---|
| rdfs:label | da-architecture-decision-records I1: the AD-014 exception lacks the principle owner's approval en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (1 points) |
| solvable with | set of Explains principle exceptions |
da-architecture-decision-records I2: TP-007 targets a platform retired before the target date edu:Question
https://knobit.org/id/register/data-architecture#DA-457
| dcterms:identifier | DA-457 |
|---|---|
| rdfs:label | da-architecture-decision-records I2: TP-007 targets a platform retired before the target date en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I2 (1.5 points) |
| solvable with | set of Explains lifecycle projections |
da-architecture-decision-records I2: AD-011 hosting belongs to the technology domain edu:Question
https://knobit.org/id/register/data-architecture#DA-458
| dcterms:identifier | DA-458 |
|---|---|
| rdfs:label | da-architecture-decision-records I2: AD-011 hosting belongs to the technology domain en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I2 (1.5 points) |
| solvable with | set of Explains the enterprise architecture domains |
da-architecture-decision-records I3: G-3 confuses Zachman with the TOGAF ADM edu:Question
https://knobit.org/id/register/data-architecture#DA-459
| dcterms:identifier | DA-459 |
|---|---|
| rdfs:label | da-architecture-decision-records I3: G-3 confuses Zachman with the TOGAF ADM en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I3 (1.5 points) |
| solvable with | set of Explains enterprise architecture frameworks |
da-architecture-decision-records I3: G-5 diagram has no legend and the wrong level of detail edu:Question
https://knobit.org/id/register/data-architecture#DA-460
| dcterms:identifier | DA-460 |
|---|---|
| rdfs:label | da-architecture-decision-records I3: G-5 diagram has no legend and the wrong level of detail en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I3 (1.5 points) |
| solvable with | set of Explains clear architecture diagrams |
da-architecture-decision-records I3: G-7 keeps the model as slide pictures, no architecture tool edu:Question
https://knobit.org/id/register/data-architecture#DA-461
| dcterms:identifier | DA-461 |
|---|---|
| rdfs:label | da-architecture-decision-records I3: G-7 keeps the model as slide pictures, no architecture tool en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I3 (1.5 points) |
| solvable with | set of Explains data architecture tools |
da-architecture-decision-records I4: G-2 states no business drivers edu:Question
https://knobit.org/id/register/data-architecture#DA-462
| dcterms:identifier | DA-462 |
|---|---|
| rdfs:label | da-architecture-decision-records I4: G-2 states no business drivers en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I4 (2 points) |
| solvable with | set of Explains the business drivers of data architecture |
da-architecture-decision-records I4: G-6 rates readiness risk low against its evidence edu:Question
https://knobit.org/id/register/data-architecture#DA-463
| dcterms:identifier | DA-463 |
|---|---|
| rdfs:label | da-architecture-decision-records I4: G-6 rates readiness risk low against its evidence en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I4 (2 points) |
| solvable with | set of Explains data architecture readiness and risk assessment |
da-architecture-decision-records I4: G-8 publishes architecture as a document, not a practice edu:Question
https://knobit.org/id/register/data-architecture#DA-464
| dcterms:identifier | DA-464 |
|---|---|
| rdfs:label | da-architecture-decision-records I4: G-8 publishes architecture as a document, not a practice en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I4 (2 points) |
| solvable with | set of Explains organisational change for data architecture |
da-architecture-decision-records I4: G-9 measures ADR counts, not compliance or value edu:Question
https://knobit.org/id/register/data-architecture#DA-465
| dcterms:identifier | DA-465 |
|---|---|
| rdfs:label | da-architecture-decision-records I4: G-9 measures ADR counts, not compliance or value en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I4 (2 points) |
| solvable with | set of Explains data architecture governance and metrics |
da-roadmap C1: the warehouse is switched off before FINREP moves edu:Question
https://knobit.org/id/register/data-architecture#DA-501
| dcterms:identifier | DA-501 |
|---|---|
| rdfs:label | da-roadmap C1: the warehouse is switched off before FINREP moves en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (3 points) |
| solvable with | set of Recognises decommissioning before the consumers move |
da-roadmap C1: the decommissioning is resequenced edu:Question
https://knobit.org/id/register/data-architecture#DA-502
| dcterms:identifier | DA-502 |
|---|---|
| rdfs:label | da-roadmap C1: the decommissioning is resequenced en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (3 points) |
| solvable with | set of Recognises decommissioning before the consumers move, Resequences decommissioning after the consumers move |
da-roadmap C1: forward and unknown dependencies edu:Question
https://knobit.org/id/register/data-architecture#DA-503
| dcterms:identifier | DA-503 |
|---|---|
| rdfs:label | da-roadmap C1: forward and unknown dependencies en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (3 points) |
| solvable with | set of Recognises a forward dependency in a roadmap, Recognises a dependency on an unknown package |
da-roadmap I1: TS-2 has no exit criteria edu:Question
https://knobit.org/id/register/data-architecture#DA-504
| dcterms:identifier | DA-504 |
|---|---|
| rdfs:label | da-roadmap I1: TS-2 has no exit criteria en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises a transition state with no exit criteria |
da-roadmap I1: WP-004 realises nothing edu:Question
https://knobit.org/id/register/data-architecture#DA-505
| dcterms:identifier | DA-505 |
|---|---|
| rdfs:label | da-roadmap I1: WP-004 realises nothing en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises a work package realising nothing |
da-roadmap I1: TP-004 is unreached edu:Question
https://knobit.org/id/register/data-architecture#DA-506
| dcterms:identifier | DA-506 |
|---|---|
| rdfs:label | da-roadmap I1: TP-004 is unreached en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises a target element no package reaches |
da-roadmap I1: WP-008 and WP-009 change Party in parallel edu:Question
https://knobit.org/id/register/data-architecture#DA-507
| dcterms:identifier | DA-507 |
|---|---|
| rdfs:label | da-roadmap I1: WP-008 and WP-009 change Party in parallel en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises parallel changes to one system of record |
da-roadmap I1: WP-005 has no owner edu:Question
https://knobit.org/id/register/data-architecture#DA-508
| dcterms:identifier | DA-508 |
|---|---|
| rdfs:label | da-roadmap I1: WP-005 has no owner en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises a work package with no owner |
da-roadmap I1: TS-3 is dated before TS-2 edu:Question
https://knobit.org/id/register/data-architecture#DA-509
| dcterms:identifier | DA-509 |
|---|---|
| rdfs:label | da-roadmap I1: TS-3 is dated before TS-2 en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises transition states out of order |
da-roadmap I2: WP-007 realises a superseded decision edu:Question
https://knobit.org/id/register/data-architecture#DA-510
| dcterms:identifier | DA-510 |
|---|---|
| rdfs:label | da-roadmap I2: WP-007 realises a superseded decision en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I2 (1 points) |
| solvable with | set of Recognises a package realising a superseded decision |
da-roadmap I2: TS-3 exits on 'Platform ready' edu:Question
https://knobit.org/id/register/data-architecture#DA-511
| dcterms:identifier | DA-511 |
|---|---|
| rdfs:label | da-roadmap I2: TS-3 exits on 'Platform ready' en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I2 (1 points) |
| solvable with | set of Recognises an unmeasurable exit criterion |
da-flows-roadmap-dependencies C1: the card-limit feed moves before the switch-off edu:Question
https://knobit.org/id/register/data-architecture#DA-551
| dcterms:identifier | DA-551 |
|---|---|
| rdfs:label | da-flows-roadmap-dependencies C1: the card-limit feed moves before the switch-off en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C1 (3 points) |
| solvable with | set of Resequences decommissioning after the consumers move |
da-flows-roadmap-dependencies C2: fraud monitoring ordered after the switch-off edu:Question
https://knobit.org/id/register/data-architecture#DA-552
| dcterms:identifier | DA-552 |
|---|---|
| rdfs:label | da-flows-roadmap-dependencies C2: fraud monitoring ordered after the switch-off en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C2 (2 points) |
| solvable with | set of Recognises decommissioning before the consumers move |
da-flows-roadmap-dependencies C2: WP-021 and WP-026 depend on each other edu:Question
https://knobit.org/id/register/data-architecture#DA-553
| dcterms:identifier | DA-553 |
|---|---|
| rdfs:label | da-flows-roadmap-dependencies C2: WP-021 and WP-026 depend on each other en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | C2 (2 points) |
| solvable with | set of Recognises a forward dependency in a roadmap |
da-flows-roadmap-dependencies I1: card transactions moved by no package edu:Question
https://knobit.org/id/register/data-architecture#DA-554
| dcterms:identifier | DA-554 |
|---|---|
| rdfs:label | da-flows-roadmap-dependencies I1: card transactions moved by no package en |
| schema:isPartOf | Data architecture (DAMA-DMBOK2) |
| schema:isPartOf | I1 (3 points) |
| solvable with | set of Recognises a flow of data its source does not hold, Recognises a target element no package reaches |
DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture schema:CreativeWork
https://knobit.org/id/register/data-architecture#REF-1
| dcterms:identifier | REF-1 |
|---|---|
| dcterms:publisher | DAMA International |
| dcterms:title | DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 4: Data Architecture en |
| schema:version | 2nd edition, revised (DMBOK2/RE) |
| skos:note | target level: CDMP Associate: the data architecture questions of the Data Management Fundamentals exam (DAMA International); CDMP has no data architecture specialist exam en |