PROFESSIONAL SUMMARY

• IT Professional with over ten years of Senior Data Modeler expertise in the planning, analysis, design and implementation of computer systems.
• Participated in and managed several full life cycle data design projects using various CASE tools including over ten years of logical/physical data modeling, over five years of data architecture, over ten years of SQL and over four years of TOAD experience.
• Possesses extensive database design expertise including over five years of DB2, over six years of Oracle, over one year of Sybase and over three years of SQL Server.
• Acquired CASE tool experience including over ten years of ERwin/Model Mart, over three years of ER Studio, over three years of Power Designer and over one year of Paradigm Plus experience.
• Possesses over one year of Bachman, System Architect and BPWIN experience.
• Worked with all levels of the development life cycle from project initiation and requirement analysis through implementation, training and support.
• Skilled at interfacing with clients, developers, managers and peers at all levels.
• Excellent requirements facilitation JAD and strong written and verbal presentation skills.
• Worked with and trained offshore developers.
• Gained over twenty years of experience in State government, insurance, banking, brokerage, medical, transportation and telecommunication industries.

TECHNICAL SKILLS

• Hardware: IBM 30xx/43xx, IBM PCs
• Operating Systems: OS/MVS/XA, TSO/ISPF, VSE/ESA, ICCF, DOS/Windows, MS Windows
• Programming Languages: COBOL, CICS, QMF, SQL, PMSS
• Databases: MS SQL Server 2000, DB2/390 8, Sybase 12.5, Oracle 11g, DB2/UDB 8.1, MySQL Amazon Cloud , Database Tools: TOAD, SQLDeveloper
• XML Tools: XMLSPY
• Data Dictionary: IDD, Predict, Data Manager, PacBase
• CASE Tools: IEW, Bachman, ERwin, System Architect, Express G, ER Studio, Power Designer

PROFESSIONAL EXPERIENCE

Confidential

Data Modeler

Working with team of business analyst, business users and data analyst created a business requirement document and functional/non functional requirements document for a major redesign application. Source data sent from external vendor via XML. Using the XSD reversed engineer into Powerdesigner data modeling tool creating a physical data model. The external data along with other internal data is used to add new tables as well as updating existing tables in ODS data model. Also updated the data warehouse from ODS and created data marts as required for this project.

Data Modeler/Architect, Consultant

• Performed maintenance on existing systems and new development.
• Worked with and supported the DA staff that included updating existing data models through service requests IBM Rational ClearQuest Tool submitted by the development staff members.
• The Service requests defined what changes are to be made to the data model and to the DBMS.
• The DA reviews the service request and discussed any data modeling issues with the requestor.
• Review the table/column names to ensure conformity to establish naming conventions.
• Review column/table definitions determining if columns or tables match definitions, if not discuss with the developer.
• Review table structure, PK and indexes and RI and discuss any issues with developer.
• Also looking for missing columns or incorrect table/column names, the need for RI between tables or the need for a look-up domain table of codes and descriptions repeating group .
• Updated both logical and physical data models, using the physical data model generate DDL.
• Test DDL script generated from the physical data model and send working script to DBA for implementation.
• Worked with the ETL team, on many projects including creating ODS DW and creating tables/views on Teradata.
• Also working with developers using MYSQL Amazon Cloud , responsible for reviewing data
• structures and creating tables.
• Also created conversion document from/to MYSQL to/from Oracle.
• Created a Power Designer training document for new data modelers.
• Created a migration plan for converting ERwin data models to Power Designer.

Environment: ERwin, Power Designer, SQL Server, Oracle, MYSQL

Confidential

Data Modeler/Architect Consultant

• Enhanced eModelers ERStudio training materials for the client.
• Taught offshore personnel to use ERStudio and trained them in data modeling technique 1st-3rd normal form dos and don'ts when designing tables and columns for APL.
• Trained a diverse group of individuals in data modeling and reviewed, approved or denied the design.
• Reviewed changes submitted by the development staff for correct naming of objects, used enterprise domains and good business definitions, reused of objects and helped developers using the ER Studio tool and data modeling techniques.

Environment: ER Studio, DB2, SQL Server, Oracle

Confidential

