Data Architecture Practices

As Data architect when you start on the project DA needs to participate in below activities : 

1. Functional Analysis Review

2. "Discussion with Dataviz if not covered under Functional Analysis"

3. Source System Analysis
   

   1. Description : In this activity DA needs to understand the source that has been requested by business, document the source tables etc
   2.  Tools : If the source is BW then use Xtract to asses the SAP BW, if source is anyother system for ex SAP, salesforce, request access of it for analysis of tables.
   3. Deliverable : Documenting the sources in mapping document 

4. Create Xtract configuration for SAPBW Description :

   1. Description : If the source for the project is the SAP BW then use use Xtract to configure and retrive data.
   2. Step by Step guide to connect to Xtract and get the URL for Talend
   3. Once you get the URL , insert it the mapping document

5. Create Tables / Views

6. Data Modeling

   1. Data architect are in charge to design the Data Model, preferably applying Dimensional Modeling Concepts and Techniques described by Ralph Kimball.
   2. After aligning the data objects allocation to a specific business domain, the Data Architect designs the Data Model, using genmymodel tool. https://app.genmymodel.com/
   3. Domain-oriented data models are stored in a dedicated Genmymodel project named: "*DOMAIN name* DOMAIN - DATA MODEL"                                                                                                       
   4. Inside a domain-oriented project, the data models are organized in a group hierarchy
      1. Level 1: domain-oriented, this group is named with the GCP project id (such as: prj-data-dm-marketing-dev)
      2. Level 2: three sub-groups: STG, ODS, DM. The Data Architect focuses on the DM, the level were the data model is stored
   5. Inside the DM group, the Data Model is described by the Data Architect by FACT (transactional data) and Dimensions tables (static or almost static data)                                                                                                                   
   6. The Data Architect completes the list of fields of each table and add the relationships between tables.
   7. Once the design is complete, the Data Architect submits the work to peer-review with the Data Architecture team.

7. Create Tables / Views

8. DPL - Modeling

9. Specifiy Maps to ODS

10. Data Transformation Rules to Data model

    1. Data transformation will cover required transformation rules to transform the data from source to target 
    2. Below are the high level details on the document
       1. Source and Target table name
       2. Type of the target table (Master table (SCD1 or SCD2) or Transaction table)
       3. Transformation rules to be applied
       4. Mandatory and primary key attributes
       5. Attributes to be used part of SCD2 to track the changes
    3. Example template: 

11. DTR to DPL

12. Updating Data Catalog Document

13. Quality inspection assurance

14. Data Flows

15. Manager Security roles on GCP