Your SlideShare is downloading. ×
0
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Click here to download Chris Fornecker's Presentation
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Click here to download Chris Fornecker's Presentation

314

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
314
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Tom or Cory
  • Transcript

    • 1. SOA Building Blocks – Civilian Case Studies Chris Fornecker CTO, General Services Administration
    • 2. Summary <ul><li>We are in EARLY stages of SOA implementation </li></ul><ul><li>Activities </li></ul><ul><ul><li>Enterprise Architecture Methodology </li></ul></ul><ul><ul><li>IT System Procurement changes </li></ul></ul><ul><ul><ul><li>Financial Management </li></ul></ul></ul><ul><ul><li>Organizational Changes </li></ul></ul>
    • 3. The “One GSA” EA Methodology <ul><li>Value Chain Analysis </li></ul>Model Driven Architecture On Service Oriented Architecture = E xecutable EA + Driving toward a repeatable process
    • 4. Value Chain <ul><li>An enterprise wide collaboration model that aligns processes and activities with respect to value generation for GSA customers </li></ul><ul><ul><li>Business process from a customer’s point of view – or, a supply chain as viewed by customer. </li></ul></ul><ul><ul><li>Not a new concept: Charles Porter 1985 </li></ul></ul>Emphasizes cross organizational horizontal activity flows vice vertical, organization centric, functional decomposition
    • 5. OneGSA Generic Value Chain Structure OneGSA Acquisition VC Policy VC Finance VC Marketing VC HR VC IT VC Mission Critical VC Customer Or Citizen Supplier
    • 6. Model Driven Architecture (MDA) <ul><li>A model is a description of a system written in a well-defined language that has formal grammar and syntax, suitable for automated interpretation by a computer. </li></ul><ul><ul><li>Example: building blueprint in a computer aided design tool </li></ul></ul><ul><li>MDA is a n open standards and vendor neutral framework that formally links business models to application implementation models. </li></ul><ul><ul><li>MDA information at: omg.org </li></ul></ul><ul><li>Manage enterprise focused business models </li></ul><ul><li>Technology independent </li></ul><ul><li>Consistent with industry direction to focus on services </li></ul>
    • 7. Holy Grail: Model-To-Integrate, aka Executable Architecture <ul><li>Business processes are configuration managed in formal models </li></ul><ul><li>Changes can be provisioned automatically from design-time to run-time systems </li></ul><ul><ul><li>Automated transformation only possible if processes are captured in formal models. </li></ul></ul><ul><li>The ability to convert high level business processes to executable code greatly increases agility and value proposition of Enterprise Architecture </li></ul><ul><li>Very disruptive: changes the way we think about application development and acquisition </li></ul>Not implying that EA projects are responsible for developing code – but that we should enable the timely implementation of architecture driven changes
    • 8. Enterprise Components in SOA <ul><li>Enterprise Components must be independent & loosely coupled </li></ul><ul><li>While being able to interoperate with each other using services </li></ul><ul><li>Making the information system a lattice of cooperating components </li></ul><ul><li>Simulated or real </li></ul><ul><li>Representing both business and technology components </li></ul><ul><li>Driven from the business model </li></ul><ul><li>Providing an “Enterprise service bus” using a services oriented architecture </li></ul>One-GSA Target Model Funds Management Contracting Solution Provider Customer Roles
    • 9. High-level role identification Customer Contracting Industry Partner Business Planning Customer Liaison Account Management User Customer Finance Offering Line Management Offering Management Customer Strategy Project Management Customer Care Accounting Customer Contact Funds Management Contracting Solution Provider Source Selection Authority Technical Management Small Business Specialist Legal Officer Administrative Support Customer Program Management Agency Customer GSA Industry Partner Contracting Team
    • 10. EA and Org Design - Role Composition Organization Position Role Legend GSA PBS FTS FSS Mid-Atlantic Region Real Estate Specialist Solution Provider Contracting Office of the Administrator Commissioner IT Solutions Customer Service Rep Solutions Provider Vehicle Acquisition & Leasing Fleet Service Rep Solution Provider Contracting Project Manager
    • 11. Using EA to define a Shared Service Specification <ul><li>Role and Activities define service responsibilities </li></ul><ul><ul><li>Map to Job Descriptions </li></ul></ul><ul><li>Boundaries are service interfaces </li></ul><ul><ul><li>Map to Software Component Interfaces </li></ul></ul><ul><li>The role, activity and interface choreography are required for ‘Architected’ Enterprise Solutions </li></ul><ul><ul><li>Example shown is ‘contract writing’ </li></ul></ul>GSA Solution Provider Contracting Customer Liaison (IAE) Issue Synopsis Evaluate Responses Issue Award Monitor Performance Post Combined Synopsis Solicitation Process IVL Modify Synopsis Amend Combined Synopsis Develop Criteria Plan Build Solicitation Pre-solicitation contact with potential offerers Issue Solicitation Solicitation Inquiries Amend Solicitation Respond to Solicitation Protest Issue Refreshed Solicitation
    • 12. Collaborations contextualize Roles
    • 13. Roles Choreography Value Chain Activities
    • 14. Inner Roles Specify Service Granularity
    • 15. Essential Change to Systems Acquisition driven by SOA concepts Order & Requirements Fund/Contract Solution Order & Requirements Solution Component Architecture Reuse Library Compose Test Contractor Design Implement Test Current Strategic Standards based models are what’s new! Not the same Case Tools or Component Based Architecture Reuse story… Component Requirements Component Requirements Component Requirements Component Component Build/adapt Components Fund/Contract Fund/Contract Fund/Contract Reuse
    • 16. Financial Management Discipline Legacy mainframe replacement Receivables Accounting Funds Management Payables Accounting Asset Accounting Financial Planning General Ledger Cost Allocation Cash Management
    • 17. Receivables Accounting Enterprise Component Provided protocols (services) Initiated protocols (services)
    • 18. Receivables Accounting Work Components
    • 19. Organizational Changes <ul><li>The Public Building Service CIO has already created a division dedicated to developing and managing business processes. </li></ul><ul><li>The newly proposed Federal Acquisition Service (former Federal Supply Service and Federal Technology Service) CIO includes a dedicated business analysts/process division </li></ul>
    • 20. Summary <ul><li>SOA strategic direction influenced Architecture Methodology </li></ul><ul><ul><li>Strong relationship between business roles and services </li></ul></ul><ul><ul><ul><li>Provide Traceability between Business and System Models </li></ul></ul></ul><ul><ul><li>USE of MDA compliant Enterprise Collaboration Architecture helps visualize role relationships while storing in a standard way. </li></ul></ul><ul><li>SOA changing the way we think about IT acquisition strategies </li></ul><ul><ul><li>Component/Service based vice monolithic COTs </li></ul></ul><ul><li>Organization adapting to greater emphasis on business process analysis </li></ul><ul><ul><li>Enables linkage of IT services to the business </li></ul></ul>
    • 21. Thank You <ul><li>Chris Fornecker </li></ul><ul><ul><li>GSA CTO </li></ul></ul><ul><ul><li>202.219.3393 </li></ul></ul><ul><ul><li>[email_address] </li></ul></ul><ul><li>George Thomas </li></ul><ul><ul><li>GSA Chief Architect </li></ul></ul><ul><ul><li>202.219.1979 </li></ul></ul><ul><ul><li>[email_address] </li></ul></ul>

    ×