1 / 19

Building a Data Layer

Building a Data Layer. Concepts, Approaches, Directions. Bryan Aucoin Alanthus Associates, Inc. 703.307.3191 alanthus@verizon.net. Agenda. Basic Concepts An Information Hierarchy of Needs Architecture Constructs Types of Databases and Repositories (and why they are different)

britanni-stevens
Télécharger la présentation

Building a Data Layer

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Building a Data Layer Concepts, Approaches, Directions Bryan Aucoin Alanthus Associates, Inc. 703.307.3191 alanthus@verizon.net

  2. Agenda • Basic Concepts • An Information Hierarchy of Needs • Architecture Constructs • Types of Databases and Repositories(and why they are different) • How Databases Work Together • Types of Data Exchange Services • Types of Data Access Services • Building a Data Layer

  3. An Hypothesis:Information Architecture as a Hierarchy of Needs The focus of the Mission/Business Applications “Use the Facts” Utilization “Find the Facts” Integrate “Find the Dots” Discover and Access The focus of the Data Layer “Get the Dots” Capture and Store Data Creation

  4. Capturing and Storing Data • The Great Data Divides • Why “One Size Does Not Fit All” in the database world • Common Architectural Constructs for Information Capture and Storage • Transactional Databases • Analytical Databases • Document Authoring • Document Repositories • How the Quadrants work together • Information Exchange Services • The Role of Data Architecture • The Creation and Management of Records

  5. The Great Data Divides The important point is that there is no “one size fits all” approach to information capture and storage.

  6. Architectural Constructs:Capture and Store: • Databases are created for specific purposes: • Forms fit functions – and for good reasons. (More below.) • There will always be needs for exceptions, but these constructs provide a basis for common architectural patterns for database/repository design.

  7. How the QuadrantsWork Together Data Exchange Services

  8. Types of Data Exchange Services • Extract, Transform, Load • Publication • Entity/Relationship Extraction • Translation

  9. Types Discovery and Access Service • Context Awareness • Structural Awareness • Transactional Services • Data Query (Structured) • Content Search and Discovery (Document-oriented) • Retrieval Services • Subscription Services • Notification Services

  10. DRM PrescribedArchitectural Patterns • Transactional Databases (Quadrant I) • Analytic Databases (Quadrant II) • Authoring Repositories (Quadrant III) • Document Repositories (Quadrant IV)

  11. Transactional DatabasesPrescribed Services Context Awareness Structural Awareness Transactional Data Query Notification

  12. Analytic DatabasesPrescribed Services Context Awareness Structural Awareness Data Query

  13. Authoring RepositoriesPrescribed Services Content Search & Discovery Retrieval Context Awareness Structural Awareness Transactional Subscription Notification

  14. Document RepositoriesPrescribed Services Content Search & Discovery Retrieval Context Awareness Structural Awareness Subscription Notification

  15. The Role of Data Architecture Data Architecture revolves around: • Semantics: Standardizing what things mean • Syntax: Standardizing how things are represented Three important components: • Context: • What’s in the database? • Content: • What’s in a database view? • What’s in a document? • Structure: • Answers the syntax questions: • How are the data organized? • How are the data structured?

  16. The Role of Data Architecture • Define the common taxonomies for context • The subject areas that the organization is interested in. • Define common standards(semantic and syntactic): • “Entities of Interest” • People • Places • Events • Materiel

  17. The Key Point… • If the databases/repositories within an organization provide the services delineated above, guided by a effective data architecture for semantic interoperability, then the information within that organization will be accessible and discoverable. • You’ll have to first two layers of the data hierarchy in place.

  18. Putting It All TogetherBuilding a Data LayerFor Each Collection Business Application Business Application Business Application … … Legacy, COTS, or Functionally Unique Application Legacy, COTS, or Functionally Unique Application Data Access and Discovery Services Authoring Repository Enterprise Document Warehouse Transactional Data Store (Structured Data) Enterprise Data Warehouse Authoring Repository Enterprise Document Warehouse Transactional Data Store (Structured e.g. ARES) Enterprise Data Warehouse Data Exchange Services Enterprise Data Layer

  19. Questions?

More Related