Each program module is compiled separately and the resulting(73) files are linked ether to make an executable application.A．objectB．sourceC．assemblerD．library
Each program module is compiled separately and the resulting(73) files are linked ether to make an executable application.
A．object
B．source
C．assembler
D．library
相关考题：
● A transport layer protocol has several responsibilities. One is to create a process-to-process (program-to-program) communication; TCP uses port （71） to accomplish this. Another responsibility of a transport layer protocol is to create a （72） and error-control mechanism at the transport level. TCP uses a sliding （73） protocol to achieve flow control. It uses the acknowledgment packet, time-out, and retransmission to achieve （74） control. The transport layer is also responsible for providing a connection mechanism for the application program. The application program sends （75） of data to the transport layer. It is the responsibility of the transport layer at the sending station to make a connection with the receiver.（71）A. numbersB. connectionsC. diagramsD. resources（72）A. procedureB. functionC. routeD. flow（73）A. pathB. windowC. frameD. diagram（74）A. packetB. timeC. errorD. phase（75）A. portsB. streamsC. packetsD. cells
● To document your code can increase program （72） and make program easier to （73）.（72）A. reliabilityB. securityC. readabilityD. usability（73）A. executeB. interpretC. compileD. maintain
A transport layer protocol has several responsibilities. One is to create a process-to-process (program-to-program) communication; TCP uses port (71) to accomplish this. Another responsibility of a transport layer protocol is to create a (72) and error-control mechanism at the transport level. TCP uses a sliding (73) protocol to achieve flow control. It uses the acknowledgment packet, time-out, and retransmission to achieve (74) control. The transport layer is also responsible for providing a connection mechanism for the application program. The application program sends (75) of data to the transport layer. It is the responsibility of the transport layer at the sending station to make a connection with the receiver.（71）A．numbersB．connectionsC．diagramsD．resources
For many years, the principle goal of computer(73)was to write short pieces of code that would execute quickly. The(74)needed to be small, because memory was expensive, and it needed to be fast, because processing power was also expensive.A．usersB．programmersC．thatD．program
●Unit testing refers to that each (73) is tested to ensure that it operates correctly.(73)A. subsystemB.deviceC.applicationD.module
Program（73）describes program's objectives, desired output, input data required, processing requirement, and documentation.A.specificationB.flowchartC.structureD.address
A management domain typically contains a large amount of management information. Each individual item of（71） information is an instance of a managed object type. The definition of a related set of managed （72）types is contained in a Management Information Base (MIB)module. Many such MIB modules are defined. For each managed object type it describes, a MIB （73） defines not only the semantics and syntax of that managed object type, but also the method of identifying an individual instance so that multiple （） of the same managed object type can be distinguished. Typically, there are many instances of each managed object （75） within a management domainA.packetsB.searchesC.statesD.instances
A management domain typically contains a large amount of management information. Each individual item of（） information is an instance of a managed object type. The definition of a related set of managed （72）types is contained in a Management Information Base (MIB)module. Many such MIB modules are defined. For each managed object type it describes, a MIB （73） defines not only the semantics and syntax of that managed object type, but also the method of identifying an individual instance so that multiple （74） of the same managed object type can be distinguished. Typically, there are many instances of each managed object （75） within a management domainA.rotation B.switchC.management D.transmission
A management domain typically contains a large amount of management information. Each individual item of（71） information is an instance of a managed object type. The definition of a related set of managed （72）types is contained in a Management Information Base (MIB)module. Many such MIB modules are defined. For each managed object type it describes, a MIB （73） defines not only the semantics and syntax of that managed object type, but also the method of identifying an individual instance so that multiple （74） of the same managed object type can be distinguished. Typically, there are many instances of each managed object （） within a management domainA.device B.state C.type D.packet
A management domain typically contains a large amount of management information. Each individual item of（71） information is an instance of a managed object type. The definition of a related set of managed （）types is contained in a Management Information Base (MIB)module. Many such MIB modules are defined. For each managed object type it describes, a MIB （73） defines not only the semantics and syntax of that managed object type, but also the method of identifying an individual instance so that multiple （74） of the same managed object type can be distinguished. Typically, there are many instances of each managed object （75） within a management domainA.path B.object C.route D.packet