1 / 25
文档名称:

IBM Press - Development of Federal Enterprise Architecture Framework using the Rational Unified Process and the UML.pdf

格式:pdf   页数:25
下载后只包含 1 个 PDF 格式的文档,没有任何的图纸或源代码,查看文件列表

如果您已付费下载过本站文档,您可以点这里二次下载

IBM Press - Development of Federal Enterprise Architecture Framework using the Rational Unified Process and the UML.pdf

上传人:bolee65 2013/12/10 文件大小:0 KB

下载得到文件列表

IBM Press - Development of Federal Enterprise Architecture Framework using the Rational Unified Process and the UML.pdf

文档介绍

文档介绍:A technical discussion of FEAF using RUP and UML
05/20/03
Development of Federal
Enterprise Architecture
Framework using the IBM
Rational Unified Process
and the Unified Modeling
Language
Allen Sayles
Senior Systems & Software Engineer
Rational Brand Services
IBM Software Group
Development of Federal Enterprise Architecture Framework using the
Rational Unified Process and the UML
The IBM® Rational Unified Process® (RUP®) is uniquely qualified to support Enterprise Architecture (EA) efforts of
groups and agencies that are following the guidelines of the Federal Enterprise Architecture Framework (FEAF). The
Rational Unified Process can help customers essfully capture, manage, and use their Enterprise Architectures. In
this paper we will explore how RUP and the UML can be used to build and manage Enterprise Architectures.
Specifically, we will examine the FEAF level IV matrix to discuss how RUP facilitates capturing various FEAF models.
Background
The Clinger-Cohen Act of 1996 mandated that federal agencies develop and maintain an enterprise IT architecture in
order to promote information sharing anization among federal agencies. In 1999, The Federal Chief Information
Officers (CIO) responded to this mandate by establishing the Federal Enterprise Architecture Framework (FEAF)
uments/. The purpose of the FEAF is to establish an agency-wide roadmap to
achieve an agency’s mission through optimal performance of its core business processes within an efficient information
technology (IT) environment. Enterprise architectures (EAs) help agencies plish this; simply stated, they are
blueprints for systematically pletely defining anization’s current (baseline) or desired (target)
environment. EAs are essential for evolving information systems and developing new systems that optimize their
mission value. This is plished in logical or business terms (., mission, business functions, information flows,
and systems environments) a