Knowledge (XXG)

Data architecture

Source đź“ť

33: 424:
Properly executed, the data architecture phase of information system planning forces an organization to specify and describe both internal and external information flows. These are patterns that the organization may not have previously taken the time to conceptualize. It is therefore possible at this
416:
Without the guidance of a properly implemented data architecture design, common data operations might be implemented in different ways, rendering it difficult to understand and control the flow of data within such systems. This sort of fragmentation is undesirable due to the potential increased cost
392:
Certain elements must be defined during the design phase of the data architecture schema. For example, an administrative structure that is to be established in order to manage the data resources must be described. Also, the methodologies that are to be employed to store the data must be defined. In
355:
Data architecture should be defined in the planning phase of the design of a new data processing and storage system. The major types and sources of data necessary to support an enterprise should be identified in a manner that is complete, consistent, and understandable. The primary requirement at
492:
These are usually suggested by the completed data architecture and database architecture designs. In addition, some technology drivers will derive from existing organizational integration frameworks and standards, organizational economics, and existing site resources (e.g. previously purchased
197:
During the definition of the target state, the data architecture breaks a subject down to the atomic level and then builds it back up to the desired form. The data architect breaks the subject down by going through three traditional architectural stages:
509:
These are also important factors that must be considered during the data architecture phase. It is possible that some solutions, while optimal in principle, may not be potential candidates due to their cost. External factors such as the
433:
Various constraints and influences will have an effect on data architecture design. These include enterprise requirements, technology drivers, economics, business policies and data processing needs.
425:
stage to identify costly information shortfalls, disconnects between departments, and disconnects between organizational systems that may not have been evident before the data architecture analysis.
160:, for example, should be dependent upon data architecture standards since data integration requires data interactions between two or more data systems. A data architecture, in part, describes the 393:
addition, a description of the database technology to be employed must be generated, as well as a description of the processes that are to manipulate the data. It is also important to design
194:
is typically responsible for defining the target state, aligning during development and then following up to ensure enhancements are done in the spirit of the original blueprint.
417:
and the data disconnects involved. These sorts of difficulties may be encountered with rapidly growing enterprises and also enterprises that service different lines of
587: 156:
A data architecture aims to set data standards for all its data systems as a vision or a model of the eventual interactions between those data systems.
752: 481: 472:, since this enables managerial decision making and other organizational processes. One of the architecture techniques is the split between managing 440:
These generally include such elements as economical and effective system expansion, acceptable performance levels (especially system access speed),
879: 625: 344:
In this second, broader sense, data architecture includes a complete analysis of the relationships among an organization's functions, available
593: 679: 168:. Data architectures address data in storage, data in use, and data in motion; descriptions of data stores, data groups, and data items; and 136:
is collected and how it is stored, arranged, integrated, and put to use in data systems and in organizations. Data is usually one of several
790: 50: 644: 656: 116: 514:, interest rates, market conditions, and legal considerations could all have an effect on decisions relevant to data architecture. 1018: 987: 97: 757: 69: 763: 54: 875: 76: 962: 695: 360:
items. A data entity is any real or abstract thing about which an organization or individual wishes to store data.
175:
Essential to realizing the target state, data architecture describes how data is processed, stored, and used in an
83: 43: 957: 936: 453: 931: 1013: 783: 746: 65: 549:
performed in high volumes, data warehousing for the support of management information systems (and potential
557:, ad hoc reporting, and support of various organizational initiatives as required (i.e. annual budgets, new 141: 1008: 870: 369: 571: 441: 394: 373: 277: 165: 145: 522: 622: 546: 967: 633: 895: 776: 498: 314: 137: 537:. These policies and rules describe the manner in which the enterprise wishes to process its data. 890: 844: 689: 558: 494: 296: 176: 740: 90: 921: 916: 900: 839: 675: 534: 526: 357: 273: 217: 977: 885: 598: 582: 525:
that also drive data architecture design include internal organizational policies, rules of
473: 381: 157: 380:. Physical data architecture encompasses database architecture. Database architecture is a 952: 849: 629: 449: 445: 203: 180: 972: 865: 823: 554: 511: 477: 465: 398: 212:
Physical - the realization of the data mechanisms for a specific type of functionality.
191: 161: 1002: 818: 410: 384:
of the actual database technology that would support the designed data architecture.
926: 345: 169: 719:
Lewis, G.; Comella-Dorda, S.; Place, P.; Plakosh, D.; & Seacord, R., (2001).
669: 497:). In many cases, the integration of multiple legacy systems requires the use of 17: 550: 469: 461: 406: 402: 32: 982: 799: 457: 576: 349: 184: 634:
TOGAF 9.1 - Phase C: Information Systems Architectures - Data Architecture
356:
this stage is to define all of the relevant data entities, not to specify
590:- (EISA) positions data security in the enterprise information framework. 418: 333: 172:
of those data artifacts to data qualities, applications, locations, etc.
401:
that is to support common data operations (i.e. emergency procedures,
377: 256:
List of things and architectural standards important to the business
132:
consist of models, policies, rules, and standards that govern which
603: 368:
Physical data architecture of an information system is part of a
530: 133: 772: 26: 768: 209:
Logical - represents the logic of how entities are related.
484:
from data retrieval systems (as done in a data warehouse).
397:
to the data by other systems, as well as a design for the
376:
to be used in the implementation of the data architecture
372:. The technology plan is focused on the actual tangible 529:, professional standards, and applicable governmental 721:
Enterprise Information System Data Architecture Guide
758:
The “Right to Repair” Data Architecture with DataOps
945: 909: 858: 832: 806: 57:. Unsourced material may be challenged and removed. 674:. pg 256: Global India Publications. p. 314. 753:Building a modern data and analytics architecture 741:Achieving Usability Through Software Architecture 714:Achieving Usability Through Software Architecture 187:and also control the flow of data in the system. 647:GeekInterview, 2008-01-28, accessed 2011-04-28 784: 8: 712:Bass, L.; John, B.; & Kates, J. (2001). 588:Enterprise Information Security Architecture 791: 777: 769: 183:operations to make it possible to design 117:Learn how and when to remove this message 726:Adleman, S.; Moss, L.; Abai, M. (2005). 545:These include accurate and reproducible 623:Business Dictionary - Data Architecture 615: 687: 594:FDIC Enterprise Architecture Framework 579:, a domain-oriented data architecture 7: 220:for enterprise architecture – 164:used by a business and its computer 55:adding citations to reliable sources 25: 988:Data Format Description Language 468:is also a common organizational 452:of raw data such as transaction 31: 464:forms through such features as 42:needs additional citations for 1: 747:The Logical Data Architecture 716:, Carnegie Mellon University. 444:reliability, and transparent 388:Elements of data architecture 963:Core architecture data model 764:TOGAF 9: Preparation Process 730:Addison-Wesley Professional. 533:that can vary by applicable 202:Conceptual - represents all 140:that form the pillars of an 723:Carnegie Mellon University. 657:Data Architecture Standards 222: 179:. It provides criteria for 1035: 429:Constraints and influences 364:Physical data architecture 958:Business process modeling 937:Unified Modeling Language 876:Entity–relationship model 668:Mittal, Prashant (2009). 645:What is data architecture 310:Technology Model/Physical 268:Business Model/Conceptual 216:The "data" column of the 694:: CS1 maint: location ( 328:Detailed Representations 1019:Enterprise architecture 553:), repetitive periodic 480:. Another is splitting 437:Enterprise requirements 142:enterprise architecture 871:Data structure diagram 572:Controlled vocabulary 542:Data processing needs 278:Enterprise data model 166:applications software 146:solution architecture 968:Enterprise modelling 932:Object–role modeling 482:data capture systems 291:System Model/Logical 138:architecture domains 51:improve this article 499:data virtualization 448:. In addition, the 315:Physical data model 66:"Data architecture" 760:, the DataOps Blog 743:, sei.cmu.edu 2001 628:2013-03-30 at the 495:software licensing 489:Technology drivers 297:Logical data model 272:Semantic model or 177:information system 996: 995: 922:Information model 917:Data-flow diagram 681:978-93-8022-820-4 527:regulatory bodies 523:Business policies 519:Business policies 460:into more useful 411:transfers of data 358:computer hardware 342: 341: 218:Zachman Framework 204:business entities 130:Data architecture 127: 126: 119: 101: 18:Data Architecture 16:(Redirected from 1026: 978:Process modeling 793: 786: 779: 770: 749:, by Nirmal Baid 700: 699: 693: 685: 665: 659: 654: 648: 642: 636: 620: 599:Information silo 583:Disparate system 474:transaction data 252:Scope/Contextual 223: 158:Data integration 122: 115: 111: 108: 102: 100: 59: 35: 27: 21: 1034: 1033: 1029: 1028: 1027: 1025: 1024: 1023: 1014:Data management 999: 998: 997: 992: 953:Database design 941: 905: 854: 828: 802: 797: 737: 709: 707:Further reading 704: 703: 686: 682: 667: 666: 662: 655: 651: 643: 639: 630:Wayback Machine 621: 617: 612: 568: 466:data warehouses 446:data management 431: 390: 370:technology plan 366: 181:data processing 162:data structures 154: 123: 112: 106: 103: 60: 58: 48: 36: 23: 22: 15: 12: 11: 5: 1032: 1030: 1022: 1021: 1016: 1011: 1001: 1000: 994: 993: 991: 990: 985: 980: 975: 973:Function model 970: 965: 960: 955: 949: 947: 943: 942: 940: 939: 934: 929: 924: 919: 913: 911: 910:Related models 907: 906: 904: 903: 898: 893: 888: 883: 873: 868: 862: 860: 856: 855: 853: 852: 847: 842: 836: 834: 830: 829: 827: 826: 821: 816: 810: 808: 804: 803: 798: 796: 795: 788: 781: 773: 767: 766: 761: 755: 750: 744: 736: 735:External links 733: 732: 731: 724: 717: 708: 705: 702: 701: 680: 660: 649: 637: 614: 613: 611: 608: 607: 606: 601: 596: 591: 585: 580: 574: 567: 564: 563: 562: 543: 539: 538: 520: 516: 515: 512:business cycle 507: 503: 502: 490: 486: 485: 478:reference data 438: 430: 427: 399:infrastructure 389: 386: 365: 362: 340: 339: 336: 330: 325: 321: 320: 317: 312: 307: 303: 302: 299: 293: 288: 284: 283: 280: 270: 265: 261: 260: 257: 254: 249: 245: 244: 239: 234: 229: 214: 213: 210: 207: 192:data architect 153: 150: 125: 124: 39: 37: 30: 24: 14: 13: 10: 9: 6: 4: 3: 2: 1031: 1020: 1017: 1015: 1012: 1010: 1009:Computer data 1007: 1006: 1004: 989: 986: 984: 981: 979: 976: 974: 971: 969: 966: 964: 961: 959: 956: 954: 951: 950: 948: 944: 938: 935: 933: 930: 928: 925: 923: 920: 918: 915: 914: 912: 908: 902: 899: 897: 894: 892: 889: 887: 884: 881: 877: 874: 872: 869: 867: 864: 863: 861: 857: 851: 848: 846: 843: 841: 838: 837: 835: 831: 825: 822: 820: 817: 815: 812: 811: 809: 805: 801: 794: 789: 787: 782: 780: 775: 774: 771: 765: 762: 759: 756: 754: 751: 748: 745: 742: 739: 738: 734: 729: 728:Data Strategy 725: 722: 718: 715: 711: 710: 706: 697: 691: 683: 677: 673: 672: 664: 661: 658: 653: 650: 646: 641: 638: 635: 631: 627: 624: 619: 616: 609: 605: 602: 600: 597: 595: 592: 589: 586: 584: 581: 578: 575: 573: 570: 569: 565: 561:development). 560: 556: 552: 548: 544: 541: 540: 536: 532: 528: 524: 521: 518: 517: 513: 508: 505: 504: 501:technologies. 500: 496: 491: 488: 487: 483: 479: 476:and (master) 475: 471: 467: 463: 459: 455: 451: 447: 443: 439: 436: 435: 434: 428: 426: 422: 420: 414: 412: 408: 404: 400: 396: 387: 385: 383: 379: 375: 371: 363: 361: 359: 353: 351: 347: 337: 335: 331: 329: 326: 323: 322: 318: 316: 313: 311: 308: 305: 304: 300: 298: 294: 292: 289: 286: 285: 281: 279: 275: 271: 269: 266: 263: 262: 258: 255: 253: 250: 247: 246: 243: 240: 238: 235: 233: 230: 228: 225: 224: 221: 219: 211: 208: 205: 201: 200: 199: 195: 193: 188: 186: 182: 178: 173: 171: 167: 163: 159: 151: 149: 147: 143: 139: 135: 131: 121: 118: 110: 107:November 2008 99: 96: 92: 89: 85: 82: 78: 75: 71: 68: â€“  67: 63: 62:Find sources: 56: 52: 46: 45: 40:This article 38: 34: 29: 28: 19: 927:Object model 814:Architecture 813: 727: 720: 713: 670: 663: 652: 640: 618: 547:transactions 432: 423: 415: 407:data backups 403:data imports 391: 367: 354: 346:technologies 343: 327: 309: 290: 267: 251: 241: 236: 231: 226: 215: 196: 189: 174: 155: 129: 128: 113: 104: 94: 87: 80: 73: 61: 49:Please help 44:verification 41: 840:Conceptual 551:data mining 470:requirement 462:information 458:image files 442:transaction 409:, external 295:Enterprise/ 242:Stakeholder 237:Data (What) 1003:Categories 983:XML schema 886:Geographic 800:Data model 610:References 450:conversion 395:interfaces 350:data types 338:Developer 274:Conceptual 185:data flows 77:newspapers 824:Structure 690:cite book 577:Data mesh 555:reporting 506:Economics 334:databases 301:Designer 946:See also 896:Semantic 880:enhanced 866:Database 850:Physical 819:Modeling 626:Archived 566:See also 419:business 374:elements 319:Builder 259:Planner 170:mappings 152:Overview 891:Generic 845:Logical 833:Schemas 559:product 454:records 332:Actual 91:scholar 901:Common 678:  671:Author 535:agency 382:schema 378:design 348:, and 282:Owner 93:  86:  79:  72:  64:  859:Types 604:TOGAF 227:Layer 98:JSTOR 84:books 807:Main 696:link 676:ISBN 531:laws 456:and 232:View 190:The 134:data 70:news 413:). 144:or 53:by 1005:: 692:}} 688:{{ 632:; 421:. 405:, 352:. 148:. 882:) 878:( 792:e 785:t 778:v 698:) 684:. 324:5 306:4 287:3 276:/ 264:2 248:1 206:. 120:) 114:( 109:) 105:( 95:· 88:· 81:· 74:· 47:. 20:)

Index

Data Architecture

verification
improve this article
adding citations to reliable sources
"Data architecture"
news
newspapers
books
scholar
JSTOR
Learn how and when to remove this message
data
architecture domains
enterprise architecture
solution architecture
Data integration
data structures
applications software
mappings
information system
data processing
data flows
data architect
business entities
Zachman Framework
Conceptual
Enterprise data model
Logical data model
Physical data model

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

↑