Larry L. Johnson [email protected] Federal Transition Framework.

19
Larry L. Johnson [email protected] Federal Transition Framework

Transcript of Larry L. Johnson [email protected] Federal Transition Framework.

Page 1: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

Larry L. [email protected]

Federal Transition Framework

Page 2: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

2Event

Place – Date

Introduction

The Federal Transition Framework (FTF) is a single information source for cross-agency information technology (IT) initiatives using a simple, familiar and organized structure. It contains government-wide IT policy objectives and cross-agency initiatives including: OMB-sponsored initiatives, e.g., E-Gov and LoB

initiatives Government-wide initiatives, e.g., Internet Protocol

Version 6 (IPV6), Homeland Security Presidential Directive 12 (HSPD 12)

Page 3: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

3Event

Place – Date

Why is the FTF Important?

Information published in the FTF Catalog is provided to support the following goals: Increase the alignment of agency enterprise

architecture with federal IT policy decisions or other forms of official guidance

Increase sharing and reuse of common, cross-agency business processes, service components and technology standards

Increase collaboration through agency participation in cross-agency communities of practice

Page 4: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

4Event

Place – Date

What are the Benefits of the FTF?

There are a number of benefits from the FTF, both for agencies and government-wide. Agencies can: Receive more consistent, complete and detailed information about

cross-agency initiatives more quickly to inform their EA, capital planning and implementation activities

Use cross-agency initiative information to make better decisions about their IT investments

Improve the effectiveness and efficiency of IT investments to realize service improvements and cost savings

The Federal Government can: Communicate more consistent, complete and detailed information

about cross-agency initiatives more efficiently Increase the level and speed of adoption of cross-agency initiatives Improve the overall effectiveness and efficiency of IT investments

related to cross-agency initiatives

Page 5: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

5Event

Place – Date

How is the FTF Used?

The FTF Catalog is used to provide information to agency decision makers in support of cross-agency initiative implementation, and to provide guidance to working groups developing cross-agency initiative architectures.

A major release of the FTF Catalog is published each year with the OMB EA Assessment Framework. Publication of the FTF Catalog is the first step in a three-step process to simplify the packaging and dissemination of information describing cross-agency IT initiatives.

Page 6: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

6Event

Place – Date

The FTF Process

Page 7: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

7Event

Place – Date

The FTF Process (2)

Step 1 The FTF Catalog is published in September of the current year (CY) with the latest version of the OMB EA Assessment Framework. The catalog describes cross-agency initiatives required to be included as an element of agency enterprise architecture.

Step 2 Agency EA self-assessments are submitted to OMB to be reviewed and assessed in March (CY+1). Submission packages include enterprise architecture work products and an EA Transition Strategy including mandatory cross-agency initiatives related to the agency mission.

Step 3 Agency budget submissions are submitted to the Office of Management and Budget (OMB) in September (CY+1). Budget submissions are verified to ensure they reflect the agency EA Transition Strategy including relevant cross-agency initiatives.

Page 8: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

8Event

Place – Date

Evolution to Model Driven Architecture

The original FTF started as a handcrafted XML Schema

To make it more accessible and understandable, a UML model was derived from the XML Schema

The FEA PMO brought the work to the OMG for transition to the OMG’s MDA and maintenance under the OMG’s open, voluntary consensus process

Page 9: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

9Event

Place – Date

OMB/OMG Collaboration

“The FEA PMO is working with the Object Management Group (OMG), a voluntary consensus standards body, to implement further refinements to the FTF Metamodel, including both UML and XML Schema representations. This is being performed through the OMG Government Domain Task Force (GovDTF) and has established the Federal Transition Framework Metamodel Working Group. Participation in the FTF Metamodel Working Group is welcomed. For further information, please visithttp://gov.omg.org/gov-wg-usgov-ftf.htm.”

Federal Transition Framework Metamodel Reference, Version 1.0 December 2006, page 4

Page 10: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

10Event

Place – Date

OMG/Government Process in a Nutshell

RFP – Request for ProposalRFP – Request for Proposal Requirements are captured by Government Domain Task Force (GovDTF) participants

drawn from Government, Industry, Vendors, and Academia. Submission

Outside the OMG Process submission teams write a specification meeting the RFP Requirements.

The submission team must have vendors who have filed a Letter of Intent to build to the specification if it is approved.

GovDTF Approval A vote is taken to select a submission and recommend it for adoption

OMG Architecture Board (AB) Both the RFP and the Submission are vetted by the AB for conformance with MDA

principals and completeness. Domain Technology Committee

Members of the DTC vote on recommending the submission for adoption based on the recommendation of the GovDTF and AB.

Board of Directors After validating that implementation plans are in place the Board votes to adopt the

specification Revision Task Force

There is always a Revision Task Force seated to address any residual errors in the specification discovered during implementation.

Page 11: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

11Event

Place – Date

From Pictures to a Platform Independent Model to a Platform Specific Model

The original FTF UML model that was rendered in a drawing tool, was entered into an MDA Tool.

The submission team refined the model in weekly “screen share” teleconferences.

The MDA Tool was then used to automatically generate the XML Schema as a Platform Specific Model

The UML model is now the master, and the XML Schema an automatically rendered derivative.

Page 12: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

12Event

Place – Date

Model Driven Architecture

Page 13: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

13Event

Place – Date

MDA Mapping

Provides specifications for transformation of a PIM into a PSM for a particular platform.

These are built into the MDA Tool.

Page 14: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

14Event

Place – Date

MDA Tools Support Multiple Languages

Page 15: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

15Event

Place – Date

Expanding the Effective Budget

FTF Submission Team Included: Government Contributors

Office of Management and Budget Social Security Administration National Archives Treasury

Industry Contributors Adaptive Everware CBDI MEGA International Telelogic AB TethersEnd Consulting Troux Technologies

Page 16: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

16Event

Place – Date

FTF Finalization Task Force (the FTF FTF)Continued Maintenance

FTF FTF Membership Government Participants

OMB/Vangent US Dept of Treasury National Archives

Industry Participants Adaptive Everware-CBD Mega International Model Driven Solutions RedHat Telelogic TethersEnd Consulting Troux Technologies

Finalization Task Force is the first Revision Task Force.

There is always a Revision Task Force seated to address any mistakes or ambiguities in the specification discovered in the course of implementation.

Life-cycle Management of a specification is built into the OMG Process.

Page 17: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

17Event

Place – Date

Benefits of the OMB/OMG Collaboration

Open Collaboration in a Pre-competitive Environment As an open, voluntary, consensus based organization, the

OMG provides a forum in which government personnel can work with Industry, Vendors and Academia to discuss government requirements for specifications in a pre-competitive environment outside of any procurement.

Effective Expansion of Budget In working with OMG members, the OMB could avail itself of

industry experts to apply to the task at no cost beyond their own participation.

Life-cycle Maintenance The OMG has a built in process for maintaining a

specification over its life time, providing further cost leverage through the efforts of OMG Membership.

Page 18: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

18Event

Place – Date

Going Forward

The OMB and OMG are in the process of forging an OMB/OMG Collaboration Agenda.

Other work items are under consideration for execution under the OMG Community Process and Model Driven Architecture.

Page 19: Larry L. Johnson Larry.Johnson@TethersEnd.com Federal Transition Framework.

19Event

Place – Date

Resources

EGov Federal Transition Frameworkhttp://www.whitehouse.gov/omb/egov/a-2-EAFTF.html

Object Management Grouphttp://www.omg.org/

OMG Government Domain Task Forcehttp://gov.omg.org/