204.B基于Web的科研信息管理系统的设计外文文献翻译.doc

《204.B基于Web的科研信息管理系统的设计外文文献翻译.doc》由会员分享，可在线阅读，更多相关《204.B基于Web的科研信息管理系统的设计外文文献翻译.doc（9页珍藏版）》请在三一办公上搜索。

1、学校代码： XXX学 号：XXX 本科毕业设计外文文献翻译（学生姓名：XXX学 院：信息工程学院系 别：计算机系专 业：软件工程班 级：软件06指导教师：XXX 讲 师二一年六月WWW-BASED RELIABILITY INFORMATION SYSTEMSo-Yeon LEE, Jai-Sang KohReliability Engineering TeamElectronics and Telecommunications Research Institute161 Kajong-Dong, Yuseng-Gu, Taejon, 305-350, KoreaE-mail : syleee

2、tri.re.krABSTRACTThis paper discusses the reliability information system developed with the concept of world wide web (WWW) and client/server architecture. An existing server and client for the system are modified to perform HTTP duties and graphically advanced reliability analysis. The technical ba

3、ckground and the relationship of the WWW and client/server system is explained. With the developed system, the design engineers and reliability analysts can analyze the reliability of the system more quickly and conveniently. ? 1998 Elsevier Science Ltd. All rights reserved.KEYWORDS: Information sys

4、tem, WWW, client/server architecture, reliability1. INTRODUCTIONInformation systems are used in many practical applications and sometimes it is very useful for decision making. The accepted notion for the information system is that it should model the flow of information in a given organizational st

5、ructure. In reliability engineering, researchers are faced with several difficult tasks in accessing and analyzing data. Most data are accumulated in the system development site apart from the reliability analysts site. In case of component data, the application-specific data (for example, applied s

6、tress levels, number of functional pins, etc.) which is designed by system developers are important when computing failure rate of each component. It is important to obtain such data at a right moment for concurrent engineering. The client/server approach is perceived as an effective way to integrat

7、e computing resources in an organization. Users can share data, applications, and processing power in the client/server environment much easier than in the traditional centralized computing environment. The ability to balance the work load between clients and servers depending on the application is

8、a key feature of the client/server system. The world wide web(WWW) has evolved into a vehicle supporting interactive data visualization and distribution. WWW greatly owns its success in the standardization aspect with the information being exchanged the clients and server. And also WWW-based systems

9、 can be built rapidly since no special resources are required when developing the client and server software or network protocols. In this paper, we describe the implementation of the reliability information system based on the technology of WWW and Client/Server. Section 2 provides a brief overview

10、 of WWW applied to the client/server computing. Section 3 introduces the implementation details of the reliability information system. And the conclusion and further study will be discussed in Section 4.2. WWW AND CLIENT-SERVER ARCHITECTUREClient/server architecture can be explained as the relations

11、hip between two processes that are cooperating to perform some tasks. R supports the scalability and the integrity of an information system. Lyu (1995) discussed the four benefits of the client/server environment such as lower cost, higher productivity, longer system life cycle, and better usability

12、. Therefore, the client/server system architecture is considered as a feasible framework for information systems. With the advent of the WWW, the most easiest way of implementing the client/server architecture is to use web browser where the client so ware does nothing more than display and format i

13、nformation retrieved from the server. Several kinds of retrieval system for bibliography are the representative examples. By using a web browser as the platform for client to access an existing client/server system, only one set of code(the HTML and helper code) for the system needs to be maintained

14、. But in the case of other systems, where the client software performs additional tasks on behalf of the server or the users, the mediator is needed to perform this work for the web browser-based clients. The typical solution is to use common gateway interface (CGI) programs. But this method is unsa

15、tisfactory for various reasons. With a CGIbased system, all work, normally done by the client, must be emulated by the CGI programs. Therefore it adds more load to the server machine. Another approach of accessing client/server applications from standard WWW browsers was made by Dossick and Kaiser.

