RDCU-02C 64607901F RDCU02C 逆变器控制板

RDCU-02C 64607901F RDCU02C 逆变器控制板 

、6步架构开发过程为架构师提供了指导
以及架构描述开发团队，并强调指导原则。这个
流程以数据为中心，而不是以产品为中心（例如，它强调对数据的关注，以及
数据之间的关系，而不是DoDAF V1.0或V1.5产品）。这
以数据为中心的方法确保了体系结构描述中视图之间的一致性
同时确保捕获所有基本数据关系，以支持各种
分析任务。架构开发过程中创建的视图
提供底层建筑数据的视觉效果图，并传达以下信息：
特定用户社区或决策所需的体系结构描述的兴趣
制造商。上图描述了这一6步过程。
出身背景
建筑发展
元模
观点和模型
展示技巧
配置管理
概述
缩略语列表和词汇表
术语
网站地图
档案
国防部
11
DoDAF体系结构开发-6步流程
http://cio-nii.defense.gov/sites/dodaf20/arch_development.html[2011年3月3日下午3:33:54]
注：重要的是要注意，体系结构描述的开发是
迭代过程是一个独特的过程，因为每个体系结构描述都是：
不同之处在于，架构创建服务于特定的目的，并且是从
这是一个特别的观点。
服务于不同的需求，需要不同类型的视图来表示
收集的数据。
代表“即时快照”（例如，架构描述可以
表示当前视图或基线，也可以表示某些
未来时间）。
随着时间的推移，随着需求变得更加集中或附加知识而变化
关于过程或需求的信息变得已知。
以下描述的方法旨在涵盖尽可能广泛的一组：
环境，以及关注架构中常用的步骤
社区
步骤1：确定架构的预期用途。定义目的和预期用途
架构（“适合用途”）；架构描述工作将如何进行
进行；架构开发中使用的方法；数据类别
需要；对其他人的潜在影响；以及这项努力取得成功的过程
根据绩效和客户满意度进行衡量。这个信息是
通常由流程所有者提供，以支持架构开发，描述
其职责范围的某些方面（过程、活动等）。
用于收集与项目目的和范围相关的信息的模板
体系结构描述、术语表和其他信息已经为
在DARS中注册该数据。
步骤2：确定架构的范围。范围定义了以下边界：
确定架构描述的深度和广度，并确定
架构的问题集，有助于定义其上下文，并定义所需的详细级别
建筑内容。尽管许多体系结构开发工作在其
方法，每项努力都是独特的，因为预期的结果或效果可能相当
不同的例如，系统开发工作通常首先关注流程
改变，然后专注于支持工作流程的自动化功能，或
活动。除了了解过程之外，这些“系统功能”的发现是
在决定如何继续开发或购买自动化支持时非常重要。

RDCU-02C 64607901F RDCU02C 逆变器控制板 

RDCU-02C 64607901F RDCU02C 逆变器控制板 

The high-level, 6-step architecture development process provides guidance to the architect
and Architectural Description development team and emphasizes the guiding principles. The
process is data-centric rather than product-centric (e.g., it emphasizes focus on data, and
relationships among and between data, rather than DoDAF V1.0 or V1.5 products). This
data-centric approach ensures concordance between views in the Architectural Description
while ensuring that all essential data relationships are captured to support a wide variety of
analysis tasks. The views created as a result of the architecture development process
provide visual renderings of the underlying architectural data and convey information of
interest from the Architectural Description needed by specific user communities or decision
makers. The figure above depicts this 6-step process.
Background
Architecture Development
Meta Model
Viewpoints & Models
Presentation Techniques
Configuration Management
Overview
Acronyms List and Glossary
of Terms
Site Map
Archives
Department of Defense
11
DoDAF Architecture Development - 6 Step Process
http://cio-nii.defense.gov/sites/dodaf20/arch_development.html[3/3/2011 3:33:54 PM]
NOTE: 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.