essential strategies, inc. global justice entity relationship model: a conceptual entity...

Essential Strategies, Inc.

Global Justice Entity Relationship Model:A Conceptual Entity Relationship Model

Presented to: The Data Architecture Subcommittee

April 12, 2007

13 Hilshire Grove Lane, Houston, TX 77055 (713) 464-8316 [email protected] www.essentialstrategies.com

Copyright (c) 2007 Essential Strategies, Inc. 2

About the Global Justice Data Model . . .

Lack of standards in sharing information are expensive.

The Department of Justice attempted to address this by dealing with the transfer of data.

XML has been adopted as the language for describing such transfers.

This has been selected as a starting point for the Data Architecture Sub-committee’s work.


Introducing The Data Resource Model . . .

Data Sharing

Data Description Data Context

Query Points and Exchange Packages (XML)


Data Elements(E/R Model)


Taxonomies (Categories)(Reference Data)


How do I exchange the data?

What does the data mean?

How do I find the data?

The Global Justice XML Data Model describes this . . .


About the Global Justice XML Data Model . . .

Designed as a standard for exchanging data. XML is the standard language for data exchange. The standard is about transactions. Not suitable for describing the underlying structure of

the data.

Addressing Data Description and Data Context will make defining

Data Sharing transactions simpler.


Characteristics of XML . . .

Fundamentally hierarchical. Can describe all people involved in a case, or Can describe all cases a person is involved in, But not both at the same time.

Difficult for non-technical people to understand. Yes, tags are ascii text. But relationships (other than simple hierarchies) are not

clear. XML describes physical transaction, not underlying

semantics of data.


<xsd:complexType name="AccidentSeverityCodeType"> <xsd:annotation> <xsd:documentation>A code list that enumerates severity levels

of an accident.</xsd:documentation> <xsd:appinfo> <i:info> <i:base i:namespace="http://www.it.ojp.gov/jxdm/3.0.3"

i:name="SuperType"/> </i:info> </xsd:appinfo> </xsd:annotation> <xsd:simpleContent> <xsd:extension base="ansi_d20:AccidentSevertyCodeType"> <xsd:attributeGroup ref="j:SuperTypeMetadata"/> <xsd:attribute ref="j:id"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType>

Sample XML . . .


<xsd:complexType name="AccidentSeverityCodeType"> <xsd:annotation> <xsd:documentation>A code list that enumerates severity levels

of an accident.</xsd:documentation> <xsd:appinfo> <i:info> <i:base i:namespace="http://www.it.ojp.gov/jxdm/3.0.3"

i:name="SuperType"/> </i:info> </xsd:appinfo> </xsd:annotation>

<xsd:simpleContent> <xsd:extension base="ansi_d20:AccidentSevertyCodeType"> <xsd:attributeGroup ref="j:SuperTypeMetadata"/> <xsd:attribute ref="j:id"/> </xsd:extension> </xsd:simpleContent>

</xsd:complexType>

Sample XML (XML Schema defines model) . . .

Who noticed that “Severity” is misspelled?


Another kind of The Global Justice Model . . .

Data Sharing

Data Context





Data Description



Today we’re going to look at this . . .

E/R Model


About the Global JusticeEntity/relationship Data Model . . .

Describes the things of significance to an organization. Definitions, Attributes, Relationships

Two dimensional Can show network of relationships. E.g: Person—<Role>—CASE—<CASE_Characteristic

Accessible Graphically represents the organization’s semantics. Specifically, it represents a set of assertions about the

organization.


Note . . .

An ERD is accessible

only if done right.

A completely incomprehensible entity / relationship model is also possible, of course.


Kinds of data model

Conceptual – describes the semantics of the organization, without regard to the technology used to manage its data. Entity classes and attributes, relationships.

Logical – describes data organized according to a particular data management approach – relational, object-oriented, XML. Object classes, tables and columns, foreign keys, XML tags.

Physical – describes how data are physically stored in (e.g. distributed) databases. Tablespaces, partitions, servers, databases, etc.


Today’s presentation . . .

A conceptual entity/relationship diagram. Based on:

