試題1

設(shè)某循環(huán)隊(duì)列Q的定義中有front和rear兩個(gè)域變量其中，front指示隊(duì)頭元素的位置，rear指示隊(duì)尾元素之后的位置，如下圖所示。若該隊(duì)列的容量為M，則其長度為(  )。

A. (Q.rear-Q.front +1)
B. [Q.rcar-a.front+M)
C. [Q.rear-Cl.front+1)%M
D.(Qrear-Q.front+M)%M

查看答案

試題2

采用 UML 進(jìn)行軟件設(shè)計(jì)時(shí)，可用  （ ）  關(guān)系表示兩類事物之間存在的特殊/一般關(guān)系，用聚集關(guān)系表示事物之間存在的整體/部分關(guān)系。
A、依賴
B、聚集
C、泛化
D、實(shí)現(xiàn)

查看答案

試題3

MPEG-I編碼器輸出視頻的數(shù)據(jù)率大約為（1）。PAL制式下其圖像亮度信號(hào)的分辨率為（2），幀速為（3）。
（1）A、128Kb/s 
B、320Kb/s 
C、1.5Mb/s 
D、15Mb/s
（2）A、352×288 
B、576×352 
C、720×576 
D、1024×720
（3）A、16幀/秒 
B、25幀/秒 
C、30幀/秒 
D、50幀/秒 

查看答案

試題4

一個(gè)功能模塊 M1 中的函數(shù) F1 有一個(gè)參數(shù)需要接收指向整型的指針，但是在功能模塊 M2 中調(diào)用 F1 時(shí)傳遞了一個(gè)整型值，在軟件測試中，  （ ）  最可能測出這一問題。
A、M1 的單元測試
B、M2 的單元測試
C、M1 和 M2 的集成測試
D、確認(rèn)測試

查看答案

試題5

在選擇開發(fā)方法時(shí)，有些情況不適合使用原型法，以下選項(xiàng)中不能使用快速原型法的情況是（ ）。
A、系統(tǒng)的使用范圍變化很大 
B、系統(tǒng)的設(shè)計(jì)方案難以確定 
C、用戶的需求模糊不清 
D、用戶的數(shù)據(jù)資源缺乏組織和管理 

查看答案

試題6

拓?fù)湫蛄惺菬o環(huán)有向圖中所有頂點(diǎn)的一個(gè)線性序列，圖中任意路徑中的各個(gè)頂點(diǎn)在該圖的拓?fù)湫蛄兄斜３窒群箨P(guān)系，（ ）為—下圖所示有向圖的一個(gè)拓?fù)湫蛄小?br />
A、1 2 3 4 5 6 7
B、1 5 2 6 3 7 4
C、5 1 2 6 3 4 7
D、5 1 2 3 7 6 4

查看答案

試題7

In a world where it seems we already have too much to do, and too many things to think about, it seems the last thing we need is something new that we have to learn.
But use cases do solve a problem with requirements: with （1 ） declarative requirements it's hard to describle steps and sequences of events.
Use cases, stated simply, allow description of sequences of events that, taken together, lead to a system doing something useful. As simple as this sounds, this is important. When confronted only with a pile of requiements, it's often（2 ）to make sense of what the authors of the  requirements really wanted the system to do. In the preceding example, use cases reduce the ambiguity of the requirements by specifying exactly when and under what conditions certain behavior occurs; as such, the sequence of the behaviors can be regarded as a requirement. Use cases are particularly well suited to capture approaches. Although this may sound simple, the fact is that (3 ) requirement capture approaches, with their emphasis on declarative requirements and "shall" statements, completely fail to capture fail to capture the (4 ) of the system's behavior. Use cases are a simple yet powerful way to express the behavior of the system in way that all stakeholders can easily understand.
But, like anything, use cases come with their own problems, and as useful as they are, they can be (5 ). The result is something that is as bad, if not worse, that the original problem. Therein it's important to utilize use cases effectively without creating a greater problem than the one you started with.
（1）A.plenty
B.loose
C.extra
D.strict
（2）A.impossible
B.possible
C.sensible
D.practical
（3）A.modern
B.conventional
C.different
D.formal
（4）A.statics
B.nature
C.dynamics
D.originals
（5）A.misapplied
B.applied
C.used
D.powerful

查看答案

試題8

查看答案

試題9

某PC的Internet協(xié)議屬性參數(shù)如下圖所示，默認(rèn)網(wǎng)關(guān)的IP地址是（ ）。

A．8.8.8.8
B．202.117.115.3
C．192.168.2.254
D．202.117.115.18

查看答案

試題10

采用面向?qū)ο蠓椒ㄩ_發(fā)軟件的過程中，抽取和整理用戶需求并建立問題域精確模型的過程叫  （ ）  。
A、面向?qū)ο鬁y試
B、面向?qū)ο髮?shí)現(xiàn)
C、面向?qū)ο笤O(shè)計(jì)
D、面向?qū)ο蠓治?/p>

查看答案