The document recommends an approach for a Federal Data Reference Model (DRM) to address issues with the current stovepiped data systems across government agencies. It proposes a federated data management approach using the DRM framework to enable horizontal and vertical information sharing across agencies. This would provide a common structure and tools to describe data, enable data integration and interoperability, and facilitate information exchange with external partners. It also discusses the related Net-Centric Data Strategy and role of Communities of Interest in implementing the goals of making data visible, accessible, understandable, and trusted across the government.
Understanding Discord NSFW Servers A Guide for Responsible Users.pdf
Drm Evolution 2005 10 19
1. Recommended Approach for the FEA Data Reference Model (DRM) Amit K. Maitra Consultant, Washington, DC October 19, 2005
2.
3.
4.
5.
6.
7.
8. Revolutionary Moments: The Mandate “ Our success depends on agencies working as a team across traditional boundaries to serve the American people, focusing on citizens rather than individual agency needs.” ~ President George W. Bush
20. Processes : The DoD Net-Centric Data Strategy aims at breaking down barriers to information sharing… B A R R I E R B A R R I E R B A R R I E R B A R R I E R “ What data exists?“ “ How do I access the data?” “ How do I know this data is what I need?” “ How can I tell someone what data I need?” “ How do I share my data with others?” “ How do I describe my data so others can understand it?” Organization “A” Organization “B” Organization “C” User is unaware this data exists User knows this data exists but cannot access it because of organizational and/or technical barriers ? User knows data exists and can access it but may not know how to make use of it due to lack of under- standing of what data represents End-User Consumer End-User Producer
21.
22.
Editor's Notes
The DRM provides a common, consistent way of categorizing and describing data to facilitate data sharing and integration
A model contains data defining the characteristics of a system. This data is used as a representation of that system for the purposes of conceptual understanding of a system controlling the exchange of information with that system controlling the presentation of that system information to end users The 'data' is typically called 'metadata' in this context
MOF is hard to teach Too abstract to understand But is the underlying architecture for MDA Secret weapon Ideal modeling technology, and The best integration architecture available It will be incorporated into most IT infrastructure over the next 10 years 20 years of disparate platforms MOF is a language used to define metamodels Metamodels define language/constructs to build models Relational for information sources BPEL, BPMI for business process XML Schema for XML documents UML for modeling applications MOF Metamodels are defined in terms of a common set of constructs Package, Classes, Attributes, Associations, References, etc. All MOF metamodels can be related MOF BENEFITS One modeling environment Information – data Logic Process Models are relatable Common constructs in disparate models can be related Best integration architecture to Model Drive execution engines