Platform Architecture Report


Published on

Published in: Education, News & Politics
  • Be the first to comment

  • Be the first to like this

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

No notes for slide
  • The Common Requirements Vision is a consensus on the role and framework of the Enterprise Architecture. A series of 6 COTS workshops were held to develop 4 deliverables: Identify and prioritize the key Enterprise Business Strategies that are, or will, drive business decisions and programs across the enterprise. Identify and prioritize the key Technology Trends that are, or will, significantly impact the State’s business strategies and architecture requirements. Identify the core Requirements for the Technical Architecture that must be met in order to support enterprise business strategies. Identify the major implications of Deliverables 1,2, and 3 on the development, maintenance, and management of the State’s application portfolio, referred to as Application Portfolio Implications.
  • A Conceptual Architecture is a logically consistent set of principles that:          Are derived from business requirements;          Guide the engineering of an organization’s information systems and technology infrastructure across the various component architectures;          Are understood and supported by senior Commonwealth management, State Agencies, Institutes of Higher Learning, and local governments; Example Principles: Balance freedom of information with privacy and security Insure IT interoperability both horizontally and vertically
  • Business Architecture (the functions of a business or government) Information Architecture (the information needed to support the functions) Application Portfolio (the computer software that processes the information) Technical Architecture (the computer hardware that enables the processing)
  • Slow going at first. After scope defined, used accelerated workshop approach. Nine Months: long pregnancy, gained weight, got cranky at the end, delivery was a relief! Change of Administrations put development on hold for 6 months. Using NASCIO Domain Templates for next two domains. Streamlining process. Architect drafts strawman domain design and uses domain team to complete design and verify. Must have the best and brightest on these teams. Need administrative support. Tip: Technicians sometimes hesitate to assume authority to set standards.
  • Just enough EA, Just in time Network - Defines the communications infrastructure. Security - Defines the technologies, security standards and policies necessary to both protect the information assets of the Commonwealth and to make the information available to the Commonwealth workforce and citizens. Middleware - Defines the components that create integration among the client and server systems to improve overall usability of the distributed architecture. Platform - Defines the client and server computing platforms and the operating systems interfaces supported. Application - Defines how applications are designed and how they cooperate. Web Services Pilot will be part of this domain. Information - Describes the logical structure of databases and the methodology used to correlate data in multiple databases. Provides a framework for defining responsibility for data integrity and distribution. Database - Defines the technical components of the software systems that support storage and retrieval of data Systems Management - Defines how the hardware and software components of the infrastructure will be monitored and controlled.
  • Obsolescent - VEA actively promotes that agencies employ a different technology. Should not plan new deployments. Discouraging any further purchases of abacuses! Transitional - VEA promotes other standard technologies. Agencies may be using this technology as a transitional strategy in movement to a strategic technology. Strategic - VEA promotes use of this technology by agencies. New developments of this technology are recommended. Emerging - VEA promotes only evaluative deployments of this technology. This technology may be in development or may require evaluation in government and university settings. Use of this technology may be high risk.
  • Policies are statements of direction and are binding. Standards describe mandatory practices and are binding Guidelines are suggested best practices, etc. Consolidation will allow us to become more prescriptive in our standards.
  • In Summary Need Owner/Sponsorship at Executive Level Good Oversight Structure Good Governance Structure Ownership/Buy-in Add Value Communicate Successes!
  • Platform Architecture Report

    1. 1. The Commonwealth of Virginia Enterprise Architecture Platform Architecture Report January 7, 2004
    2. 2. Enterprise Architecture <ul><li>Common Requirements Vision </li></ul><ul><ul><li>Enterprise Business Strategies </li></ul></ul><ul><ul><li>Technology Trends </li></ul></ul><ul><ul><li>Requirements for the Technical Architecture </li></ul></ul><ul><ul><li>Application Portfolio Implications </li></ul></ul><ul><ul><li> </li></ul></ul>
    3. 3. Enterprise Architecture <ul><li>Conceptual Architecture </li></ul><ul><ul><li>A Logically Consistent Set of Principles </li></ul></ul><ul><ul><ul><li>Derived From Business Requirements </li></ul></ul></ul><ul><ul><ul><li>Guide the Engineering of the Domain Architectures </li></ul></ul></ul><ul><ul><ul><li>Are Understood and Supported </li></ul></ul></ul><ul><ul><ul><li> </li></ul></ul></ul>
    4. 4. Enterprise Architecture <ul><li>Business Architecture </li></ul><ul><li>Information Architecture </li></ul><ul><li>Application Portfolio </li></ul><ul><li>Infrastructure (Technical) Architecture </li></ul>
    5. 5. Enterprise Architecture <ul><li>Architecture Domains </li></ul><ul><ul><li>Design Based on Business Strategy, Technology Trends, Business Information Requirements </li></ul></ul><ul><ul><li>Teams of Experts </li></ul></ul>
    6. 6. Enterprise Architecture Technical Architecture Domains Systems Management Platform Database Middleware Information Security Application Network
    7. 7. Enterprise Architecture <ul><li>Domain Architecture Technology Categories </li></ul><ul><ul><li>Obsolescent </li></ul></ul><ul><ul><li>Transitional </li></ul></ul><ul><ul><li>Strategic </li></ul></ul><ul><ul><li>Emerging Technology </li></ul></ul>
    8. 8. Enterprise Architecture <ul><li>Policies, Standards and Guidelines </li></ul><ul><ul><li>Developed from Domain Architecture Reports </li></ul></ul>
    9. 9. Enterprise Architecture <ul><li>Next Steps </li></ul><ul><ul><li>Update the Vision </li></ul></ul><ul><ul><li>Develop Remaining Domain Architectures </li></ul></ul><ul><ul><li>Update the Existing Domain Architectures </li></ul></ul><ul><ul><li>Update the Policies, Standards and Guidelines </li></ul></ul><ul><ul><li>The Architecture Is Never Complete </li></ul></ul>
    10. 10. Platform Architecture Report <ul><li>Scope </li></ul><ul><ul><li>Personal Computing Devices </li></ul></ul><ul><ul><ul><li>Desktops </li></ul></ul></ul><ul><ul><ul><li>Notebooks </li></ul></ul></ul><ul><ul><ul><li>Handhelds </li></ul></ul></ul><ul><ul><li>Servers </li></ul></ul><ul><ul><ul><li>High-end </li></ul></ul></ul><ul><ul><ul><li>Midrange to Low-end </li></ul></ul></ul><ul><ul><li>Storage </li></ul></ul>
    11. 11. Platform Architecture Report <ul><li>Technical Topics </li></ul><ul><ul><li>General Discussion </li></ul></ul><ul><ul><li>“As Is” Architecture </li></ul></ul><ul><ul><li>Issues/Challenges </li></ul></ul><ul><ul><li>Technology Use Trends </li></ul></ul><ul><ul><li>Additional Recommendations </li></ul></ul><ul><li>Summaries of Recommendations </li></ul><ul><li>Glossary </li></ul>
    12. 12. Platform Architecture Report <ul><li>Review of Recommendations </li></ul><ul><ul><li>ITIB to Review Platform Technical Recommendations (p.87) </li></ul></ul><ul><ul><li>VITA Architectural Review Board Reviews Operational Recommendations (p.93) </li></ul></ul><ul><li>Request ITIB Action at Next Meeting </li></ul><ul><li>Next Step – Policies, Standards, Guidelines </li></ul>
    13. 13. Enterprise Architecture <ul><li>Questions? </li></ul>
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.