The GJXDM User Guide: Module 3, Part 2, “Global Justice XML Data Dictionary Core

Components”, Building Exchange Content Using the Global Justice XML Data Model: A User Guide for Practitioners and Developers. June, 2005.

My book: David C. Hay, Data Model Patterns: Conventions of Thought. (New

York, Dorset House). 1995.

The model is a set of natural language assertions about the nature of law enforcement activities.

I did not have the opportunity to interview anyone who knows anything about the Justice Department.


How to Read the assertions . . .

Each BOOK must be primarily about one and only one TOPIC.

Each TOPIC may be addressed in one or more BOOKS.

Each

<first entity>

must be[or]may be

<relationship name>

one and only one[or]one or more

<second entity>

primarily about

BOOK

TOPICNOTE: These are assertions.

Are they true?

!!??

one and only oneprimarilyEach BOOK must be about one

or more TOPICS.


Quote for the day . . .

“In modeling, It is more important to be clear than to be correct!

- If you are clearly wrong, someone will tell you,

- but if you are obscurely right, you may never know!”

- Ken Orr The Ken Orr Institute


The model . . .

Cases – the investigations, trials, and follow-ups. People and organizations – the officers, suspects,

judges, lawyers, and so forth.




The model . . .


Cases and Activities . . .

CASE# CASE NUMBER* DESCRIPTION* START DATEo END DATE

ACTIVITY# IDo NAMEo DESCRIPTIONo REASONo SCHEDULED START DATE AND TIMEo SCHEDULED END DATEo ACTUAL START DATEo ACTUAL END DATEo COMPLETED INDICATOR

part of

composed of

part of composed of

part of

composed of

stake-out (3/24/05)discovery (5/2/05)arraignment (9/14/05)laboratory test (7/19/05)

investigation #2543trial #9750appeal #9750-3



CASE TYPE# NAMEo DESCRIPTION

CASE ACTIVITY RULE# SEQUENCE NUMBERo COMMENT

ACTIVITY TYPE# NAMEo DESCRIPTION


part of

composed of

an example of

embodiedin

a constraint on

subject to

constrained by

the object of

an example of

embodiedin

part of composed of

a sub- type of a super- type ofa sub-type of a super-type of

part of

composed of

Activity Types and Case Types . . .

stake-out discoveryarraignmentlaboratory test

investigationtrialappeal

stake-out (3/24/05)discovery (5/2/05)arraignment (9/14/05)laboratory test (7/19/05)

investigation #2543trial #9750appeal #9750-3







EVIDENCE# ID* DESCRIPTIONo DATE DISCOVERED* DATE ENTEREDo DATE ARCHIVED

EVIDENCETYPE# NAMEo DESCRIPTION

ACTIVITY STATUS# SEQUENCE NUMBER* START DATEo END DATE

ACTIVITYSTATUSTYPE# NAMEo DESCRIPTION

CASE STATUS# SEQUENCE NUMBER* EFFECTIVE DATEo END DATE

CASE STATUSTYPE# NAMEo DESCRIPTION

of

in

an example of

embodiedin

submittedto

evaluated in terms of

anexampleof

embodied in

part of

composed of

of

in

anexampleof

embodied in

an example of

embodied in

a constraint on

subject to

constrained by

the object of

an example of

embodied in

part of composed of

a sub- type of a super- type ofa sub-type of a super-type of

part of

composed of

Stati and Evidence . . .

fingerprintphotograph

PendingActiveComplete

PendingActiveComplete







EVIDENCE# ID* DESCRIPTIONo DATE DISCOVERED* DATE ENTEREDo DATE ARCHIVED

EVIDENCE TYPE# NAMEo DESCRIPTION

RESULTTYPE# NAMEo DESCRIPTION

RESULT# SEQUENCE NUMBE* DATE ENTEREDo EXPIRATION DATE

ACTIVITY STATUS# SEQUENCE NUMBER* START DATEo END DATE

ACTIVITYSTATUS TYPE# NAMEo DESCRIPTION

CASE STATUS# SEQUENCE NUMBER* EFFECTIVE DATEo END DATE

