LEADER 05287nam 2200649Ia 450 001 9910827468503321 005 20230120011848.0 010 $a1-283-06975-X 010 $a9786613069757 010 $a0-12-385127-0 035 $a(CKB)2670000000074969 035 $a(EBL)675402 035 $a(OCoLC)714568473 035 $a(SSID)ssj0000468261 035 $a(PQKBManifestationID)12213153 035 $a(PQKBTitleCode)TC0000468261 035 $a(PQKBWorkID)10498143 035 $a(PQKB)10020848 035 $a(Au-PeEL)EBL675402 035 $a(CaPaEBR)ebr10464273 035 $a(CaONFJC)MIL306975 035 $a(CaSebORM)9780123851277 035 $a(MiAaPQ)EBC675402 035 $a(EXLCZ)992670000000074969 100 $a20101227d2011 uy 0 101 0 $aeng 135 $aur|n|---||||| 181 $ctxt 182 $cc 183 $acr 200 10$aData architecture$b[electronic resource] $efrom zen to reality /$fCharles Tupper 205 $a1st edition 210 $aAmsterdam ;$aBoston $cMorgan Kaufmann$d2011 215 $a1 online resource (442 p.) 300 $aDescription based upon print version of record. 311 $a0-12-385126-2 320 $aIncludes bibliographical references and index. 327 $aFront Cover; Data Architecture; Copyright Page; Contents; Preface; SECTION 1 THE PRINCIPLES; Chapter 1 Understanding Architectural Principles; Defining Architecture; Design Problems; Patterns and Pattern Usage; Concepts for Pattern Usage; Information Architecture; Structure Works!; Problems in Architecture; Architectural Solutions; The "Form Follows Function" Concept; Guideline: Composition and Environment; Guideline: Evolution; Guideline: Current and Future; Data Policies (Governance), the Foundation Building Codes; Data Policy Principles 327 $aChapter 2 Enterprise Architecture Frameworks and MethodologiesArchitecture Frameworks; Brief History of Enterprise Architecture; The Zachman Framework for Enterprise Architecture; The Open Group Architecture Framework; The Federal Enterprise Architecture; Conclusions; Enterprise Data Architectures; Enterprise Models; The Enterprise Data Model; The Importance of the Enterprise Data Model; Object Concepts: Types and Structures Within Databases; Inheritance; Object Life Cycles; Relationships and Collections; Object Frameworks; Object Framework Programming; Pattern-Based Frameworks 327 $aArchitecture Patterns in UseU.S. Treasury Architecture Development Guidance; TADG Pattern Content; TADG Architecture Patterns; IBM Patterns for e-Business; Enterprise Data Model Implementation Methods; Chapter 3 Enterprise-Level Data Architecture Practices; Enterprise-Level Architectures; System Architectures; Enterprise Data Architectures; Enterprise Technology Architectures; Enterprise Architecture Terminology-Business Terms; The Enterprise Model; The Enterprise Data Architecture from a Development Perspective; Subject Area Drivers; Naming and Object Standards; Data Sharing 327 $aData Dictionary-Metadata RepositoryDomain Constraints in Corporate and Non-Corporate Data; Organizational Control Components; Data Administration; Database Administration; Setting Up a Database Administration Group; Repository Management Areas and Model Management; Chapter 4 Understanding Development Methodologies; Design Methods; Why Do We Need Development Methodologies?; The Beginnings; Structured Methods; Structured Programming; Structured Design; Structured Analysis; Still Having Problems; Requirements Definitions; Problems with Structured Approaches 327 $aPersonal Computers and the Age of ToolsEngineering Concepts Applied; Other Principles Utilized; The Birth of Information Engineering; Information Engineering as a Design Methodology; The Synergy of Tools and Information Engineering; Problems with Information Engineering; Implementing the Best of IE while Minimizing Expense; SECTION 2 THE PROBLEM; Chapter 5 Business Evolution; The Problem of Business Evolution; Expansion and Function Separation; Separate Function Communication; Manual Data Redundancy; Data Planning and Process Planning; Corporate Architecture; Using Nolan's Stages of Growth 327 $aProblems with Older Organizations 330 $a Data is an expensive and expansive asset. Information capture has forced storage capacity from megabytes to terabytes, exabytes and, pretty soon, zetabytes of data. So the need for accessible storage space for this data is great. To make this huge amount of data usable and relevant, it needs to be organized effectively. Database Base Management Systems, such as Oracle, IBM's DB2, and Microsoft SqlServer are used often, but these are being enhanced continuously and auxiliary tools are being developed every week; there needs to be a fundamental starting point for it all. That stating point is 606 $aData structures (Computer science) 606 $aSoftware architecture 615 0$aData structures (Computer science) 615 0$aSoftware architecture. 676 $a005.1/2 700 $aTupper$b Charles D$01710846 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9910827468503321 996 $aData architecture$94101762 997 $aUNINA