An Emerging Technology Components Life Cycle in the ...

796 views
694 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
796
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Carnegie Mellon’s IDEAL model an organizational improvement model that serves as a roadmap for initiating, planning, and implementing improvement actions. Solution Envisioning scenario and inquiry-based approach into the possibility of solution concepts using capability cases as catalysts to helping translate business vision into IT solutions. Legitimate Intrapreneuring a number of approaches where there is executive sponsorship for agile teams to lead emerging technology promotion within the organization. CoE Incubators A number of organizations now have Centers of Excellence who have the edict to maintain competency in specific technologies and mediate the introduction of this technologies across the business. Technology Adoption Patterns (Rising and DeLano) Linda Rising and David DeLano led a workshop at OOPSLA ’96 entitled, “Introducing Patterns Into the Work-place.” SKUNK Works Pilots Replication Centers
  • Yes, you will be modeling, but before you dive into it, You are really going to need to understand the requirements, stakeholders, scenarios of use, the scope of the domain of application. It also important to pick the right technology and vendors – really understand the value proposition Needs to happen separately and before any modeling. Make sure that this technology can solve this business problem better than any other approach – even for the demonstrator type project – showcases the technology. Otherwise, you’ll never get past the prototype. Must pick a business problem where the special capabilities that this brings to the users are needed and important. For all of these reasons, Envisioning is important. Tips and Traps: if you have no search at all, don’t jump into ontologies. Start from something – existing business rules or taxonomy. Ontology technology should be both necessary and sufficient. Get the competency questions first? Competency questions that are at odds – what do you do with the conflicts? Need a process to get to the Stakeholders in order to get to the competency questions. Power a methodology that gets the stakeholders engaged and envisioning what they can and are going to do? How are you going to build it? How are you going to deploy it?
  • An Emerging Technology Components Life Cycle in the ...

    1. 1. An Emerging Technology Components Life Cycle in the Government Enterprise Architecture Framework (GEAF) Prepared for the Joint AIC Emerging Technology and Components Subcommittees Meeting, January 6, 2004, and for the Second Quarterly Emerging Components Conference, January 26, 2004 By Brand L. Niemann
    2. 2. Background <ul><li>Our recent cross-Subcommittee discussions of the “IRS 30 components” has provided a significant change in thinking: </li></ul><ul><ul><li>“ We (US PTMO) are in the midst of these kind of issues that we have to address. The governance, cost model, ownership, etc. My approach is no longer component reuse, it goes beyond components. I called it &quot;asset reuse&quot;. (Daud Santosa, December 2, 2003, to Mike Dunham and Brand Niemann.) </li></ul></ul><ul><li>The Noblestar/Flashline Federal Asset Management Solution Pilot is already addressing that within the work on the Government Enterprise Architecture Framework (GEAF) in Goal 3 of the Governance Subcommittee: </li></ul><ul><ul><li>See Government Enterprise Architecture Framework (GEAF) Meeting, October 27, 2003, and OASIS eGOV Technical Committee Meeting: Registries and Repositories Workshop, October 30, 2003, presentations posted to the AIC QuickPlace (December 4, 2003) and at http://web-services.gov. </li></ul></ul>
    3. 3. Reuse Workflow Pattern Source: See Enterprise Architect Summit Conference Presentation on “Software Reuse: Patterns and Anti-Patterns” by Charles Stack at http://web-services.gov.
    4. 4. Explanation <ul><li>Based on Open Standards and Asset-Based Software Engineering Principles: </li></ul><ul><ul><li>View software as an asset. </li></ul></ul><ul><ul><li>Engineering discipline. </li></ul></ul><ul><ul><li>Portfolio management. </li></ul></ul><ul><ul><li>Measure-Evaluate-Improve. </li></ul></ul><ul><li>Being Applied to the Recreation One-Stop Components in Support of the “Building Out the BRM: Enabling a Common Process View”: </li></ul><ul><ul><li>See November 20, 2003, presentation by OMB FEA-PMO. </li></ul></ul><ul><ul><li>Also see EPA comments to FEAPMO to improve CPV Model based on experience with the Recreation One-Stop Components, December 5, 2003, so far. </li></ul></ul>
    5. 5. Explanation <ul><li>One of Five Government Enterprise Architecture Framework Components Registries and Repositories Demonstrated to the Federal Enterprise Architecture Program Management Office (FEAPMO-APCG, Inc.) on December 15, 2003: </li></ul><ul><ul><li>(1) Emerging Components Collaboration Registry/Repository (ECCRR) (&quot;esir&quot;) (operational); </li></ul></ul><ul><ul><li>(2) Government Enterprise Architecture Framework Components Registry and Repository (GEAFRR) (operational); </li></ul></ul><ul><ul><li>(3) Topic Maps of eGov and EA Conferences (operational); </li></ul></ul><ul><ul><li>(4) Federal Asset Management Solution (to be publicly available soon on the Web); and </li></ul></ul><ul><ul><li>(5) Federal Enterprise Architecture Capability Manager with Semantic Technologies (operational, but not on the Web yet). </li></ul></ul>Note: See http://web-services.gov for URLs and other links.
    6. 6. Explanation <ul><li>Each of these GEAF Registries and Repositories Has Its Own “Component Life Cycle” – “Asset Reuse Workflow Pattern”. </li></ul><ul><li>The Noblestar/Flashline Federal Asset Management Solution Pilot: </li></ul><ul><ul><li>Essentially Follows the NASCIO EA Tool-Kit (July 2002) Component Life Cycle Which Appears to be the Only EA with one! (See next slides.) </li></ul></ul><ul><ul><li>Has Already Built a Reusable “FEA FlashPack” Component for One of Its Clients (Department of the Navy, But Requests Confidentiality At This Stage)! </li></ul></ul><ul><ul><ul><li>See PDF file at http://web-services.gov . </li></ul></ul></ul><ul><li>We are Working with NASCIO and the States (e.g. SBIR, Angel Investors, etc.) to Implement This: </li></ul><ul><ul><li>Second Quarterly Emerging Components Conference, January 26, 2004, at the White House Conference Center. </li></ul></ul><ul><ul><ul><li>See http://componenttechnology.org </li></ul></ul></ul>
    7. 7. Explanation <ul><li>The NASCIO EA Tool-Kit (July 2002) Component Life Cycle: </li></ul><ul><ul><li>Emerging – New technology, which has the potential to become current. </li></ul></ul><ul><ul><li>Current – Recommended technology. Technology meets the requirements of the enterprise architecture. </li></ul></ul><ul><ul><li>Twilight – Items that do not conform to the Business/Technology Drivers. </li></ul></ul><ul><ul><li>Sunset – Items that do not conform to the Business/Technology Drivers and has a set discontinuation date. </li></ul></ul><ul><li>The NASCIO EA Tool-Kit Also Contains a Blueprint Framework Which Consists of a Series of Templates Including Ones for Technology and “Compliance Component” (see next slide for part of template for the later). </li></ul><ul><li>The NASCIO EA Tool-Kit Also Contains a Lexicon (see excerpts in slides 10-14). </li></ul><ul><li>NASCIO has also just released their Enterprise Architecture Maturity Model Version 1.3, December 2003 (see slide 15). </li></ul>
    8. 8. Explanation Note: Template Continued on the Next Slide.
    9. 9. Explanation NASCIO Compliance Component Template (continued)
    10. 10. NASCIO EA Tool-Kit Lexicon <ul><li>Lexicon: Provides a glossary and cross-reference for words that may have multiple meanings. The purpose is to create common definitions to allow for clearer understanding. </li></ul><ul><li>NASCIO: The National Association of State Chief Information Officers represents state chief information officers and information resource executives and managers from the 50 states, six U. S. territories and the District of Columbia. State members are senior officials from any of the three branches of state government who have executive-level and statewide responsibility for information resource management. </li></ul><ul><li>Enterprise Architecture Development Tool-Kit: A guide for municipal, county, state and federal government to develop and define adaptive enterprise architecture. Includes process models and templates with several examples. </li></ul><ul><li>Component: In object-oriented programming and distributed object technology, a component is a reusable program building block that can be combined with other components in the same or other computers in a distributed network to form an application. </li></ul>
    11. 11. NASCIO EA Tool-Kit Lexicon <ul><li>Emerging Technologies: The most current technologies. These items will usually require testing prior to acceptance by industry as the current standard. It is generally understood that emerging technologies be considered carefully before implementing in an enterprise-wide architecture. </li></ul><ul><li>Current Technologies: Technologies that are the current standard for use within the enterprise, tested and generally accepted as standard by industry. These items comply with or support the principles listed for the discipline. </li></ul><ul><li>Twilight Technologies: Technologies being phased out by the enterprise. </li></ul><ul><li>Sunset Technologies: Technologies that have been phased out and cannot be used within the organization past a specified date. </li></ul>
    12. 12. NASCIO EA Tool-Kit Lexicon <ul><li>Technology: Tools or tool systems by which we transform parts of our environment and extend our human capabilities (Tornatzky and Fleischer 1990). </li></ul><ul><li>Technology Drivers: Internal business processes or needs and external innovation that influence technology. These are captured in three stages: </li></ul><ul><ul><li>• Technology Trends – Emerging trends within the technology world that are impacting how services and the IT portfolio will be provided. </li></ul></ul><ul><ul><li>• IT Best Practices – Trends and approaches that are most successful at providing services and IT portfolio. </li></ul></ul><ul><ul><li>• IT Principles – Those practices and approaches that the organization chooses to institutionalize to better all provided services and IT portfolio pieces. </li></ul></ul>
    13. 13. NASCIO EA Tool-Kit Lexicon <ul><li>Business Drivers: Internal goals and strategies and external trends that influence the business. These are captured in three stages of drivers: </li></ul><ul><ul><li>• Industry Trends – Emerging trends within the business world that are impacting how services and information will be provided. </li></ul></ul><ul><ul><li>• Business Best Practices – Trends and approaches that are most successful at providing services and information over time. </li></ul></ul><ul><ul><li>• Business Principles – Business practices and approaches that the organization chooses to institutionalize to better all provided services and information. </li></ul></ul>
    14. 14. NASCIO EA Tool-Kit Lexicon <ul><li>Framework: Illustration of the various architecture elements, used as a guide for assisting governments as they create enterprise architectures for their organizations. Currently in the NASCIO Tool-Kit there are four Frameworks: </li></ul><ul><ul><li>• Enterprise Architecture Framework </li></ul></ul><ul><ul><li>• Architecture Governance Framework </li></ul></ul><ul><ul><li>• Business Architecture Framework </li></ul></ul><ul><ul><li>• Technology Architecture Framework </li></ul></ul><ul><li>Blueprint: Plan or guide, commonly used in construction, laid out logically and including essential elements to address and follow as building progresses. </li></ul><ul><li>Template: A form used as a guide, such as a document in which the standard parts are already included and the variable parts are completed as appropriate. </li></ul>
    15. 15. NASCIO Enterprise Architecture Maturity Levels (2003) <ul><li>EA Level 0: No Program </li></ul><ul><li>EA Level 1: Informal Program </li></ul><ul><li>EA Level 2: Repeatable Program </li></ul><ul><li>EA Level 3: Well - Defined Program </li></ul><ul><li>EA Level 4: Managed Program </li></ul><ul><li>EA Level 5: Continuously Improving Program </li></ul>
    16. 16. Technology Adoption Life Cycle <ul><li>Innovators </li></ul><ul><li>Early Adopters </li></ul><ul><li>Early Majority </li></ul><ul><li>Late Majority </li></ul><ul><li>Laggards </li></ul><ul><li>Techies: Try It! </li></ul><ul><li>Visionaries: Out Ahead. </li></ul><ul><li>Pragmatics: Stick with the herd. </li></ul><ul><li>Conservatives: Hold On! </li></ul><ul><li>Skeptics: No Way! </li></ul>
    17. 17. How Do We Adopt Emerging Technology? Bottom-up Top-down Solution Envisioning Pilots COE Incubators Skunk works Intrapreneuring Organizational Transformation IDEAL™ Replication Centers Conference Attendance Sandboxes
    18. 18. Moving From an Understanding of the Business Situation and Intent to IT Solutions
    19. 19. Technology Adoption Using a Solution Envisioning Approach Situation Analysis Wants Who What Why Business Dynamics: Assess forces & explore scenarios of the future Business Outcomes: Agree desired results & Measures of effectiveness Capability Envisioning Design By Example: Explore Capability Cases Conceptual Architecture: Develop solution vision Capability Design Technology Selection Solution Architecture Change Management Scenarios Capability Cases Stakeholder Analysis 1 2 3 Implementation Planning When How Where are we now? How is our world changing? What does technology make possible? What are the new ways to archive? How do we get there? What do we have to change?
    20. 20. Reusable Solutions Need to be “Situated&quot; and Co-evolved with the Solution Providers Initial Solution Development Situation Analysis Capability Envisioning Capability Realization Adoption is a Collaborative Process of “Co-Evolution” Customer-Specific Solution Adoption Solution Adaptation Customer-Specific Solution Adoption Solution Adaptation Situation Analysis Capability Envisioning Capability Realization
    21. 21. A Solution Needs to be Understood from a Number of Viewpoints Access Context Re-Constructor Ingest Knowledge Conditioner Authentication Marker Content Quality Assurer Mediated Query Preservation Planning Event Monitor Preservation Strategy Developer Service Level Agreement Builder Archival Storage Content Migrator Message Stabilizer Administration Service Manager Negotiator Policy Engine Digital Authenticator Access Event Tracker Data Management Domain Mediator Configurator
    22. 22. How Does Solution Envisioning Work? <ul><li>By Being “Situated” </li></ul><ul><ul><li>Facilitates a shared understanding of forces, challenges, and desired results. </li></ul></ul><ul><ul><li>Expands the space of solution possibilities through the use of capability cases as “innovation catalysts”. </li></ul></ul><ul><ul><li>Enables business and IT to do joint creative work towards a shared vision. </li></ul></ul><ul><ul><li>Builds confidence and commitment towards implementing the shared vision. </li></ul></ul><ul><ul><li>Helps communicate the vision to other parties. </li></ul></ul>
    23. 23. The Method We Are Using for the Semantic Pilots is “ Solution Envisioning with Capability Cases ” Solution Envisioning is a scenario-driven approach to experiencing a future system through analogies and examples using a Catalog of Capability Cases . A Capability Case is a known technology solution to a business problem – a best practice for applying a technology to achieve business results Like an architect presents building designs, Solution Envisioning is &quot; design by example &quot; for IT systems.
    24. 24. Experiences with “Quick Win” Components <ul><li>eForms for eGov: </li></ul><ul><ul><li>Supported the Business Gateway and Other eGov Initiatives. </li></ul></ul><ul><li>Semantic Technologies for eGov: </li></ul><ul><ul><li>Launched Semantic Interoperability SIG and Second Conference in September 2004. </li></ul></ul><ul><li>Emerging Components for eGov: </li></ul><ul><ul><li>SBA/SBIR for eGov Workshop (June 26, 2003): </li></ul></ul><ul><ul><ul><li>Approved presentation to SBIR Program Managers and Participation In Conferences. </li></ul></ul></ul><ul><ul><li>First Quarterly Conference (October 20, 2003): </li></ul></ul><ul><ul><ul><li>Featured “Mixed”* Components and SBIR and non-SBIR Success Stories. </li></ul></ul></ul><ul><ul><li>Second Quarterly Conference (January 26, 2004): </li></ul></ul><ul><ul><ul><li>Featuring three States (AZ, CT, & MD), NASCIO, etc. </li></ul></ul></ul><ul><ul><li>Third Quarterly Conference (March 23-25, 2004) </li></ul></ul><ul><ul><ul><li>Citizen Entrepreneurs: Advancing Small Business Innovation from the States Toward Open, eGov Components at FOSE 2004. </li></ul></ul></ul>*See next slide for explanation and illustration of “mixed” components.
    25. 25. “Mixed” Components Interoperability-Collaboration Domain Open Source Domain Proprietary Domain Open Standards Domain e.g.,Microsoft’s .NET e.g., GSA’s OSERA e.g., OASIS UBL, W3C Semantic Web, etc. Emerging Components for eGov: Bringing “Mixed” Components Together Within the Interoperability-Collaboration Domain!
    26. 26. SBIR Relationship to eGov/FEA
    27. 27. SBIR “Innovation” Model PHASE I Feasibility Research PHASE III Product Development to Commercial Market PHASE II Research towards Prototype Private Sector Investment/ Non-SBIR Federal Funds (before/during/after!) Source: National Science Foundation Taxes Federal Investment
    28. 28. Draft Agenda, January 26 th <ul><li>1. Welcome and Logistics: Brand Niemann, EPA and CIOC/AIC Emerging Technology Subcommittee (8:45-9:15 a.m.) </li></ul><ul><ul><li>An Emerging Technology Components Life Cycle in the Government Enterprise Architecture Framework (GEAF) </li></ul></ul><ul><li>2. State Citizen Entrepreneurs (AZ, CT, & MD), Postcards from SBIR National Conference (October 27-30, 2003) and the 2003 NASVF Conference (November 2-5, 2003), and Some Next Steps (9:15 a.m. -12 Noon with 15 minute break) </li></ul><ul><ul><li>Morning Panel Chaired by Tony Stanco, Founding Director, The Center of Open Source & Government, George Washington University. Advancing Small Business Innovation from the States Toward Open, eGov Components (1) Marsha Kolich, Business Development Manager, Office of Innovation and Technology, Arizona Department of Commerce, and 5 Small Businesses, (2) Victor Budnick, President and Executive Director, Connecticut Innovations and Selected Small Businesses, and (3) Dr. Philip Singerman, State of Maryland Technology Development Corporation, and Selected Selected Small Businesses. Also Maurice Swinton, Assistant Administrator, Office of Technology (SBIR/STTR), US SBA and Dan Loague, Executive Director, National Association of Seed and Venture Funds. And finally, Susan Turnbull, GSA and CIOC/AIC Emerging Technology Subcommittee, Preview of the Third Quarterly Emerging Components Conference at FOSE 2004, March 23-25, 2004! </li></ul></ul><ul><li>3. Lunch and Small Business Gallery Tour (12 Noon-1:30 p.m.) </li></ul><ul><ul><li>Lunch on own at nearby restaurants or order catered box lunch by 8:45 a.m. and eat and tour the Small Business Gallery in the Conference Center. </li></ul></ul><ul><li>4. Afternoon Session Keynote: Gerry Wethington, CIO, State of Missouri, and President, National Association of Chief Information Officers (NASCIO) (Invited), (1:30-2 p.m.) </li></ul><ul><ul><li>Innovative Funding for Innovative State IT. </li></ul></ul>
    29. 29. Draft Agenda, January 26 th <ul><li>5. Reports 1: 20 Minutes Each (2-3 p.m.): </li></ul><ul><ul><li>An SOA (Services Oriented Architecture) for the Federal Enterprise Paper, and PowerPoint, Richard C. Murphy, Sun Certified Enterprise Architect and Founding Member of the Worldwide Institute of Software Architects </li></ul></ul><ul><ul><li>Global Justice Information Sharing Initiative Web Site and PowerPoint; Service-Oriented Architecture Subcommittee Activities, Thomas Henderson and Scott Fairholm </li></ul></ul><ul><ul><li>Federal Asset Management Solution (Flashline Registry and Repository): Registration of New Components FEA FlashPack and PowerPoint. Web Site to be made publicly available soon. Noblestar and Flashline Team </li></ul></ul><ul><li>6. Break (3-3:15 p.m.) </li></ul><ul><li>7. Reports 2: 20 Minutes Each (3:15-4:15 p.m.) </li></ul><ul><ul><li>Emerging Technology Component Registration Pilot, Owen Ambur, Co-Chair, Government XML Working Group and Member of the Emerging Technology Subcommittee, other members of the team. Please help us populate the site with emerging technology components that you are offering and/or would like to participate in developing and maturing. Sam Hunting has developed a topic map facilitating access to the submissions. Your input and feedback will help to enhance the value of the pilot. </li></ul></ul><ul><ul><li>E-Forms for E-Gov Pilot Team Final Report Webpage; Rick Rogers, Fenestra, Pilot Team Lead </li></ul></ul><ul><ul><li>An Enterprise Architecture For How People Work The Case for an Intelligent Document Architecture, Demonstration by Alistair Lee (Phase 3 of their &quot;Eforms for eGov Pilot&quot;: Runtime Web Service Implementation with Arbitrary XML Schema </li></ul></ul><ul><li>8. Adjourn and Networking Until Conference Center Closes (4:30-5 p.m.) </li></ul>

    ×