CASE STATUSTYPE# NAMEo DESCRIPTION

EVENT# IDo DESCRIPTIONo CIRCUMSTANCES* EVENT DATE

EVENTTYPE# NAMEo DESCRIPTION

of

in

an exampleof

embodied in

for

the source of

anexampleof

embodiedin

submitted to

evaluated interms of

anexampleof

embodied in

part of

composed of

of

in

anexampleof

embodied in

an example of

embodied in

a constraint on

subject to

constrained by

the object of

an example of

embodied in

during

context for

the trigger of

triggeredby

an example of

embodied in

part of composed of

a sub- type of a super- type ofa sub-type ofa super-type of

a sub- type of a super- type of

for

thesourceof

part of

composed of

thecause of

theresultof

Events and Results . . .

Charge- Felony- Infraction- Misdemeanor- Offense- Violation

Supervision- Corrections- Detention

AlertAssessmentArrestBail postedBond setBookingCitation

Call about a burglary

John Smith arrested

John Smith charged with felony




The model . . .


People and Organizations . . .

PERSON* SURNAMEo GIVEN NAME

ORGANIZATION* ORGANIZATION NAME* SETUP DATEo PURPOSE

COMPANYo TAX ID

COMPANYDEPARTMENT

GOVERNMENT

GOVERNMENTAGENCY

GOVERNMENTINTERNALORGANIZATION

OTHERORGANIZATION

POLITICALORGANIZATION

composedof

part of

part of

composedof

composedof

part of

The Procurement Office

The F.B.I.

Lockheed Martin

Accounting Department

The Federal Government of the U.S.

The Republican Party


Parties . . .

“Person”“Organization”

“Company Department”

“Company”etc.

PARTY# ID

PARTY TYPE# NAME* DESCRIPTION



COMPANYDEPARTMENT

GOVERNMENT

GOVERNMENTAGENCY


OTHERORGANIZATION


COMPANYo TAX ID

an example of

embodied in

composedof

part of

part of

composedof

composedof

part of

a sub- type of

a super- type of


Party Relationships . . .

MarriageOrganizational StructureLabor Union Membership

PARTY# ID


PARTYRELATIONSHIP# EFFECTIVE DATEo UNTIL DATE

PARTYRELATIONSHIPTYPE# NAME* DESCRIPTION



GOVERNMENT

GOVERNMENTAGENCY


OTHERORGANIZATION


COMPANYo TAX ID

COMPANYDEPARTMENT

an example of

embodied in

composedof

part of

part of

composedof

composedof

part of

from

parent in

to

child in

an example of

embodied in

a sub- type of

a super- type of

David Hay is married to Jolanta Hay


PARTY# ID


PARTY RELATIONSHIP# EFFECTIVE DATEo UNTIL DATE

PARTYRELATIONSHIPTYPE# NAME* DESCRIPTION



GOVERNMENT

GOVERNMENTAGENCY


OTHERORGANIZATION


COMPANYo TAX ID

COMPANYDEPARTMENT

an example of

embodied in

composedof

part of

part of

composedof

composedof

part of

from

parent in

to

child in

an example of

embodied in

a sub- type of

a super- type of

from

a constraint on

to

a constraint on

Some metadata . . .

Organizational structure:from Organization

to Organization


Scars marks and tattoosMarked part of the body

TattooScar

Nonspecific markBreast

Armetc.

Categories and Characteristics . . .

Driver’s License numberIncorporation Date

Cabinet Department indicator

Arm, nonspecific, artificialBreast, nonspecific, artificialBreast implant, left and right

Scars marks and tattoos

PARTY# ID



PARTY RELATIONSHIPTYPE# NAME* DESCRIPTION

PARTYCHARACTERISTICVALUE* VALUE* EFFECTIVE DATEo UNTIL DATE

PARTYCHARACTERISTIC# NAMEo DESCRIPTIONo MINIMUM VALUEo MAXIMUM VALUE

PARTYCATEGORIZATION# EFFECTIVE DATEo UNTIL DATE

PARTY CATEGORY# NAMEo DESCRIPTION

