ImageVerifierCode 换一换
格式:PPT , 页数:18 ,大小:795.53KB ,
文档编号:2495121      下载积分:18 文币
快捷下载
登录下载
邮箱/手机:
温馨提示:
系统将以此处填写的邮箱或者手机号生成账号和密码,方便再次下载。 如填写123,账号和密码都是123。
支付方式: 支付宝    微信支付   
验证码:   换一换

优惠套餐
 

温馨提示:若手机下载失败,请复制以下地址【https://www.163wenku.com/d-2495121.html】到电脑浏览器->登陆(账号密码均为手机号或邮箱;不要扫码登陆)->重新下载(不再收费)。

已注册用户请登录:
账号:
密码:
验证码:   换一换
  忘记密码?
三方登录: 微信登录  
下载须知

1: 试题类文档的标题没说有答案,则无答案;主观题也可能无答案。PPT的音视频可能无法播放。 请谨慎下单,一旦售出,概不退换。
2: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。
3: 本文为用户(三亚风情)主动上传,所有收益归该用户。163文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知163文库(点击联系客服),我们立即给予删除!。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 本站仅提供交流平台,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

版权提示 | 免责声明

1,本文(TOGAF技术架构内容介绍ppt课件.ppt)为本站会员(三亚风情)主动上传,163文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。
2,用户下载本文档,所消耗的文币(积分)将全额增加到上传者的账号。
3, 若此文所含内容侵犯了您的版权或隐私,请立即通知163文库(发送邮件至3464097650@qq.com或直接QQ联系客服),我们立即给予删除!

TOGAF技术架构内容介绍ppt课件.ppt

1、TOGAFTOGAF技术架构内容介绍技术架构内容介绍1 12 2目的映射应用架构阶段定义的应用构建到一系列技术构建,这些技术构建表现为从市场得到的或组织内配置在技术平台里的硬件和软件由于定义了架构解决方案的物理实现,技术架构与实施和迁移计划联系紧密技术架构将定义技术组合的基线和目标视图,详细的面向目标架构的路线图,以及识别路线图中关键的工作包3 3技术架构阶段的方法识别主要应用构件需求(无论是内部还是行业,在需求和可用间选择)检查技术参考模型和目标状态(特别是建立定义好的重用构建快)定义成本模型和时间模型更多考虑外包、采购、租赁、更新期、通用部署、产品开发、测试等4 4技术架构储藏库已有的IT

2、服务目录TOGAF的TRM通用的技术模型,如TMF5 5技术架构开发方法输入6 6外部外部 参考资料参考资料 架构参考资料(P2) 产品候选信息非架构的非架构的输入输入 架构工作要求书(P7) 能力评估(P4)沟通计划(P4)架构的输入架构的输入企业架构组织模型定制的架构框架技术原则架构工作说明书架构愿景架构储藏库(可重用的构建块、共用的参考模型、组织特定参考模型、组织标准)架构定义文档草稿架构需求规格说明书草稿架构路线图的业务、数据和应用架构构件输入输入优化和更新架构愿景阶段的交付物优化和更新架构愿景阶段的交付物 架构工作说明书(P8) 验证的技术原则和新技术原则架构定义文档草稿架构定义文档

3、草稿 基线技术架构1.0版 目标技术架构1.0版(技术构件以及信息系统的关系、技术平台、环境及位置、预计的处理量和在技术构件上的分布、物理(网络)通信、硬件和网络规格等) 技术架构相关视图架构需求规格书草稿架构需求规格书草稿 差距分析结果 阶段B和C的需求输出 更新的技术需求输出输出7 7技术架构开发步骤下面是完成技术架构主要活动的列表,在十几架构开发中可能有不同的顺序活动包括:选择参考模型、视点和工具开发基准技术架构描述开发目标技术架构描述进行差距分析定义路线图构件解决跨架构图景的影响进行利益相关者的正式审查最终确定技术架构建立架构定义文档SWOT分析技术架构对业务流程改进和实施后支持人员的

