19.2 NESMA 唯一和非唯一搜索条件的组合案例分析

Combination of unique and non-unique search criteria（唯一和非唯一搜索条件的组合）

原文

Problem description

When a unique Customer Number is entered into the function Query Customers, data about the customer attached to that number will appear on the screen. The buttons Next and Previous are not active when this is done.
If a Customer Name (or part of a Customer Name) is entered, all customers with that particular name are retrieved. However, only the first customer with this name is displayed on the screen. When the name of a City is also entered, only those customers that reside there are selected.
If only the city is entered, then all the customers from that city are selected.
The buttons Next and Previous allow the user to browse forward or backwards through the customers selected.
How many and what type of functions should be counted?

Discussion

In this case, the user has the option to enter either the customer number or the customer name, and may even combine the customer name with the city. Two exclusive or separate selections are possible, each of which is considered an individual function.

Querying by customer number is an external inquiry. The size of the output is fully determined: namely, all data about a particular customer.

The external inquiry consists of seven data element types: customer number (twice), customer name, address, zip code, city, and order date. Besides the error message and the Search button are counted. Total number is nine data-element-types.

Querying by (a part of a) customer name and/or by city is an external output. The output varies in size because the number of customers that will be selected is not known beforehand. In this case, there is only one external output because the user has more options in which the selections he makes do not exclude each other (i.e., an and/or situation).

Ten data element types determine the function’s complexity: customer number, customer name (twice), address, zip code, city (twice), and order date plus the Search button.

The buttons Next and Previous are used to navigate through the output and are therefore not counted as additional functions or data element types.

Solution

Count one external inquiry with nine data element types for querying by customer number.
Count one external output with ten data element types for querying by customer name and/or by city.

翻译

问题描述

当在“查询客户”功能中输入唯一的客户编号时，屏幕上将显示与该编号相关的客户数据。完成此操作后，“下一步”和“上一步”按钮将不激活。
如果输入了客户名称（或客户名称的一部分），则检索具有该特定名称的所有客户。但是，屏幕上只显示具有此名称的第一个客户。当同时输入城市名称时，仅选择居住在那里的客户。
如果只输入城市，则选择该城市的所有客户。
按钮Next和Previous允许用户向前或向后浏览所选客户。
应该计算多少个什么类型的功能点？

讨论

在这种情况下，用户可以选择输入客户编号或客户名称，甚至可以将客户名称与城市相结合。可以进行两个独占或单独的选择，每个选择都被视为一个单独的功能。

按客户编号查询是一种外部查询。输出的大小是完全确定的：即关于特定客户的所有数据。

外部查询由七种数据元素类型组成：客户编号（两次）、客户名称、地址、邮政编码、城市和订单日期。此外，还统计了错误消息和搜索按钮。总数为九种数据元素类型。

按客户名称和/或城市查询是一种外部输出。输出大小不同，因为将被选择的客户数量事先未知。在这种情况下，只有一个外部输出，因为用户有更多选项，其中他所做的选择不会相互排斥（即，和/或情况）。

十种数据元素类型决定了功能的复杂性：客户编号、客户名称（两次）、地址、邮政编码、城市（两次）和订单日期加上搜索按钮。

按钮Next和Previous用于在输出中导航，因此不被视为附加功能或数据元素类型。

解决方案

统计一个外部查询，包含九种数据元素类型，用于按客户编号查询。
统计一个外部输出，包含十种数据元素类型，以便按客户名称和/或城市查询。

为什么不识别内部逻辑或外部逻辑文件？

个人理解

• 对于一个完整的分析，应该至少识别一个外部逻辑文件，但是我感觉此案例讨论的是搜索。所以只针对两个独立搜索功能给出了分析结论。
• 同时联系应用场景此功能不可能单独存在，可能有customer 的维护功能，如果已经识别了ILF，那么此处就不应该重复识别逻辑文件。