PARTY CATEGORYSCHEME# NAMEo DESCRIPTION




OTHERORGANIZATION


COMPANYo TAX ID

COMPANYDEPARTMENT

GOVERNMENT

GOVERNMENTAGENCY

an example of

embodied in

composedof

part of

part of

composedof

composedof

part of

from

parent in

to

child in

an example of

embodied in

a descriptor of

described by

of

evaluated at

of

subject to

into

the object of

part of

composed of

defined bydefiner of

part of

composed of

narrowerthan

broader than

broader than

narrower than

assigned by

assigner of

defined by

definer of

by

classifier in


Some more metadata . . .

Driver’s License number:Person

Incorporatio Date:CompanyCabinet Department

indicator:Government Agency

PARTY# ID



PARTY RELATIONSHIPTYPE# NAME* DESCRIPTION

PARTY CHARACTERISTICVALUE* VALUE* EFFECTIVE DATEo UNTIL DATE

PARTY CHARACTERISTIC# NAMEo DESCRIPTIONo MINIMUM VALUEo MAXIMUM VALUE

PARTY CATEGORIZATION# EFFECTIVE DATEo UNTIL DATE

PARTY CATEGORY# NAMEo DESCRIPTION

PARTY CATEGORYSCHEME# NAMEo DESCRIPTION

PARTY TYPECONSTRAINT




OTHERORGANIZATION


COMPANYo TAX ID

COMPANYDEPARTMENT

GOVERNMENT

GOVERNMENTAGENCY

an example of

embodied in

composedof

part of

part of

composedof

composedof

part of

from

parent in

to

child in

an example of

embodied in

a descriptor of

described by

of

evaluated at

of

subject to

into

the object of

part of

composed of

defined by

definer of

a sub- type of

a super- type of

narrower thanbroader than

broader than

narrower than

on

subject to

on

subject to

based on

the basis for

assiged by

assigner of

defined by

definer of

by

classifier in


Positions . . .

Police officerJudge

Attorney

Houston Police officer District Judge

District Attorney


Roles . . .

AccusedAtty for defense

Lab analystetc.


This model was specific to Criminal Justice . . .

To make it specific to your agency (welfare, forest service, etc), change the model: Make the name of the CASE entity class PROJECT Remove EVIDENCE and EVIDENCE TYPE entity classes.

That’s all . . .


This model was specific to Criminal Justice . . .

To make it specific to your agency (welfare, forest service, etc), change the following data: Activity type Case type Activity status type Case status type Event type Result type Party Relationship Type Party Characteristic Party Category Scheme / Party Category Position Type Activity Role Type Case (Project) Role

That’s all . . .

NOTE: No structural changes are required.


Ok, you can certainly elaborate on this . . .

Add attributes to PARTY. Thereby making it specific to your agency only. Thereby making it harder to track their values over time. Thereby making it harder to capture other metadata about

them.

Add more concrete entity classes. Thereby making it specific to your agency only. Thereby increasing the maintenance requirements for your

DBAs

This is a trade-off with economic consequences.


By the way, this model is wrong . . .

You discovered that today. Before we can adopt it . . .

We must pass it by as many agencies as possible. They will certainly find legitimate changes and

enhancements that should be included.


NIEM documentation and standards include a data dictionary, data model, andIEPDs. The data dictionary is a well‑defined vocabulary of data names andstructures.

The data model is the body of concepts and rules that underlie the structure of the data dictionary, including data components arranged by domain, the type of data being represented (date, integer, Boolean, string, etc.), and a semantically precise, context‑rich definition of each component.

Together the data dictionary and model become a database, from which XML schemas are generated. These schemas contain the data components that are reused to construct the IEPDs.

Introduction to theNational Information Exchange Model

(NIEM), June 30, 2006p. 14.

But what about NIEM . . . ?


Now, let’s flesh outThe Data Resource Model . . .

Data Sharing

Data Description Data Context



What does the data mean?






Questions ?

essential strategies, inc. global justice entity relationship model: a conceptual entity...

Documents

data exchange

global justice data

data mean

essential strategies

global justice xml data

data resource model

underlying semantics

global justice model