Required Skills

Data Modeler

Work Authorization

  • Us Citizen

  • Green Card

Preferred Employment

  • Corp-Corp

Employment Type

  • Consulting/Contract

education qualification

  • UG :- - Not Required

  • PG :- - Not Required

Other Information

  • No of position :- ( 1 )

  • Post :- 8th Dec 2021

JOB DETAIL

1.      Erwin Data Modeling Tool (Preferably version 8 or above)and/or ER Studio Data Modeling tool (preferably version 16 or above)

2.      Oracle 10g or above

3.      SQL (Structure Query Language) skills

Core Capabilities

•        ER Diagram design

•        Logical / Physical Model design

•        Metadata Management (Data Dictionary and Data Lineage)

•        Data Normalization and De-Normalization rules knowledge

•        Source to Target mapping document creation skills

•        Responsible for identifying data entities and describing the relationships between them, as a model, based on business context, process and existing systems clearly showing source to target mappings.  Generally a data modeler is concerned with intra-system data design.

•        Understand the concepts of persistent and transient data design & modelling including entity-relationship, conceptual, logical and physical models. High-level data design patterns & frameworks (e.g. Kimball, Inmon, Data Vault, NoSQL, XML, canonical models)

•        Derive data concepts from documented requirements

•        Ability to clarify requirements with stakeholders to resolve gaps, uncertainties and conflicts

•        Familiar with concepts of Relational Data-Base Management Systems (RDBMS); Big Data; Extract Transform & Load (ETL); Business Intelligence (BI) and Analytics toolsets

•        Understands the concepts of data entities, attributes, relationships

•        Understands the use of advanced constructs including super-types/sub-types, self-referencing relationships and arcs

•        Can identify logical entities from a business scenario and determine full scope of relationship cardinalities including optionality

•        Build complex logical models featuring distinctions including identifying/non identifying relationships, subtype discriminators

•        Good knowledge of at least one major RDBMS’ physical metadata capabilities.

•        Can build a basic physical schema and objects based on a provided logical model

•        Familiar with modelling approaches to change data capture (slowly changing dimensions)

•        Can create comprehensive multidimensional models based on in-principle reporting requirements

Company Information