16、They suggested a scheme to use a HTTP proxies as a method of connecting an existing client/server system to the web. This HTTP proxy intercepts HTTP requests for data and transforms them into requests for the legacy system using its native protocols. It is possible to use browser-specific tools like

17、 Netscapes Plug-In APIs to create web browser based clients for client/server systems. However, using these APls limits the use of the resulting web-based client sofivcare to specific platforms and specific web browsers. This is an unnecessary limitation which negates many benefits of creating a web

18、-based client.3. IMPLEMENTED SYSTEMElectronics and Telecommunications Research Institute(ETRI) has developed the reliability information system called the ERIS. It computerized the calculation of the component failure rates and the reliability of a complex system. The client program of the ERIS cons

19、isted of two independent programs having different hardware platform, workstaion and personal computer. It was inconvenient to the users who are not familiar with UNIX environment. The special requirements for reliability software tools are pointed out by Birolini. In order to be a useful tool for u

20、sers, having a large component database is the very important compared to other requirements. Under the standalone computing environment, users should own the component data storage independently. It will be waste of computing resources and time. The most available tools are standalone so it is very

21、 inconvenient to share component data between users. Considering the above requirements and opinions collected from field trial of the ERIS, we draw the following items. User-friendly human interface : The man-machine interface is important for efficient handling of large amount of data. Also it is

22、helpful understanding the overall results of an analysis.Openness : The information service must be broadly accessible. Openness also reflects in the end users possibilities to easily integrate reliability information into other application for use in the client station. Data sharing : Once the comp

23、onent data had been entered into DBMS, then the data should be shared with other users. User management : User information database will efficiently handle the increasing number of users.Security : An appropriate security must be considered to prevent the design data being opened to outside.Only the

24、 users who have correct identification number (ID) and password can access server database. Based on the above requirements, the ERIS has been developed with following characteristics. The functions of the system are classified by two categories: user/component database management and reliability an

25、alyses.We applied the combined WWW method of access and legacy client/server architecture to ERIS. Web browser is commonly used efficiently by the general users in displaying and formatting information retrieved from a server database. ERIS applied the web browser concept in user management. Users c

26、an request an ID for use of the ERIS through homepage. Once he/shes ID is registered to user DB, he/she can download ERIS client program anywhere. The client programs of the ERIS are implemented as windows programs. They handle application-specific functions that the original clients handled on beha

27、lf of the server. They have a more easy-to-access and user-friendly interfaces which supplies a good foundation for incorporating reliability studies into the design process. The communication between server process and client process for the request of the standard component data is made through ty

28、pical TCP/IP. Figure 1 shows the combined structure of WWW and client/server architecture in ERIS. The server has two processes such as CGI and COM. CGI module handles the HTTP request from client web browsers and returns corresponding results. COM is a communication process which manages the reques

29、t for component data. There are temporary database filtering the incorrect component and user information. Thus only the verified users and component information can be registered.A workstation with a UNIX operating system is used as a server, and PCs as clients. The INFORMIX database management sys

30、tem is used to manage the user and component data. The server process is implemented using ESQL/C language. Client programs are developed using MS visual C+ and Delphi development kit.4. CONCLUSIONSThe developed system ERIS is widely used by both system developers and reliability analysts. By combin

31、ing the concept of the WWW and the legacy client/server structure, we constructed the reliability design environment directly accessible on the desk of the design engineers. By using WWW, the time needed to distribute and install of the tools is reduced much better than before. Also the ERIS can ser

32、ve other organization through the internet. The growing technology and popularity of the WWW will motivate the change from legacy client/server systems to the totally web-based system.REFERENCES1. J. Lyu. On Developing an Inventory Management System in the Client/Server Environment. Computers andind

33、ustrial engineering, 29, 93-97 (1995).2. R. Orfali, D. Harkey and J. Edwards. Essential ClientServer Survival Guide, Van Nostrand Reinhold, NY (1994).3. E. S. Dossick and E.G. Kaiser. WtVW access to legacy client/server applications. Computer Networks and ISDNSystems, 28, 931-940 (1996).4. M. K. JEO