Data Modeler/Architect, Consultant

• Updated existing data models through service requests submitted by development staff. The Service requests defined what changes were to be made to the data model and to the DBMS.
• Reviewed the service requests and discussed any problems with the requestor.
• Assessed table/column names to ensure conformity to establish naming conventions, reviewed definitions, determined if columns or tables matched the definition and discussed with developer, evaluated table structure, PK
• and indexes , RI and discuss any issues with the developer for resolution.
• Performed changes on logical and physical models created DDL and pass to DBA for implementation.
• Worked on the redesign of IVRU Interactive Voice Response Unit and AL3 download.
• New logical data models, facilitated data analysis JAD sessions with business users and developers,
• documented existing/new data elements and performed data normalization or
• denormalization where necessary.
• Developed a physical data model to be submitted to developers for review and if approved, submitted to DBA for implementation.
• Served as Senior DA to mentor new staff.

Environment: ERwin 3.5/4.1/7, DB2/390 8, SQL Server 2000, Oracle 9

Confidential

Data Modeler/Architect, Consultant

• Updated existing data models through service requests submitted by the development staff. The Service request defined what changes were to be made to the data model and to the DBMS.
• Reviewed the service requests and discussed any problems with the requestor.
• Assessed table/column names for conformity to establish naming conventions, reviewed definitions to determine if columns or tables matched definitions and discussed with the developer.
• Reviewed new table structure, PK, indexes, and RI and discuss any issues with the developer for resolution.
• Updated both logical and physical data models, compared the previous data model to the current one to obtain change DDL.
• Worked on the redesign of LTC, CMS and LTCV.
• On new data model projects created conceptual data models and logical data models, facilitated data analysis JAD sessions with business users and developers, documented existing/new data elements and performed data normalization or de-normalization.
• Developed a physical data model and DDL to be submitted to developers for review. If approved, the DDL was submitted to DBA for implementation.

Environment: ERwin 3.5/4.1, DB2/390 8, SQL Server 2000, Oracle 9, DB2/UDB 8.1, Sybase 12

Confidential

Data Modeler, Consultant

Handled data design of new and old applications, facilitated data analyst JAD sessions with business users and developers, documented existing/new data elements, performed data normalization and created subject data models. These data models were at the conceptual level with many super-type/sub-type entities.

Environment: Express G

Confidential

Data Modeler, Consultant

• Performed data design of new and old applications, facilitated data analyst JAD sessions with business users and developers, documented existing/new data elements, performed data normalization and created subject data models.
• Reviewed with the project team all data designs, submitted to DBA for implementation.

Environment: ERwin, DB2, SQL Server 7.0, Oracle 8

Confidential

Data Modeler, Consultant

• Worked in a team environment on the data design of major/minor applications and evaluation of some ETL tools. These applications were both mainframe and client/server-based.
• Met with the business users and/or business analyst to collect data elements with definitions to be used bythe application. If this was a new entity, performed data normalization, reviewed with the team and sent to DBA for implementation. If just adding to exiting database table, sent updates to the DBA for implementation.

Followed Sprint data design standards and system design methodology.

Environment: ERwin, DB2, SQL Server 7.0

Confidential

Data Modeler

• Redesigned the company database, facilitated data analysis JAD sessions with business users, documented existing/new data elements and created a corporate data model.
• Participated in the selection of a policy/claims system. Used corporate data model as guide for selecting the new PC software.
• Performed other data modeling tasks that included updating the existing DB2 model with new data elements and entities and creating new entities and data elements for SQL Server 7.

Environment: ERwin, DB2, SQL Server 7.0

Confidential

Data Modeler, Consultant

defined benefits data model, recommended corrections and developed some small data models.Environment: ERwin, System Architect, Sybase, UNIX

Confidential

Data Modeler, Consultant

• Managed the data design of the KY Technical School system and facilitated data modeling JAD sessions.
• Worked with a team of system analysts to collect information on the current KY Technical School systems some manual and some automated .
• Analyzed information collected and created an initial document with major business processes and data structures.
• Facilitated JAD sessions where forty school administrators plus the commissioner of KY Technical School were in attendance.
• Organized information collected into a system design document with business processes, rules, data attribute and entity definitions, and a data model.

