DoD Architecture Framework Version 1.5 - Chief Information Officer

More documents

Recommendations

Info

Force, 2000] Technology Architectures, 1 May 2000. [DISA, 2002] Defense Information Systems Agency, Joint Technical Architecture, v4.0, 17 July 2002. Director for Information Systems, Command, Control, Communications and [DISC4, 1998] Computers (DSC4), Army Enterprise Architecture Guidance Document, v01.1, 23 December 1998. [DoD JP 1-02, 2001] Department of Defense Joint Publication, JP 1-02, “Dictionary of Military and Associated Terms,” Joint Publication 1-02, August 2002. [DoD TRM, 2001] Department of Defense, Technical Reference Model, v2.0, 9 April 2001. [DoDAF 2003] DOD Architecture Framework (DoDAF), V1.0, Vols I, II, and III, 15 August 2003 Department of Defense Directive, DoDD 4630.5, Interoperability and [DODD 4630.5, 2004] Supportability of Information Technology (IT) and National Security Systems (NSS), 5 May 2005. [DoDD 5000.1, 2003] Department of Defense Directive, DODD 5000.1, The Defense Acquisition System, May 12, 2003. Department of Defense Directive, DODD 8000.1, Management of DoD Information [DoDD 8000.1, 2003] Resources and Information Technology, 27 February 2002; Administrative Reissuance, 20 March 2002. [DoDD 8100.1, 2002] Department of Defense Directive, DODD 8100.01, Global Information Grid Overarching Policy, 19 September 2002. [DoDD 8115.01, 2005] Department of Defense Directive, DODD 8115.1, Information Technology Portfolio Management, 10 October 2005. [DoDD 8320.02G, 2006] DoD 8320.02-G, Guidance for Implementing Net-Centric Data Sharing, ASD(NII) CIO, 12 April 2006. [DoDD 8320.2, 2004] DoD Directive 8320.2, Data Sharing in a Net-Centric Department of Defense, ASD(NII) CIO, 2 December 2004. Department of Defense Instruction, DODI 4630.8, Procedures for Interoperability [DoDI 4630.8, 2004] and Supportability of Information Technology (IT) and National Security Systems (NSS), 30 June 2004. [DoDI 5000.2, 2003] DoD Instruction 5000.2, Operation of the Defense Acquisition System, 12 May 2003. [DODM 2006] DoD CIO Memo, Data Strategy Implementation Report to the Deputy Secretary of Defense, 31 March 2006. [Dunn, 2006] Discussions with Bruce Dunn, U.S. Army Communications Electronics Research Development and Engineering Center (CERDEC), Ft. Monmouth, NJ. [EISG, 2006] “U.S. Air Force ESC Enterprise Integration Systems Group (EISG) Master Plan and Schedule”, COL D. Madden, 7 April 2006. [EAAF, 2006] “Federal Enterprise Architecture Program EA Assessment Framework 2.1,” December 2006. [FEA DRM 2005] “Federal Enterprise Architecture Data Reference Model”, v2.0, 17 November 2005, http://www.whitehouse.gov/omb/egov/documents/fea-drm1.PDF. [FIPS 183, 1993] Integration Definition for Function Modeling (IDEF0), Federal Information Processing Standards (FIPS) Publication 183, 21 December 1993. [FIPS 184, 1993] Integration Definition for Data Modeling (IDEF1X), Federal Information Processing Standards (FIPS) Publication 184, 21 December 1993. [HAREL, 1987a] Harel, D., “Statecharts: A Visual Formalism for Complex Systems,” The Science of Computer Programming, 1987, 8, pp. 231-274. Harel, D., A. Pnueli, J.P. Schmidt, and R. Sherman, On The Formal Semantics of [HAREL, 1987b] Statecharts, Proceedings, Second IEEE Symposium, Logic Computer Science, Dorset House, New York, 1987, pp. 54-64. M. Endrei, J Ang, A Arsanjani, S. Chua, P. Comte, P. Krogdahl, M. Luo, T. Newling, “Patterns: Service-Oriented Architectures and Web Services,” IBM [IBM, 2004] RedBooks, IBM 2004 http://publibb.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg246303.htmlOpen C-2
http://www.bpmmag.net/ http://www-306.ibm.com/software/solutions/webservices/eis/soa-versus-eai/. Information Integration For Concurrent Engineering (IICE) IDEF3, Process [IDEF3, 1995] Description Capture Method Report, KBSI-IICE-90-STR-01-0592-02, Knowledge Based Systems, Incorporated, 1995. “Recommended Practice for Architectural Description of Software-Intensive Systems,” IEEE Std 1471, 2000 [IEEE 1471] http://www.ieee.org [IEEE Std 1471 and Beyond] http://members.bellatlantic.net/~rfh2/writings/hilliard01-sei-workshop.pdf. Institute of Electrical and Electronics Engineers, IEEE STD 610.12, Standard [IEEE 610.12, 1990] Glossary of Software Engineering Terminology, The Institute of Electrical and Electronics Engineers, Inc., Piscataway, New Jersey, 1990. Institute of Electrical and Electronics Engineers, IEEE STD 1471, Recommended [IEEE STD 1471, 2000] Practice for Architectural Description of Software-Intensive Systems, The Institute of Electrical and Electronics Engineers, Inc., New York, New York, 2000. [ITMRA, 1996] Information Technology Management Report Act (Clinger-Cohen Act of 1996). Joint Staff, J8, Introduction to the Joint Capabilities and Integration Development [JS/J8, 2003] System, Briefing, 2003, Online, Available: http://dod5000.dau.mil/. Kristensen, Lars M., S. Christensen, and Kurt Jensen, The Practitioner's Guide To [Kristensen, 1998] Coloured Petri Nets, Springer-Verlag, 1998. Levis, A., and L. Wagenhals, “C4ISR Architectures I: Developing a Process for [Levis, 2000] C4ISR Architecture Design,” Systems Engineering, Vol. 3, No. 4, Fall 2000. Naqvi, Shamim, and Shalom Tsur, LDL: A Logical Language for Data and [Naqvi, 1989] Knowledge Bases, Computer Science Press, Rockville, Maryland, 1989. Allied Data Publication 34, NATO C3 Technical Architecture, Volume 2: [NATO, 2000] Architectural Descriptions and Models, v4.0, 7 March 2003, pp. 35-38. “DoD Net-Centric Data Strategy”, Memorandum, 9 May 2003, [NCDS 2003] http://www.defenselink.mil/nii/org/cio/doc/Net-Centric-Data-Strategy-2003-05- 092.pdf. “Net-Centric Operations and Warfare Reference Model” Office of the Assistant [NCOW RM, 2005] Secretary of Defense (OASD)(NII), 17 November 2005. “Memorandum: Global Information Grid Enterprise Services (GIG ES) - Net- [NCW, 2004] Centric Environment,” OASD(NII), July 2004 http://www.defenselink.mil/nii/doc/docArchive.html#NII. [NDS, 2005] Department of Defense, “National Defense Strategy,” March 2005. Neill, C.J., and J. D. Holt, "Adding Temporal Modeling to the UML to Support [Neill, 2002] Systems Design,” Systems Engineering, Vol. 5, No. 3, Fall 2002. Nicholson, D., Mercer, B., Ang, H., (2005), “Addressing Conceptual Deficiencies In DoDAF Through An Architecture Specification Model-ASM,” Proceedings of [Nicholson, 2005] Conference on Defense Transformation And Network-Centric Systems, SPIE Vol. #5820, Orlando, Florida. National Reconnaissance Office, National Reconnaissance Office Architecture [NRO, 2001] Framework (DRAFT), v0.9, May 2001. O’Rourke, C., Fishman, N., & Selkow, W., “Enterprise Architecture Using the [O’Rourke, 2003] Zachman Framework,” Thomson Course Technology publishing, 2003, ISBN 0- 619-06446-3. Office of the Assistant Secretary of Defense for (C3I), Global Information Grid [OASD (C3I), 2000] (GIG) Architecture (v1.0) DRAFT, 31 December 2000. Organization for the Advancement of Structured Information Standards (OASIS), [OASIS, 2006] “Reference Model for Service Oriented Architecture 1.0”, OASIS Standard, 12 October 2006, http://www.oasis-open.org/specs/index.php#soa-rmv1.0. Office of Management and Budget, Circular A-130: Management of Federal [OMB, 2000] Information Resources, 30 November 2000. Office of Management and Budget, Business Reference Model (BRM) v2.0, Service [OMB, 2003] Component Reference Model (SRM) v1.0, Technical Reference Model (TRM) v1.0, C-3
Page 1 and 2: wreath stars Text DoD Architecture
Page 3 and 4: 3.3 FACILITATING THE USE OF ARCHITE
Page 5 and 6: prepare the way for more efficient
Page 7 and 8: C4ISR Architecture Framework, Versi
Page 9 and 10: 1.2 SCOPE OF DODAF v1.5 NCO require
Page 11 and 12: Table 1-3: New Products for v1.5 Ne
Page 13 and 14: A federated architecture is a distr
Page 15 and 16: enables the incorporation of inform
Page 17 and 18: Applicable View Framework Product F
Page 19 and 20: 2 ARCHITECTURE DEVELOPMENT 2.1 ARCH
Page 21 and 22: Step 1: Determine Intended Use of A
Page 23 and 24: architecture federation, net-centri
Page 25 and 26: associated reference models, and ca
Page 27 and 28: 3 ARCHITECTURE USAGE 3.1 THE VALUE
Page 29 and 30: DoD policies and directives call fo
Page 31 and 32: Applicable Architecture Product Dat
Page 33 and 34: 4 GOVERNING, DEVELOPING, MAINTAININ
Page 35 and 36: ANNEX A GLOSSARY A&T ABM ASD(C3I) A
Page 37 and 38: PfM PPBE SIPRNET SOA SoS SV TA TV U
Page 39 and 40: Data Data Model Data-Entity* Defens
Page 41 and 42: Needline* Net-Centric Environment N
Page 43: ANNEX C REFERENCES [ADM, 2004] Arch

DoD Architecture Framework Version 1.5 - Chief Information Officer

Create successful ePaper yourself

Delete template?

Save as template?