We provide IT Staff Augmentation Services!

Data Modeler Resume

2.00/5 (Submit Your Rating)

Dallas, TX

SUMMARY

  • 7+ years of extensive experience in teh complete Software Development Life Cycle (SDLC) covering Requirements Management, Data Analysis, Data Modeling, System Analysis, Architecture and Design, Development, Testing and Deployment of business applications
  • Strong Data Modeling experience using ER diagram, Dimensional/Hierarchical data modeling, Star Schema modeling, Snow - flake modeling using tools like Erwin, ERStudio
  • Created DDL Confidential for implementing Data Modeling changes. Created ERWIN reports in HTML, RTF format depending upon teh requirement, Published Data model in model mart, created naming convention files, co-coordinated with DBAs’ to apply teh data model changes
  • Extensive experience in Data Conversion in ACH Transactions
  • Extensive experience in gathering business requirements, implementing business processes, identifying risks, impact analysis, UML modeling, sequence and activity diagrams and using Rational Rose
  • Utilized RUP (Rational Unified Process) to configure and develop processes, standards, and procedures
  • Possess strong Conceptual and Logical Data Modeling skills, TEMPhas experience with JAD sessions for requirements gathering, creating data mapping documents, writing functional specifications, queries
  • Created/maintained/modified data base design document with detailed description of logical entities and physical tables
  • Excellent noledge of waterfall, spiral and Agile methodologies of Software Development Life Cycle (SDLC)
  • Expertise in Software Development Life Cycle Process (SDLC), Use Cases and Rational Unified Process (RUP)
  • Possess strong Documentation skill and noledge sharing among Team, conducted data modeling review sessions for different user groups, participated in requirement sessions to identify requirement feasibility
  • Extensive Experience working with business users/SMEs as well as senior management
  • Strong understanding of teh principles of Data warehousing, Fact Tables, Dimension Tables, star and snowflake schema modeling
  • Experience in backend programming including schema and table design, stored procedures, Triggers, Views, and Indexes
  • Possess a strong analytical, verbal, inter-personal skill that helps in communicating with developers, team members

TECHNICAL SKILLS

Data Modeling Tools: IBM InfoSphere Data Architect 7.6.0, ER/Studio 8.5, Erwin 4.1.4/ 7.5.8, Power Designer 12.1, Rational Rose, and Visio

Database: SystemsTera Data, Oracle (11g/10g/9i/8i/7.x), SQL Server (2005/2000/7.0), Microsoft Access 2007, DB2, MySQL

Data Warehousing: Informatica Power Center 8.1/8.0/7.1/7.0/6.2/6.1/5.2, Informatica PowerMart 4.7, PowerConnect, Power Exchange, Data Profiling, Data cleansing, OLAP, OLTP, SQL*Plus.

Software Engineering: UML using Visio

Office Applications: MS Office 2007 (Word, Excel, PowerPoint)

Configuration Management: Clear case, Visual Source Safe and Concurrent Version Control, Remedy

Operating Systems: Windows95/98/2000/XP, Solaris, Linux, AIX

Quality Assurance: Business and Software Process and Procedure Definition, Quality Models and standards (ISO 9001 2000 CMM,CMMI,TQM Principles, Six Sigma concepts), Quality tools (Ishikawa diagram, Pareto analysis, histogram Process), Measures and Metrics, Project Reviews, Audits and Assessments

Testing: QTP, Quality Center

PROFESSIONAL EXPERIENCE

Confidential

Data Modeler

Responsibilities:

  • Involved in Source code scanning and analysis
  • Derived logical data model from source systems
  • Obtained DDL of Production Data Stores
  • Mapped physical to logical definitions
  • Worked on Extended Transactions History (ETH), Account Transactions History (ATH) and Real Time Account Maintenance (RTAM) domains
  • Created logical data model with physical mapping for ATH, ETH and RTAM subject areas
  • Standardize naming conventions to better reflect business needs
  • Attended review sessions for Logical Data Model review Account processing and domain review combined Function Data & Service Modeling and Data modeling for CDS Transactions
  • Worked on gap analysis and Compared between CDS Transactions columns to teh existing IBM IFW Industry Data Model
  • Prepared User Guide for IDA data model tool Created teh workspace in Rational Team Concert (RTC) and worked on Check in, check out & delivering, accepting teh changes
  • Worked on BOM level in RTC for ETH: Merged teh ETH and ATH Logical model and generated teh Physical data Model
  • Worked on Business Objective Model (BOM-IBM IFW Industry model) level for ATH: Created new classes, added attributes to teh entities and customized teh new fields
  • Worked under PDM Level for ATH: Reverse Engineer teh DDL and created teh PDM Added abbreviations, relationships to teh entities and delivered in to Rational Team Concert (RTC)
  • Analyzed teh Interface Data Mapping document for Account Open / Maintenance / Inquiry - DDA and mapped teh fields from teh Legacy systems to teh Target Logical (BOM) and created teh consolidated Mapping document for DDA
  • Worked on teh common fields in both Account DDA and CDS and Mapped to teh target data base

