ASTM F2218-2002(2015) Standard Guide for Hardware Implementation for Computerized Systems《计算机系统硬件实现的标准指南》.pdf

《ASTM F2218-2002(2015) Standard Guide for Hardware Implementation for Computerized Systems《计算机系统硬件实现的标准指南》.pdf》由会员分享，可在线阅读，更多相关《ASTM F2218-2002(2015) Standard Guide for Hardware Implementation for Computerized Systems《计算机系统硬件实现的标准指南》.pdf（13页珍藏版）》请在麦多课文档分享上搜索。

1、Designation: F2218 02 (Reapproved 2015) An American National StandardStandard Guide forHardware Implementation for Computerized Systems1This standard is issued under the fixed designation F2218; the number immediately following the designation indicates the year oforiginal adoption or, in the case o

2、f revision, the year of last revision. A number in parentheses indicates the year of last reapproval. Asuperscript epsilon () indicates an editorial change since the last revision or reapproval.1. Scope1.1 This guide provides assistance in the choice of comput-ing hardware resources for ship and mar

3、ine environments anddescribes:1.1.1 The core characteristics of interoperable systems thatcan be incorporated into accepted concepts such as the OpenSystem Interconnection (OSI) model;1.1.2 Process-based models, such as the Technical Refer-ence Model (TRM), that rely on interoperable computinghardwa

4、re resources to provide the connection between theoperator, network, application, and information; and,1.1.3 The integrated architecture that can be used to meetminimum information processing requirements for ship andmarine environments.1.2 The use of models such as OSI and TRM provide astructured m

5、ethod for design and implementation of practicalshipboard information processing systems and provides plan-ners and architects with a roadmap that can be easily under-stood and conveyed to implementers. The use of such modelspermit functional capabilities to be embodied within concretesystems and eq

6、uipment.1.3 The information provided in this guide is understood torepresent a set of concepts and technologies that have, overtime, evolved into accepted standards that are proven invarious functional applications. However, the one universalnotion that still remains from the earliest days of inform

7、ationprocessing is that technological change is inevitable.Accordingly, the user of this guide must understand that suchprogress may rapidly invalidate or supersede the informationcontained herein. Nonetheless, the concept of implementingship and marine computing systems based on these functionalpri

8、nciples allows for logical and rational development andprovides a sound process for eventual upgrade and improve-ment.2. Referenced Documents2.1 ASTM Standards:2E1013 Terminology Relating to Computerized Systems(Withdrawn 2000)3F1757 Guide for Digital Communication Protocols for Com-puterized System

9、s2.2 ANSI Standards:4X3.131 Information SystemsSmall Computer SystemsInterface-2 (SCSI-2)X3.172 American National Standard Dictionary for Infor-mation SystemsX3.230 Information SystemsFibre ChannelPhysicaland Signaling Interface (FC-PH)X3.232 Information TechnologySCSI-2 Common AccessMethod Transpor

10、t and SCSI Interface ModuleX3.253 Information SystemsSCSI-3 Parallel Interface(SPI)X3.269 Information TechnologyFibre Channel Protocolfor SCSIX3.270 Information TechnologySCSI-3 ArchitectureModel (SAM)X3.276 Information TechnologySCSI-3 Controller Com-mands (SCC)X3.277 Information TechnologySCSI-3 F

11、ast-20X3.292 Information TechnologySCSI-3 Interlocked Pro-tocol (SIP)X3.294 Information TechnologySerial StorageArchitectureSCSI-2 Protocol (SSA-S2P)X3.297 Information SystemsFibre ChannelPhysicaland Signaling Interface-2 (FC-PH2)X3.301 Information TechnologySCSI-3 Primary Com-mands (SPC)X3.304 Info

12、rmation TechnologySCSI-3 MultimediaCommands (MMC)MS58 Information TechnologyStandard RecommendedPractice for Implementation of Small Computer Systems1This guide is under the jurisdiction of ASTM Committee F25 on Ships andMarine Technology and is the direct responsibility of Subcommittee F25.05 onCom

13、puter Applications.Current edition approved May 1, 2015. Published June 2015. Originallyapproved in 2002. Last previous edition approved in 2008 as F2218 08. DOI:10.1520/F2218-02R15.2For referenced ASTM standards, visit the ASTM website, www.astm.org, orcontact ASTM Customer Service at serviceastm.o

14、rg. For Annual Book of ASTMStandards volume information, refer to the standards Document Summary page onthe ASTM website.3The last approved version of this historical standard is referenced onwww.astm.org.4Available from American National Standards Institute (ANSI), 25 W. 43rd St.,4th Floor, New Yor