34、NG, S. Y. LEE, C. O. JEONG and J. S. KOH. ERIS : A Reliability Design Tool forTelecommunication Systems. Computers and industrial engineering, 30, 523-530 (1996).5. A. Birolini. Quality and Reliability of Technical Systems. Springer-Verlag, NY (1994).and component information can be registered.本文摘自：

35、 Computers ind. Engng Vol. 35, Nos 3-4, pp. 599-602, 1998 1998 Elsevier Science Ltd. All rights reservedPrinted in Great BritainPII: S0360-8352(98)00168-5 译文：基于互联网的可靠性信息系统摘要 论文主要讨论的是信息可靠性系统随着广域网和服务器构造的发展。对系统中现有客户和服务器进行修正改造来执行HTTP任务和高级制图分析。同时，文章还对全球信息网的技术背景和关系，以及,客户机/服务器系统做了解释分析。藉由系统开发，设计工程师和可信度分析家可以

36、更为方便快捷地对系统的可靠性进行分析。 关键字：信息系统，WWW，客户机/服务器结构，可靠性1.引言 信息系统有广泛的实际应用性，它还可以对决定性策略做出有用判断。一般认为，信息系统是构建在某一特定组织结构模型数据流程。在可靠性工程学中，研究员在存取和数据分析方面会有一些困难.系统开发过程中积累的多数数据都是从可靠性分析家那里获取的。在成份数据中, 计算机每个成份的故障率时，特定应用数据 ( 举例来说,应用的重要程度，功能引脚的数字,等等.)对于系统开发者的设计来讲都是很重要的。 在组织机构中，客户端/服务器结构被视为整合计算机数据的好方法。与传统集中计算机环境相比，在客户端/服务器环境下，用

37、户共享数据、应用、处理进程都更加容易。平衡工作的能力取决于应用是客户端/服务器系统的重要角色。互联网发展成为了支持交互式数据显示及分发的传输手段。互联网在客户端与服务器交互信息的标准化方面获得了巨大成功。同样，在发展客户端与服务器软件或网络协议时，如果没有要求特殊资源，基于互联网的系统可以迅速被创造。在本章，我们阐述了基于互联网和客户端/服务器技术的可靠性信息系统的实现。第二章概述了客户端/服务器计算的互联网响应。第三章介绍了可靠性信息系统的实现细节，并在第四章进行了进一步的研究总结和讨论。2.互联网和客户端/服务器结构 客户机/服务器结构的关系可以说是两个进程合作运行一些任务。它支持信息系统

38、的完整性和可扩充性。Lyu(1995)论证了客户端/服务器结构的四项优势：成本降低、生产率提高、系统生命周期较长以及更好的可用性。因此，客户端/服务器系统结构被认为是一个可行的信息系统结构。随着互联网的发展，实现客户端/服务器结构的最简单的方法，就是在客户端软件的任务不过是显示及格式化从服务器取得的信息时使用网络浏览器。很多书目检索系统就是代表性的例子。在网络浏览器作为客户端存取一个已存在的客户端/服务器系统的平台时，只有一类系统代码（HTML和帮助代码）需要维护。但对于其他系统，客户端软件在执行代表服务器或用户的额外任务的时候，协调机制需要为基于网络浏览器的客户端运行这些工作。典型的解决办法

39、是使用通用网关接口(CGI)程序。但由于种种原因，这一方法并不理想.。在一个基于CGI的系统中，所有通常由客户端处理的任务必须由CGI程序模拟。因此增加了服务器的负担。另一种从标准互联网浏览器获得客户端/服务器应用的方法是由Dossick和Kaiser发明的。他们提出了一项以HTTP代理连接已存在的客户端/服务器网络系统的计划。HTTP代理拦截HTTP数据请求，并使用原始设定把他们的请求转移向源系统。使用类似于Netscape的嵌入式APIs的浏览器专用工具创建客户端/服务器系统的基于浏览器的客户端是可行的。不过，使用这种APIs把产生的基于网络客户端软件的使用限制在了专用平台以及专用网络浏览

