试题（74）Changes often happen in（74）．（74）A．Initiating Process B．Executing ProcessC．Planning

试题（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

Schedule control is concerned with all the following except (74)

A.influencing the factors that create schedule changes to ensure that the changes are beneficial

B.determing that the schedule has changed

C.managing the actual changes when and as they occur

D.changing the shedule based on customer demands

changes and providing a method to validate approved changes．(74) is not a project configuration management tool．

（74）

A．Rational Clearcase

B．Quality Function Deployment

C．Visual SourceSafe

D．Concurrent Versions System

Changes often happen in（）．

A．Initiating Process

B．Executing Process

C．Planning Process

D．Closing Process

A.learn; from

B.turn; in

C.connect; with

D.changes; into

he software. Configuration managementpractices include configuration identification，change control ，（74）and configuration audit.

A.milstones marking

B.status reporting

C.stakeholder management

D.quality audit

ing on requirements and then controlling changes and communicating to relevant stakeholders. It is a （74 ） process throughout a project. A requirement is a capability to which a project outcome (product or service) should conform.

A.communicating

B.collecting

C.filing

D.documenting

A.at least

B.at once

C.at most

D.at all

What are the changes in the Japanese attitude to work and life？

A、Businessmen often discuss business at nightclubs, where they eat and drink and have a good time.

B、People can talk about business while doing some sports such as golf.

C、They hate work now.

D、They think work is not necessary.

●The presentation layer is concerned with the _(71) and semantics of the informationexchanged between two systems． The processes in two systems are usually exchanginginformation in the form. of character (72)-,numbers, and so on． The information should be changed to bit (73) before ．being transmitted． Because different computers use different encoding systems, the presentation layer is responsible for (74) between these different encoding methods． The presentation layer at the sender changes the information from its sender-dependent format into a common format． The presentation layer at the receiving machine changes the common format into its (75) dependent format．

(71)A．frequency B．syntax C．dialog D．format

(72)A．numbers B．functions C．strings D． codes

(73)A．systems B．characters C．layers D． streams

(74)A．capability B．interoperability C．reliability D．dependability

(75)A．receiver B．user C．server D． customer