slide1 n.
Skip this Video
Loading SlideShow in 5 Seconds..
June 3, 2004 MITRE, McLean, Virginia Emerging Technology Subcommittee, PowerPoint Presentation
Download Presentation
June 3, 2004 MITRE, McLean, Virginia Emerging Technology Subcommittee,

Loading in 2 Seconds...

play fullscreen
1 / 36
Download Presentation

June 3, 2004 MITRE, McLean, Virginia Emerging Technology Subcommittee, - PowerPoint PPT Presentation

Download Presentation

June 3, 2004 MITRE, McLean, Virginia Emerging Technology Subcommittee,

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Fourth Quarterly Emerging Technology Components Conference: An Emerging Public-Private Partnership at MITRE June 3, 2004 MITRE, McLean, Virginia Emerging Technology Subcommittee, Architecture & Infrastructure Committee, CIO Council

  2. Welcome • On behalf of: • The organizers of the Fourth Conference: • Susan Turnbull, GSA, Brand Niemann, EPA, Tony Stanco, George Washington University, and Rick Tucker, MITRE. • To all those who are presenting, participating, and assisting. • This is the first of what we hope will be a long-term relationship with MITRE! • Logistics: • MITRE escort is required outside the conference area and will be provided (e.g. lunch in the cafeteria, etc.)

  3. Overview • Title: • Emergence of a Distributed Services Grid: Realizing Multiplicative Returns when eGovernment Service Components Align in a Services-Oriented Architecture. • Purpose: • To Explore the Potentials and Realities of Realizing Enterprise Architecture through the Lessons of Communities Building the Grid.

  4. Overview • Key Questions: • How do the common "build" principles that power the Internet illumine the agile path from today's business process conversations to tomorrow's business process components? • How do semantic technologies lightly abstract and assemble shared meaning to sustain quality business conversations? • What distributed enterprise design tools accommodate the multiple forms of expertise that need to be expressed and integrated in agile business components within each Services life-cycle? • What can we learn from early developers and early adopters?

  5. Agenda • 8:00 a.m. Networking • 8:30 a.m. Welcome • 8:45 a.m. Keynote 1: Bridging Across Communities • 9:30 a.m. Keynote 2: Grid Computing • 10:00 a.m. Open Dialogue • 10:15 a.m. Break • 10:30 a.m. Keynote 3: Software Factories • 11:15 a.m. Open Dialogue • 11:30 a.m. Networking Lunch (MITRE escorts to and from cafeteria required) • 1:00 p.m. Lessons from Early Developers and Adopters • 2:00 p.m. Open Dialogue and Swing for the Fences Seminar Preview • 2:15 p.m. May 11th Workshop Summary and Logic Library Demo and Case Study (CT Awards!) • 3:15 p.m. Open Dialogue and Best Practices Workshop Preview • 3:30 p.m. Adjourn

  6. Welcome • Susan Turnbull, GSA, Emerging Technology Subcommittee, and Brand Niemann, EPA, Emerging Technology Subcommittee: • The Why: • Skating to Where the Puck Will Be (slides 7 - 8) • The What: • Service Components on a Service Grid (slides 9-10) • The How: • Organizational Relationships and Collaboration For a Change (slides 11-16) • The Who: • Entrepreneurs (slides 17-20)

  7. The Hockey Rink and “Break Through Performance” Game Analogy:A Level Playing Surface and “Skate to Where the Puck Will Be”* *Wayne Gretzky (considered by most to be the greatest hockey player of all-time).

  8. CIO Council’s FY04 Strategic Plan • Emerging Technology Subcommittee, Architecture & Infrastructure Committee: • The mission is to provide a foresight mechanism that draws from FEA reference models and the capital planning and investment control process to create greater synergy between technology push cycles and market pull cycles in order to support a performance-based framework for innovation prototyping and adoption (bold added). • February 2004, page 9.

  9. Started far apart in applications & technology Grid and Web Services Standards-Marc Brooks, MITRE Grid GT1 GT2 OGSi WS-I Compliant Technology Stack Have been converging WSRF BPEL WS-* WSDL, SOAP XML HTTP Web Convergence of Core Technology Standards allows Common base for Business and Technology Services

  10. Use, Intent Pragmatic Web Trust Security/Identity Inference Engine Reasoning/Proof OWL Higher Semantics RDF/RDF Schema Semantics Structure XML Schema Syntax: Data XML Emerging XML Stack Architecture for the Semantic Web + Grid + Agents - Leo Obrst, MITRE • Semantic Brokers • Intelligent Agents • Advanced Applications • Use, Intent: Pragmatics • Trust: Proof + Security + Identity • Reasoning/Proof Methods • OWL, DAML+OIL: Ontologies • RDF Schema: Ontologies • RDF: Instances (assertions) • XML Schema: Encodings of Data Elements & Descriptions, Data Types, Local Models • XML: Base Documents • Grid & Semantic Grid: New System Services, Intelligent QoS Agents, Brokers, Policies Intelligent Domain Services, Applications Sem-Grid Services Water, LISP?

  11. Organizational Relationships Industry Advisory Council (IAC) U.S. CIO Council OMB - FEAPMO Enterprise Architecture Special Interest Group Architecture & Infrastructure Committee IT Workforce Connections Best Practices Committee WGs and CoPs Subcommittees: Governance Components Emerging Technologies Semantic Interoperability Community of Practice Chief Architects Forum

  12. Brief History • The AIC chartered three Working Groups (Collaboration Expedition Workshops, XML, and XML Web Services) which were and still are very successful. • The AIC, which started as one integrated activity, reorganized into three Subcommittees and put the three WGs into the Emerging Technology Subcommittee. • The AIC decided it no longer wanted WGs, but by then the WGs had become CoPs and sources of best practices so they continued to support the AIC as well as broader needs. • For example the XML Web Services WG CoP morphed into Semantic Interoperability CoP! • The AIC decided it then wanted to become an integrated activity again like a CoP and formed the CAF CoP and wants to do a joint meeting with the Best Practices Committee in July! • The CIO’s have realized that they can’t do Enterprise Architecture alone, but need the expertise, participation, and resources of a network of CoPs and a re-training of the IT workforce!

  13. Collaboration for a Change Trust and Time Turf Wars Network Coordinate Cooperate Collaborate Exchange Information AND Harmonize Activities AND Share Resources AND Enhance Partner’s Capacity Exchange Information AND Harmonize Activities AND Share Resources Exchange Information AND Harmonize Activities Exchange Information Based on the concepts from A.T. Himmelman “Collaboration for a Change: Definitions, Models, Roles and a Collaboration Process Guide” and a tool developed by Lancaster Community Health Plan.

  14. Examples of Enhancing Partner’s Capacity • May 11, 2004 Collaboration Expedition Workshop in Cooperation with Componenttechnology.Org at NSF, Ballston, VA, on Emerging Technology Innovations in Software Components Development, Reuse, and Management – Applications to Government Enterprise Architecture. • NASVF Helps SBIR Phase III with More Seed Investing Seminars in Communities. • CIO Council Helps SBIR Program Managers with eGov/FEA Topics. • SBA Brings “Break Through” Performance Components Directly to eGovernment Programs. • Emerging Technology Subcommittee Helps the Component Technology Subcommittee with Candidate Components • Emerging Technology Subcommittee Helps Simplify and Unify the FEA and Architecture & Infrastructure Committee Process and Tasks and Embed the Business Processes and the EA in the Components Themselves under a Service-Oriented Architecture. • Componenttechnology.Org Brings Pre-vetted eGOV Emerging Technology Components to the NASVF.

  15. Collaboration Registry & Repository

  16. Collaboration Registry & Repository • Componenttechnology.Org: • Company/Entrepreneur Proposing eGovernment Solutions. • Government Agency Looking for eGovernment Solutions. • Venture Capital/Angel Investor Willing to Fund a Company/Entrepreneur Proposing eGovernment Solutions. • Government Agency with a SBIR Program Willing to fund a Company/Entrepreneur and Hand-off the SBIR Project to the Venture Community in Phase III. • Other Interested Party Seeking to Help.

  17. The Emerging Technology Component “Break Through Performance” Life Cycle of Vivisimo.Com • A product of Phases I and II of the National Science Foundation’s SBIR (Small Business Innovation Research Program). • A product of the Phase III SBIR from Innovation Works – Associated with the NASVF (National Association of Seed and Venture Funds). • Highly Recommendation by the NSF SBIR Program Manager for Our October 20th First Quarterly Conference. • An Outstanding Presentation and Answers to Questions. • Sets the Standard for “Break Through Performance” for eGov: • Sustainable Business Model/Profitable (Vivisimo well over $1 million/year within two years). • Open Standards/Interoperable/Reusable (e.g. works with FirstGov and supports eGov Act of 2002 need for categorization of government information!) • Product Commercialization and Procurement (Available through GSA Schedule-SBIR Phase II). • Publicity (e.g. Washington Post Express, January 6, 2004, “Googles to Come”.

  18. Special Recognition

  19. Mapping of the FEA Reference Models to Emerging Technology Components (1) See slide 18 for more details. Two SBIR, two non-SBIR, and three CIOC pilots.

  20. Special Recognitions for "Break Through" Performance Presented at the Second Quarterly Emerging Technology Components Conference, January 26, 2004, White House Conference Center • 1. The Adobe "eForms for eGov" Team, for its support of the "eForms for eGov Pilot" and its principles of Web Services Interoperability from the very start, and for being the first to reach "Stage 3" with eForms for eGov and incorporate a full-featured registry/repository. • 2. Broadstrokes, in partnership with IDSi, for commercializing the original CIO Council award-winning VoiceXML Pilot, to deliver a full GIS plus voice emergency notification product called Smart Response. • 3. Development InfoStructure (DevIS), in partnership with the Department of Labor's WorkForce Connections (WFC) Program, for developing "SCORM" and Section 508 Compliant Multimedia Content Management Software which was released recently as EZRO (EZ Reusable Objects), Open Source Software, under General Public License. • 4. Image Matters, a very successful SBIR Program participant with the U.S. Army, whose products, userSmarts and the Ontology Manipulation Toolkit provide Semantic Geospatial Interoperability. • 5. The Noblestar/Flashline Team for the FEA FlashPack Pilot and Component-Asset Reuse Workflow Patterns and Life Cycles in a standards-based Component Registry and Repository. • 6. George Thomas, GSA Enterprise Architect, and Member of the Emerging Technology Subcommittee, for the "Executable FEA“, a design-time MDA (Model-Driven Architecture) and runtime SOA (Service-Oriented Architecture) toolset and EA repository in support of GSA's vision of "One GSA EA“ and the FEA.

  21. Agenda • 8:45 a.m. Bridging Across Communities (Enterprise Architecture, Emerging Technologies, Component Technologies, and Others): • Opportunities for promoting more agile architectures that are more than just models hiding in tools or documents. A broad perspective, a perspective focused on multi-agency architectures and the dynamic aspects of architectures, and bridging the EA and information security communities. • Rick Tucker, MITRE, Principal Enterprise Architect, and Others.

  22. Agenda • 9:30 a.m. Grid Computing: • How are the common "build" principles that power the Internet transforming enterprises and tapping contributions by innovators? • Michael Fitzmaurice, Northrup Grummann and Beowulf Users Group: • • Note: June 8th Meeting on GRID 101 • 10:00 a.m. Open Dialogue • 10:15 a.m. Break

  23. Agenda • 10:30 a.m. Software Factories - Assembling Applications with Languages, Patterns, Frameworks and Tools: • Software Fabrication is automating software development in larger sized organizations similar to the manufacturing model that the automobile and chip-making industries adopted 15 years ago. • Jack Greenfield, Architect for Enterprise Frameworks and Tools, Microsoft, and lead author of “Software Factories”. • See • 11:15 a.m. Open Dialogue • 11:30 a.m. Networking Lunch (MITRE Escorts to and from the cafeteria are required)

  24. Agenda • 1:00 p.m. Lessons from Early Developers and Adopters: • Tony Stanco, GWU - Lab to IPO: The High-tech Start-up; Scott Mendenhall GWU/Entrepreneur; Kevin Dziekonski, GWU/ Entrepreneur; David Barbe, University of Maryland School of Business and Entrepreneurship Program; Arun Sood, George Mason University, Department of Computer Science. • 2:00 p.m. Open Dialogue and Swing for the Fences Seminar Preview: • Seed Investing for Entrepreneurs Seminar, July 7, 2004, organized by NASVF at the University of Maryland (by invitation). David Barbe, University of Maryland and Tony Stanco, GWU.

  25. Agenda • 2:15 p.m. Emerging Technology Innovations in Software Components Development, Reuse, and Management-Applications to Government Enterprise Architecture: • Highlights from the May 11th Collaboration Workshop in Cooperation with Componenttechnology.Org, Jana Crowder, Noblestar, and • Logic Library Demo and Case Study, Brent Carlson, Vice President of Technology and Co-founder, LogicLibrary, Inc. • CT Awards (to be announced)

  26. Agenda • 3:15 p.m. Open Dialogue and Best Practices Workshop Preview: • Rick Murphy, Blueprint Technologies, and • Jay Peltz, FederalConnections.Org • 3:30 p.m. Adjourn

  27. Strategic Directions • GAO Report-The Federal Enterprise Architecture and Agencies’ Enterprise Architectures Are Still Maturing, May 19, 2004: • The FEA is more akin to a classification scheme (taxonomy) for government operations than a true enterprise architecture. • Since the terms are not well-defined, GAO asks if the expected relationship between the FEA and agencies’ architectures is clear enough for agencies to “map” and “align” their architectures with the FEA (the semantic interoperability problem). • The agencies’ enterprise architectures may not provide sufficient content for driving implementation of systems. • The CIO Council is taking the lead on developing the “security profile”.

  28. Strategic Directions • OMB Enterprise Architecture Assessment V 1.0 Guidelines, May 15, 2004: • Component – A self-contained business process or service with pre-defined functionality that may be exposed through a business or technology interface. • Information Value Chain Model – A set of artifacts within the EA that describes how the enterprise converts its data into useful information. • Patterns – Frequently occurring combinations of business and technical elements that can be used to deliver re-usable business services across the enterprise.

  29. Strategic Directions • OMB Enterprise Architecture Assessment V 1.0 Guidelines, May 15, 2004: • Node Diagram – Diagrams depicting the interdependencies between elements of the architecture. Node diagrams can be used to describe the interaction of business functions with technology components, the relationship of performance objectives to elements of the architecture, and other relationships. • Shared Services – Architectural elements (business processes and/or technology components) that are used by multiple organizations within the enterprise.

  30. Strategic Directions • KM.Gov Discussion of Business Function Models (Denise Bedford, May 26, 2004): • The World Bank’s is a narrow and deep hierarchy: • Level 1 = General Business Area • Level 2 = Business Activity • Level 3 = Business Process • Level 4 = Task • Note: A ‘service taxonomy’ is an inherent part of a business taxonomy and emerges at Level 3 and below. If you can keep business function and organizational unit as separate attributes, you can then see which organizational units may be offering the same kinds of services and this might help to form communities of practice across organizational units!

  31. Strategic Directions • Enterprise Information Interoperability Workshop, June 28-29, 2004 (by invitation): • After a rousing keynote speaker (Jeffrey Pollack, co-author of Semantic Interoperability - available Fall 2004 from John Wiley & Sons) and plenary session that is designed to stir your thinking, we will divide participants into three teams of approximately 20 each. The groups will select their own leadership and will be given a case study. Each group will have a facilitator and scribe. The teams will produce solutions to a case study that will be briefed the morning of the second day. • We anticipate a productive exchange of ideas that will stimulate new thinking with consideration for emerging technologies. We will publish the consolidated findings for presentation on Executive Day at the Association for Enterprise Integration (AFEI) Enterprise Integration Expo in September 2004.

  32. Strategic Directions • Adaptive Information: Improving Business Through Semantic Interoperability, Grid Computing & Enterprise Integration, Jeffrey Pollack and Ralph Hodgson, John Wiley & Sons, Fall 2004: • Semantic Interoperability Framework: • A highly dynamic, adaptable, loosely-coupled, flexible, real-time, secure, and open infrastructure service to facilitate a more automated information sharing framework among diverse organization environments. • Model-Driven Architecture: • An approach to system development that emphasizes the use of models to separate specification of software application independent from the platform that supports it. The three primary goals of the MDA are portability, interoperability, and reusability.

  33. Strategic Directions • Adaptive Information: Improving Business Through Semantic Interoperability, Grid Computing & Enterprise Integration, Jeffrey Pollack and Ralph Hodgson, John Wiley & Sons, Fall 2004 (continued): • Service Grid: • A distributed system framework base around one or more Grid services instances. Grid services instances are (potentially transient) services that conform to a set of conventions (expressed as WSDL interfaces) for such purposes as lifetime management, discovery of characteristics, notification and so forth. They provide for the controlled management of the distributed and often long-lived state that is commonly required in sophisticated distributed applications.

  34. Strategic Directions • Adaptive Information: Improving Business Through Semantic Interoperability, Grid Computing & Enterprise Integration, Jeffrey Pollack and Ralph Hodgson, John Wiley & Sons, Fall 2004 (continued): • Frictionless information flows are the inevitable future of information technology. • Models, independent of platform and data, will drive semantic interoperability. • Component-driven service-oriented architectures (SOA) will provide flexible and dynamic connectivity-once they are fully enabled by semantic interoperability. • Autonomic computing concepts will drive strategic technology development in a number of industries and software solution spaces. • Intelligence information sharing problems are a useful context to examine the strengths of flexible, dynamic and loosely-coupled adaptive architectures.

  35. Strategic Directions • Semantics and Alignment on the EA Summit Agenda, Rancho Mirage, CA, June 6-8, 2004: • "The biggest issue facing enterprise architects today is aligning the direction of information technology with business strategy," observes Richard Murphy, chief architect of Blueprint Technologies. • “Semantic technology is social networking for applications," explains Ralph Hodgson, executive partner with the TopQuadrant consulting firm. "It can allow the system to connect one activity to another automatically."

  36. Strategic Directions • Some recommendations: • Involve taxonomy (ontology) expertise in improving the FEA classification scheme (taxonomy) and its extension into the agencies. (This should also help the Line of Business Task Forces work.) • Involve knowledge management expertise in building a comprehensive knowledge-base (repository) of enterprise architecture (OMB budget, solutions like Service-Oriented, Web Services, etc.) See: GCN, May 20, 2004, Forman calls for new approach to the Federal Enterprise Architecture.