15、k, NY 10036, http:/www.ansi.org.ACopyright ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United States1Interface (SCSI-2), (X3.131.1994) for ScannersNCITS 306 Information TechnologySerial StorageArchitectureSCSI-3 Protocol (SSA-S3P)NCITS 309 Information Te

16、chnologySCSI-3 Block Com-mands (SBC)2.3 IEEE Standards:5100 Standard Dictionary for Electrical and Electronic Terms488 Digital Interface for Programmable Instrumentation610.7 Standard Glossary for Computer Networking Termi-nology796 Microcomputer System Bus802.11 Wireless LAN Medium Access Control a

17、nd PhysicalLayer Specifications1003.2d POSIXPart 2 Shell and UtilitiesAmendment:Batch Environment1003.5 Binding for System Application Program Interface(API)1003.b Binding for System Application Programming Inter-face (API)Amendment 1: Real-time Extensions1014 Versatile Backplane Bus: VMEbus1101.10

18、Additional Mechanical Specifications for Micro-computers using the IEEE Std 1101.1 Equipment Practice1155 VMEbus Extensions for Instrumentation: VXIbus1212.1 Communicating Among Processors and PeripheralsUsing Shared Memory (Direct Memory Access DMA)1394 High Performance Serial Bus1496 Chip and Modu

19、le Interconnect Bus: Sbus1394 32-bit Microprocessor Architecture2.4 ISO Standards:41155 Portable Operating System Interface for ComputerEnvironments (POSIX)9945-1 System Application Program Interface (API) Clanguage9945-2 Shell and Utilities2.5 TIA/EIA Standard:6568-A Commercial Building Telecommuni

20、cations CablingStandard3. Significance and Use3.1 This guide is aimed at providing a general understand-ing of the various types of hardware devices that form the coreof information processing systems for ship and marine use.Ship and marine information processing systems require spe-cific devices in

21、 order to perform automated tasks in a special-ized environment. In addition to providing information ser-vices for each individual installation, these devices are oftennetworked and are capable of supplementary functions thatbenefits ship and marine operations.3.2 A variety of choices exists for de

22、ployment of informa-tion processing devices and greatly increases the complexity ofthe selection task for ship and marine systems. The choice of aparticular device or system cannot be made solely on thesingular requirements of one application or function. Moderninformation processing systems are usu

23、ally installed in acomplex environment where systems must be made to interactwith each other. Ship and marine installations add an evenfurther layer of complexity to the process of choosing adequatecomputerized systems. This guide aims to alleviate this task bygiving users specific choices that are

24、proven technologies thatperform in a complex environment.3.3 Hardware resources used in ship and marine installa-tions are a result of careful consideration of utility andfunction. These resources may require some physical special-ization in order to inhabit a particular environment, but they arein

25、no way different from equipment used in shore-basedsituations. Ship and marine computer system configurations,interconnections, and support services are essentially the sameas those found in a land-based network environment and as aresult, the skill sets of ship and marine information processingsyst

26、em users, administrators, and support personnel are inter-changeable with those of shore-based activities.4. Standards Profiles4.1 Standards profiles are sets of specifications bundledtogether to describe the technical standard for a function or aservice (such as operating systems, network, and data

27、 inter-change services), and will include minimum criteria for theinformation and technology that support specific functionalrequirements. Profiles equate to the lowest level process, anddocument agreed-to implementation requirements used inbuilding and operating systems. Systems using the samestand

28、ards, but different options, will probably not interfacecorrectly. The Technical Reference Model (TRM) is useful forassembling standards profiles across technology categories ofComputing Resources, Information Management, and Appli-cations.4.1.1 The TRM identifies and specifies the support services(

29、multimedia, communications, and so forth) and interfaces thatprovide a common operating environment and support the flowof information among enterprise and common support appli-cations. This model represents the computer resources, infor-mation management, and applications categories and interfacesw

30、ith the communication and networking technology categoriesthat are appropriately represented by the ISO Open SystemInterconnect model. The TRM addresses standard profiles thatprovide seamless application support over widely distributedcomputing resources and attendant interfaces between thecomputing

31、 resources and other technologies.4.2 Computing hardware resources represent generally con-sists of Central Processing Unit(s) (CPU), Input and Output(I/O) interfaces, main memory, buses, and peripherals. Theexternal environment considerations that affect computinghardware resource selection are sec

