● （72）describes, in detail, the project’s deliverables and the work required to create tho

ividual 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 (75) within a management domain

(71) A．rotation

B．switch

C．management

D．transmission

(72) A．path

B．object

C．route

D．packet

(73) A．connection

B．window

C．module

D．destination

(74) A．packets

B．searches

C．states

D．instances

(75) A．device

B．state

C．type

D．packet

“sockets” interface. Although this API was developed for __（71）__ in the early 1980s it has also been implemented on a wide variety of non-Unix systems。 TCP/IP __（72）__ written using the sockets API have in the past enjoyed a high degree of portability and we would like the same __（73）__ with IPv6 applications。 But changes are required to the sockets API to support IPv6 and this memo describes these changes。These include a new socket address structure to carry IPv6 __（74）__，new address conversion functions，and some new socket options。These extensions are designed to provide access to the basic IPv6 features required by TCP and UDP applications，including multicasting， while introducing a minimum of change into the system and providing complete __（75）__ for existing IPv4 applications。

A.Windows

B.Linux

C.Unix

D.DOS

The de facto standard Application Program Interface (API) for TCP/IP applications is the “sockets” interface. Although this API was developed for （71） in the early 1960s it has also been implemented on a wide variety of no-Unix systems. TCP/IP （72） Written using the sockets API have in the past enjoyed a high degree of portability and we would like the same （73） with IPv6 applications. But changes are required to the sockets API to support IPv6 and this memo describes these changes. These include a new socket address structure to carry IPv6 （74） ,new address conversion functions, and some new socket options. These extensions are designed to provide access to the basic IPv6 features requited by TCP and UDP applications, including multicasting, while introducing a minimums of change into the system and providing complete （75） for existing IPv4 applications.

A.Windows

B.Linux

C.Unix

D.DOS

ckets” interface. Although this API was developed for __（71）__ in the early 1980s it has also been implemented on a wide variety ofnon-Unix systems。 TCP/IP __（72）__ written using the sockets API have in the past enjoyed a high degreeof portability and we would like the same __（73）__ with IPv6 applications。 But changes are requiredto the sockets API to support IPv6 and this memo describes these changes。These include a new socket address structure to carry IPv6 __（74）__，new address conversion functions，and some new socket options。These extensions aredesigned to provide access to the basic IPv6 features required by TCP and UDPapplications，including multicasting， while introducing aminimum of change into the system and providing complete __（75）__ for existing IPv4 applications。

A.Windows

B.Linux

C.Unix

D.DOS@@@SXB@@@A.applications

B.networks

C.protocols

D.systems@@@SXB@@@A.portability

B.availability

C.capability

D.reliability@@@SXB@@@A.connections

B.protocols

C.networks

D.addresses@@@SXB@@@A.availability

B.compatibility

C.capability

D.reliability

试题（71）～（75）

The software architecture is a set of software components, subsystems, relationships, interactions, the properties of each of these elements, and the set of guiding principles that together constitute the fundamental properties and constraints of a software system or set of systems. （71） defines a general set of element types and their interactions. The examples include Pipes and Filters, Model-View-Controller, and Reflection. A （72） in software architecture is a representation used to understand or document one or more aspects of a problem or solution. Architecture is usually used in conjunction with many adjunct terms. The （73） defines the key strategies, organization, goals and related processes of the enterprise. At the enterprise level, the （74） may be more of a set of guidelines on how the various software architectures should be constructed consistently across the enterprise. The （75）, which describes the high-level set of elements involved in application from a particular domain along with their interactions, is often used to focus on subsystem definition rather than application process level definition.

（71）

A. Architectural pattern

B. Architectural description

C. Architectural view

D. Architectural viewpoint

（72）

A. model

B. domain

C. component

D. subsystem

（73）

A. enterprise architecture

B. technical architecture

C. infrastructure architecture

D. business architecture

（74）

A. enterprise architecture

B. data architecture

C. application architecture

D. information architecture

（75）

A. product-line architecture

B. reference architecture

C. technology architecture

D. infrastructure architecture

试题(71)～(75)

The analysis phase answers the questions of who will use the system, what the system will do, and where and when it will be used. During this phase, the project team investigates ny current system,identifies (71) , and develops a concept for the new system. This phase as three steps: first, (72) is developed to guide the project team's efforts. It usually ncludes an analysis of the current system and its problems, and the ways to design a new ystem. The next step is (73) The analysis ofthis information - in conjunction withinput rom the project sponsor and many other people - leads to the development of a concept for a ew system. The system concept is then used as a basis to develop a set ofbusiness analysis odels that describes how the business will operate if the new system were developed. The set of models typically includes models that represent the (74) necessary to support the nderlying business process. Last, the analyses, system concepts, and models are combined nto a document called the (75), which is presented to the project sponsor and other key ecision makers that decide whether the project should continue to move forward.

(71) A. improvementopportunities

B. logicalmodel

C. systemrequirements

D. systemarchitecture

(72) A. a user manual

B. an analysis strategy

C. an analysis use case

D. a design user case

(73) A. project scope definition

B. prob,lems analysis

C. decisionanalysis

D. requirementsgathering

(74) A. dataandprocesses

B. systeminfrastructures

C. externalagents

D. systemsoftware

(75) A. requirementsstatement

B. designspecification

C. systemproposal

D. project charter

The analysis phase answers the questions of who will use the system, what the system will do, and where and when it will be used. During this phase, the project team investigates ny current system,identifies (71) , and develops a concept for the new system. This phase as three steps: first, (72) is developed to guide the project team's efforts. It usually ncludes an analysis of the current system and its problems, and the ways to design a new ystem. The next step is (73) The analysis ofthis information - in conjunction withinput rom the project sponsor and many other people - leads to the development of a concept for a ew system. The system concept is then used as a basis to develop a set ofbusiness analysis odels that describes how the business will operate if the new system were developed. The set of models typically includes models that represent the (74) necessary to support the nderlying business process. Last, the analyses, system concepts, and models are combined nto a document called the (75), which is presented to the project sponsor and other key ecision makers that decide whether the project should continue to move forward

A.improvementopportunities

B.logicalmodel

C.systemrequirements

D.systemarchitecture@@@SXB@@@A.a user manual

B.an analysis strategy

C. an analysis use case

D.a design user case@@@SXB@@@A.project scope definition

B.prob,lems analysis

C.decisionanalysis

D.requirementsgathering@@@SXB@@@A.dataandprocesses

B.systeminfrastructures

C.externalagents

D.systemsoftware@@@SXB@@@A.requirementsstatement

B.designspecification

C.systemproposal

D.project charter

A proposal is a formal report that describes a problem

and recommends a solution. ()

A. It describes the reachability of routes in stub areas.

B. It describes the reachability of routes in totally-stubby areas.

C. It describes the reachability of routes in not-so-stubby areas.

D. It describes the reachability of routes in partially-stubby areas.

A.It describes the beginnings and other basic parts of a culture.

B.It describes the beginnings and other basic parts of a culture.

C.It describes the beginnings and other basic parts of a culture.

D.It describes the beginnings and other basic parts of a culture.