2026上半年软考高级系统分析师备考资料：第8章知识点分值分布及试题

2026上半年软考高级系统分析师第8章《专业英语》考试知识点分值分布及试题如下：

第8章 专业英语

一、分值分布

二、试题示例

1.专业英语--5分

试题【2022年上半年系统分析师考试上午真题】

Requirements validation is the process of checking that requirements actually define the system that the customer really wants. It overlaps with analysis as it is concerned with finding problems with the requirements. Requirements validation is important because errors in a requirements document can lead to extensive rework costs when these problems are discovered during development or after the system is in service. The cost of fixing a requirements problem by making a system change is usually much greater than repairing design or coding errors. The reason for this is that a change to the requirements usually means that the system design and implementation must also be changed. Furthermore, the system must then be re-tested.

During the requirements validation process, different types of checks should be carried out on the requirements in the requirements document. These checks include:

1. （ ）：A user may think that a system is needed to perform certain function. However, further thought and analysis may identify additional or different functions that are required. Systems have diverse stakeholders with different needs and any set of requirements is inevitably a compromise across the stakeholder community.

2. （ ）：Requirements in the document should not conflict. That is, there should not be contradictory constraints or different descriptions of the same system function.

3. （ ）：The requirements document should include requirements that define all functions and the constraints intended by the system user.

4. Realism checks: Using knowledge of existing technology, the requirements should be checked to ensure that they can actually be implemented. These checks should also take account of the （ ） for the system development.

5. Verifiability: To reduce the potential for dispute between customer and contractor, system requirements should always be written so that they are verifiable. This means that you should be able to write a set of tests that can demonstrate that the delivered system meets each specified （ ） .

选项1：

A：Security checks

B：Validity checks

C：Consistency checks

D：Completeness checks

选项2：

A：Security checks

B：Safety checks

C：Consistency checks

D：Usability checks

选项3：

A：Consistency checks

B：Usability checks

C：Operational checks

D：Completeness checks

选项4：

A：tools

B：tests

C：models

D：budget and schedule

选项5：

A：requirement

B：model

C：design

D：implementation

答案：B、C、D、C、A

解析：需求验证是检查需求是否实际定义了客户真正想要的系统的过程。它与分析重叠，因为它关注的是发现需求中的问题。需求验证是很重要的，因为当这些问题在开发过程中或系统投入使用后被发现时，需求文件中的错误会导致大量的返工成本。通过改变系统来修复需求问题的成本通常比修复设计或编码错误要大得多。原因是对需求的改变通常意味着系统的设计和实施也必须改变。此外，还必须重新测试系统。

在需求验证过程中，应该对需求文件中的需求进行不同类型的检查。这些检查包括：

1.（ ）: 用户可能认为需要一个系统来执行某些功能。然而，进一步的思考和分析可能会发现需要额外的或不同的功能。系统有不同的利益相关者，有不同的需求，任何一套需求都不可避免地是整个利益相关者群体的妥协。

2. （ ）: 文件中的要求不应冲突。也就是说，不应该有相互矛盾的约束或对同一系统功能的不同描述。

3.（ ）: 需求文件应该包括定义所有功能的需求和系统用户所期望的约束。

4. 现实性检查。利用现有技术的知识，应该对需求进行检查，以确保它们能够真正被实现。这些检查也应该考虑到系统开发的（ ）。

5. 可验证性。为了减少客户和承包商之间潜在的争议，系统需求的编写应该始终是可验证的。这意味着你应该能够编写一套测试，以证明所交付的系统符合每一个指定的（ ）。

（1）A.安全检查 B.有效性检查C.一致性检查 D.完整性检查

（2）A.安全检查 B.安全检查 C.一致性检查 D.可用性检查

（3）A.一致性检查B.可用性检查C.操作性检查 D.完整性检查

（4）A.工具 B.测试 C.模型D.预算和时间表

（5）A.需求 B.模型 C.设计D.实施