32、urity, communications,real-time, and high availability. The computing hardwareresource provides the environment necessary to support appli-cation software. From the perspective of the applicationsoftware, services are provided by the computing resource,whether the particular services are provided lo

33、cally or remotelyas part of a distributed system.4.3 The architecture needed to support a typical applicationconsists of computers that perform as clients and servers. The5Available from Institute of Electrical and Electronics Engineers, Inc. (IEEE),445 Hoes Ln., P.O. Box 1331, Piscataway, NJ 08854-

34、1331, http:/www.ieee.org.6Available from Telecommunications Industry Association (TIA), 1320 NorthCourthouse Road, Suite 200, Arlington, VA 22201, http:/www.tiaonline.org.F2218 02 (2015)2servers host the primary application software and contain theprocessing power necessary to support multiple users

35、. Serversalso host the data needed to support the application. Thestandard 3-tiered application architecture consists of (1)anapplication server, (2) a data server, and (3) presentation clients(see Fig. 1).4.4 In the future, most application processing software willbe hosted on the server computers.

36、 Clients will use presenta-tion software that connects to the servers using a commoninterface. At that time, client computers will likely be lessexpensive and tailored to the users individual preferencebecause application interoperability will not be a significantfactor.4.5 Today, however, most appl

37、ication software is hosted onthe client and interoperability among clients is a critical factor.Even within the client-server application architecture, applica-tion specific software resident on the client is still prevalent.This demands consistency of client workstations across anentire installatio

38、n to achieve seamless interoperability. Table 1outlines a rationale for the client-server deployment strategy.4.6 Driven by the current state of client-server technology,the general philosophy for implementing computing resourcesis the concept of homogeneous clients and heterogeneousservers. Homogen

39、eous clients facilitate providing a consistentinterface between the user and the system and make systemsupport and maintenance less complex. Heterogeneous serverssupport the various computing requirements of applicationsneeded to support ship and marine operations. The sameadvantages that homogeneou

40、s clients enjoy can be achieved ifservers are homogeneous as well. Independent of whether ornot the server suite employed is heterogeneous orhomogeneous, it is important that they perform their functiontransparently to the user (that is, the user neither knows norcares about the location, number, or

41、 vendor of the server beingused.) Requiring servers to be homogeneous would restrict theintroduction of new server technology, choking innovation andpreventing the installation from taking advantage of advancesin computing such as massively parallel processors.5. Computing Hardware5.1 Computing Reso

42、urcesComputing resources consist ofmany computing hardware components and configurations ofthese components. This section covers the various hardwarecomponents that make up a computing resource system andexamines how these components are commonly configured.5.2 Component TechnologiesThe major hardwa

43、re compo-nents of Computing Resources are the Central Processing Unit(CPU), one or more backplane buses, main memory (bothRAM and cache), Input/Output (I/O) interfaces, and peripher-als. This section will examine each of these areas and provideguidance on the selection of these component technologie

44、s aspart a computing resource system.5.2.1 CPUThe CPU is the “engine” of the computersystem and, combined with the OS (operating system), formsthe core of the computing resource. Since the OS drives manydecisions concerning the computer resource, a CPU that iscompatible with the OS becomes an overri

45、ding factor indetermining the type of CPU. Other than the OS, the mainfactors to consider in determining the type of CPU for thecomputer are processing speed (performance) and cost. Forcomputing resources, such as servers and multiprocessors,scalability of the number of processors can be a significa

46、ntfactor in determining CPU.5.2.2 BusThe computer bus connects the different com-ponents of the computer resource together and allows them topass data between them at high speeds. Computer resourceconfigurations, such as personal workstations, often limit ordetermine the type of bus that will be use

47、d. Often there areFIG. 1 Three-Tiered Application ArchitectureF2218 02 (2015)3multiple buses connected together to allow for multiple typesof component cards or to extend a non-expandable system bus.Considerations in determining the type of bus to use are:number and type of commercial products compa

48、tible with thebus architecture, number of parallel data bit lines, clock speed,and cost. Once the appropriate bus architecture is determined,an important computer resource factor becomes how manyinterface slots are available on the bus for component cards.5.2.2.1 Use buses that provide the necessary

49、 performanceeconomically and are compatible with the board level compo-nents that are needed to meet requirements. For buses thatprovide slots for component cards, use standard buses that aresupported by multiple vendors providing compatible compo-nent cards.5.2.3 Main MemoryMain memory is the storage ware-house of the computer where data and programs are stored forefficient processing. In the context of this section, mainmemory refers to cache and RAM. The main factor to considerin acquisition of a computer system is the quantity (inmegabytes) of