Applying UML for modeling the physical design of data warehouses
Contemporary Issues in Database Design and Information Systems Development, ISSN: 1935-2662, Page: 55-99
2007
- 7Captures
Metric Options: CountsSelecting the 1-year or 3-year option will change the metrics count to percentiles, illustrating how an article or review compares to other articles or reviews within the selected time period in the same journal. Selecting the 1-year option compares the metrics against other articles/reviews that were also published in the same calendar year. Selecting the 3-year option compares the metrics against other articles/reviews that were also published in the same calendar year plus the two years prior.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Metrics Details
- Captures7
- Readers7
Book Chapter Description
In previous work, we have shown how to use unified modeling language (UML) as the primary representation mechanism to model conceptual design, logical design, modeling of extraction, transformation, loading (ETL) processes, and defining online analytical processing (OLAP) requirements of data warehouses (DW). Continuing our work on using UML throughout the DW development lifecycle, in this chapter, we present our modeling techniques of physical design of DW using component diagrams and deployment diagrams of UML. Our approach allows the DW designer to anticipate important physical design decisions that may reduce the overall development time of a DW such as replicating dimension tables, vertical and horizontal partitioning of a fact table, and the use of particular servers for certain ETL processes. We illustrate our techniques with a case study. © 2007, IGI Global.
Bibliographic Details
http://www.scopus.com/inward/record.url?partnerID=HzOxMe3b&scp=84899379117&origin=inward; http://dx.doi.org/10.4018/978-1-59904-289-3.ch003; http://services.igi-global.com/resolvedoi/resolve.aspx?doi=10.4018/978-1-59904-289-3.ch003; https://www.igi-global.com/viewtitle.aspx?TitleId=7021; https://dx.doi.org/10.4018/978-1-59904-289-3.ch003; https://www.igi-global.com/gateway/chapter/7021
IGI Global
Provide Feedback
Have ideas for a new metric? Would you like to see something else here?Let us know