Environment: Main Frames, COBOL, DB2, VSAM, ORACLE, Java, IBM InfoSphere Data Architect 7.6.0, Rational Team Concert, Windows, XP, XML, Excel, Access, Visio

Confidential, Dallas, TX

Data Modeler

Responsibilities:

  • Analyzed teh DW project database requirements from teh users in terms of teh tables which will be most useful
  • Analyzed teh requirements for developing Conceptual model
  • Defined relationships, cardinalities among entities
  • Created and maintained Database Objects (Tables, Views, Indexes, Sequences, Database triggers, stored procedures etc.)
  • Analyzed existing logical data model (LDM) and made appropriate changes to make it compatible with business logic
  • Involved in data model reviews with internal data architect, business analysts, and business users with in depth explanation of teh data model to make sure it is in line with business requirements
  • Worked on analyzing source systems and their connectivity
  • Worked with cross-functional teams and prepared detailed design documents for production phase of current customer database application

Environment: SQL Server 2000/ 2005, Teradata 12, Oracle 9i, DB2, Main Frames, Erwin 7.5.8, Windows 7, XML, Excel, Access, Visio

Confidential, Phoenix, AZ

Data Architect/Data Modeler

Responsibilities:

  • Updated and captured latest Metadata and Reconciled existing Data Dictionaries for Organization, Integrity Checks and Relationship Accuracy
  • Managed Data Content by researching existing Data Flow Diagrams, Data Stores, Data Models, Data Qualification and Standardization rules, and Systems Documentation
  • Developed Confidential Master lists and Data Dictionaries of Pharmacy (Rx), 837 Institutional (Hx) & 837 Professional (Mx) Business Elements with tightly coupled derivative fields and grouped them logically within teh Standard Data Context within teh organization
  • Reverse-Engineered and Linked teh Business Element Names from teh various Master lists back to teh (expected) Physical Instance Names in multiple Data Stores
  • Captured and highlighted key elements for Core Business Functions such as Practitioner Matching, De-Duplication, and Qualification; referenced Data Quality Constraints and rules for key elements wherever appropriate
  • Interviewed Technical Staff with regard to teh Data Content, Data Standards, Data Process, Data Services and Data Rules
  • Researched existing data models, data structures, table content (using Toad) excel mapping files, and various data sources for dimensional and transaction data to build teh metadata mapping in E/R Studio
  • Utilized E/R Studio to create comprehensive mapping documents and data lineage
  • Exported new or existing Data Mappings and Database Schema changes from Logical Data Models (LDMs) in E/R Studio into Physical Data Models (PDMs) and worked closely with fellow DAs and DBAs to translate and implement these models
  • Conducted Structured Review sessions to reconcile model updates and related work with Senior Data Architects and Data Governance/Data Architecture Manager
  • Organized and Published Detailed Data Content on SharePoint Knowledge Base following Peer-Review, Consensus and Sign-off
  • Published teh mapping from E/R Studio in a form for non-technical viewing such as in JPEG, PDF formats

Environment: Main Frames, COBOL, DB2, VSAM, ORACLE Exadata, ER Studio 8.5, Windows XP, XML, Excel, Access, Visio

Confidential, Richmond, VA

Data Modeler/Data Analyst

Responsibilities:

  • Designed, Developed and maintained web based platform for teh E-Rebate System. It Includes teh modules such as Rebate Contract Management, Data Management, Rebate Processing, Rebate Post Processing, Rebate Reconciliation, Rebate Reporting and contract Modeling
  • Rebate Contract Managements teh module that manages teh rebate contracts dealing with teh pharmaceutical manufacturer as well as teh client for sharing purposes. This modules is essential to teh identical of how much to bill and when, as well as how much to share with teh client. Teh information housed in this module TEMPhas a direct correlation to teh efficiency of teh other modules
  • Rebate Contract Managements includes teh components such as Client Global, Manufacturer Global, Client Contract and manufacturer Contract
  • Global level module list all teh clients and manufacturer details
  • Client Contract is a legal arrangement between PBM and teh client for processing teh claims, pharmacy benefit design an as well as rates
  • Manufacturer Contract is a legal arrangement between a pharmacy (manufacturer) company and a PBM, health plan, state or other entity where rebate reimbursement arrangements are defined for a drug or multiple drugs
  • Participated in JAD session with business users and sponsors to understand and document teh business requirements in alignment to teh financial goals of teh company
  • Created teh conceptual model for teh data warehouse using Erwin data modeling tool
  • Reviewed teh conceptual EDW (Enterprise Data Warehouse) data model with business users, App Dev and Information architects to make sure all teh requirements are fully covered
  • Analyzed large number of COBOL copybooks from multiple mainframe sources (16) to understand existing constraints, relationships and business rules from teh legacy data
  • Worked on rationalizing teh requirements across multiple product lines
  • Reviewed and implemented teh naming standards for teh entities, attributes, alternate keys, and primary keys for teh logical model
  • Implemented Agile Methodology for building an internal application
  • Reviewed teh logical model with application developers, ETL Team, DBAs and testing team to provide information about teh data model and business requirements
  • Worked with ETL to create source to target mappings (S2T)
  • Worked with DBA to create teh physical model and tables
  • Worked on Mercury Quality Center to track teh defect logged against teh logical and physical model.
  • Had brain storming sessions with application developers and DBAs to discuss about various demoralization, partitioning and indexing schemes for physical model
  • Worked on Requirements Traceability Matrix to trace teh business requirements back to logical model

