SB821 3BSE018109R1 SB 821 驱动控制器

SB821 3BSE018109R1 SB 821 驱动控制器 

这种支持超出了操作和系统解决方案的细节或总结，
包括项目计划、项目状态报告、财务和预算
关系和风险管理。除了个别解决方案的详细视图外
框架支持企业范围内的视图和目标的交流，这些视图和目标说明了
这些解决方案的上下文以及组件之间的相互依赖性。超越
解决方案空间、沟通计划的标准机制、财务
建立信息和项目状态，以便管理人员和经理能够
评估和指导他们的项目。
国防部EA是一种体系结构描述，是用于评估的企业资产
与国防部企业的任务保持一致，加强客户支持，以
支持能力组合管理（PfM），并确保运营目标和
战略得到满足。国防部EA如下所示。它包括国防部体系结构政策，
工具、标准、国防部级体系结构描述，如国防部信息
企业体系结构（DoD IEA）、国防部级能力体系结构描述，以及
组件架构描述。其目的是指导投资组合
战略和决策，定义能力和互操作性需求，提供访问
划分体系结构信息，建立和实施标准，指导安全和
国防部的信息保证要求，并提供
从现有国防部环境向未来过渡的基础。国防部企业体系结构是
体系结构描述的联合，解决方案体系结构描述必须
符合其内容包括但不限于规则、标准、服务和系统
优化和维护流程或流程的一部分所需的生命周期信息
自给自足的组织希望通过管理其IT投资组合来创建和维护。这个
国防部企业体系结构提供了一种战略，使组织能够支持其当前的运作
同时作为向其目标环境过渡的路线图。过渡
过程包括组织的PfM、PPBE和EA规划过程，以及
服务和系统生命周期方法。JCA组合描述了未来、所需的作战、作战、业务和防御
情报能力，以及所需的系统和服务。他们提供
组织协调和联合国防部企业体系结构内容以支持国防部
投资组合管理结构。未来国防部作战环境的描述
相关能力需求代表了国防部企业体系结构的目标体系结构。
这些是由功能所有者和JCA开发人员确定的时间阶段。
在以网络为中心的操作环境中，从“现状”迁移到“未来”需要
国防部信息环境体系结构（DoD IEA）和网络中心战略
作为过渡序列的统一参考，并指导过渡序列，以确保
根据需要，适当描述了运营/业务能力和IT能力。
国防部首席信息官正在制定一项政策，以描述联邦如何成熟
国防部企业体系结构及其与联邦解决方案体系结构描述的关系。

SB821 3BSE018109R1 SB 821 驱动控制器 

SB821 3BSE018109R1 SB 821 驱动控制器 

Such support extends beyond details or summaries of operational and systems solutions,
and includes program plans, programmatic status reporting, financial and budget
relationships, and risk management. In addition to detailed views of individual solutions, the
framework supports the communication of enterprise-wide views and goals that illustrate the
context for those solutions, and the interdependencies among the components. Beyond the
solution space, standard mechanisms for communicating program plans, financial
information, and project status are established so that executives and managers can
evaluate and direct their programs.
The DoD EA is an Architectural Description that is an enterprise asset used to assess
alignment with the missions of the DoD enterprise, to strengthen customer support, to
support capability portfolio management (PfM), and to ensure that operational goals and
strategies are met. The DoD EA is shown below. It is comprised of DoD architecture policy,
tools, and standards, DoD-level Architectural Descriptions like the DoD Information
Enterprise Architecture (DoD IEA), DoD-level Capability Architectural Descriptions, and
Component Architectural Descriptions. Its purposes are to guide investment portfolio
strategies and decisions, define capability and interoperability requirements, provide access
to Segment architecture information, to establish and enforce standards, guide security and
information assurance requirements across the Department of Defense, and provide a sound
basis for transition from the existing DoD environment to the future. The DoD EA is a
federation of Architectural Descriptions with which Solution Architectural Descriptions must
conform. Its content includes but is not limited to rules, standards, services and systems
lifecycle information needed to optimize and maintain a process, or part of a process that a
self-sufficient organization wants to create and maintain by managing its IT portfolio. The
DoD EA provides a strategy that enables the organization to support its current operations
while serving as the roadmap for transitioning to its target environment. Transition
processes include an organization’s PfM, PPBE, and EA planning processes, along with
services and systems lifecycle methodologies.The JCA portfolios describe future, required operational, warfighting, business, and Defense
intelligence capabilities, together with the systems and services required. They provide the
organizing construct for aligning and federating DoD EA content to support the Department
portfolio management structure. The description of the future DoD operating environment
and associated capability requirements represent the target architecture of the DoD EA.
These are time-phased as determined by functional owners and JCA developers.
Migration in a net-centric operating environment from the “As-Is” to the “To-Be” requires
that the DoD Information Environment Architecture (DoD IEA) and the Net-Centric strategies
act as uniform references for, and guide the transition sequence to ensure that both
operational/business capabilities and IT capabilities, as required, are properly described.
Policy is being developed by the DoD CIO to describe how federation will be used to mature
the DoD EA as well as its relationship to federated, solution Architectural Descriptions.