Confidential

Data Modeler, Consultant

• Worked with ten other data modelers on GTE's Process Re-Engineering project.
• Modeled customer and product data from information collected at JAD sessions.

Environment: ERwin, PacBase

Confidential

Data Modeler, Consultant

• Performed data analysis and design of Statewide Reporting Information Management Systems SRIM .
• Working JAD sessions that included programmers, DBA and school administrators. Collected initial data attributes and entities.
• Reviewed information from existing mainframe systems, end-user workstations and manual systems.
• Created logical data model from information above focusing on student attendance and accountability.
• Utilized Bachman CASE tool in designing the data models as well as forward/reverse-engineering the model into a physical design.
• Used the physical model to generate Oracle 7, DDL via Bachman CASE tool. The developers used SQL Windows as a development tool to access the SRIM database in a client/server environment.

Environment: Bachman, Oracle 7

Confidential

Senior Data Analyst, Consultant

• Performed data analysis and design of the BCBST Strategic System Initiative SSI that included twenty new projects.
• Worked with three other data analysts, developing an Enterprise Data Model from which detail project data models were developed.
• Developed project data models as the result of a meeting with the development teams and end-users. Project teams comprised Auther Anderson Consultants and BCBST system staff.
• Collected data requirements and data attribute definitions from the project team to create logical data models using ICASE tool Excelerator II, OS/2 and DB2/2 .
• Shared ICASE data models among other data analysts and system developers.
• Assisted in developing data administration standards and procedures for SSI.

Environment: Excelerator II, OS/2, DB2/2

Confidential

Senior Data Analyst, Consultant

• Performed data analysis and design of the client's DSS Case Management System TWIST Project .
• Worked with two other data analysts an IBM consultant and a KY state employee developing an enterprise data model that included over twenty high-level entities and 300 data attributes.
• Presented the enterprise data model to development staff and end-users for approval.
• Developed a detail logical data model from the Enterprise model that included meeting with the application development staff IBM and state employees and end-users and collecting definitions for all data attributes and entities.
• Entered this information onto Bachman Analyst CASE tool.
• Merged the three detail data models into one logical data model with 200 entities and over 1,500 data attributes.
• Normalized the detail data model and prepared for forward-engineering to create a physical data model.
• Utilized Bachman CASE tool to prepare the physical data model for generating DDL for DB2.
• Kept the merged logical data model in sync change control .

Environment: DSS Case Management System TWIST Project , Bachman CASE, DB2, DDL

Confidential

Senior Data Analyst

• Served as Team Leader for data analysis and design, participated in JAD sessions for several projects that included the New Agent Comp System, Generalized Disbursement System, Medical Fee System, Billing and Client Information System.
• During JAD worked with end users, development staff and DBA collecting information on business functions, data attributes and entity definitions.
• During the design phase of the project a logical data model was created and presented to business users and the development team for review and approval.
• As part of IS documentation a logical data design document was generated which included a statement of purpose, ER data model, relationship rules, validation process and entity and data attribute reports.
• A physical data model was created and passed to DBA for DDL generation.
• Used Bachman to reverse-engineer client, marketer and medical fee systems into a physical model then created a logical model.
• Developed standards for using Bachman CASE tool and data design standards.
• Maintained the corporate Data Dictionary, storing data attribute and entity definitions. This was made available to business users and development staff.

Environment: Data Dictionary, Bachman CASE Tool

Confidential

Senior Data Analyst

Worked with two other data analysts responsible for the data analysis and design of financial projects, Creating metadata repository using QMF with ISPF front end, and participated in developing a Securities Enterprise data model.

Environment: Metadata Repository

Confidential

Data Administrator

• Hired as a Programmer/Analyst and promoted to a Data Administrator position to create and establish the data administration organization.
• Evaluated and selected software to support the DA functions and selected and implemented a corporate-wide Data Dictionary system.
• Created Data Dictionary standards, procedures and naming conventions.
• Hired staff members to maintain Data Dictionary and perform data analysis.
• Promoted the concept of data administration to business users, project managers and development staff members.

Environment: Data Dictionary