為幫助考生備考2023下半年軟考軟件設(shè)計(jì)師考試，希賽網(wǎng)整理了2023下半年軟件設(shè)計(jì)師入學(xué)摸底測(cè)試卷，以便考生對(duì)知識(shí)學(xué)習(xí)掌握的程度有個(gè)認(rèn)知，方便后面的備考計(jì)劃安排。

以下為2023下半年軟件設(shè)計(jì)師入學(xué)摸底測(cè)試卷部分試題，完整試題及答案請(qǐng)考生在本文文首本文資料處或文末的資料下載欄目下載查看。

5、計(jì)算機(jī)中，系統(tǒng)總線用于( )連接。

A、接口和外設(shè)

B、運(yùn)算器、控制器和寄存器

C、主存外設(shè)部件

D、DMA控制器和中斷控制器

6、以下關(guān)于采用一位奇校驗(yàn)方法的敘述中，正確的是( )。

A、若所有奇數(shù)位出錯(cuò)，則可以檢測(cè)出該錯(cuò)誤但無(wú)法糾正錯(cuò)誤

B、若所有偶數(shù)位出錯(cuò)，則可以檢測(cè)出該錯(cuò)誤并加以糾正

C、若有奇數(shù)個(gè)數(shù)據(jù)位出錯(cuò)，則可以檢測(cè)出該錯(cuò)誤但無(wú)法糾正錯(cuò)誤

D、若有偶數(shù)個(gè)數(shù)據(jù)位出錯(cuò)，則可以檢測(cè)出該錯(cuò)誤并加以糾正

11、著作權(quán)中，( )的保護(hù)期不受限制。

A、發(fā)表權(quán)

B、發(fā)行權(quán)

C、署名權(quán)

D、展覽權(quán)

12、若模塊A通過(guò)控制參數(shù)來(lái)傳遞信息給模塊B，從而確定執(zhí)行模塊B中的哪部分語(yǔ)句，則這兩個(gè)模塊的耦合類(lèi)型是( )耦合。

A、數(shù)據(jù)

B、標(biāo)記

C、控制

D、公共

36、采用貪心算法保證能求得最優(yōu)解的問(wèn)題是( )。

A、0-1背包

B、矩陣鏈乘

C、最長(zhǎng)公共子序列

D、部分(分?jǐn)?shù))背包

37、以下關(guān)于好的軟件設(shè)計(jì)原則的敘述中，不正確的是( ) 。

A、模塊化

B、提高模塊獨(dú)立性

C、集中化

D、提高抽象層次

40、以下關(guān)于軟件設(shè)計(jì)原則錯(cuò)誤的是( )。

A、模塊的作用域應(yīng)該在其控制域之內(nèi)

B、遵循“高內(nèi)聚，低耦合”的設(shè)計(jì)原則

C、多扇入、少扇出

D、模塊的功能應(yīng)該是不可預(yù)測(cè)的。

41、系統(tǒng)可維護(hù)性是指維護(hù)人員理解、改正、改動(dòng)和改進(jìn)軟件系統(tǒng)的難易程度，其評(píng)價(jià)指標(biāo)不包括( )。

A、可理解性

B、可測(cè)試性

C、可修改性

D、一致性

53、在用例圖中，一個(gè)用例明顯混合了多種場(chǎng)景，不同的情況會(huì)產(chǎn)生多種分支，大部分的情況下實(shí)現(xiàn)該用例，而對(duì)于一些特定情況可能通過(guò)其他用例進(jìn)行實(shí)現(xiàn)，這是( )關(guān)系。

A、包含關(guān)系

B、擴(kuò)展關(guān)系

C、泛化關(guān)系

D、依賴(lài)關(guān)系

55、某高校人力資源管理系統(tǒng)的數(shù)據(jù)庫(kù)中，教師關(guān)系模式為T(mén)(教師號(hào)，姓名，部門(mén)號(hào)，崗位，聯(lián)系地址，薪資)，函數(shù)依賴(lài)集F={教師號(hào)→(姓名，部門(mén)號(hào)，崗位，聯(lián)系地址)，崗位→薪資｝。T關(guān)系的主鍵為( )，函數(shù)依賴(lài)集F( )。

問(wèn)題1

A、教師號(hào)，T存在冗余以及插入異常和刪除異常的問(wèn)題

B、教師號(hào)，T不存在冗余以及插入異常和刪除異常的問(wèn)題

C、(教師號(hào)，崗位)，T存在冗余以及插入異常和刪除異常的問(wèn)題

D、(教師號(hào)，崗位)，T不存在冗余以及插入異常和刪除異常的問(wèn)題

61、The beauty of software is in its function,in its internal structure,and in the way in which it is created by a team. To a user,a program with just the right features presented through an intuitive and(1 )interface is beautiful.To a software designer,an internal structure that is partitioned in a simple and intuitive manner,and that minimizes internal coupling is beautiful.To developers and managers ,a motivated team of developers making significant progress every week,and producing defect-free code,is beautiful.There is beauty on all these levels.

Our world needs software——lots of software. Fifty years ago software was something that ran in a few big and expensive machines. Thirty years ago it was something that ran in most companies and industrial settings. Now there is software running in our cell phones,watches,appliances,automobiles,toys,and tools. And need for new and better software never(2).As our civilization grows and expands,as developing nations build their infrastructures,as developed nations strive to achieve ever greater efficiencies,the need for more and more Software(3 )to increase. It would be a great shame if,in all that software,there was no beauty.

We know that software can be ugly. We know that it can be hard to use,unreliable ,and carelessly structured. We know that there are software systems whose tangled and careless internal structures make them expensive and difficult to change. We know that there are software systems that present their features through an awkward and cumbersome interface. We know that there are software systems that crash and misbehave. These are(4)systems. Unfortunately,as a profession,software developers tend to create more ugly systems than beautiful ones.

There is a secret that the best software developers know. Beauty is cheaper than ugliness. Beauty is faster than ugliness. A beautiful software system can be built and maintained in less time,and for less money ,than an ugly one. Novice software developers don't understand this. They think that they have to do everything fast and quick. They think that beauty is(5).No! By doing things fast and quick,they make messes that make the software stiff,and hard to understand,beautiful systems are flexible and easy to understand. Building them and maintaining them is a joy. It is ugliness that is impractical.Ugliness will slow you down and make your software expensive and brittle. Beautiful systems cost the least build and maintain,and are delivered soonest.

問(wèn)題1

A、Simple

B、Hard

C、Complex

D、duplicated

問(wèn)題2

A、happens

B、exists

C、stops

D、starts

問(wèn)題3

A、starts

B、continues

C、appears

D、stops

問(wèn)題4

A、practical

B、useful

C、beautiful

D、ugly

問(wèn)題5

A、impractical

B、perfect

C、time-wasting

D、practical