Notes
Outline
Architecture Modeling and Repository Tools
Assessment Criteria and Approach
10/5/2002
Outline
Purpose and Scope
Definitions
Uses of a FEA Tool Set
Tool Users Categories
Tool Users Characteristics
Tools Assessment Criteria
Tools Assessment Approach
Summary and Conclusions
Purpose
Scope: Architecture Tools
Scope
Modeling and Repository Tools Criteria Working Sub-Group responsible for setting:
Tool assessment criteria
Tool assessment approach
Tool criteria and approach cover
Modeling tools for producing architecture work products, and
Repository tools that store architecture elements and work products
EA Documentation Environment
Definition — Enterprise Architecture (EA)*
An EA is an explicit description and documentation of current and desired relationships among business and management processes and information technology
Definition — Enterprise Architecture (EA)*
The EA will define
Principles and goals and
Set direction on
promotion of interoperability,
open systems,
public access,
compliance with GPEA,
end user satisfaction, and
IT security
Definition — General Uses of an Enterprise Architecture (EA)* and an EA Tool Set
An Enterprise Architecture:
Is the basis for decision making and planning
Governs the identification, selection, and development of standards
Is the mechanism for managing change within the enterprise
Enables effective communication about the enterprise
Therefore, an EA tool set must help:
Organize, integrate, and roll-up architecture information
Identify standards and associate them with architecture information
Include capabilities for configuration and change management
Serve as a centralized repository to effect communication
Definition — Federal Enterprise Architecture (FEA)*
FEA [is] a business-based framework for Government-wide improvement
The FEA is being constructed through a collection of interrelated "reference models" designed to facilitate cross-agency analysis and the identification of duplicative investments, gaps, and opportunities for collaboration within and across Federal Agencies. These models are defined as:
Business Reference Model (BRM)
Performance Reference Model (PRM)
Data and Information Reference Model (DRM)
Application Capability Reference Model (ARM)
Technical Reference Model (TRM)
Definition — General Uses of a Federal Enterprise Architecture* and a FEA Tool Set
The FEA is being constructed to facilitate:
Cross-agency analysis
Identification of duplicative investments and gaps
Identification of opportunities for collaboration within and across federal agencies
Therefore a FEA tool set must help:
Organize, integrate, and roll-up architecture information across-agencies
Identify IT systems and standards and associate them with architecture information
Include capabilities for configuration and change management
Serve as a centralized repository to effect communication
Uses of a FEA Tool Set
Facilitate identifying, organizing, and disseminating
The enterprise vision
The business processes and business functions
Facilitate integrating architecture development within the enterprise
Facilitate collaboration, information sharing, and information reuse
Provide decision makers with better, more consistent information and tools
Facilitate linking important program milestones and resource decisions to architecture activities
Tool Users Categories
Architecture Designers and Developers: Require direct support through modeling, modeling standards, and customization capabilities
Enterprise Architects: Need to maintain, update, and oversee the architectural elements and work products across the enterprise
Planners, Stakeholders, and Management: Need to run analysis, obtain guidance, and evaluate baseline and current models
Browsers: Need specific views and perspectives of the architecture via technologies such as the web
Tool Users Characteristics
May be in several locations
Have a variety of platforms
Require numerous mechanisms to access the information
from viewing relatively static information on web pages
to interactive access to components and relationships