IC Conceptual Data Model (CDM)

Slides:



Advertisements
Similar presentations
DoDAF V2.0 Community Update Overview
Advertisements

OASIS Reference Model for Service Oriented Architecture 1.0
Ken Laskey, co-editor 5th SOA for E-Government Conference 1 May 2008
Reference Architecture for Enterprise Integration CIMOSA GRAI/GIM PERA Dima Nazzal.
Reference Models مدل های مرجع معماری.
Chapter 6 Methodology Conceptual Databases Design Transparencies © Pearson Education Limited 1995, 2005.
Lecture Fourteen Methodology - Conceptual Database Design
Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles,
1 ECCF Training 2.0 Introduction ECCF Training Working Group January 2011.
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
DCMO - CIO Architecture Federation Pilot Larry Singer 5 January, 2012.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
The chapter will address the following questions:
Developing Enterprise Architecture
Proposed EA Assessment Framework 2.0 Chief Architect’s Forum (CAF) Dick Burk Chief Architect and Director of Federal Enterprise Architecture Program, OMB.
Computer System Analysis Chapter 10 Structuring System Requirements: Conceptual Data Modeling Dr. Sana’a Wafa Al-Sayegh 1 st quadmaster University of Palestine.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
PROJECT NAME: DHS Watch List Integration (WLI) Information Sharing Environment (ISE) MANAGER: Michael Borden PHONE: (703) extension 105.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Methodology - Conceptual Database Design Transparencies
Methodology Conceptual Databases Design
1 Chapter 15 Methodology Conceptual Databases Design Transparencies Last Updated: April 2011 By M. Arief
Introduction to MDA (Model Driven Architecture) CYT.
1 Introduction to Software Engineering Lecture 1.
Methodology - Conceptual Database Design
FEA DRM Management Strategy Presented by : Mary McCaffery, US EPA.
Design Concepts By Deepika Chaudhary.
1 ECCF Training 2.0 Introduction ECCF Training Working Group January 2011.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Winter 2007SEG2101 Chapter 31 Chapter 3 Requirements Specifications.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
Software Engineering Lecture 10: System Engineering.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Models of the OASIS SOA Reference Architecture Foundation Ken Laskey Chair, SOA Reference Model Technical Committee 20 March 2013.
Welcome: To the fifth learning sequence “ Data Models “ Recap : In the previous learning sequence, we discussed The Database concepts. Present learning:
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Daniel Amyot, University of Ottawa Based on slides by Gunter Mussbacher (2009) and Stéphane Somé (2008) with material from these standards: IEEE ,
1 The XMSF Profile Overlay to the FEDEP Dr. Katherine L. Morse, SAIC Mr. Robert Lutz, JHU APL
COP Introduction to Database Structures
Michael J. Novak ASQ Section 0511 Meeting, February 8, 2017
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Understanding Enterprise Architecture
Methodology Conceptual Databases Design
Agenda Federated Enterprise Architecture Vision
Data Vertical Working Group
Methodology Conceptual Database Design
Chapter 6 Structuring System Requirements: Conceptual Data Modeling
Entity Relationship (E-R) Modeling
SysML v2 Formalism: Requirements & Benefits
DATA VERTICAL Technical Exchange
CV-1: Vision The overall vision for transformational endeavors, which provides a strategic context for the capabilities described and a high-level scope.
Web Ontology Language for Service (OWL-S)
Alignment of Part 4B with ISAE 3000
Chapter 5 Designing the Architecture Shari L. Pfleeger Joanne M. Atlee
DoDAF 2.x Meta Model (DM2) Conceptual Level
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Business Relationship Management
Continuity Guidance Circular Webinar
CAF Quarterly Meeting Measuring the Value of an EA Practice
Methodology Conceptual Databases Design
, editor October 8, 2011 DRAFT-D
Systems Architecture & Design Lecture 3 Architecture Frameworks
CORE Name: CORE® Description:
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Software Development Process Using UML Recap
Lecture 10 Structuring System Requirements: Conceptual Data Modeling
Software Architecture & Design
Presentation transcript:

IC Conceptual Data Model (CDM) Classification IC Conceptual Data Model (CDM) Joint Architecture Working Group Jerry Makowka, 703-874-8495 Bruce Fenchel, 703-874-8759 ICEA 26 May 2011 Classification

Agenda Background Uses Models Dictionary Relationship to JARM Documentation

