22 NESMA 选择屏幕和使用搜索键更改数据 案例分析

22 选择屏幕和使用搜索键更改数据

这个更改功能的案例的目标有两个：用户可以变更客户数据，但在他这样做之前，他首先能以用户友好的方式选择客户。从功能的角度来看，这可以通过不同的方式实现。本节将讨论此功能的两种不同实现，并说明在这两种情况下应如何进行计数。

22.1 通过单独的选择屏幕进行选择

问题描述

使用菜单，用户选择更改客户数据。应用程序随后出现屏幕1，用户必须在该屏幕上输入唯一的客户编号或（部分）客户名称。用户不应同时输入。

输入唯一的客户编号后，相关客户的数据将显示在更改屏幕上。（请参见屏幕2。）

当输入客户名称（或客户名称的一部分）时，应用程序检索具有该名称的所有客户。如果只找到一个客户，该客户的数据将立即显示在更改屏幕（屏幕2）上。

如果找到多个客户，他们将出现在选择屏幕上。（请参见屏幕3。）

用户通过（屏幕3）选择需的客户后，该客户的更多数据将显示在更改屏幕（屏幕2）上。

然后可以通过屏幕2更改客户数据。

选择数据的选项是否构成更改数据选项的一部分，还是一个单独的功能？输入客户所需的独立外部输入是否计算在内？客户数据的显示是否为单独的外部查询？总共应该计算多少个功能？

讨论

如果在屏幕1上输入了客户编号，在更改屏幕（屏幕2）上显示了正确的客户数据，则要更改的数据的显示是外部输入“更改客户”的一部分。此显示不算作单独的外部查询。

当用户输入一个非唯一的客户名称并且符合此标准的客户出现在屏幕3上时，可以选择要更改的客户。通过客户名称搜索客户在选择屏幕（屏幕3）上显示客户信息。该选择客户数据的大小不是事先完全确定的； 例如，选择客户数量的大小取决于输入的查询条件（名称）。然后可以选择所需的客户。在单独的屏幕上显示选定客户被视为附加功能。

由于本概述的逻辑布局不同，因此计算了一个附加功能；由于输出大小不同，因此应计算一个外部输出。

有时，当用户通过客户名称进行选择时，应用程序仅检索一个客户。发生这种情况时，应用程序不显示选择屏幕（屏幕3）。相反，它会在屏幕2显示的详细数据。这仅仅是一种优化，因此被认为是为选择屏幕（屏幕3）计数的外部输出的一部分。没有额外的外部输出或外部查询。

用户在屏幕3上进行选择后，所选客户的所有数据将显示在屏幕2上，然后可以进行更改。屏幕2上所选客户的数据显示（就像通过客户编号选择时一样）被视为变更功能的一部分，而不是单独的外部查询。

通过选择字段指示所选客户不会导致单独的外部输入。

这两种情况下的变化功能相同，因此算作一个外部输入

答案

计算更改功能的一个外部输入。
计算一个外部输出，以显示满足选择标准的客户。

22.2 通过更改屏幕进行选择

问题描述

使用菜单，用户选择更改客户数据。应用程序显示屏幕1，用户必须在该屏幕上输入唯一的客户编号或客户名称（但不是两者）。然后，更改功能具有如下所示的屏幕顺序。

输入两个选择标准之一后，符合标准的（第一个）客户的数据显示在屏幕2上。如果客户编号用作选择标准，则只有一个客户可以满足标准。在这种情况下，功能键不起作用。但是，如果使用客户名称作为选择标准，则许多客户可能满足该标准。用户将不会收到他在前一示例中为选择客户而显示的那种概览屏幕，而是能够使用功能键PF2和PF3浏览所选客户，直到找到他想要的客户。

外部输出或外部查询是否计入此外部输入（即更改客户数据的能力）？总共应该计算多少个功能？

讨论

在屏幕1上输入客户编号而在更改屏幕（屏幕2）上显示了正确的客户数据，则要更改的数据的显示是外部输入更改客户的一部分。显示不算作单独的外部查询。

当用户可以在屏幕1上输入非唯一的客户名称，浏览屏幕2上的客户，直到找到正确的客户，然后更改客户的数据时，必须按照以下方式进行分析。当用户通过客户名称搜索客户时，此搜索可能导致可通过功能键选择显示在更改屏幕上的多个客户。该选择在大小上不是预先完全确定的； 例如，选择的大小取决于满足选择标准的客户数量。然后可以选择所需的客户。所选客户的显示被视为附加功能。确定了一个附加功能，因为提供的功能实际上与前一个示例中相同，在前一个示例中，所选客户在概览屏幕上显示，并且因为显示和浏览所选客户的能力需要与仅显示和更改数据时不同的逻辑处理。更具体地说，应该确定一个外部输出，因为输出大小不同。

有时，当用户通过客户名称选择数据时，应用程序仅检索一个客户，在这种情况下，用于浏览的功能键不处于活动状态。这种情况被认为是外部输出的一部分，用于选择。这种情况不会导致额外的外部输出或外部查询。

