Your SlideShare is downloading. ×

Agile Adaptive Architectures


Published on

Mr. Dennis E. Wisnosky is the Chief Architect and Chief Technical Officer (CTO) of the Department of Defense (DOD) Business Mission Area within the office of the Deputy Under Secretary of Defense for …

Mr. Dennis E. Wisnosky is the Chief Architect and Chief Technical Officer (CTO) of the Department of Defense (DOD) Business Mission Area within the office of the Deputy Under Secretary of Defense for Business Transformation. As Chief Architect and CTO, Mr. Wisnosky is responsible for providing expert guidance and oversight in the design, development, and modification of the federated architectures supporting the Department's Business Mission Area.

Published in: Business, Technology
1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide
  • Transcript

    • 1. Welcome! Transformation and Innovation October 30, 2007 Breakfast Briefing “ Agile Adaptive Architectures”
    • 2. About the Workflow Management Coalition
      • Member-Based Non-Profit Consortium Focused on Business Process Interchange , and the Promotion of Open Architectures in Business Process Management
      • Founded in 1993, is the Longest Standing Standards Body in the BPM Software Sector
      • The ONLY Standards Body Focused Exclusively on Business Process Management
      • Approximately 300 Members Across Software, Financial Services, Healthcare, Government, Telecom, IT Services and Other Industries
    • 3.
      • Promotes Industry Understanding of BPM via Research, Publications, Awards, as well as Education and Training
      • Responsible for the Creation and Continued Development of Two Leading BPM Standards: XPDL and Wf-XML
      • Members Represent Key Contributors to Other Standards Including BPEL , BPMN , ASAP
      About the Workflow Management Coalition
    • 4.
      • XPDL is the Most Implemented Open Process Definition Format
      • Used in Over 70 Independent Software Products (BPM, ERP, EA, ECM)
      • Promoted by Various Governmental and Governance Bodies as Required Standard for New BPM Implementations
      • Provides Today the Only Standard Serialization for BPMN Process Models
      Standards Work by the WfMC
    • 5. WfMC’s Online XPDL Resource Center
      • Currently a Hidden Site Only Accessible by Members and Participants in this Seminar
      • Access Tools including XPDL Schema, Specification Documents, Sample Process Models, and a Downloadable XPDL and BPMN Modeling Tool
      • Training Tools Include White Paper, Slides, and Coming Soon: Online Learning Modules, Testing and Certification, as well as Online XPDL Code Validation
    • 6. WfMC DC Area Chapter
      • Focused on the Role of Workflow and Business Process Management Within Federal Enterprise Architecture Initiatives
      • SIGs Dedicated to Federal Government, Security and Defense, State and Local Government, and Non-Profit/NGOs
      • Members-Only Access to Research, Private Networking Events, Training & Certification
      • 2-Day Conference April 22-23, 2008 at Transformation and Innovation 2008
    • 7. Today’s Agenda
      • “ A RESTful WfXML: User-Centric Resource Oriented Architecture (ROA) Approach” Pat G. Cappelaere, Open Geospatial Consortium & WfMC
      • "Overcoming Momentum! Enterprise Business Transformation and Agile Adaptive Architectures" Dennis E. Wisnosky, BMA CTO, Chief Architect
      • "Putting Your EA to Work” Ervin Reeves, Founder, EntArch; Senior Enterprise Architect, Office of the CIO, NHTSA
      • Fred Ackerman Appian, Vice President, Federal Business Unit
    • 8. Dennis E. Wisnosky Chief Technical Officer Department of Defense Business Mission Area
      • Pioneer in distributed computing and federated computing architectures; named by Fortune Magazine one of the Seven Heroes of Manufacturing
      • Provides expert guidance and oversight in the design, development, and modification of federated architectures supporting the Department's Business Mission Area
      • Oversees the DOD Business Enterprise Architecture (BEA)
      • Ensures federated architectures of the BMA fully support the Department's vision, mission, strategy and priorities for Business Transformation
      • Verifies the BEA and component architectures remain consistent and compliant with the Federal Enterprise Architecture (FEA)
      • Recognized as a creator of the Integrated Definition (IDEFs) language , the standard for modeling and analysis in management and business improvement efforts
      • Author of several books including DoDAF Wizdom the decisive source within DoD and other government organizations for managing enterprise architecture projects
    • 9. Enterprise Business Transformation Dennis E. Wisnosky BMA – CTO, Chief Architect Overcoming Momentum! “ Agile Adaptive Architectures”
    • 10. Reach of the Business Mission Area This includes Iraq! "The Secretary of Defense is responsible for a half-trillion dollar enterprise that is roughly an order of magnitude larger than any commercial corporation that has ever existed. DoD estimates that business support activities—the Defense Agencies and the business support operations within the Military Departments—comprise 53% of the DoD enterprise.”
    • 11. Iraq Task Force Background
      • Deputy Secretary of Defense memo creating Task Force
      • Task Force Mission: Evaluate DoD business enterprise processes and associated systems in Iraq affecting contracting, logistics, fund distribution, financial management and align to the theater commanders goals for reconstruction and economic development.
    • 12. The Business Mission Area (BMA) Within the BMA Paul A. Brinkley Deputy Under Secretary of Defense for Business Transformation DoD Mission Areas - Top Down View War Fighting Mission Area Business Mission Area Intelligence Mission Area Enterprise Information Environment Mission Area
    • 13. “ We are focused on change and driven by our responsibility and accountability to the men and women of our Armed Forces who protect this great nation.” DEPUTY SECRETARY OF DEFENSE GORDON R. ENGLAND SEPTEMBER 16, 2005 The BTA is the primary change agent for the BMA
    • 14. How the BTA Works - Goals to Capabilities Enterprise Architecture Process Architecture (OVs) Information Architecture (SVs) Solution Architecture ( Tiered Accountability/ Federation) Technical Architecture (TVs) Goals, Objectives, and Priorities Enterprise Transition Plan Business Mission Area OSD Goals Component Goals IRB DBSMC Capabilities Delivered to the Warfighter BTA/DBSAE builds and delivers OSD Systems DISA provides Infrastructure BTA builds architecture and transition plan the Business Transformation Agency (BTA)
    • 15. “ Super Size Me” – Not a Healthy Go Forward Strategy
      • Federated Architectures/not Integrated Architectures
      • Platoon Sized Teams/not Battalions
      • Commodity Based Service Level Agreements/not Perpetual Annuity Contracts
      • Services Delivering Capabilities/not Systems Named by Marketing Departments
      • “ Breaking up is hard to do”
      The Details Follow!
    • 16. Federated Architectures Not Integrated Architectures Capabilities and Systems Program System Functions { } Federated Enterprise Architecture We are Underway! Component EAs Program Architectures Typical Mission Area Enterprise Architecture Content Enterprise Info. Exchange Reqs Enterprise Operational Activities Enterprise Business Rules Enterprise Processes Enterprise Structural Business Rules Enterprise Data (Objects, Entities and Attributes) Enterprise System Functions Enterprise Initiatives Enterprise Level Governance Operational View Federation Implemented Capabilities and Systems Army Operational Activities Navy Operational Activities Air Force Operational Activities Other Component Operational Activities Army Enterprise Processes Navy Enterprise Processes Air Force Enterprise Processes Other Component Enterprise Processes Army Logical Data Structure Navy Logical Data Structure Air Force Logical Data Structure Other Component Logical Data Structure Army Initiatives and System Functions Navy Initiatives and System Functions Air Force Initiatives and System Functions Other Component Initiatives and System Functions Program Operational Activities E I E S e r v i c e s f o r R e g i s t e r i n g , D i s c o v e r i n g & U t i l i z i n g A r c h i t e c t u r e D a t a E I E S e r v i c e s f o r R e g i s t e r i n g , D i s c o v e r i n g & U t i l i z i n g A r c h i t e c t u r e D a t a { } Implemented Capabilities and Systems Program Processes { } Implemented Capabilities and Systems Program Data { } Implemented Systems View Federation Systems View Federation
    • 17. DoD Architecture Federation:
      • BMA Federation:
      • Linking BMA Architectures to the Business Enterprise Architecture (BEA)
      • Sharing functions and applications across the organization as discrete, reusable, business-oriented services
      Expand upon the DoD GIG Architecture Federation Strategy and Net-Centricity Global Information Grid (GIG) Architecture Federation Strategy v1.2, August 2007
    • 18.
      • Work within DoD Federated Architecture Framework
      • Work within SOA Standards
      • Deliver Capabilities not Systems
      • Deliver Capabilities in months not years
      Platoon Sized Teams/Not Battalions There is Evidence that this is better!
    • 19. Software Project Success Depends Upon Its Size Source: Capers Jones 8% 7% 6% 3% 1% 89% 80% 60% 23% 15% 2% 8% 17% 35% 36% 1% 5% 17% 39% 48% 10 100 1,000 10,000 100,000 Projects Completed Early Project Completed On Time Projects Completed Late Projects Cancelled Project Function Points
    • 20. Commodity Based Service Level Agreements/Not Perpetual Annuity Contracts
      • Market place adjusted service boundaries/ interfaces.
      Agile Adaptive Architectures bring this about!
    • 21. Agile Adaptive Architectures Adapted from: Rouse, W.B. (2003). Engineering complex systems: Implications for research in systems engineering. IEEE Transactions on Systems, Man, and Cybernetics – Part C , 33 (2), 154-156. Self Organization Organizational Design Design Heterarchy Hierarchy Network Personal Commitments Contracts Relationships Agility Efficiency Focus Capability Outcomes Processes Measurement Incentives & Inhibitions Command & Control Methods Leadership Management Roles Agile Adaptive Architectures Enforce: Traditional Architectures Enforce:
    • 22. “ Services Delivering Capabilities, not Systems Named by Marketing Departments” Nope! Yep! This is Happening Now!
    • 23. Example Services DBSAE Business Services:
        • Central Contractor Registry (CCR)
        • Online Reps and Certs Application (ORCA)
        • Electronic Document Access (EDA)
      Near Term Potential DBSAE Business Services:
        • Federal Procurement Data System – Next Generation (FPDS-NG)
        • Inter-Government fund Transfer (IGT)
        • Defense Travel System (DTS) Per Diem Table
    • 24. “ Breaking up is hard to do”
      • Loyalty vs. Utility over time
      • Program performance level measured in a way that fosters fortressing against progressive change
      • We get used to flaws and shortcomings
      Throw out the Legacy Systems
    • 25. Back in My Home Town F
    • 26. Questions???