TOGAF技术架构内容介绍.ppt

TOGAF技术架构内容介绍目的映射应用架构阶段定义的应用构建到一系列技术构建，这些技术构建表现为从市场得到的或组织内配置在技术平台里的硬件和软件由于定义了架构解决方案的物理实现，技术架构与实施和迁移计划联系紧密技术架构将定义技术组合的基线和目标视图，详细的面向目标架构的路线图，以及识别路线图中关键的工作包技术架构阶段的方法识别主要应用构件需求（无论是内部还是行业，在需求和可用间选择）检查技术参考模型和目标状态（特别是建立定义好的重用构建快）定义成本模型和时间模型更多考虑外包、采购、租赁、更新期、通用部署、产品开发、测试等技术架构储藏库已有的IT服务目录TOGAF的TRM通用的技术模型，如TMF技术架构开发方法输入外部外部 参考资料参考资料 架构参考资料（P2）产品候选信息非架构的非架构的输入输入 架构工作要求书（P7）能力评估（P4）沟通计划（P4）架构的输入架构的输入企业架构组织模型定制的架构框架技术原则架构工作说明书架构愿景架构储藏库（可重用的构建块、共用的参考模型、组织特定参考模型、组织标准）架构定义文档草稿架构需求规格说明书草稿架构路线图的业务、数据和应用架构构件输入输入优化和更新架构愿景阶段的交优化和更新架构愿景阶段的交付物付物 架构工作说明书（P8）验证的技术原则和新技术原则架构定义文档草稿架构定义文档草稿 基线技术架构1.0版 目标技术架构1.0版（技术构件以及信息系统的关系、技术平台、环境及位置、预计的处理量和在技术构件上的分布、物理（网络）通信、硬件和网络规格等）技术架构相关视图架构需求规格书草稿架构需求规格书草稿 差距分析结果 阶段B和C的需求输出 更新的技术需求输出输出技术架构开发步骤下面是完成技术架构主要活动的列表，在十几架构开发中可能有不同的顺序活动包括：选择参考模型、视点和工具开发基准技术架构描述开发目标技术架构描述进行差距分析定义路线图构件解决跨架构图景的影响进行利益相关者的正式审查最终确定技术架构建立架构定义文档SWOT分析技术架构对业务流程改进和实施后支持人员的影响细节技术模型的类型开发方法选择-自建、外包等成本和时间模型对标准和技术业务周期的影响参考模型 TRM移植性交互性尽量减少交互的变化Figure 43-1 Technical Reference Model High-Level ViewTRM 细节图The three entities:Application Software(see Section 43.3.3)Application Platform(see Section 43.3.4)Communications Infrastr ucture(see Section 43.3.5)n The two interfaces:Application Platform Interface(see Section 43.3.6)Communications Infrastructure Interface(see Section 43.3.7)Application Software1.Business Applications which implement business processes for a particular enterprise or vertical industry.The internal structure of business applications relates closely to the specific application software configuration selected by an organization.2.Infrastructure Applications which provide general-purpose business functionality,based on infrastructure ser vices.Examples of business applications Patient record management services used in the Medical industryInventor y management services used in the Retail industryGeological data modeling services used in the Petroleum industryExamples of Infrastructure applicationsElectronic payment and funds transfer servicesElectronic mail client servicesPublish and subscribeIntelligent agentsCalendaring and scheduling servicesGroupware servicesWorkflow servicesSpreadsheetsPresentation softwareDocument editing and presentationManagement applications,performing general-purpose system and network management functions for the system administratorSoftware engineering tools,providing software development functions for systems development staffApplication PlatformPlatform ConceptIt is important to recognize that the Application Platform in the TOGAF TRM is a single,generic,conceptual entity.From the viewpoint of the TOGAF TRM,the Application Platform contains all possible services.In a specific Target Architecture,the Application Platform will contain only those services needed to support the required functions.Moreover,the Application Platform for a specific Target Architecture will typically not be a single entity,but rather a combination of different entities for different,commonly required functions,such as desktop client,file server,print serverapplication server,Inter net server,database server,etc.,Extending the TRMInterfaces Between ServicesA key goal of architecture development is for service modules to be capable of replacement by other modules providing the same service functionality via the same service API.Future DevelopmentsThe TRM deals with future developments in the Application Platform in two ways.Firstly,as interfaces to services become standardized,functionality which previously for med par t of the Application Software entity migrates to become part of the Application Platform.Secondly,the TRM may be extended with new ser vice categories as new technology appears.Communications InfrastructureThe Communications Infrastructure provides the basic services to interconnect systems and provide the basic mechanisms for opaque transfer of data.It contains the hardware and software elements which make up the networking and physical communications links used by a system,and of course all the other systems connected to the network.It deals with the complex world of networks and the physical Communications Infrastructure,including switches,ser vice providers,and the physical transmission media.A primary driver in enterprise-wide Technology Architecture in recent years has been the growing awareness of the utility and cost-effectiveness of the Internet as the basis of a Communications Infrastructure for enterprise integration.This is causing a rapid increase in Inter net usage and a steady increase in the range of applications linking to the network for distributed operation.Application Platform InterfaceThe Application Platform Interface(API)specifies a complete interface between the Application Software and the underlying Application Platform across which all services are provided.A rigorous definition of the interface results in application portability,provided that both platform and application conform to it.For this to work,the API definition must include the syntax and semantics（句法规则和语义）（句法规则和语义）of not just the programmatic interface,but also all necessary protocol（协议）and data structure definitions.Portability（可移植性）depends on the symmetry of conformance of both applications and the platform to the architected API.That is,the platform must support the API as specified,and the application must use no more than the specified API.The API specifies a complete interface between an application and one or more services offered by the underlying Application Platform.An application may use several APIs,and may even use different APIs for different implementations of the same service.Communications Infrastructure InterfaceThe Communications Infrastructure Interface is the interface between the Application Platform and the Communications Infrastructure.Figure 43-1 seeks to reflect the increasingly important role of the Internet as the basis for inter and intra-enterprise interoperability.The horizontal dimension（维度）of the model in Figure 43-1 represents diversity,and the shape of the model is specifically 明确地intended to emphasize minimum diversity at the interface between the Application Platform and the Communications Infrastructure.In particular,the model emphasizes the importance of focusing on the core set of services that can be guaranteed to be supported by every IP-based network,as the foundation on which to build todays interoperable enterprise computing environments.QualitiesThere is a set of attributes or qualities that are applicable across the components.For example,for the management service to be effective,manageability must be a pervasive（无处不在地）quality of all platform services,applications,and Communications Infrastr ucture services.Figure 43-2 captures this concept by depicting描述 the TRM components sitting on a backplane底板 of qualities.Another example of a service quality is security.The proper system-wide implementation of security requires not only a set of Security services,corresponding to the security services category shown in the platform,but also the support(i.e.,the security awareness)of software in other parts of the TRM.Thus,an application might use a security service to mark a file as read-only,but it is the correct implementation of the security quality in the operating system services which prevents write operations on the file.Security and operating system services must co-operate in making the file secure.Qualities are specified in detail during the development of a Target Architecture.Some qualities are easier than others to describe in terms of standards.For instance,support of a set of locales区域设置 can be defined to be part of the specification for the international operation quality.