REPORT DOCUMENTATION PAGE
Form Approved
OMB No. 0704-0188
Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data
sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any
other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for information Operations
and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-
0188), Washington, DC 20503.
1. AGENCY USE ONLY
(Leave Blank)
2. REPORT DATE
October 2001
3. REPORT TYPE AND DATES COVERED
Final
4. TITLE AND SUBTITLE
An Enterprise Information System Data Architecture Guide
5. FUNDING NUMBERS
F19628-00-C-0003
6. AUTHOR(S)
Grace Alexandra Lewis, Santiago Comella-Dorda, Pat Place, Daniel Plakosh, Robert C. Seacord
7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES)
Software Engineering Institute
Carnegie Mellon University
Pittsburgh, PA 15213
8. PERFORMING ORGANIZATION
REPORT NUMBER
CMU/SEI-2001-TR-018
9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES)
HQ ESC/XPK
5 Eglin Street
Hanscom AFB, MA 01731-2116
10. SPONSORING/MONITORING AGENCY
REPORT NUMBER
ESC-TR-2001-018
11. SUPPLEMENTARY NOTES
12A DISTRIBUTION/AVAILABILITY STATEMENT
Unclassified/Unlimited, DTIC, NTIS
12B DISTRIBUTION CODE
13. ABSTRACT (MAXIMUM 200 WORDS)
Data architecture defines how data is stored, managed, and used in a system. It establishes common guidelines for
data operations that make it impossible to predict, model, gauge, or control the flow of data in the system. This is even
more important when system components are developed by or acquired from different contractors or vendors.
This report describes a sample data architecture in terms of a collection of generic architectural patterns that both de-
fine and constrain how data is managed in a system that uses the Java 2 Enterprise Edition (J2EE) platform and the
Open Applications Group Integration Specification (OAGIS). Each of these data architectural patterns illustrates a
common data operation and how it is implemented in a system.
14. SUBJECT TERMS
Data architecture, J2EE, OAGIS, component-based design, enterprise information
systems, architectural patterns
15. NUMBER OF PAGES
72
16. PRICE CODE
17. SECURITY CLASSIFICATION OF
REPORT
Unclassified
18. SECURITY CLASSIFICATION OF
THIS PAGE
Unclassified
19. SECURITY CLASSIFICATION OF
ABSTRACT
Unclassified
20. LIMITATION OF ABSTRACT
UL
NSN 7540-01-280-5500 Standard Form 298 (Rev. 2-89) Prescribed by ANSI Std. Z39-18 298-102