Data architecture pack
Ratings for the Data architecture pack
Model enterprise data entities, ownership and flows, and plan data governance, integration and migration
Who it is for. Enterprise and data architects who own the data architecture domain: the data half of TOGAF Phase C, its catalogs, matrices, diagrams and gap analysis, and the wider practice of data governance, master data, quality, lineage, platforms, integration, migration and retention.
225 blocks, 80 prompts, 6 prompt sets, 40 variables, in 19 topics. Version 2.
Made for Pro. Every download starts with 14 days of Pro, so you can add this pack today and use all of it; on the Free plan you can add it and read it, with your library read-only until you move to Pro or remove it. How packs work on Free and Pro
How to add a pack
- Download the pack. It is a single file that ends in .promptmason.json.
- In PromptMason, open Settings → Backup & data → Block packs and choose Add a pack from a file….
- Pick the file you downloaded.
The pack is added next to what you have, in a folder named for the pack with one subfolder for each topic. See Add a block pack for the details.
What is inside
Topics
- Data principles and the data architecture charter
- Baseline data architecture
- Data entity and data component catalog
- Conceptual, logical and physical data models
- Business glossary and data definitions
- Data entity to function and application matrices
- Data dissemination and lifecycle diagrams
- Data classification and data security architecture
- Privacy by design in the architecture
- Target data architecture, gap analysis and roadmap components
- Master and reference data management
- Data ownership, stewardship and the governance operating model
- Data quality dimensions and rules
- Data lineage and metadata management
- Analytics and data platform target states
- Enterprise data integration patterns
- Data migration architecture
- Data retention and archiving
- Data due diligence and integration in mergers and acquisitions
Data principles and the data architecture charter
- Role blocks
- Enterprise data architect, Data architect writing for business leaders
- Context blocks
- Organization and data landscape, Architecture engagement, Modelling standards and repository, Data principles in force, Draft artefact to review
- Task blocks
- Data principles catalog, Review a draft data principle, Data architecture scope and concerns note, Architecture approach note to the sponsor, Kick-off conversation with the chief data officer, Principle exception request
- Format blocks
- Principle statement, Architecture document section, Short note to a stakeholder, Review findings
- Constraints blocks
- Work only from the material given, Not legal advice, Principles must be testable, Say which work product this feeds, Write for the reader named, Name the standard, do not quote it
- Prompts
- Data principles catalog; Review a draft principle; Scope the data architecture work; Approach note and CDO kick-off; Principle exception request
- Prompt sets (what is a prompt set?)
- Run Phase C, Data Architecture. From the scope of the data work to its stakeholder review: baseline, target, gaps and work packages, in order.
- Scope the data architecture work
- Baseline inventory and entity list
- Baseline description and questions to owners
- Baseline assessment and system of record conflicts
- Target data architecture
- Gap analysis and impact
- Roadmap work packages
- Stakeholder review of the data architecture
Baseline data architecture
- Context blocks
- Baseline inventory
- Task blocks
- Inventory of data stores by domain, Baseline data entity list, Baseline data architecture description, Baseline assessment, System of record conflicts list, Questions for application owners
- Format blocks
- Catalog table
- Constraints blocks
- Name the system of record or say there is none, Say what is unknown and how to find out
- Prompts
- Baseline inventory and entity list; Baseline description and questions to owners; Baseline assessment and system of record conflicts
Data entity and data component catalog
- Role blocks
- Data modeller
- Context blocks
- Catalog extract
- Task blocks
- Define the data entities, Logical data components, Physical data components, Catalog review for overlap and gaps, Catalog maintenance standard, Catalog walkthrough note to domain owners
- Format blocks
- Standard document
- Constraints blocks
- One entity, one definition, Catalog entries complete or marked draft, Use the glossary's words
- Prompts
- Define the data entities; Logical and physical data components; Review the catalog; Catalog standard and walkthrough note
Conceptual, logical and physical data models
- Role blocks
- Data architecture reviewer
- Context blocks
- Data model description
- Task blocks
- Conceptual data model for a domain, Logical data model from the conceptual, Physical data model considerations, Data model review, Reconcile two models of one domain, Explain a data model to business readers
- Format blocks
- Model described in words, Plain-language brief for leaders
- Constraints blocks
- Logical before physical, Review the artefact, not the author, Business terms for business readers
- Prompts
- Conceptual data model; Logical data model; Physical model considerations; Model review and reconciliation; Explain the model to the business
- Prompt sets (what is a prompt set?)
- Model a domain from conceptual to physical. One domain modelled conceptual, logical and physical, reviewed, and explained to the business, in order.
- Conceptual data model
- Logical data model
- Physical model considerations
- Model review and reconciliation
- Explain the model to the business
Business glossary and data definitions
- Role blocks
- Business glossary owner
- Context blocks
- Glossary extract, Data governance bodies and policies
- Task blocks
- Define a business term, Resolve a definition conflict, Glossary coverage review, Glossary standard, Definition sign-off request to a business owner, Glossary to data model mapping
- Format blocks
- Glossary entry, Mapping table
- Constraints blocks
- Definitions must decide edge cases, Decision rights by role, never by person
- Prompts
- Define a business term; Resolve a definition conflict; Glossary coverage and model mapping; Glossary standard
Data entity to function and application matrices
- Context blocks
- Matrix inputs
- Task blocks
- Data entity to business function matrix, Application to data matrix, Analyse the matrices for system of record candidates, Gaps and overlaps from the matrices, Conversation with application owners about a conflict, Matrix refresh and repository update note
- Format blocks
- Matrix as a table
- Constraints blocks
- A matrix ends with what it shows
- Prompts
- Entity to business function matrix; Application to data matrix; What the matrices show; Settle a system of record conflict
Data dissemination and lifecycle diagrams
- Context blocks
- Data flow facts
- Task blocks
- Data dissemination diagram, Copies and hops analysis, Data lifecycle diagram for an entity, Lifecycle events and owning functions, Cross-domain flow narrative, Diagram review
- Format blocks
- Diagram described for drawing, Register table, Lifecycle states table
- Constraints blocks
- Diagrams a colleague can draw
- Prompts
- Data dissemination diagram; Copies and hops; Entity lifecycle; Flow narrative for leaders; Review a diagram
Data classification and data security architecture
- Role blocks
- Data security architect
- Context blocks
- Classification scheme, Access facts
- Task blocks
- Classify a domain's entities, Data security diagram, Access patterns and segregation at the architecture level, Classification standard, Classification gap list, Security requirements for the architecture requirements specification
- Format blocks
- Classification table
- Constraints blocks
- Classification follows the scheme, Least data, least access
- Prompts
- Classify the entities; Data security diagram; Access patterns and security requirements; Classification standard and gaps
Privacy by design in the architecture
- Role blocks
- Privacy-minded data architect
- Context blocks
- Personal data facts, Legal and compliance inputs
- Task blocks
- Personal data inventory for an initiative, Privacy design review, Inputs to a privacy impact assessment, Cross-border data map, Rights-request support design, Privacy questions for legal
- Format blocks
- Personal data inventory table
- Constraints blocks
- Obligations come from legal and compliance, Personal data is named, never implied
- Prompts
- Personal data inventory; Privacy design review; Privacy assessment inputs and questions for legal; Cross-border map and rights support
- Prompt sets (what is a prompt set?)
- Design an initiative for privacy. From the personal data inventory to the design review, the privacy assessment inputs and the cross-border map, in order.
- Personal data inventory
- Privacy design review
- Privacy assessment inputs and questions for legal
- Cross-border map and rights support
Target data architecture, gap analysis and roadmap components
- Context blocks
- Target drivers, Baseline and target descriptions
- Task blocks
- Target data architecture description, Target data components and building blocks, Data gap analysis, Impact on business, application and technology architectures, Candidate work packages for the roadmap, Target architecture brief for leaders, Data architecture stakeholder review and sign-off, Data requirements for the architecture requirements specification
- Format blocks
- Gap analysis table, Stakeholder review record, Work packages table
- Constraints blocks
- Every gap names a baseline, a target and an owner, Vendor-neutral by default
- Prompts
- Target data architecture; Building blocks and data requirements; Gap analysis and impact; Roadmap work packages; Stakeholder review of the data architecture; Target brief for leaders
Master and reference data management
- Role blocks
- Master data architect
- Context blocks
- Master data facts
- Task blocks
- Master data domain assessment, MDM architecture style options, Golden record and survivorship rules, Reference data governance, Hierarchy management design, Master data case for the governance body
- Format blocks
- Scorecard layout, Decision paper for the governance body
- Constraints blocks
- Trade-offs both ways
- Prompts
- Master data assessment; MDM style decision and case; Golden record and hierarchies; Reference data governance
- Prompt sets (what is a prompt set?)
- Master an entity. From which entities deserve mastering to the style decision and the golden record rules, in order.
- Master data assessment
- MDM style decision and case
- Golden record and hierarchies
Data ownership, stewardship and the governance operating model
- Role blocks
- Data governance lead
- Context blocks
- Data roles and people facts
- Task blocks
- Data ownership model, RACI for a data domain, Data steward role description, Governance council charter, Policy and standards hierarchy, Governance operating model paper
- Format blocks
- RACI table, Role description, Operating model description
- Constraints blocks
- Every role has time and a measure
- Prompts
- Ownership model and RACI; Data steward role; Council charter and policy hierarchy; Governance operating model paper
Data quality dimensions and rules
- Role blocks
- Data quality lead
- Context blocks
- Quality facts
- Task blocks
- Critical data elements, Quality rules by dimension, Thresholds and quality targets, Quality scorecard design, Root cause at the architecture level, Quality remediation plan, Quality requirements for the architecture requirements specification
- Format blocks
- Rule specification table
- Constraints blocks
- A quality rule names element, dimension, test and threshold, Stay at the enterprise level
- Prompts
- Critical elements and quality rules; Thresholds and scorecard; Root cause and remediation; Quality requirements for the specification
Data lineage and metadata management
- Role blocks
- Metadata and lineage architect
- Context blocks
- Lineage facts
- Task blocks
- Lineage scope and granularity, Lineage for a critical report, Metadata architecture, Metadata standard, Lineage gap assessment, Impact analysis with lineage
- Constraints blocks
- Lineage states its granularity and evidence
- Prompts
- Lineage scope and a critical report's lineage; Metadata architecture; Metadata standard; Lineage gaps and impact analysis
Analytics and data platform target states
- Role blocks
- Analytics platform architect
- Context blocks
- Platform facts
- Task blocks
- Platform options compared, Platform target state description, Specify a data product, Domain and platform team split, Consumption patterns and serving layer, Platform transition stages
- Format blocks
- Options comparison table, Data product specification
- Constraints blocks
- Every data product names its consumers
- Prompts
- Platform options; Target platform state; Data product; Team split and transition stages
Enterprise data integration patterns
- Role blocks
- Data integration architect
- Context blocks
- Integration facts
- Task blocks
- Integration pattern per flow, Canonical model or point to point, Data exchange standard and event governance, Data contracts between domains, Integration principles, Integration gap list
- Format blocks
- Pattern recommendation per interface
- Prompts
- Integration pattern per flow; Canonical model decision; Exchange standard and data contracts; Integration principles and gaps
Data migration architecture
- Role blocks
- Data migration architect
- Context blocks
- Migration facts
- Task blocks
- Migration strategy options, Data migration diagram, Entity-level source to target mapping, Cleanse before or after decision, Reconciliation and cutover approach, Migration risk register, Legacy archive decision
- Constraints blocks
- Every migration object reconciles
- Prompts
- Migration strategy and diagram; Mapping and cleansing decisions; Reconciliation and cutover; Migration risks and legacy archive
- Prompt sets (what is a prompt set?)
- Plan a data migration. From the migration strategy to the mapping, the reconciliation and cutover, and the risks and legacy archive, in order.
- Migration strategy and diagram
- Mapping and cleansing decisions
- Reconciliation and cutover
- Migration risks and legacy archive
Data retention and archiving
- Role blocks
- Data lifecycle and retention architect
- Context blocks
- Retention inputs
- Task blocks
- Map entities to retention classes, Archive tier design, Deletion and disposal design, Legal hold design, Retention gap assessment, Note to records management and legal
- Constraints blocks
- Retention periods come from the schedule
- Prompts
- Retention mapping; Archive and disposal design; Legal hold and retention gaps; Note to records management and legal
Data due diligence and integration in mergers and acquisitions
- Role blocks
- Data due diligence lead
- Context blocks
- Deal facts
- Task blocks
- Data due diligence request list, Data landscape assessment of the target, Data risk register for the deal, Integration options for the two data estates, Day one data requirements, Data integration roadmap after close, Carve-out data architecture
- Format blocks
- Due diligence findings, Checklist with owners
- Constraints blocks
- Fact, inference, unknown
- Prompts
- Due diligence request list; Landscape assessment and data risks; Integration options and carve-out; Day one and the integration roadmap
- Prompt sets (what is a prompt set?)
- Data due diligence and integration for a deal. From the data request list to the day one actions and the integration roadmap, in order.
- Due diligence request list
- Landscape assessment and data risks
- Integration options and carve-out
- Day one and the integration roadmap