在这两种情况下，变化功能相同，因此算作一个外部输入。

答案

计算更改功能为一个外部输入。
计算一个外部输出，以便浏览满足选择标准的客户。

---

22 SELECTION SCREENS AND CHANGING DATA WITH A SEARCH KEY

This example treats a change function whose objective is twofold: A user should be able to change customer data but, before he does this, he should first be able to select the customer in a user-friendly way. From a functional standpoint, this can be realized in different ways. This section will discuss two different implementations of this functionality and will indicate how counting should take place in both situations.

22.1 Selection via a separate selection screen

Problem description

Using a menu, the user indicates that he wants to change customer data. The application subsequently presents screen 1 on which the user must enter a unique customer number or a (part of a) customer name. The user should not enter both.

When a unique customer number is entered, the data for the customer concerned appears on the change screen. (See screen 2.)

When a customer name (or a part of a customer name) is entered, the application retrieves all customers with that name. If only one customer is found, the data of that customer appears immediately on the change screen (screen 2).

If several customers are found, they appear on the selection screen. (See screen 3.)

After the user enters the customer desired via the Choice field (screen 3), more extensive data of that customer appears on the change screen (screen 2).

The customer data can then be changed via screen 2.

Does the option to select data make up a part of the option to change data, or is it a separate function? Is a separate external input counted for entering the customer desired? Is the display of the customer data a separate external inquiry? How many functions should be counted in total?

Discussion

If the correct customer data is displayed on the change screen (screen 2) as a result of a customer number having been entered on screen 1, then the display of the data to be changed is part of the external input “Change Customer”. This display is not counted as an individual external inquiry.

Counting is carried out as follows, however, when the user enters a non-unique customer name and customers meeting this criterion appear on screen 3, after which the customer to be changed can be chosen. Searching for the customer via customer name results in a displayed selection of customers on the selection screen (screen 3). This selection is not determined fully in size beforehand; i.e., the size of the selection varies depending on how many customers meet the selection criterion (name). The customer desired can then be selected. This display of selected customers on a separate screen is seen as additional functionality.

Since the logical layout of this overview is different, an additional function is counted; because the output varies in size, one external output should be counted.

Sometimes an application retrieves only one customer when a user selects via customer name. When this happens, the application does not display the selection screen (screen 3). Instead, it immediately retrieves the detailed data that screen 2 displays. This is merely an optimization and is therefore considered to be part of the external output counted for the selection screen (screen 3). No additional external output or external inquiry is counted for this.

After the user has made a selection on screen 3, all the data for the customer selected is displayed on screen 2, after which changes can be made. The display of data for the customer selected on screen 2 (just as when selecting via customer number) is seen as a part of the change function and is not an individual external inquiry.

Indicating the selected customer via the Choice field does not result in a separate external input.

The change function is the same in both cases, and is therefore counted as one external input.

Solution

Count one external input for the change function.
Count one external output for displaying the customers that meet the selection criterion.

22.2 Selection via the change screen

Problem description

Using a menu, the user indicates that he wants to change customer data. The application subsequently presents screen 1 on which the user must enter a unique customer number or a customer name (but not both). The change function then has the screen sequence illustrated below.

After entering one of the two selection criteria, the data of the (first) customer that meets the criterion appears on screen 2. If Customer Number is used as the selection criterion, then only one customer can satisfy the criterion. Function keys are not active in such a case. If Customer Name is used as the selection criterion, however, a number of customers may satisfy the criterion. The user will not receive the kind of overview screen he did in the previous example in order to select a customer, but instead will be able to use the function keys PF2 and PF3 to browse through the customers selected until he has found the one he wants.

Are external outputs or external inquiries counted for this external input (i.e., for the ability to change customer data)? How many functions should be counted in total?

Discussion

If the correct customer data is displayed on the change screen (screen 2) as a result of a customer number having been entered on screen 1, then the display of the data to be changed is part of the external input Change Customer. The display is not counted as an individual external inquiry.

Analyzing must be carried out as follows when a user can enter a non-unique customer name on screen 1, browse through the customers on screen 2 until the correct one has been found, and then change the data of the customer. When the user searches for a customer via customer name, this search may result in the selection of a number of customers that can be displayed on the change screen via the function keys. This selection is not fully determined in size beforehand; i.e., the size of the selection varies depending on how many customers meet the selection criteria. The customer desired can then be selected. The display of the selected customers is seen as additional functionality. An additional function is identified because the functionality provided is in fact the same as in the previous illustration in which the selected customers were represented on an overview screen, and because the display and ability to browse through the selected customers entails a different logical processing than when data is merely presented and changed. More concretely, one external output should be identified because the output varies in size.

Sometimes it occurs that an application retrieves only one customer when a user selects data via customer name, in which case the function keys for browsing are not active. Such a situation is considered to be a part of the external output that is counted for selecting. The situation does not result in an additional external output or external inquiry.

The change function is the same in both cases and is therefore counted as one external input.

Solution

Count one external input for the change function.
Count one external output for the ability to browse through the customers that meet the selection criterion.