Environment: Erwin, Quest Central for DB2 v 4.8, COBOL copybooks, Mainframe DB2, SQL Server 2000,Oracle 11g SQL*Loader, Mercury Quality Center 9, Informatica Power Center 8.1

Confidential, West Newyork, NJ

Data Modeler

Responsibilities:

  • Involved in Source code scanning and analysis
  • Derived logical data model from source systems
  • Obtained DDL of Production Data Stores
  • Mapped physical to logical definitions
  • Created logical data model with physical mapping for Financial Instrument subject area
  • Abstract EDM from physical data model
  • Standardize naming conventions to better reflect business needs, e.g. Address, etc.
  • Assign primary keys to all tables; evaluate use of multiple dates in teh primary keys
  • Evaluate use of ‘Blank’ and ‘Null’ as valid attribute values in entity definitions
  • Eliminated repetitive attributes (e.g. numbered codes in tables should go to a separate table), levels and type codes, (e.g. simplify product table to make it more manageable through normalization; eliminate redundancies across databases, price and classification)
  • Reduced total number of tables (e.g. avoid single attribute tables, many Issue tables)
  • Developed logical models for Transaction - Events affecting client holdings or accounts Client Account - Holding vehicle for assets, Products & Services - Firm service or offering, e.g. check writing, debit cards, etc. Party - Individual or organization of interest to Confidential WMA Position - Teh intersection of a client account with a financial instrument Financial Instrument - Reference data & pricing for WMA instruments Corporate Action - Any event that brings material change to a financial instrument Operational Position Keeping - Real-time positions and balances General Ledger - Accounting books of business for Confidential WMA
  • Defined EDM for Subject Areas such as Financial Instrument, Party, Client/Account and Operational Position Keeping
  • Defined mappings from EDM back to physical for teh following subject areas:
  • Financial Instrument to PDB, FPM, KAR
  • Party to CRDB
  • Client/Account to CRDB
  • Operational Position Keeping to RPB
  • Exported EDM to Virtualization-friendly format
  • Provided a consistent, structured view of teh data for front-end applications

Environment: Main Frames, COBOL, DB2, VSAM, ORACLE, Erwin 7.5.3, Windows XP, XML, Excel, Access, Visio.

Confidential, St. Louis, MO

Relational Data modeler

Responsibilities:

  • Involved in gathering business requirements and translated business requirements
  • Actively participated inJAD sessionswith teh subject matter expert, stake holders and other management team in teh finalization of User Requirement Documentation
  • Experience in identifying entities required and teh relation between teh entities to create Conceptual logical model
  • Efficiently developed theData model and ERD diagrams using Power designer
  • Created and maintainedLogical Data Model (LDM)for teh project which includes documentation of allentities, attributes, data relationships, primary and foreign keystructures, allowed values, codes, business rules, glossary terms, etc.
  • Validated and updated teh appropriateLDM'sto process mappings, screen designs,use cases, business object model, and system object model as they evolve and change
  • Creating of theXML data modelfor theExpress PA projectfor teh Rules engine and providing teh model in .XSD formatfor teh services team
  • Creating themapping documentsto teh find out teh gaps between teh mockup screens, services and database
  • Identifying thegaps and fills those gapsin teh database by communicating with DBA
  • Enhancing teh existing data model byreverse engineeringby adding new tables based on teh business requirements which will enhance in web services
  • Identifying teh required fields for teh Drug and Coverage check web services in teh database and understanding initial data loading Process
  • Creatinglogical and physical model databaseandschema in oracle
  • Reverse engineeringexistingdatabase to conductsourcedata analysistoidentify teh relationshipbetween data sources
  • Schema Replication for development purpose using Power designer
  • Normalizing theData and Developing teh Relational databasefor teh differentweb services and database
  • Creating of teh database Confidential using Power designer and submitting to teh DBA

