Core Architecture Data Model
Logical models are more formal, often with considerations of unique data representation (non-redundancy or “normalization”), emphasis on semantic well-definedness and exclusivity (nonoverlapping entities), and domain-level completeness. Logical data models need not commit to a specific Data Base Management System (DBMS). Physical data models are usually the most detailed and the level sufficient for database generation. The Physical model must contain all the information necessary for implementation. The Physical model often addresses performance considerations.
1 2 3 4 DoD Architecture Framework Working Group (2003). DoDAF 1.5 Volume 2, 15 August 2003.
↑ Architecture Needed to Guide Modernization of DOD’s Financial Operations. GOA May 2001.
1 2 3 4 5 6 7 8 DoD (2003). DoDAF 1.0 Deskbook 15 Aug 2003.
1 2 Shishko, Robert (2006). “6.1. 1 The Application of Architecture Frameworks to Modelling Exploration Operations Costs”. INCOSE International Symposium 16 (1): 815-824. https://hdl.handle.net/2014/39752.
1 2 3 4 5 6 DoD (2007). DoD Architecture Framework Version 1.5 Volume 1. 23 April 2007