40、器上。这种不必要的限制抵消了很多创建基于网络客户端的好处。3. 系统实施 电子电信研究所(ETRI)开发了叫做ERIS的可靠性信息系统。它可以使用计算机进行合成系统的失误率以及可靠性的计算。ERIS的客户端程序包括由两个中立程序组成，他们处于不同的硬件平台：工作站以及个人电脑上。不熟悉UNIX环境的用户会使用时会不方便。 需要特别指出的是可靠性软件工具是由Birolini提出的。为了成为对用户有用的软件，相对于其它要求，一个够大的数据库是非常重要的。在单机环境下，用户可以拥有独立的数据存储。这将浪费计算机的资源和时间。大多数现有工具都是独立的，用户之间共享数据非常不方便。基于上述在ERIS测试

41、中收集的要求和意见，我们设定了以下元素：-友好的用户界面：人机界面对于有效处理大量数据是非常重要的。同时他对理解分析结果是非常有帮助的。-公开性：信息服务一定是被广泛使用的。开放性同样体现在终端客户的可靠性信息能够被此客户端使用的其他应用轻松获得。-数据共享：一旦部分数据进入DBMS，那么此数据应该可以被其他用户分享。 -用户管理：用户信息存储能够有效处理增加的用户。 -安全性：安全设计必须被适当考虑，以防止设计数据被外界开启。只有拥有唯一正确的用户识别号码(ID)和密码的用户才能进入数据库服务器。基于上述要求，ERIS发展了以下功能。该系统分为以下两类：用户/数据库管理和可靠性分析。我们结合

42、了连接互联网方法以及源客户端/服务器结构开发ERIS。网络浏览器在显示及格式化信息时能够被所有用户有效使用。网络浏览器使用的管理概念适用于ERIS。ERIS允许通过用户管理提出的网络浏览器申请。用户可以通过主页申请ERIS的使用ID。一旦他/她的ID在用户数据库注册，他/她能够在任何地方下载ERIS客户端程序。ERIS客户端程序的实现类似于Windows程序。他们通过利于服务器的原始客户端处理专用应用功能。他们拥有更好的易存储性及用户友好界面，为了合并可靠性学习，他们提供了一个好的查询给设计进程。服务器进程和客户端进程的联系，是符合TCP/IP协议的标准数据要求的。我提供了ERIS的互联网和客

43、户端/服务器结构的组合结构。服务器拥有CGI和COM两个进程。CGI组件解决从客户端网络浏览器发出的HTTP请求并返回对应的结果。COM是管理数据请求的联系进程。有一个临时数据库过滤错误成分及用户信息。只有认证用户及信息数据才可以被注册。服务器是使用UNIX操作系统的工作站，客户端则是PC机。Informix数据库管理系统用来管理用户及数据。服务器进程通过ESQL/C语言实现。客户端程序通过MS Visual C+及Delphi开发工具进行开发。4. 结论 ERIS是设计工程师和可信度分析家普遍采用的开发系统。通过结合互联网和继承客户端/服务器结构的概念，我们在设计引擎的范围，建立了可迅速理解

44、的可靠性设计环境。通过使用互联网，分发安装工具的时间比以前减少了很多。ERIS同样可以通过互联网为其他组织提供服务。互联网的技术发展和流行化将激发传统基于互联网系统向客户端/服务器系统的转变。参考资料 1. J. Lyu. On Developing an Inventory Management System in the Client/Server Environment. Computers andindustrial engineering, 29, 93-97 (1995).2. R. Orfali, D. Harkey and J. Edwards. Essential Clien

45、tServer Survival Guide, Van Nostrand Reinhold, NY (1994).3. E. S. Dossick and E.G. Kaiser. WtVW access to legacy client/server applications. Computer Networks and ISDNSystems, 28, 931-940 (1996).4. M. K. JEONG, S. Y. LEE, C. O. JEONG and J. S. KOH. ERIS : A Reliability Design Tool forTelecommunication Systems. Computers and industrial engineering, 30, 523-530 (1996).5. A. Birolini. Quality and Reliability of Technical Systems. Springer-Verlag, NY (1994).