Environment: Oracle 10g, Power designer, Oracle SQL developer, SQL plus, Visio, MS office, CVS, Putty, Soap UI.

Confidential, Richmond, VA

Data Modeler

Responsibilities:

  • Interacted with business users to analyze teh business process and requirements and transforming requirements into Conceptual, logical and Physical Data Models, designing database, documenting and rolling out teh deliverables
  • Conducted analysis and profiling of potential data sources, upon high level determination of sources during initial scoping by teh project team
  • Coordinated data profiling/data mapping with business subject matter experts, data stewards, data architects, ETL developers, and data modelers
  • Worked on Bank Data ware house and Mortgage Data ware house
  • Developed logical/ physical data models using Erwin tool across teh subject areas based on teh specifications and established referential integrity of teh system
  • Normalized teh database to put them into teh 3NF of teh data warehouse
  • Involved in dimensional modeling, identifying teh Facts and Dimensions
  • Maintain and enhance data model with changes and furnish with definitions, notes, reference values and check lists
  • Worked very close with Data Architectures and DBA team to implement data model changes in database in all environments. Generated DDL Confidential for database modification, Teradata Macros, Views and set tables
  • An enthusiastic and project-oriented team player with solid communication and leadership skills and teh ability to develop different solutions for challenging client needs

Environment: Teradata, SQL Server 2000/ 2005, Erwin 7.5.2, Windows XP, XML, Excel, Access, Visio.

Confidential, Charlotte, NC

Data Modeler/Data Analyst

Responsibilities:

  • Building Data Mart (Conceptual, Logical and Physical) for reporting environment
  • Creating Data Dictionary for user defined databases (Collateral, Securities and Reporting) in Oracle, SQL Server
  • Worked on Data Conversion for ACH Transactions
  • In teh role of Data Analyst performed analysis and design of extensions to an existing data warehouse/mart business intelligence platform
  • Define enterprise data architecture vision, strategy, principles and standards; get buy-in from stake-holders, management, business partners, and propagate throughout teh company
  • Segregated data and organized teh data for common subjects using ODS
  • Generated operational reports from ODS as opposed to teh transactional/ legacy system
  • Performed Data Architecture in Designing and implementing a Metadata Repository providing a centralized information source for teh data models, data maps, processes, documents, contact lists, project calendars and issues affecting teh merger with Wachovia
  • Implemented Agile Methodology for building an internal application
  • Worked on Data Aggregation
  • Generating Discrepancy reports using Ascential Data Stage
  • Preparing Functional Specifications Document for teh project
  • Technical hands-on expertise using OLAP tool Business Objects 4/5.x/6.0 /XIR2(Reports, Designer, Web Intelligence, Info view, and Supervisor)
  • Universe designing, developing and generating complex, Adhoc, dashboard Reports
  • Analyzing data in both application and reporting databases and solving teh discrepancies
  • Tracking Data Model Change Requests to closure
  • Reverse engineering old database and creating subject areas for each schema
  • Preparing High Level Data Flow for all teh major Applications
  • Well experienced in writing Complex queries, stored procedures, functions, cursors and packages using PL/SQL Programming
  • Developed robust and efficient oracle PL/SQL procedures, packages and functions that were useful for day to day data analysis
  • Fine tuned existing PL/SQL code and worked on upgrade from 9i to 10g
  • Fine tuned Oracle SQL to be more efficient

Environment: Oracle 9i/10g, SQL Server 2000/ 2005, Erwin 7.5.2, Power Designer 12.1, BO 6.5/ XIR2,Qlikview 8.5, Ascential Data Stage 7.5, Clear Quest, Windows XP, XML, Excel, Access.

Confidential

Systems Analyst

Responsibilities:

  • Responsible for accuracy of teh data collected and stored in teh corporate support system
  • Worked on analyzing source systems and their connectivity
  • Performed data review, evaluate, design, implement and maintain company database
  • Involved in construction of data flow diagrams and documentation of teh processes
  • Interacted with end users for requirements study and analysis by JAD (Joint Application Development)
  • Performed gap analysis between teh present data warehouse to teh future data warehouse being developed and identified data gaps and data quality issues and suggested potential solutions
  • Participated in system and use case modeling like activity and use case diagrams
  • Analyzed user requirements and worked with teh data modelers to identify entities and relationship for data modeling
  • Actively participated in teh design of data model like conceptual, logical models using Erwin

Environment: Erwin 4.x, Oracle 9.x, Toad, and MS Excel and Access

We'd love your feedback!