SDLC Deliverable Templates



Extraction, Transformation, and Load (ETL) SpecificationBureau of Information Systems< KEYWORDS \* MERGEFORMAT Project Name>Table of Contents TOC \o "2-3" \h \z \t "Heading 1,1" Revision History PAGEREF _Toc306868833 \h 31.Introduction PAGEREF _Toc306868834 \h 41.1Summary PAGEREF _Toc306868835 \h 41.2Scope of Initiative PAGEREF _Toc306868836 \h 41.3Resources PAGEREF _Toc306868837 \h 41.4Definitions, Acronyms and Abbreviations PAGEREF _Toc306868838 \h 42.Transformation Component Documentation PAGEREF _Toc306868839 \h 52.1Data Import/Extract PAGEREF _Toc306868840 \h 52.2Data Import Method PAGEREF _Toc306868841 \h 52.3Data Acquisition PAGEREF _Toc306868842 \h 52.4Data Integrity PAGEREF _Toc306868843 \h 62.5Data Refresh Frequency PAGEREF _Toc306868844 \h 62.6Data Security PAGEREF _Toc306868845 \h 73.Data Quality PAGEREF _Toc306868846 \h 83.1Performance Measures and Standards PAGEREF _Toc306868847 \h 83.2Resources PAGEREF _Toc306868848 \h 8Revision HistoryDateVersionDescriptionAuthor<dd/mm/yy><x.x><details><name>2/23/20161.2Reviewed for content; changed DPW to DHS.Don Pidich - EKMSIntroductionThe purpose of the Extraction, Transformation, and Load (ETL) Specification Document is to capture details that pertain specifically to ETL development to be used by the developer as an aid in ETL development. SummaryAddress in the section:Who is the business owner (The Client)?What is the business that the Client does?What business need, problem or objective will be addressed?Where do they want the data?When do they need it by?Were previous attempts made to integrate the data?Scope of InitiativeAddress in this section:The business process statusExpected business objectiveDescribe need for integration with any external systemResourcesAddress in this section:Requesting Business ClientProject Manager or Business AnalystDetailed specification of the operational source systemsDefinitions, Acronyms and AbbreviationsAdd items and terms that need to be defined in this sectionTransformation Component Documentation[This section outlines a more detailed description of the processes that are currently utilized and the proposed processes developed to achieve the objectives of this initiative.]Data Import/ExtractAddress in this section:Database tables namesFile Exports namesTransactions processesSpecial: parameter or control filesData Import MethodAddress in this section:Direct access by table or file on source systemExtract from sourceFile transferredRequired permissionsData AcquisitionAddress in this section:What data is needed?Will technical data specifications be provided?Fixed lengthComma SeparatedHow will the data sets be identified and selected?How often are source systems updated?How much data can be expected?How often will the data be received?What state is the source system?Production?Testing – when will the design be finalized?When can a production extract be ready for use by the developer?Are there any specific bottlenecks to getting the data?Data Transform SpecificationAddress in this section:Has any technical analysis been previously performed?Do design specification or data models exist?What kind of history or trending information is needed?Are there any known fields that require a derived calculation?Data IntegrityAddress in this section:How reliable is the source system data (e.g., empty fields, dates stored as text, invalid code values, text fields with odd or control characters, etc.)?Are the source data sets used by more than one data owner?How often does the source system change?How will changes be communicated to the users and development team?Data Refresh FrequencyAddress in this section:How often should the Data Warehouse process refresh?DailyWeeklyMonthlyQuarterlySemi-AnnuallyOtherData SecurityAddress in this section:Do monitoring requirements need to be satisfied?Are there any federally mandated HIPAA considerations?Is there need to build in additional privacy? Encryption Data maskingAuditingBackupsData Target/ResultAddress in this section:How long will be data retention?How often can the data be purged?What interface will the Client/Users access the data?CognosReportsTrainingAdhoc other…Does the project data have an expiration date?Data QualityPerformance Measures and StandardsAddress in this section:What measure will determine the success of this project?Do specific (Federal or otherwise) compliance measures exist?Do other specific outcomes exist?Expected ReportsTotals and expected countsTechnical comparison (e.g., using SQL, etc.)ResourcesAddress in this section:Who will be performing the user acceptance testing?Do they have a timeline or window for testing?When will they be doing it? ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download