4、影响细节技术模型的类型开发方法选择-自建、外包等成本和时间模型对标准和技术业务周期的影响8 8参考模型 TRM移植性交互性尽量减少交互的变化Figure 43-1 Technical Reference Model Figure 43-1 Technical Reference Model High-Level High-Level ViewView9 9TRM 细节图The three entities: Application Software (see Section 43.3.3) Application Platform (see Section 43.3.4) Communicat

5、ions 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)1010A APPLICATIONPPLICATION S SOFTWAREOFTWARE1. Business Business ApplicationsApplications which implement business processes

6、 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 Infrastructure ApplicationsApplications which provide general-purpose business functiona

7、lity, based on infrastructure ser vices.1111EXAMPLES 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 industry1212EXAMPLES OF INFRASTRUCTURE APPLIC

8、ATIONSElectronic payment and funds transfer servicesElectronic mail client servicesPublish and subscribeIntelligent agentsCalendaring and scheduling servicesGroupware servicesWorkflow servicesSpreadsheetsPresentation softwareDocument editing and presentationManagement applications, performing genera

9、l-purpose system and network management functions for the system administratorSoftware engineering tools, providing software development functions for systems development staff1313A APPLICATIONPPLICATION P PLATFORMLATFORMPlatform ConceptIt is important to recognize that the Application Platform in t

10、he 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 Appl

11、ication 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 server, application server, Inter net server, database server, etc.,Extendi

12、ng 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

13、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.1414C COMMUN

14、ICATIONSOMMUNICATIONS I INFRASTRUCTURENFRASTRUCTUREThe Communications Infrastructure provides the basic services to interconnect systems interconnect systems and provide the basic basic mechanisms mechanisms for opaque transfer of data. It contains the hardware and software elements which make up th

15、e networking networking and physical communications links 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 provide

16、rs, 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 Internet as the basis of a Communications a Communications Infrastructure for enter

17、prise integration. This is causing a rapid increase in Inter net usage and a steady increase net usage and a steady increase in the range of applications linking to the network for distributed operation.1515A APPLICATIONPPLICATION P PLATFORMLATFORM I INTERFACENTERFACEThe Application Platform Interfa

18、ce (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 w

19、ork, the API definition API definition must include the syntax syntax and semantics 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

20、 and the platform to the architected API. That is, the platform must support the API must support the API as specified, and the application must use must use no more than the no more than the specified APIspecified API.The API specifies a complete interface between an application and one or more ser

21、vices 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.1616C COMMUNICATIONSOMMUNICATIONS I INFRASTRUCTURENFRASTRUCTURE I INTERFACENTERFACEThe Communications Infrastructure Interface

22、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 diver

23、sity, 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 core set of services that can

24、 be guaranteed to be supported by every IP-based network, as the foundation on which to build todays interoperable enterprise computing environments.1717Q QUALITIESUALITIESThere is a set of attributes or qualities that are applicable across the components. For example, for the management service to

25、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 securit

26、y. The proper system-wide implementation of security requires not only a set of Security not only a set of Security servicesservices, corresponding to the security services category shown in the platform, but also the support also the support (i.e., the security awareness) of of software in software

27、 in other parts of the TRMother 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 se

28、rvices must co-operate in making the file secure.Qualities are specified in detail during the development of a Target detail during the development of a Target ArchitectureArchitecture. 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. 1818

侵权处理QQ:3464097650--上传资料QQ:3464097650

【声明】本站为“文档C2C交易模式”,即用户上传的文档直接卖给(下载)用户,本站只是网络空间服务平台,本站所有原创文档下载所得归上传人所有,如您发现上传作品侵犯了您的版权,请立刻联系我们并提供证据,我们将在3个工作日内予以改正。


163文库-Www.163Wenku.Com |网站地图|