SAMC11POW 57171847K SAMC11 POW 控制器 电源板

SAMC11POW 57171847K SAMC11 POW 控制器 电源板 

注：重要的是要注意，体系结构描述的开发是
迭代过程是一个独特的过程，因为每个体系结构描述都是：
不同之处在于，架构创建服务于特定的目的，并且是从
这是一个特别的观点。
服务于不同的需求，需要不同类型的视图来表示
收集的数据。
代表“即时快照”（例如，架构描述可以
表示当前视图或基线，也可以表示某些
未来时间）。
随着时间的推移，随着需求变得更加集中或附加知识而变化
关于过程或需求的信息变得已知。
以下描述的方法旨在涵盖尽可能广泛的一组：
环境，以及关注架构中常用的步骤
社区
步骤1：确定架构的预期用途。定义目的和预期用途
架构（“适合用途”）；架构描述工作将如何进行
进行；架构开发中使用的方法；数据类别
需要；对其他人的潜在影响；以及这项努力取得成功的过程
根据绩效和客户满意度进行衡量。这个信息是
通常由流程所有者提供，以支持架构开发，描述
其职责范围的某些方面（过程、活动等）。
用于收集与项目目的和范围相关的信息的模板
体系结构描述、术语表和其他信息已经为
在DARS中注册该数据。
步骤2：确定架构的范围。范围定义了以下边界：
确定架构描述的深度和广度，并确定
架构的问题集，有助于定义其上下文，并定义所需的详细级别
建筑内容。尽管许多体系结构开发工作在其
方法，每项努力都是独特的，因为预期的结果或效果可能相当
不同的例如，系统开发工作通常首先关注流程
改变，然后专注于支持工作流程的自动化功能，或
活动。除了了解过程之外，这些“系统功能”的发现是
在决定如何继续开发或购买自动化支持时非常重要。
为描述服务的体系结构描述收集的信息类似于
为描述系统的体系结构描述收集的信息。描述
架构描述将收集关于订阅的附加信息，
目录服务、组织内的分销渠道和支持
系统/通信网络需求。
联合作战的体系结构描述开发也会出现类似情况。共同的
能力是指具有预期结果和预期执行能力的过程
日期。支持这些类型的开发的体系结构描述
能力通常需要重用军事部门已经建立的数据，并且
机构、分析和配置为新的或更新的流程，以提供所需的
能力。包括军事服务和/或机构响应所需的过程，
所需的自动化支持，以及所需结果和支持的明确定义
性能度量（度量）。这些类型的数据在模型中显示。
这一步的重要概念是明确为项目定义的工作范围
这实现了预期的结果。范围广泛或问题定义不明确可能会延迟
或者阻止成功。流程所有者主要负责确保：
范围界定是正确的，项目可以成功完成。
通过定义和描述要使用的数据，可以更好地确定范围的清晰度
在创建视图之前提出的架构描述

SAMC11POW 57171847K SAMC11 POW 控制器 电源板 

SAMC11POW 57171847K SAMC11 POW 控制器 电源板 

OTE: It is important to note that the development of Architectural Description is an
iterative process and a unique one, in that every Architectural Description is:
Different in that architecture creation serves a specific purpose, and is created from a
particular viewpoint.
Serving differing requirements, necessitating different types of views to represent the
collected data.
Representative of a 'snapshot in time' (e.g., the Architectural Description may
represent the current view or baseline, or it may represent a desired view in some
future time).
Changeable over time as requirements become more focused or additional knowledge
about a process or requirement becomes known.
The methodology described below is designed to cover the broadest possible set of
circumstances, and also to focus on the most commonly used steps by the architecture
community.
Step 1: Determine Intended Use of Architecture. Defines the purpose and intended use
of the architecture ("Fit-for-Purpose"); how the Architectural Description effort will be
conducted; the methods to be used in architecture development; the data categories
needed; the potential impact on others; and the process by which success of the effort will
be measured in terms of performance and customer satisfaction. This information is
generally provided by the process owner to support architecture development describing
some aspect of their area of responsibility (process, activity, etc.).
A template for collection of high-level information relating to the purpose and scope of the
Architectural Description, its glossary, and other information, has been developed for
registration of that data in DARS.
Step 2: Determine Scope of Architecture. The scope defines the boundaries that
establish the depth and breadth of the Architectural Description and establish the
architecture's problem set, helps define its context and defines the level of detail required for
the architectural content. While many architecture development efforts are similar in their
approach, each effort is also unique in that the desired results or effect may be quite
different. As an example, system development efforts generally focus first on process
change, and then concentrate on those automated functions supporting work processes or
activities. In addition to understanding the process, discovery of these 'system functions' is
important in deciding how to proceed with development or purchase of automation support.
Information collected for Architectural Descriptions describing services is similar to
information collected for Architectural Descriptions describing systems. For describing
services, Architectural Description will collect additional information concerning subscriptions,
directory services, distribution channels within the organization, and supporting
systems/communications web requirements.
Similar situations occur with Architectural Description development for joint operations. Joint
capabilities are defined processes with expected results, and expected execution capability
dates. The Architectural Descriptions supporting the development of these types of
capabilities usually require the reuse of data already established by the military services and
agencies, analyzed, and configured into a new or updated process that provides the desired
capability. Included are the processes needed for military service and/or agency response,
needed automation support, and a clear definition of both desired result and supporting
performance measures (metrics). These types of data are presented in models.
The important concept for this step is the clarity of scope of effort defined for the project
that enables an expected result. Broad scoping or unclear definition of the problem can delay
or prevent success. The process owner has the primary responsibility for ensuring that the
scoping is correct, and that the project can be successfully completed.
Clarity of scope can better be determined by defining and describing the data to be used in
the proposed Architectural Description in advance of the creation of views that present