Borrador V 0.3

1

Data Warehouse Engineering Process (DWEP) with U.M.L. 2.0 Edwar Javier Herrera Osorio, [email protected] Universidad Nacional de Colombia



II. RELATED WORK

Abstract—Is an update the Data Warehouse Enginieering Process (DWEP) to uml version 2.0, which allows us to extend the diagrams in UML data models: Logical, conceptual and physical. Index Terms— Data warehouse, UML, Unified process, data models

I. INTRODUCTION

dsadadsad III. DATA WAREHOUSE ENGINEERING PROCESS If you are using Word, use either the Microsoft Equation Editor or the MathType add-on (http://www.mathtype.com) for equations in your paper (Insert | Object | Create New | Microsoft Equation or MathType Equation). “Float over text” should not be selected.

T

he data warehouse (DW) is one of the components of the intelligence business, Bill Inmon defines it: “... A data warehouse is a subject-oriented, integrated, timevariant, nonvolatile collection of data in support of management’s decisions...” [1], and Ralph Kimball: “… the Data Warehouse is a collection of data in the form of a database that stores and organizes information that is extracted directly from operational systems (sales, production, finance, marketing, etc..) and external data…”[2]. Building a DW is a challenging and complex task because a DW concerns many organizational units and can often involve many people. Lujan poses at the 2004 [3,4] Data Warehouse Engineering Process (DWEP), a methodology for building the data warehouse based on the Unified Modeling Language (UML) 1.4 [5] and the Unified Process (UP) [6], which allows the user to tackle DW all design stages, from the operational data sources to the final implementation and including the definition of the ETL (Extraction, Transformation, and Loading) processes and the end users' requirements. The rest of the paper is structured as follows. In Section 2, we briefly present some of the most important related work and point out the main shortcomings. In Section 3, we summarize DWEP: first is presented charts proposed by Lugan[3,4], then presented updates to the UML diagrams to version 2.0 (the results achieved so far) and shows the use of these devices in the workflows that make up our process. Finally, we present the main contributions and the future work in Section 4.

IV. CONCLUSION A conclusion section is not required. Although a conclusion may review the main points of the paper, do not replicate the abstract as the conclusion. A conclusion might elaborate on the importance of the work or suggest applications and extensions. APPENDIX Appendixes, if needed, appear before the acknowledgment. ACKNOWLEDGMENT The preferred spelling of the word “acknowledgment” in American English is without an “e” after the “g.” Use the singular heading even if you have many acknowledgments. Avoid expressions such as “One of us (S.B.A.) would like to thank ... .” Instead, write “F. A. Author thanks ... .” Sponsor and financial support acknowledgments are placed in the unnumbered footnote on the first page, not here. REFERENCES [1] [2] [3]

[4] [5]

[6] .

W. Inmon, Building the data warehouse. Wiley, 2002. R. Kimball and M. Ross, The Data Warehouse Toolkit: The Complete Guide to Dimensional Modeling. Wiley, 2002. S Lujan and J Trujillo. A Data Warehouse Engineering Process. Advances in Information Systems, Springer Berlin / Heidelberg, Volume 3261/2005 , pp. 14–23. S Lujan , Data WareHouse Desig with UML, PHD. Thesis, Universidad de Alicante, 2005 Object Management Group (OMG): Unified Modeling Language Specification 2.0, Internet: http://www.omg.org/technology/ documents/ modeling_spec_catalog.htm#UML. 2009 . Jacobson, I., Booch, G., Rumbaugh, J.: The Unified Software Development Process. Object Technology Series. Addison-Wesley . 1999.

Borrador V 0.3

First A. Author Edwar Javier Herrera Osorio (05/10/1977), systems engineer, Distrital university 2004, specialist in database development, foundation university of Bogotá Jorge Tadeo Lozano, 2007, Master candidate in systems engineering and computer science 2008 National University of Colombia The second paragraph uses the pronoun of the person (he or she) and not the author’s last name. It lists military and work experience, including summer and fellowship jobs. Job titles are capitalized. The current job must have a location; previous positions may be listed without one. Information concerning previous publications may be included. Try not to list more than three books or published articles. The format for listing publishers of a book within the biography is: title of book (city, state: publisher name, year) similar to a reference. Current and previous research interests end the paragraph. The third paragraph begins with the author’s title and last name (e.g., Dr. Smith, Prof. Jones, Mr. Kajor, Ms. Hunter). List any memberships in professional societies other than the IEEE. Finally, list any awards and work for IEEE committees and publications. If a photograph is provided, the biography will be indented around it. The photograph is placed at the top left of the biography. Personal hobbies will be deleted from the biography.

2