Background (1 of 2) In August 2010, the Data Vertical Working Group (DVWG) was formed by the JAWG to complete the definition of the JARM Data Vertical (DV). The DV once complete will consist of the following artifacts; The IC Conceptual Data Model (IC CDM) The CDM Generalization Hierarchy The Data Dictionary The IC Data Architecture Framework (The IC CDM projected onto the JARM 10-Layer Model) The IC Meta-Model CONOPS for the DV Each component of the DV is intended to support the same purposes and uses as the JARM.

Background (2 of 2) The primary purpose of the IC CDM is to identify and document the key IC data entities, their definitions, and the relationships between the data entities. The IC CDM provides the foundation for the development of the artifacts for the JARM Data Vertical. The IC CDM is a clear, accurate visual representation of the essential business objects and the relationships necessary for the IC to operate as a federation. This includes the data regarding capabilities, activities, resources, information, guidance, and procedures as defined in the context of the JARM. The IC CDM will be added to the IC Enterprise Standards Baseline as informational guidance

Uses The IC CDM does the following: Provides the means to organize and characterize data information within the IC Establishes a common basis for logical and physical data models Provides the means to understand the inter-relationships between data-related capabilities and requirements across the IC portfolios. Enables a clear understanding of data at each layer of the 10 layer model.

IC CDM Concept Diagrams

IC CDM

IC CDM Level-0

Guidance Generalization Hierarchy

CDM Dictionary Exemplar Data Vertical DV Definition Source A Priori Condition The required environment state for an activity to begin. Derived from DM2 Activity Work, not specific to a single organization, system or individual that transforms inputs (Resources) into outputs (Resources) or changes their state. DM2 Adaptability Measure A quantitative measure of the ease with which Performers satisfy differing Constraints and Capability and Service needs. Administrative Management Capabilities that are focused on the planning, management, and day-to-day operation/maintenance of the internal, physical infrastructure of the enterprise. Adapted From JARM 2.0 Agreement A consent among parties regarding the terms and conditions of activities that said parties participate in. Analysis Capabilities that support operations focused on accessing intelligence data and information and applying analytical expertise to provide enhanced intelligence support to consumers and customers. Automatic Activity Activity conducted primarily using only Information Technology and/or machines. Authored Business Operations Management Capabilities that ensure Government resources are used efficiently to enable the mission. JARM Capability The ability to achieve an outcome under specified (performance) requirements and conditions through a combination of activities and resources. Adapted from DM2

IC CDM Documentation JARM Documentation Data Vertical Volume IC CDM Description 1 EXECUTIVE SUMMARY 2 INTRODUCTION 2.1 Purpose 2.2 Scope 2.3 CDM Development Approach 2.4 Terminology 2.5 Applicable Documents 3 CDM OVERVIEW 3.1 CDM Subject Areas 3.2 CDM Level 0 3.3 CDM Level 1 3.4 CDM Level 2 3.5 CDM Level 3 4 GENERALIZATION HIERARCHY 5 APPENDICES 5.1 Appendix – Acronyms 5.2 Appendix – Definitions and Aliases 5.3 Appendix – Subtype to JARM Layer Mapping 5.4 Appendix – Map of CDM to Existing Domain CDMs 5.5 Appendix - IC Core Vignette 5.6 Appendix - Intelligence Center Vignette Data Vertical Volume IC CDM Chapter DV Framework Chapter DV Metamodel DV CONOPS

Relationship to JARM Capability Generalization Hierarchy

IC Data Architecture Framework IC CDM projected on JARM 10 Layer Model

IC Core Business Object Mapped to CDM Exemplar IC Core Business Object Description CDM Entity Abstract Business Object Abstract representation of a business object. CDM Abstract Resource Abstract representation of an information resource. Resource Access Assertion Captures an access decision assertion to be enforced by a policy enforcement service (i.e., asserts that a subject is permitted to perform action on a resource(s)) Guidance/ Rule/ Constraint/Performance Constraint Access Attribute Attributes for accessing information resources. Resource/ Information/ Partially Structured Data Access Policy Defines the polices for access to or the performance of an action on a Resource(s) Guidance/ Policy Action Event Captures enterprise event/action information. Used in pub/sub model. Condition Address Attributes about an entity's physical address. Location/ Physical Location

Questions

Bonus Material MagicDraw Diagrams

CDM Subject Areas

CDM Level-0

CDM Level-1

CDM Level-2

CDM Level-3

CDM Level-4

Capability Generalization Hierarchy

Guidance Generalization Hierarchy

Measure Generalization Hierarchy

Location, Activity, Condition, & Initiative Generalization Hierarchy

Resource Generalization Hierarchy