Home >Education >Version Control

Version Control

Date post:19-Nov-2014
Category:
View:474 times
Download:1 times
Share this document with a friend
Description:
 
Transcript:
  • 1. U.S. Department of Housing and Urban Development Office of the Chief Information Officer Enterprise Architecture Program DATE REVISION xxXxBYxXxx 202-708-1821, [email protected] State Enterprise Technical Architecture ENTERPRISE ARCHITECTURE Version 1.1PRACTICEDATE: 7/16/03 AUTHOR: Andrew E. Koslov Technical Future State Architecture Version 1.1 6/8/2010 Page 1 of 12

2. Version ControlVersionAuthor/Editor Date Changes 0.1Andrew E. Koslov07/25/2002 First draft 0.2Andrew E. Koslov08/14/2002 Editorial, revision of chart 1, additional sections 0.3Andrew E. Koslov09/11/2002 Second Draft 0.99 Andrew E. Koslov09/30/2002 Final Draft 1.0Andrew E. Koslov11/04/2002 Public Version 1 (Editorial, linkage with 5-layer model) 1.1Andrew E. Koslov11/18/02 Editorial changes ContentsVERSION CONTROL.............................................................................................2CONTENTS............................................................................................................2BACKGROUND......................................................................................................3TECHNICAL APPROACH AND TAXONOMY.......................................................4TECHNICAL ARCHITECTURE PRINCIPLES.......................................................8FUNCTIONAL SERVICES HIERARCHY...............................................................9KEY TECHNOLOGIES.........................................................................................10ARCHITECTURAL COMPONENTS....................................................................11PRODUCTS..........................................................................................................11 Technical Future State Architecture Version 1.1 6/8/2010 Page 2 of 12 3. BackgroundThis document represents the first version of HUDs Future State Enterprise Technical Architecture. It is based on extensive collective development work by the Enterprise Architecture Team and is build on the conceptual foundation that includes business visioning, development of the Conceptual Architecture principles and models, and the Requirements for Technical Architecture. The Future State Technical Architecture provides the technical guidance to investment managers, systems designers, application developers, and project managers in creating and acquiring information technology products compliant with the long-term technical direction of the Department. It was developed taking full advantage of the EA Process Model adopted by HUDs Enterprise Architecture Program (see HUD Enterprise Architecture Framework, Draft), with additional original engineering effort by the Enterprise Architecture Team, applying principles spelled out in HUDs Conceptual Architecture (see Attachment A, Enterprise Architecture Principles) to the results of an extensive best practices analysis of current technologies, HUDs current state architecture, using Requirements for Technical Architecture (RTAs) as the functional requirement framework. Technical Future State ArchitectureVersion 1.1 6/8/2010Page 3 of 12 4. Technical Approach and TaxonomyIn the traditional Enterprise Architecture framework that HUD had adopted, four layers of focus are defined: Business, Information, Applications and Technology. Recognizing the importance of public outreach in a Federal agency, HUDs EA Practice defined the Stakeholder layer that provides additional focus on the business process participants. From the product focus standpoint, we logically distinguish between Business Architecture, interested in the business process, process participants, and process-centric information flows, and Technical Architecture that defines technical components of the enterprise that are deployed in response to business needs. (Fig. 1) Business ArchitectureStakeholder Business S1: PresentationKT101: HTML/XML Rendering S5: Communications KT501: Clustering and High Availability ServicesKT102: API ManagementServicesKT502: Network-Attached StorageKT103: Multimedia Delivery KT503: Monitoring and Administration KT104: Hardware Access KT504: Packet DeliveryKT105: Watchlist TechnologiesKT505: Physical ConnectivityInformation S2: ApplicationKT201: Network-Centric Services Technical Architecture KT202: Distributed CodeKT203: Monolithic CodeS6: SecurityKT601: Authentication KT204: Watchlist Technologies Services KT602: Encryption ApplicationsComponent-based KT603: Filtering KT604: Monitoring and Detection Technical ArchitectureKT605: Auditing and Logging S3: Middleware and KT301: Caching and optimizationIntegration Services KT302: Transaction Management & Integration KT303: Load Balancing and IntegrationKT304: Watchlist Techologies S7: PlatformKT701: Client Platform ServicesTechnologyKT702: Production Server PlatformKT703: Development PlatformS4: Data and ObjectKT401: MetadataKT704: Watchlist Platform Management Services KT402: Database ManagementKT403: Object Management KT 404: Data DeliveryKT 405: Watchlist Technologies2/5/2003 Figure 1. Technical Architecture vis the Five-Layer EA FrameworkThe Future State Technical Architecture consists of two components: HUD Future State Technical Architecture Framework (this document), and Future State Technical Architecture Implementation Guidelines. The Future State Technical Architecture Framework includes a Technical Architecture Taxonomy and a Technical Reference Model. The TA Taxonomy is a result of original engineering effort by HUDs EA Team. The Technical Reference Model is based on the TA Taxonomy and was influenced by the Technical Reference Models developed by META Group1 and the Gartner Group2. Taxonomically we view the information processing services continuum as a four-level- deep hierarchy consisting (from top to bottom) of Functional Services, Key Technologies, Architectural Components and Products. For example, HTML Rendering is a key technology within the Functional Services area of Presentation Services. An HTML1 Business Case for Reuse: a Decision-Making Framework for Enterprise Architects and Infrastructure Development, META Practice Vol. 5, No. 5, June 2001 2 IT 2002 Conference Proceedings, Gartner Group, 2002.Technical Future State ArchitectureVersion 1.1 6/8/2010Page 4 of 12 5. Browser is an architectural component within this Key Technology, and Microsoft Internet Explorer (current version 6.02) is a product representing this Architectural Component. A fully developed Future State Technical Architecture would thus contain a set of recommended choices at each level of the hierarchy, with appropriate Implementation Guidelines, mapped to HUDs Requirements for Technical Architecture (see Attachment B), in turn derived from its Common Requirements Vision and implemented through the development of Segment Architectures. In developing the Future State Technical Architecture, the EA Team relied heavily on HUDs Conceptual Architecture Models (Fig. 1) and elements of technical architecture guidance from the Federal CIO Council. Technology selections and product choice decisions were driven by the following factors: Relevance to HUDs business needs as defined in Requirements for TechnicalArchitecture, and results of the Segment Architecture development. Support for EA Principles relevant to the technical architecture; Compliance and/or support of industry standards; Market share and market dominance; Past and current HUD investments in technology, products and support skills; Long-term technical viability of the technology, product and vendor; Market trend analyses from independent sources. Technical Future State ArchitectureVersion 1.1 6/8/2010Page 5 of 12 Fig. 2. Technical Architecture Taxonomy 6. Presentation Services Private Access Protected AccessPublic Access(Intranet)(Extranet)(Internet) Application ServicesProcess Management CollaborationIntegration Services Integration Performance Enhancement Data and Object Management Services Metadata Management Transaction HandlingDecision SupportObject Management Figure 3: HUD Conceptual Architecture, Functional Model mapped to TA ServicesThe TA Framework was developed in order to provide structure and hierarchical reference to the recommendations and designs of the Technical Architecture. This Framework is fully compliant with the Future State Conceptual Models, and seems useful to both understand and communicate technical concepts and choices set forth in the Future State Technical Architecture.FunctionalServices Key Technologies Architectural Components Products Figure 2. Technical Architecture Taxonomy Technical Future State Architecture Version 1.1 6/8/2010 Page 6 of 12 7. The Information Technology continuum is being viewed as a set of services developed, acquired or provided to end users by a set of delivery mechanisms. Since HUD made a decision to outsource its technical infrastructure services and thus, most of the IT delivery mechanisms, to an Information Technology Services provider under the HITS contract, we decided not to develop the delivery mechanisms area at the same level of detail as core data processing and information delivery services. Recognizing the importance of specifying the functional and performance interface between information processing services and delivery mechanisms (infrastructure services), we will develop these interface specifications to a higher level of detail in future releases of the Technical Architecture. Technical Future State ArchitectureVersion 1.1 6/8/2010Page 7 of 12 8. Technical Architecture PrinciplesPreviously developed EA Principles and Requirements for Technical Architecture are too generic to serve as direct inputs into the Future State Technical Architecture. Following is a set of Technical EA Principles that should be used as design principles in subsequent engineering analyses, technology and product identification and market trend mapping. 1. HUD is committed to fully leverage functional and technological benefits of

Popular Tags:

Click here to load reader

Embed Size (px)
Recommended