International Journal of Advanced Engineering, Management and Science (IJAEMS)
[Vol-1, Issue-2, May- 2015] ISSN: 2454-1311
Comparative Study of Data Warehouse Design Approaches: A Survey R. Shyam Sundar, S. Sneha , U. Avanthika, M. Saranya Abstract— The action of developing a abstracts barn starts with anecdotic and acquisition requirements, designing the dimensional archetypal followed by testing and maintenance. The architecture appearance is the a lot of important action in the acknowledged architecture of a abstracts warehouse In this paper, we surveyed and evaluated the abstract accompanying to the assorted I. INTRODUCTION A Abstracts Warehouse (DW) is authentic as “a subjectoriented, integrated, time-variant, non-volatile accumulating of abstracts in abutment of management’s controlling process” [1]. Abstracts warehouses abundance huge bulk of advice from assorted abstracts sources which is acclimated for concern and analysis. Therefore, the abstracts is stored in the multidimensional (M D) anatomy [34]. A multidimensional archetypal food advice into facts and dimensions. A actuality contains the absorbing concepts or measures (fact attributes) of a business action (sales, deliveries, etc.), admitting a ambit represents the angle or appearance for allegory a actuality (product, customer, time, etc.) application hierarchically organized ambit attributes. Multidimensional modelling requires specialized architecture techniques that resemble the acceptable database architecture methods [5] as apparent in table 1.The database architecture consists of afterward 5 phases. The aboriginal appearance is Assay of operational systems
abstracts barn architecture approaches on the base of architecture belief and adduce a ambiguous article aggressive conceptual architecture framework based on UML that meets all types of user needs. Keywords— Data barn design, Multidimensional modeling, Unified Modeling Language. whose aim is to aggregate the advice apropos the pre absolute operational system. It involves the designer, forth with the humans complex in managing the advice arrangement and produces in achievement the (conceptual or logical) schemes of either the accomplished or allotment of the advice system. The next appearance consists in acquisition and clarification the user requirements. It involves the artist and users of the DW, and produces in achievement the specifications apropos the best of facts and ambit etc.Next is the Conceptual architecture [36] which aims at bearing an implementation-independent and alive conceptual action for the DW, according to the called conceptual model. Analytic architecture takes as ascribe the conceptual action and creates a agnate analytic action (which is added detailed) on the called belvedere by because some set of constraints. And finally, a appearance of concrete design, that takes into annual issues accurately accompanying to the accoutrement called for accomplishing such as indexing and allocation.
Table 1. Database Architecture Methods Step Analysis of Operational System Requirements Elicitation
Input Information regarding the operational systems Database scheme
Conceptual design Logical design
Database scheme and Specifications Conceptual schema
Physical design
Logical schema
Output Database schemes Specifications for data warehouse Conceptual schema Logical schema Physical schema Page | 54
International Journal of Advanced Engineering, Management and Science (IJAEMS)
Conceptual modelling is the all-important foundation for architecture a database that is well-documented and absolutely satisfies the user requirements. In this phase, the multidimensional action of the abstracts barn is defined. It is the alpha of the architecture action on which the success of absolute abstracts barn depends. Though several conceptual models accept been proposed, none of them has been accustomed as a accepted so far, and all vendors adduce their own proprietary architecture methodsObviously, there is a charge of actuality of a accepted conceptual model. In this paper, we accomplish a allusive abstraction of assorted approaches and techniques for abstracts barn architecture and adduce an Article Oriented framework for the conceptual architecture of a abstracts warehouse. We accept acclimated UML ( [2], [3], [4]) in the architecture action as it has become a accepted for article modelling during assay and architecture accomplish of software arrangement development. So, it reduces the accomplishment of acquirements new notations or methodologies for every subsystem to be modeled. II.
BACKGROUND WORK OF DW DESIGN APPROACHES In the literature, altered abstracts models [24, 25,26] both conceptual and analytic accept been proposed for abstracts barn architecture .These approaches are based on their own beheld modelling languages or accomplish use of ablebodied accepted graphical characters like ER archetypal or UML, but to the best of our knowledge, there is no accepted adjustment or archetypal that allows us to archetypal all aspects of a DW. Moreover, during our analysis we noticed that a lot of the analysis efforts in designing and modelling DWs accept been focused on the development of MD abstracts models and conceptual design, the absorption on the concrete architecture of DWs has been actual poor. The avant-garde columnist in the acreage of abstracts barn architecture is Juan Trujilio.He has fabricated a above contribution. He proposed the use of UML for the architecture of abstracts warehouse. He authentic four UML
[Vol-1, Issue-2, May- 2015] ISSN: 2454-1311
profiles for modelling altered aspects of abstracts warehouse: the UML contour for Multidimensional Modelling, the Abstracts Mapping profile, the ETL contour and Database Deployment profile. In [ 25 ],authors adduce an access that provides a abstract foundation for the use of OO databases and Article relational databases in DW.This access introduces a set of basal constraints and extensions to UML for apery multidimensional modelling backdrop for DW.In [ 10,27 ], authors accept proposed a multidimensional contour for the Abstracts barn conceptual action and Client conceptual schema. The columnist has aswell apparent plan in the acreage of concrete schema. He has presented the database deployment contour in [13 ]. Another columnist who aswell has a cogent role in the architecture of abstracts barn is Stefano Rizzi. The columnist in [ 8] proposed a graphical conceptual archetypal for abstracts warehouses, alleged Dimensional Fact model, and gave a semi-automated alignment to body it from the above-mentioned (conceptual or logical)schemes. Then in [11] based on the Dimensional Fact Archetypal (DFM), he gave a accepted abstruse framework for abstracts barn design. Then he discussed some issues in Multidimensional modelling for the architecture of abstracts ceramics abode in [16].After that altered authors gave altered techniques and models for the architecture of abstracts barn which we accept discussed and compared in the next section. III.
COMPARITIVE ANALYSIS OF DW DESIGN TECHNIQUES We accept analyzed analysis plan done in abstracts barn architecture and its accompanying issues. A abrupt collapsed allegory has been provided beneath in table 1 on the base of afterward criteria: Proposal, Framework/Architecture, Approach or address proposed, action used, whether the architecture can be continued to analytic and concrete architecture also, case abstraction and apparatus used.
Page | 55
International Journal of Advanced Engineering, Management and Science (IJAEMS)
[Vol-1, Issue-2, May- 2015] ISSN: 2454-1311
Table 2. Comparison of Work done by different Author
Page | 56
International Journal of Advanced Engineering, Management and Science (IJAEMS)
[Vol-1, Issue-2, May- 2015] ISSN: 2454-1311
Page | 57
International Journal of Advanced Engineering, Management and Science (IJAEMS)
[Vol-1, Issue-2, May- 2015] ISSN: 2454-1311
Page | 58
International Journal of Advanced Engineering, Management and Science (IJAEMS)
[Vol-1, Issue-2, May- 2015] ISSN: 2454-1311
Page | 59
International Journal of Advanced Engineering, Management and Science (IJAEMS)
[Vol-1, Issue-2, May- 2015] ISSN: 2454-1311
Page | 60
International Journal of Advanced Engineering, Management and Science (IJAEMS)
IV.
PROPOSED OBJECT ORIENTED FRAMEWORK FOR DATAWAREHOUSE CONCEPTUAL DESIGN 4.1 Apparatus of the Framework: Our framework takes into annual the requirements of the users. The framework is disconnected into two levels namely- Requirements akin and Architecture level. At the Requirement level, the requirements are aggregate from altered users and a absolute assay is made. The Integrator basic integrates the calm requirements. Each akin comprises of a amount of apparatus to ascendancy accurate tasks forth with abundant metadata athenaeum to acceleration up the accomplished process. In the next level, that is the architecture level; UML artist helps in extracting above altar and classes from abstracts aggregate from assorted abstracts sources and constructs UML chic diagrams. The UML chic diagrams are adapted to multi-dimensional archetypal represented in the anatomy of brilliant or snowflake schema. The about-face is done by applying assertive mapping rules that advice in mapping the classes to facts and dimensions.
Fig. 3. Proposed Framework V. CONCLUSION AND FUTURE SCOPE In this paper, we accomplish a allusive abstraction of altered approaches acclimated for abstracts barn design. In the abstract survey, altered authors [4, 5, 6, 7,8, 9,10,11,12,13] accept proposed altered techniques at altered levels i.e. conceptual akin ,logical akin and concrete level. Our allusive abstraction is based on afterward criteria: Proposal, Framework/Architecture, Access or address
[Vol-1, Issue-2, May- 2015] ISSN: 2454-1311
proposed, Schema used, whether the architecture can be continued to analytic and concrete architecture also, Case abstraction and Tool used.We aswell adduce an Article Aggressive framework for abstracts barn conceptual design. Our framework has abounding benefits.Firstly,the article aggressive multidimensional access [29] is the best as it satisfies all the belief appropriate for the abstracts barn architecture and it is added adjustable as the user requirements are consistently changing.Secondly,we accept acclimated UML which is simple to apprentice and can archetypal all absolute apple objects. Thirdly, brilliant and snowflake schemas are added able for abstracts barn architecture as they are simple to apprentice and charge beneath joins [18]. In the future, we are in the action of testing the proposed framework on a case abstraction and implementing the aforementioned application JAVA at the front-end and Oracle 10g at the back-end. VI. ACTION EVOLUTION This access focuses on ambit updates [1, 2], instances updates [4], facts updates and attributes updates [3]. In [1], authors proposed some operators to ascertain ambit updates. Those operators are: • Generalize operator: it allows the conception of new akin (ln) to which a above-mentioned one (l) rolls up. Authors took the archetype of the ambit " abundance " to which they authentic a new akin "type of abundance " again the akin " blazon of abundance " generalize the ambit "store ". • Specialize operator: it allows abacus a new akin (ln) to a dimension. Authors accept to specialize the ambit "day" with the akin "hour ", and again the akin "hour" specializes the ambit "day ". • Relate levels operator: it allows defining a cycle up action amid two absolute levels of the aforementioned dimension. Authors authentic a affiliation amid the akin "category" and the akin "brand". Those two levels were independent. • Unrelated levels operator: it allows deleting a affiliation amid two levels. Authors deleted the affiliation amid the levels "company" "category" and the akin "brand ". • Delete akin operator: it allows to annul a akin again to ascertain new relations amid levels. Authors deleted the akin "branch" again a absolute affiliation amid the levels "category" and "item" was defined. Page | 61
International Journal of Advanced Engineering, Management and Science (IJAEMS) •
•
Add instance operator: it allows abacus an instance to a akin in the dimension. Authors added the instance account 5 to the akin "item ". Delete instance operator: it allows deleting an instance of a level. Authors deleted the instance account 4 of the akin "item ". Alter dimension Y Add level X: type of X Default 'value of X'
After defining operators to handle ambit updates, authors of [1] saw that they accept to handle the app pulse of ambit structural updates on the abstracts cube. In fact, they proposed some abstracts cube adjustment afterwards the Dellevel update, Add level update, DelInstance update, AddInstance amend by accretion for anniversary cube appearance an announcement to advance it. In this paper, no accomplishing was done to abutment those changes impact. In [2] authors proposed an addendum to the plan presented in [1] and authentic the WareHouse Change System (WHES) ancestor to abutment ambit and cubes update. In fact, they continued the SQL accent and gave bearing to the Multidimensional Abstracts analogue Accent (MDL). This closing accustomed defining operators for to abutment change of ambit and cubes. For ambit update, authors authentic the afterward operators: • CreateDimension: this abettor allows the conception of a new ambit (with its name, its backdrop and its levels). • DropDimension: this abettor allows the abatement of an absolute ambit (with its name, its backdrop and its levels). • RenameDimensi Alter cube Y on: this abettor Add axis X allows alteration the name of a Default ' value of X' accustomed dimension. • AddLevel: this abettor allows the add of a new akin to a accustomed dimension. • DeleteLevel: this abettor allows the abatement of a akin from a accustomed dimension.
[Vol-1, Issue-2, May- 2015] ISSN: 2454-1311
•
International Journal of Database Management Systems ( IJDMS ), Vol.2, No.4, November 2010 • RenameLevel: this abettor allows alteration the name of a accustomed level. • AddProperty: this abettor allows the add of a acreage or aspect to a accustomed ambit or a accustomed level. • D Alter dimension Product eletePrope rty: this Add level brand: char (20) abettor Default 'ABC' allows the abatement of a acreage from a ambit or from a level. To add a akin X (brand) to a ambit Y (product) application the MDL, users should account the afterward syntaxes with X= cast and Y= product: Alter ambit Y Alter ambit Product Add akin X: blazon of X Add akin brand: burn (20) Default 'value of X' Default 'ABC' For cube updates, authors authentic the afterward operators: • CreateCube: this abettor allows the conception of a new cube. • DropCube: this abettor allows the abatement of a accustomed cube. • RenameCube: this abettor allows the change of the name of a accustomed cube. • AddMeasure: this abettor allows the add of a admeasurement to a accustomed cube. • DeleteMeasure: this abettor allows the abatement of a admeasurement from a accustomed cube. • RenameMeasure: this abettor allows the change of the name of a accustomed measure. • AddAxis: this abettor allows the add of an arbor of Alter cube sales Add axis city Default ' Grenoble' analyse to a accustomed cube. Let's acknowledgment that a cube is the actuality table and the arbor is the ambit in the relational schema. To add an arbor X (city) to a cube Z (sales) application the MDL, users should account the afterward syntax: Page | 62
International Journal of Advanced Engineering, Management and Science (IJAEMS)
Alter cube Y Alter cube sales Add arbor X Add arbor city Default ' amount of X' Default ' Grenoble' In [3], authors authentic a academic description of multidimensional schemas and instances. This academic description constitutes the abstracts model. This closing was authentic as follows: a MD archetypal is a 6 tuple (F, L, A, gran, class, attr) area F is a bound set of actuality names, L is a bound set of ambit akin names, A is a bound set of attributes names, Gran is a action that assembly a actuality with a set of ambit akin names, Chic : is a affiliation authentic on the akin name, Attr is a action mapping an aspect to a accustomed actuality or to a accustomed ambit level After defining the abstracts model, authors presented a set of academic change operations. Those closing can accept an aftereffect on the archetypal or not. The afterward change operations accept no furnishings on the model: International Journal of Database Management Systems ( IJDMS ), Vol.2, No.4, November 2010 • Insert level: it consists on extending the MD archetypal by a new ambit level. This operation has no furnishings on instances. • Delete level: it consists on deleting a ambit akin from an MD archetypal but the deleted ambit accept to not be affiliated to the fact. This operation has no furnishings on instances. • Insert attribute: it consists on creating new aspect after adhering it to a ambit akin or fact. This operation has no furnishings on instances. • Delete attribute: it consists on deleting an aspect which is a broken aspect (A € F, A € D). This operation has no affects on instances. • Insert allocation relationship: it consists on defining a allocation accord amid two absolute ambit levels. This operation has no aftereffect on instances. • Delete allocation relationship: it consists on deleting a allocation accord after deleting the agnate ambit levels. This operation has no aftereffect on instance. • The afterward change operations accept furnishings on the model: • Connect aspect to ambit level: it consists on abutting an absolute aspect to a ambit level. This operation has an aftereffect on the instance. In fact, it should ascertain a new action for anniversary new aspect to accredit an aspect amount to anniversary affiliate of the agnate level.
[Vol-1, Issue-2, May- 2015] ISSN: 2454-1311
•
Disconnect aspect from ambit level: it consists on disconnecting an aspect from a ambit level. This operation has an aftereffect on the instance back it should annihilate the deleted aspect functions. • Connect aspect to fact: it consists on abutting an absolute aspect to a fact. This operation has an aftereffect on the instance. In fact, it should ascertain a action that maps coordinates of the cube to measures. • Disconnect aspect from fact: it consists on disconnecting an absolute aspect from a fact. This operation has an aftereffect on instance. In fact, it should annul the action that maps coordinates to measures. • Insert fact: it consists on extending the MD archetypal by a new actuality and after adhering ambit levels to this fact. It should ascertain ambit for this actuality separately. This operation has no aftereffect on the instance but has an aftereffect on the MD archetypal back it should ascertain a new action that assembly a actuality with a set of ambit akin names. • Annul fact: it consists on removing an absolute actuality from the MD archetypal but this actuality accept to not be affiliated to any ambit and don’t accommodate any attributes. This operation has no aftereffect on the instance but has an aftereffect on the MD archetypal back the name of the deleted actuality will be removed from the bound set of actuality names. • Insert ambit into fact: it consists on inserting a ambit at a accustomed ambit akin into an absolute fact. This operation has as an aftereffect the accretion of the new fact. • Delete dimension: it consists on deleting a ambit which is affiliated to a actuality from it. This operation has as an aftereffect the deleting of the action that maps coordinates of the cube to measures. In [3], authors authentic a action change algebra based on academic description but no accomplishing was done. VII. ACTION VERSIONING This access focuses on befitting trace of changes by befitting altered versions of a accustomed DW [5, 6]. In [5] authors accomplish the aberration amid action change and action versioning. In fact, for them action change consists in appointment old abstracts from old action and afterlight it in a new schema. However, action versioning consists in befitting the history of all versions by banausic addendum or by concrete autumn of altered versions. For the action Page | 63
International Journal of Advanced Engineering, Management and Science (IJAEMS)
versioning, authors of [5] analyze two types of versions. In fact, they presented absolute versions and another versions. The absolute versions abutment changes accompanying to alien abstracts sources (changes in the absolute world) but the another versions abutment changes occurred by the " what if analysis". That happens if accommodation makers try to adumbrate or to simulate altered basal accessible business scenarios. Let’s acknowledgment that an another adaptation is or will be created from a absolute adaptation and several another versions can be created from several absolute versions or from the aforementioned absolute version. As absolute version, authors of [5] presented the archetype of alteration the borders of regions (city Konin confused from the arena A to the arena B) in the case of badge DW and its impacts on after-effects of the admeasurement “total-fine” of the actuality table “inspected violation”. In this case, authors proposed to accumulate the old adaptation with abstracts afore changes and to actualize a new adaptation with abstracts afterwards changes. As another version, authors presented basal scenarios. They apish the book of affective the abuse 2 from the accumulation A to the accumulation B, again the accommodation maker can analyze the absolute bearings with the basal one. In [5], every adaptation absolute or another has a accurate time [begin accurate time, end accurate time] in which the adaptation is alleged valid. It is the time constraints on versions. At the accomplishing level, authors acclimated the abstracts administration address to abstain the concrete archetype of abstracts in every DW version. In fact, they stored in a accustomed DW adaptation alone abstracts that are new or afflicted in a accustomed adaptation and added abstracts accompanying to a ancestor adaptation and again aggregate by its adolescent versions. To archetypal this, a ancestor multiversion DW was implemented in beheld C++. In [6], authors handled evolutions in multidimensional structures and provided a new conceptual model. In fact, they proposed a case abstraction in which the actuality table is accompanying to birds and ambit tables are Date, Gender, City-limits and country. Authors authentic for anniversary city-limits the districts acceptance to it in the year 2001 (the districts D1 and D2 accord to the city-limits C1 and D3 belongs to C2). In 2002, some changes happened. In fact, D2 was not any added belongs to C1 but to C2. Due to this change the concern about the amount of birds per year and per commune will change. To break this problem, authors of [6] handled ambit action change (creation and abatement of a dimension, conception and abatement of a hierarchy,
[Vol-1, Issue-2, May- 2015] ISSN: 2454-1311
conception and abatement of a level, move of a akin in the hierarchical action structure) and change on associates (creation of a member, abatement of a member, transformation of a member's name or attribute, amalgamation of n associates into one member, agreeable of one affiliate into n associates and reclassification of a affiliate in the ambit structure). In fact, for anniversary change, a new adaptation was authentic in adjustment to accumulate trace and to account the analogue of a DW (time variant). Anniversary adaptation is accurate aural a time accurate interval. This band-aid was developed with the beheld basal interface on the bartering OLAP environment. VIII. APPEARANCE SYNCHRONIZATION AND MAINTENANCE This access focuses on advancement a embodied appearance in acknowledgment to abstracts changes [7, 8, 9, and 10] or to abstracts sources changes [10, 11, 12, 13, and 14] and sometimes to adviser the DW superior beneath action change [15]. Research works abundant in the ambience of appearance aliment can be classified in the afterward categories: International Journal of Database Management Systems ( IJDMS ), Vol.2, No.4, November 2010 • View adjustment [7, 8, 9, and 10]: this access consists in adapting angle to changes by abacus meta abstracts to embodied views. Those meta abstracts accommodate structural updates accompanying to embodied view. • View synchronization (rewriting of views) [10, 11, 12, 13, and 14]: abounding analysis works were absorbed in this access because it is in affiliation with added problems such as abstracts integration, abstracts barn modeling… In [10] Bell presents an access for activating adjustment of angle accompanying to abstracts sources(relations sources) changes. The capital abstraction of this plan is to abstain the recomputation of angle which are authentic from several sources. In fact, the key abstraction is to compute the new appearance from the old one. Bell presents the appearance adjustment botheration from two altered credibility of views.The aboriginal point of appearance is from the user or from the DW artist or ambassador and the additional point of appearance is from abstracts sources. For the aboriginal point of view, the user or the DW artist can accompany into play action changes on angle (e.g. abacus an attribute, annul an attribute, modifying an aspect area in a appearance schema) apart of the abstracts sources. Again the changes of Page | 64
International Journal of Advanced Engineering, Management and Science (IJAEMS)
the appearance analogue advance to recompute the embodied view. This is the so alleged "view adaptation". For the additional point of view, the abstracts sources (relation sources) can change their schema. This blazon of changes can blow the DW structural bendability back it may invalidate the embodied views. In this case the band-aid is to bottle the structural bendability of the DW. This affectionate of appearance adjustment is so alleged "the structural appearance maintenance". Bell advised the appearance adjustment botheration from both point of angle citation above. Let's alpha with the appearance adjustment from point of appearance abstracts sources or affiliation sources: the columnist of [10] presents the app pulse of action changes of abstracts sources on the SELECT, WHERE and FROM clauses of the appearance query.For the SELECT clause, authors took the case of deleting an aspect A from a abstracts antecedent and its app pulse on the embodied appearance V. This closing should be rewritten (V’) in adjustment to be adapted by deleting the aspect A, again the old appearance V is deleted and the new appearance V’ is renamed as V. this abstraction was translated into the afterward query. IX. COMPARATIVE STUDIES In this area we adduce to analyze researches works accompanying to the aforementioned access of DW evolution. For the action change approach, our allusive abstraction is based on the afterward criteria: akin evolution, instance evolution, ambit change and actuality evolution.Works in [1], [2] and [3] accurate the akin change but if we detail this blazon of change we will acquisition that anniversary columnist accurate a set of akin change but not the total. In fact, authors in [1], [2] and [3] tacked into annual the Add and the Delete of akin but alone authors in [1] advised the Relate and Unrelate of akin and alone [2] advised the Rename of level.Hurtado in [1] was absorbed in Instance change by introducing the Add and Delete of instance.Benitez [2] and Blashka [3] were absorbed in Ambit evolution. In fact, both of them presented the Add, the Delete of ambit and the Add, the Delete of aspect but alone [2] presented the rename of dimension.Benitez [2] and Blashka [3] were absorbed in Actuality change but anniversary columnist was absorbed in some operators which accurate such evolution. In fact, Benitez [2] presented the Add, the Delete and the Rename of admeasurement while Blashka presented the Add and the Delete of fact.
[Vol-1, Issue-2, May- 2015] ISSN: 2454-1311
Table 3. Schema Evolution Dimensi Criteria Level Instance on Fact evolutio evolutio evolutio evolutio Author n n n n Hurtado [1]
x
Benitez [2]
x
x
x
Blaschka [3]
x
x
x
x
REFERENCES [1] Inmon, W.H., Hackathorn, and R.D (1994) Using the data warehouse. Wiley-QED Publishing, Somerset, NJ, USA. [2] June 1999,UML Modelling Language Specification. Version 1.3, Available at http://www.rational.com/uml/resources/documention / (March 2009). [3] Booch G., Rumbaugh J., and Jacobson I.(1999 ) The Unified Modelling Language User Guide, AddisonWesley Longman, p.482. [4] Vassiliadis P. and Sellis, T.,(1999) “A Survey of Logical Models for OLAP Databases”. SIGMOD Record 28(4),pp 64–69. [5] S. Rizzi, A. Abelló, J. Lechtenbörger, J. Trujillo(2006) “Research in data warehouse modelling and design: dead or alive?” DOLAP, ACM, , pp. 3–10. [6] A. Abelló, J. Samos, and F. Saltor (2001) “A Framework for the Classification and Description of Multidimensional Data Models” In Proceedings of the 12th International Conference on Database and Expert Systems Applications (DEXA’01). [7] M. Blaschka, C. Sapia, G. Höfling, and B. Dinter,(1998) “ Finding your way through ultidimensional data models” In Proceedings of the 9th International Conference on Database and Expert Systems Applications DEXA’98, volume 1460 of Lecture Notes in Computer science, pp 198–203, Vienna, Austria, August 1998. Springer-Verlag. Page | 65
International Journal of Advanced Engineering, Management and Science (IJAEMS)
[8] Stefano Rizzi, Matteo Golfarelli. (1998) “A Methodological Framework for Data Warehouse Design”. DOLAP 98 Washington DC USA.Copyright ACM 1999 l-581 13-120-8/98/l 1...$5.00. [9] Juan Trujilio,E.Medina and S.Lujan Mora (2002) ,”A Web Oriented Approach to manage Multidimensional Models through XML Schemas and XSLT ‘’ EDBT 2002 Workshops, LNCS 2490, pp. 29–44, 2002. Springer-Verlag Berlin Heidelberg. [10] S.Lujan Mora and I.Song (2002),“Multidimensional Modeling with UML Package Diagrams “ In Proc. of the 21st Int. Conf. on Conceptual Modeling.Lecture Notes in Computer Science pp 199213,Finland,October 7-11,2002, . Springer-Verlag International Journal of Database Management Systems ( IJDMS ) Vol.4, No.1, February 2012 [11] Stefano Rizzi, Matteo Golfarelli,D.Maio (1998) ”The Dimensional Fact Model:A Conceptual Model for Data Warehouses.” International Journal of Cooperative Information Systems(IJC IS),7(2-3):215247. [12] Lujan Mora and Juan Trujilio (2003) “A Comprehensive Method for Data Warehouse Design.”in Proceedings of 5th International Workshop on Design and Management of Data Warehose(DMDW’03), pp 1.1-1.14. [13] Juan Trujillo and Sergio LujánMora (2004) ” Physical Modeling of Data Warehouses using UML” DOLAP’04, Washington, DC, USA.Copyright 2004 ACM 1581139772/04/0011 ...$5.00. [14] Sergio Luján-Mora1, Panos Vassiliadis and Juan Trujillo. (2004) ” Data Mapping Diagrams for Data Warehouse Design with UML”in Proceedings of 23 rd International Conference on Conceptual Modeling (ER 04),volume 3288 of LNCS,China,Springer [15] Lujan Mora and Juan Trujilio (2006) .”Physical Modeling of Data warehouses by using UML Component and Deployment Diagrams:Design and implementation issues.” Journal of Database Management 17(1) [16] Rizzi,Trujilio,Abello. (2006) ” Research in Data Warehouse Modeling and Design:Dead or Alive?”. DOLAP’06, Arlington, Virginia, USA.Copyright 2006 ACM 1-59593-530-4/06/0011 ...$5.00. [17] Deepti Mishra, Ali Yazici, Beri, Pinar Baẟaran. (2008) ” A Casestudy of Data Models in Data Warehousing.” 978-1-4244-2624-9/08/$25.00 ©2008 IEEE. [18] Kamal Alaskar1 and Akhtar Shaikh. (2009)” Object
[Vol-1, Issue-2, May- 2015] ISSN: 2454-1311
Oriented Data Modeling for Data Warehousing(An Extension of UML approach to study Hajj pilgrim’s private tour as a Case Study). International Arab Journal of e-Technology, Vol. 1, No. 2. [19] Hui Ma,Yiping Yang and Fan Zhang (2009) ”The Anti-standardized Design Research of Data Warehouse”. IEEE. [20] Fernandez Medina et al. (2010)” Model Driven Development of Secure XML Data Warehouses: A Case Study” EDBT 2010, Lausanne, Switzerland. Copyright 2010 ACM 978-1-60558-945-9/10/0003 $10.00. [21] Francois Pinet et. al. (2010) ”The use of UML to design agricultural data warehouses.” AgEng 2010,International Conference on Agricultural Engineering.France [22] Jesús Pardillo and Jose-Norberto Mazón. (2011) ” Using Ontologies for the Design of Data Warehouses.” International Journal of Database Management Systems ( IJDMS ), Vol.3, No.2. [23] Payal Pahwa and Shweta Taneja. (2011) ”Design of a Multidimensional model using Object Oriented Features in UML.” IARS International journal. [24] L. Cabibbo and R.Torlone(1998) “A Logical Approach to Multidimensional Databases” in Proceedings of 6th International Conference on Extending Database Technology EDBT 98 ,Volume 1337 of LNCS,pp 183-197, Spain,Springer. [25] J. Trujillo, M. Palomar, J. Gómez, I.-Y. Song(2001),” Designing data warehouses with OO conceptual models”, IEEE Comput. 34 (12) (2001) 66– 75. [26] N.Tryfona,F.Busborg and J.G.Chriastiansen(1998) ,”StarER:A Conceptual Model for Data Warehouse Design”,in Proceedings of the ACM 2 nd International Workshop on Data Warehousing and OLAP , DOLAP 99,pp 3-8 . [27] Luj´n-Mora S., Trujillo J., and Song, I.(2002), “Multidimensional modeling with UML package diagrams warehouses, ” in Proceedings of 21 st International Conference on Conceptual Modeling, ER 02 ,Volume 2503 of LNCS,pp 199-213,Finland ,Springer. International Journal of Database Management Systems ( IJDMS ) Vol.4, No.1, February 2012 [28] Golfarelli, M., & Rizzi, S. (2001).” WanD: A CASE Tool for Data Warehouse Design”. In Demo Proceedings 17th International Conference on Data Engineering (ICDE 2001), Heidelberg, Germany, 7-9. Page | 66
International Journal of Advanced Engineering, Management and Science (IJAEMS)
[Vol-1, Issue-2, May- 2015] ISSN: 2454-1311
[29] Luj´n-Mora S., Trujillo J., and Song, I., “A UML profile for multidimensional modeling in data warehouses,” Data Knowl. Eng. 59(3) 725–769. [30] Anjana Gosain,Suman Mann, (2010)”Object Oriented Multidimensional Model for a Data Warehouse with Operators”, International Journal of Database Theory and Application Vol. 3, No. 4. [31] Rodolfo Villarroel, Emilio Soler, Eduardo FernándezMedina, Juan Trujillo4,and Mario Piattini (2006),” Using UML Packages for Designing Secure Data Warehouses”, ICCSA 2006, LNCS 3982, pp. 1024 – 1034 .© Springer-Verlag Berlin Heidelberg. [32] Payal Pahwa, Shweta Taneja and Garima Thakur(2011)” Uclean: A Requirement based Object Oriented ETL Framework”, International Journal of Computer Science & Engineering Survey (IJCSES) Vol.2, No.4, November 2011. [33] Sarkar, A., Choudhury, S., Chaki, N. & Bhattacharya, S, (2009) “Conceptual Level Design of Object Oriented Data Warehouse: Graph Semantic Based Model”, INFOCOMP Journal of Computer Science, pp. 60-70. [34] Ponniah, P, (2001) Data Warehousing Fundamentals: A Comprehensive Guide for IT Professionals, pp 402. [35] Elmasri, R. & Navathe, S.B, (2000) Fundamentals of Database Systems, Addison Weasely PubCo. ISBN 0201542633. [36] Nazri, Mior Nasir Mior,Noah, Shahrul Azman Mohd,Hamid, Zarinah (2008),” Automatic data warehouse conceptual design “,International Symposium on Information Technology,Malaysia. [37] Karen C. Davis Sandipto Banerjee (2007),” Teaching and Assessing a Data Warehouse Design Course”, 24th British National Conference on Databases (BNCOD'07) 0-7695-2912-7/07 $20.00 © 2007 IEEE. [38] Mayank Sharma, Navin Rajpal and B.V.R.Reddy (2010),” Physical Data Warehouse Design using Neural Network” . International Journal of Computer Applications 1(3):86–94, February 2010. Published By Foundation of Computer Science. [39] Abraham Silberschatz, Henry F. Korth, and Sudarshan (2002). Database System Concepts pp 445-489. 4th Edition, McGraw Hill. [40] Marotta, A., Ruggia, R.(2002),” Data warehouse design: a schema-transformation approach”, Computer Science Society, 2002. SCCC 2002. Proceedings. 22nd International Conference of the Chilean. Page | 67