单项选择题 For nearly ten years, the Unified Modeling Language (UML) has been the industry standard for visualizing, specifying, constructing, and documenting the 1 of a software-intensive system. As the 2 standard modeling language, the UML facilitates communication and reduces confusion among project 3 The recent standardization of UML 2.0 has further extended the language's scope and viability. Its inherent expressiveness allows users to 4 everything from enterprise information systems and distributed Web-based applications to real-time embedded systems. The UML is not limited to modeling software. In fact, it is expressive enough to model 5 systems, such as workflow in the legal system, the structure and behavior of a patient healthcare system, software engineering in aircraft combat systems, and the design of hardware. To understand the UML, you need to form a conceptual model of the language, and this requires learning three major elements: the UML's basic building blocks, the rules that dictate how those building blocks may be put together, and some common mechanisms that apply throughout the UML.
1.
A.classes
B.components
C.sequences
D.artifacts
A B C D
D
2.
A.real
B.legal
C.de facto
D.illegal
A B C D
C
3.
A.investors
B.developers
C.designers
D.stakeholders
A B C D
D
4.
A.model
B.code
C.test
D.modify
A B C D
A
5.
A.non-hardware
B.non-software
C.hardware
D.software
A B C D
B
People are indulging in an illusion whenever they find themselves explaining at a cocktail (鸡尾酒) party, say, that the are "in computers", or " in telecommunications", or "in electronic funds transfer". The implication is that they are part of the high-tech world. Just between us, they usually aren't. The researchers who made fundamental breakthroughs in those areas are in a high-tech business. The rest of us are 6 of their work. We use computers and other new technology components to develop our products or to organize our affairs. Because we go about this work in teams and projects and other tightly knit working group (紧密联系在一起的工作小组), we are mostly in the human communication business. Our successes stem from good human interactions by all participants in the effort, and our failures stem from poor human interactions. The main reason we tend to focus on the 7 rather than the human side of work is not because it's more 8 , but because it's easier to do. Getting the new disk drive installed is positively trivial compared to figurine out why Horace is in a blue funk (恐惧) or why Susan is dissatisfied with the company aver only a few months. Human interactions are complicated and never very crisp (干脆的,干净利落的) and clean in their effects, but they matter more than any other aspect of the work. If you find yourself concentrating on the 9 rather than the 10 . you're like the vaudeville character (杂耍人物) who loses his Keys on a dark street and looks for them on the adjacent street because, as he explains, "The light is better there!"
6.
A.creators
B.innovators
C.appliers
D.inventors
A B C D
C
7.
A.technical
B.classical
C.social
D.societal
A B C D
A
8.
A.trivial
B.crucial
C.minor
D.insignificant
A B C D
B
9.
A.technology
B.sociology
C.physiology
D.astronomy
A B C D
A
10.
A.technology
B.sociology
C.physiology
D.astronomy
A B C D
B
NAC's (Network Access Control) role is to restrict network access to only compliant endpoints and 11 users. However, NAC is not a complete LAN 12 solution; additional proactive and 13 security measures must be implemented. Nevis is the first and only comprehensive LAN security solution that combines deep security processing of every packet at 100Gbps, ensuring a high level of security plus application availability and performance. Nevis integrates NAC as the first line of LAN security 14 In addition to NAC, enterprises need to implement role-based network access control as well as critical proactive security measures-real-time, multilevel 15 inspection and microsecond threat containment.
11.
A.automated
B.distinguished
C.authenticated
D.destructed
A B C D
C
12.
A.crisis
B.security
C.favorable
D.excellent
A B C D
B
13.
A.constructive
B.reductive
C.reactive
D.productive
A B C D
C
14.
A.defense
B.intrusion
C.inbreak
D.protection
A B C D
A
15.
A.port
B.connection
C.threat
D.insurance
A B C D
C
Soon, more of the information we receive via the Internet could come 16 in digital wrappers. Wrappers are made up 17 software code that's targeted to do specific things with the data 18 within them, such as helping to define queries for search engines. They also keep 19 from 20 access to that code.
16.
A.package
B.packaged
C.packages
D.packaging
A B C D
B
17.
A.of
B.off
C.on
D.out
A B C D
A
18.
A.close
B.closed
C.enclose
D.enclosed
A B C D
D
19.
A.insiders
B.money
C.outsiders
D.warehouse
A B C D
C
20.
A.gain
B.gained
C.gains
D.gaining
A B C D
D
The purpose of the requirements definition phase is to produce a clear, complete, consistent, and testable 21 of the technical requirements for the software product. During the requirements definition phase, the requirements definition team uses an iterative process to expand a broad statement of the system requirements into a complete and detailed specification of each function that the software must perform and each 22 that it must meet. The starting point is usually a set of high-level requirements from the 23 that describe the project or problem. In either case, the requirements definition team formulates an overall concept for the system and then defines 24 showing how the system will be operated, publishes the system and operations concept document, and conducts a system concept review (SCR). Following the SCR, the team derives 25 requirements for the system from the high-level requirements and the system and operations concept. Using structured or object-oriented analysis the team specifies the software functions and algorithms needed to satisfy each detailed requirement.
21.
A.function
B.definition
C.model
D.statement
A B C D
D
22.
A.criterion
B.standard
C.scenarios
D.system
A B C D
A
23.
A.producer
B.customer
C.specification
D.analyser
A B C D
B
24.
A.rules
B.principles
C.programmer
D.scenes
A B C D
C
25.
A.detailed
B.outlined
C.total
D.complete
A B C D
A
Virtualization is an approach to IT that pools and shares 26 so that utilization is optimized and supplies automatically meet demand. Traditional IT environments are often silos, where both technology and human 27 . are aligned around an application or business function. With a virtualized 28 , people, processes, and technology are focused on meeting service levels, 29 is allocated dynamically, resources are optimized, and the entire infrastructure is simplified and flexible. We offer a broad spectrum of virtualization 30 that allows customers to choose the most appropriate path and optimization focus for their IT infrastructure resources.
26.
A.advantages
B.resources
C.benefits
D.precedents
A B C D
B
27.
A.profits
B.costs
C.resources
D.powers
A B C D
C
28.
A.system
B.infrastructure
C.hardware
D.link
A B C D
B
29.
A.content
B.position
C.power
D.capacity
A B C D
D
30.
A.solutions
B.networks
C.interfaces
D.connections
A B C D
A
Why is 31 fun? What delights may its practitiopect as his reward? First is the sheer joy of making things. As the child delights in his mud pie, so the adult enjoys building things, especially things of his own design. Second is the pleasure of making things that are useful to other people. Third is the fascination of fashioning complex puzzle-like objects of interlocking moving parts and watching them work in subtle cycles, playing out the consequences of principles built in from the beginning. Fourth is the joy of always learning, which springs from the 32 nature of the task. In one way or another the problem is ever new, and its solver learns something: sometimes 33 , sometimes theoretical, and sometimes both. Finally, there is the delight of working in such a tractable medium. The 34 , like the poet, works only slightly removed from pure thought-stuff. Few media of creation are so flexible, so easy to polish and rework, so readily capable of realizing grand conceptual structures. Yet the program 35 , unlike the poet's words, is real in the sense that it moves and works, producing visible outputs separate from the construct itself. It prints results, draws pictures, produces sounds, moves arms. Programming then is fun because it gratifies creative longings built deep within us and delights sensibilities we have in common with all men.
31.
A.programming
B.composing
C.working
D.writing
A B C D
A
32.
A.repeating
B.basic
C.non-repeating
D.advance
A B C D
C
33.
A.semantic
B.practical
C.lexical
D.syntactical
A B C D
B
34.
A.poet
B.architect
C.doctor
D.programmer
A B C D
D
35.
A.construct
B.code
C.size
D.scale
A B C D
A
Observe that for the programmer, as for the chef, the urgency of the patron (顾客) may govern the scheduled completion of the task, but it cannot govern the actual completion. An omelette (煎鸡蛋) , promised in two minutes, may appear to be progressing nicely. Butwhen it has not set in two minutes, the customer has two choices--waits or eats it raw. Software customers have had 36 choices. Now I do not think software 37 have less inherent courage and firmness thanchefs, nor than other engineering managers. But false 38 to match the patron's desireddate is much more common in our discipline than elsewhere in engineering. It is very 39 to make a vigorous, plausible, and job risking defense of an estimate that is derived by no quantitative method, supported by little data, and certified chiefly by the hunches of the managers. Clearly two solutions are needed. We need to develop and publicize productivity figures, bug-incidence figures, estimating rules, and so on. The whole profession can only profit from 40 such data. Until estimating is on a sounder basis, individual managers will need to stiffen their backbones and defend their estimates with the assurance that their poor hunches are better than wish derived estimates.
36.
A.no
B.the same
C.other
D.lots of
A B C D
B
37.
A.Testers
B.constructors
C.managers
D.architects
A B C D
C
38.
A.Tasks
B.jobs
C.Works
D.scheduling
A B C D
D
39.
A.easy
B.difficult
C.simple
D.painless
A B C D
B
40.
A.sharing
B.excluding
C.omitting
D.ignoring
A B C D
A
Ravi, like many project 41 , had studied the waterfall model of software development as the primary software life-cycle 42 . He was all set to use it for an upcoming project, his first assignment. However, Ravi found that the waterfall model could not be used because the customer wanted the software delivered in stages, something that implied that the system had to be delivered and built in 43 and not as 44 . The situation in many other projects is not very different. The real world rarely presents a problem in which a standard process, or the process used in a previous project, is the best choice. To be the most suitable, an existing process must be 45 to the new problem. A development process, even after tailoring, generally cannot handle change requests. To accommodate change requests without losing control of the project, you must supplement the development process with a requirement change management process.