﻿<?xml version="1.0" encoding="UTF-8"?><StrategicPlan xsi:schemaLocation="http://www.stratml.net http://www.schema-archive.com/xml.gov/stratml/v1r0/cur/StrategicPlan.xsd" xmlns="http://www.stratml.net" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><!--This document transformed using a tool developed by Drybridge Technologies for information navigate to http://www.drybridge.com--><!--The schema posted at http://www.schema-archive.com is provided as a courtesy for on-line validation of various standards. You should verify that the schema provided meets your requirements.--><Name>Net-Centric Enterprise Solutions for Interoperability, Department of the Navy</Name><StrategicPlanCore><Organization><Name>Net-Centric Enterprise Solutions for Interoperability, Department of the Navy</Name><Acronym>NESI</Acronym><Identifier>_b9b64ffd-e65f-48b1-82ed-dfc9812a31d7</Identifier></Organization><Vision><Description>The vision for NESI is that it will be the definitive source of net-centric implementation guidance for the DoD. The knowledge expressed in NESI will be accurate, current, accessible, cover all pertinent technical areas, and be easy to maintain. In addition, NESI will provide flexible tools for using this knowledge to achieve shared objectives across diverse organizations.</Description><Identifier>_bbcdf746-cb27-4852-89dd-03f15974354a</Identifier></Vision><Mission><Description>To support government and industry system and software engineers who are developing net-centric solutions as well as their associated program managers</Description><Identifier>_883e04f5-bdab-4f0a-a412-4f750d1d5f23</Identifier></Mission><Goal><Name>Net-Centricity</Name><Description>Promote realization of the net-centric aspects of the GIG architecture, per the DoD Global Information (GIG) Architecture  [R1170], through the evolution of legacy systems and the development of new systems that comply with DoD net-centric direction. </Description><Identifier>_a6309af9-d4f8-4910-a508-2866bc070cbb</Identifier><SequenceIndicator>1</SequenceIndicator><Objective><Name>Data Definitions</Name><Description>Define related terms and concepts</Description><Identifier>_156246a3-edb1-44ee-ba55-74e0c254d20c</Identifier><SequenceIndicator>1.1</SequenceIndicator></Objective><Objective><Name>Architectural and Engineering Knowledge</Name><Description>Identify specific architectural and engineering knowledge at multiple levels of abstraction</Description><Identifier>_e5801c10-4bd4-48a0-ac61-4fcdb62e85d5</Identifier><SequenceIndicator>1.2</SequenceIndicator><OtherInformation>Identify succinct, atomic, actionable guidance Define the context for the guidance Identify, define, and develop examples Identify appropriate reference material </OtherInformation></Objective><Objective><Name>Knowledge Vetting</Name><Description>Vet this knowledge across pertinent communities</Description><Identifier>_1508e99a-975e-4d37-9c06-ac9e398f0edb</Identifier><SequenceIndicator>1.3</SequenceIndicator></Objective><Objective><Name>Knowledge Tools</Name><Description>Identify tools to store, tag, sort, filter, and distribute this knowledge</Description><Identifier>_4f8185c9-08bf-469f-a1b3-1399c88c0146</Identifier><SequenceIndicator>1.4</SequenceIndicator></Objective><Objective><Name>Knowledge Maintenance</Name><Description>Maintain this knowledge </Description><Identifier>_1a4999f0-908a-409c-8782-e2f58b8de4eb</Identifier><SequenceIndicator>1.5</SequenceIndicator><OtherInformation>Evolve as the concept of net-centricity evolves. Remain current with changes in DoD net-centric directives, mandates, and instructions.</OtherInformation></Objective></Goal><Goal><Name>Component-Based N-Tier Framework</Name><Description>Promote the consistent application of a sound technical approach to net-centricity based on a component-based N-tier framework for application development. </Description><Identifier>_fd88e462-4bf6-4e86-beb0-d6a0afd72083</Identifier><SequenceIndicator>2</SequenceIndicator><OtherInformation>(Note: this framework may be implemented in many different ways; e.g., with different infrastructure distribution strategies). </OtherInformation></Goal><Goal><Name>Software Component Reuse</Name><Description>Promote the reuse of software components so that they can be composed easily into new mission capabilities with minimal development effort. </Description><Identifier>_fc22403c-9c74-4513-983b-18c499c36ef4</Identifier><SequenceIndicator>3</SequenceIndicator><OtherInformation>NESI establishes a technical basis that allows developers to leverage reuse opportunities. </OtherInformation><Objective><Identifier>_59cc2ea8-4c3c-43c1-80e9-28909bc83142</Identifier><SequenceIndicator>3.1</SequenceIndicator></Objective></Goal><Goal><Name>Enterprise Integration and Interoperability</Name><Description>Promote enterprise integration and interoperability through the reuse of enterprise design patterns, well-defined public service interfaces, and loosely coupled components. </Description><Identifier>_994e7c89-4d70-4a8e-ab9f-0c827230cc65</Identifier><SequenceIndicator>4</SequenceIndicator><OtherInformation>These are key elements to meet the criteria in the Net-Centric Operations and Warfare Reference Model (NCOW RM).</OtherInformation></Goal><Goal><Name>Infrastructure</Name><Description>Provide a model for the distribution of infrastructure elements in which Enterprise Services are provided and managed across the enterprise by the NCES program and individual programs share infrastructure resources in a Node-based approach.</Description><Identifier>_3b960128-3166-4ba6-b2a6-b2b99e035829</Identifier><SequenceIndicator>5</SequenceIndicator></Goal></StrategicPlanCore><AdministrativeInformation><PublicationDate>2010-02-08</PublicationDate><Source>http://nesipublic.spawar.navy.mil/nesix/Frames/P1286</Source><Submitter><FirstName>Arthur</FirstName><LastName>Colman (www.drybridge.com)</LastName><EmailAddress>colman@drybridge.com</EmailAddress></Submitter></AdministrativeInformation></StrategicPlan>