Journey of a SOA Service Definer

1
Journey of a SOA Service Definer

• Serving the Present, Intercepting the Future

Dr. Michael J. Kurtz Assistant Archivist, Office
of Records Services, Washington DC National
Archives Records Administration
2
The National Archives and Records Administration

• Our mission is to
• Safeguard and preserve the records of our
  Government
• Establish principles, policies, and
  responsibilities for Records Management
  throughout the Federal Government
• And to help Government agencies achieve effective
  Records Management!

3
eGovernment Initiative Portfolios

• E-Training
• Recruitment One-Stop
• Enterprise HR Integration
• E-Clearance
• E-Records Management
• E-Payroll
• E-Gov Travel
• Integrated Acquisition Environment

• Government to Citizen
• Government to Business
• Internal Efficiency Effectiveness
• Government to Government

4
Context of Presentation

• Not about Records Management, per se.
• Just one example
• More about our experiences and lessons learned in
  Service Definition
• Precision,
• Technology Independent
• Simultaneously well defined, yet pliable.
• Services that can
• Deploy to environments today
• Deploy to SOA environments tomorrow
• Evolve over time.

Simultaneously well defined, yet pliable and
formable to unanticipated environments.
5
Overview of Journeys Start

• NARA undertook RMS Definition
• For Todays and Tomorrows Environments.
• Future of Federal Architectures is SOA, but
• Federal SOA not yet here but steadily emerging
• Agencies each define own EA thereby assuring
  diversity
• SOA will evolve in concept as well as deployment
• RMS Community of Practice (CoP)
• Formed under leadership of NARA
• Began as 18 Federal Agencies facilitated by NARA
• Focused on defining functional requirements

6
and End

• RMS CoP employed Model Driven Architecture (MDA)
  
• For Platform Independent Service Definition
• For mapping Service Definition to specific
  technology
• To assure interoperability and consistency
• Service Definition is only part of the solution
• Optimal ROI requires effective business processes
• Thus Records Management Maturity Model is born

7
In the Beginning NARA and Others Realized

• Electronic records are a reality
• Impacts almost all technology acquisitions
• RM Business Practices are diverse
• Many Current Systems
• Do not formally identify RM functions
• but are performing them nonetheless
• and are not interoperable.

• The National Archives and Records Administration
  recognized this is a reality within government
  today and into tomorrow and plotted a course to
  the future.

8
The Target Federal Service Oriented Architecture

• In June 2008 the Architecture and Infrastructure
  Committee of the Federal CIO Council in
  collaboration with The American Council for
  Technology / Industry Advisory Councils
  Enterprise Architecture Shared Interest Group
  published v1.1 of
• A Practical Guide to FederalService Oriented
  Architecture

9
The Nature of the Target Architecture
From the Practical Guide For Federal SOA
FederalServiceOrientedArchitecture

• Forward Looking
• Envisioning emerging SOA related best practices
  and technologies, and then
• Imagining an organization that has fully
  embraced and adopted the service oriented model.
  

10
Service Definers Dilemma

• How do you define a service that can be
  provisioned to an environment definition that is
• Forward Looking
• Envisioned
• Emerging
• Imagined
• Different depending on any agencys particular
  Technology Platform

11
The Target Architecture
From the Practical Guide For Federal SOA
Cant Change
Can Change
Cant Change
Provide me the serenity to accept things I can't
change, the courage to change the things I can
and the wisdom to know the difference.
SOA Serenity
12
Our Starting Place

• In the longer term
• Standards will emerge for SOA Infrastructure
• Enterprise Service Buses,
• Service Registries,
• etc.
• But we cant wait for that
• In the short term
• The target environment is not well defined so
  start by
• bringing in the experts
• focus on the business requirements

13
RMS Interagency Project Team Participating
Agencies
14
RMS IPT Issued their Final Report September 7,
2006

• Report Contains
• Functional Requirements Only
• UML Representations
• Now What?!
• Advance availability and interoperability of RMS
  Tools
• Advance RM Maturity

15
Functional Requirements Done.Now What?

• CoP initiated two key OMG standards
• RM Service specification using OMGs Model Driven
  Architecture to assure
• consistent behavior,
• interoperability,
• uniform semantics, and
• data exchange
• Records Management Maturity Model to
• enable assessment,
• gap analysis, and
• facilitate optimal RM processes

16
Model Driven Architecture
AutoMagical Transformation (Built into the MDA
Tooling)

• Platform Independent Model (PIM) for Composable
  Services
• Service Contract exact definition of available
  operations
• Information Sharing common semantics
• The Hard Part!
• Automated Transformation for Provisioning
  Agility!
• Platform Specific Model (PSM) for binds to Target
  Environment

Contract
Fulfillment
17
One PIM Maps to Multiple PSMs
YadaYada
C
DotNet
JAVA
Platform Independent Model Based on Business
Requirements
WSDL
Platform Specific Models Based on Technology
18
Business Process Maturity Its the Business
Process !

• For SOA Success
• Must support Business Process point of view
• Dont automate failure!
• Mature Processes facilitate Service Definition

No matter how great the hammer is, it doesnt
work well if you dont know how to use it
properly.
19
Keys to RMS Success

• RM Community of Practice
• Model Driven Architecture
• Records Management Maturity Model (RM3)

20
Not the end of the Journey
Were really not at the end of a journey, but on
a course of continuous process and technological
improvement.
21
The old way Records Management as an Application

• The application through which a record is
  captured, is different than the application used
  to generate it.
• Users must learn yet another application.
• The use of the application must be inserted in
  uncountable places in the business process.

22
The new way Records Management as an
environment, realized through SOA
23
Standards the Future

• RM Service and RM Maturity model are just the
  first two standards in this area
• Plan to establish further standards
• Extend RMS enabling RM in an integrated
  environment.

24
Imagine the Possibilities

• Auto-differentiation of records from non-records
  including email.
• Assure Legal and Legitimate Destruction.
• Auto-processing of records based on
• content
• context
• creator/receiver
• Allowing scalability and cost efficiency removing
  the burden from the user.

25
Its Not Just Government
yada yada yada
OSHA Part 1904
NY Stock Exchange Rule 440
Security Exchange Commission Rule 17a
EPA Clean Air Act 40 CFR Parts 61 and 63
Sarbanes Oxley
IRS Revenue Procedure 97-22
United Nations Model Law on Electronic Commerce
FDA Part 11
Records Management through SOA is an idea whose
time has come for everyone.
26
Questions?

• With Assistance of
• John Butler
• Larry Johnson