23 NESMA 直接处理和延时处理案例分析

最新推荐文章于 2024-06-08 00:52:59 发布

不知之知

最新推荐文章于 2024-06-08 00:52:59 发布

阅读量149

点赞数

分类专栏： NESMA 文章标签：软件工程

NESMA 专栏收录该内容

44 篇文章 7 订阅

订阅专栏

23 DIRECT AND DELAYED PROCESSING（直接处理和延时处理）

译文

问题描述

应用程序为其用户提供了根据地区更新被保险人的保险组的机会；例如，地区盗窃保险费。该应用程序允许其用户通过屏幕将邮政编码系列分配给不同的保险组。在本示例中，处理了三种功能不同的情况。每种情况都说明了应如何进行功能点分析。

第一种情况下的更新是在输入邮政编码序列后立即进行的。然后可以输入新的系列。当用户使用该功能对一个或多个保险组完成调整后，应用程序将打印交易报告以进行验证。

在第二种情况下，用户可以输入一个或多个邮政编码序列。数据处理在夜间进行。调整保险组后，应用程序将打印交易报告以进行验证。输入邮政编码序列后，将无法再对其进行维护。

在第三种情况下，用户可以输入一个或多个邮政编码序列。应用程序在夜间处理数据，然后打印事务报告以进行验证。然而，现在，输入的邮政编码序列在输入后，但在夜间处理之前，仍然可以更改或删除。

对于上述每种情况，确定应确定哪些功能。在情况2和/或3中具有邮政编码序列的事务文件是否视为内部逻辑文件？

23.1 直接处理

讨论

这个功能的主要目的是调整保险组。保存的数据是功能上永久的数据。这意味着存在外部输入。交易报告的创建与功能密不可分，报告本身满足功能要求；也就是说，出于验证目的，这是必要的。事务报告也跨越应用程序边界。由于这些原因，为事务报告标识一个外部输出，尽管该功能与外部输入有着不可分割的联系。

答案

识别以下功能：

调整保险组识别一个外部输入
交易报告识别一个外部输出

23.2 延时处理

讨论

这个功能的主要目的是调整保险组。保存的数据是功能上永久的数据。这意味着至少存在一个外部输入。FPA将输入邮政编码序列和每晚处理数据视为延迟处理。它将夜间处理和邮政编码序列的输入视为一个整体。

临时保存的邮政编码序列无法维护，并且不是永久性的，因为数据在夜间处理期间处理后不再存在。换句话说，数据被“消耗”。因此，邮政编码序列形成了一个不能被视为内部逻辑文件的临时数据集。

事务报告的创建与夜间处理密不可分，报告本身满足功能需求；也就是，出于验证目的，这是必要的。事务报告也跨越应用程序边界。由于这些原因，事务报告被标识为外部输出，即使该功能与外部输入有着不可分割的联系。

答案

计算如下功能:

为进入保险组并对保险组进行夜间调整识别一个外部输入
交易报告识别一个外部输出

23.3 延后处理并维护

讨论

存储的邮政编码系列可以维护，因此构成一个内部逻辑文件。此外，还确定了两个维护功能：一个用于更改邮政编码序列，另一个用于删除邮政编码序列。

答案

计算如下功能：:

一个外部输入用于邮政编码系列的初始输入和夜间处理。
包含邮政编码系列的事务文件的一个内部逻辑文件。
用于从事务文件中更改和删除邮政编码序列的两个外部输入。
交易报告识别一个外部输出

原文

Problem description

An application provides its users the opportunity to update an insurance group for those insured on the basis of region; e.g., regional theft insurance premiums. The application enables its users to assign a zip code series to a different insurance group by means of a screen. In this illustration, three functionally different situations are handled. Each situation shows how function point analysis should be carried out.

The update in the first situation takes place immediately after a zip code series has been entered. Then a new series can be entered. When the user is finished with the function and one or more insurance groups have been adjusted, the application prints a report of the transactions for verification purposes.

In the second situation, the user can enter one or more zip code series. The processing of the data is done at night. When the insurance groups have been adjusted, the application prints a report of the transactions for verification purposes. Once the zip code series have been entered, they can no longer be maintained.

In the third situation, the user can enter one or more zip code series. The application processes the data at night, after which it prints a report of the transactions for verification purposes. Now, however, the zip code series entered can still be changed or deleted after they have been entered, but before their nightly processing.

For each of the situations above, determine which functions should be identified. Does the transaction file with the zip code series in situation 2 and/or 3 count as an internal logical file?

23.1 Direct processing

Discussion

The main objective of this function is the adjustment of the insurance groups. The data that is saved is functionally permanent data. This means that an external input is present. The creation of the transaction report is inextricably bound to the function, and the report itself fulfills a functional requirement; i.e., it is necessary for verification purposes. The transaction report also crosses the application boundary. For thesereasons, an external output is identified for the transaction report, even though the function is inextricably bound to the external input.

Solution

Count the following functions:

One external input for entering and adjusting the insurance groups
One external output for the transaction report

23.2 Delayed processing

Discussion

The main objective of this function is the adjustment of the insurance groups. The data saved is functionally permanent data. This means that at least one external input is present. FPA considers the entering of the zip code series and the nightly processing of the data as delayed processing. It sees the nightly processing and the entering of the zip code series as a whole.

The zip code series temporarily saved cannot be maintained and are not permanent because the data no longer exists after being processed during the nightly processing. In other words, the data is “consumed”. The zip code series therefore form a temporary dataset that cannot be considered an internal logical file.

The creation of the transaction report is inextricably bound to the nightly processing, and the report itself fulfills a functional requirement; i.e., it is necessary for verification purposes. The transaction report also crosses the application boundary. For these reasons, the transaction report is identified as an external output, even though the function is inextricably bound to the external input.

Solution

Count the following functions:

One external input for entering the insurance groups and for the nightly adjustment of the insurance groups
One external output for the transaction report

23.3 Delayed processing and maintenance

Discussion

This main objective of this function is the adjustment of the insurance groups. The data that is saved is functionally permanent data. This means that at least one external input is present. FPA considers the entering of the zip code series and the nightly processing of the data as delayed processing. It sees the nightly processing and the entering of the zip code series as a whole.

The zip code series stored can be maintained and therefore make up an internal logical file. Furthermore, two maintenance functions are identified: one for changing zip code series and one for deleting them.

Solution

Count the following functions:

One external input for the initial input of zip code series and the nightly processing together.
One internal logical file for the transaction file containing zip code series.
Two external inputs for the changing and deleting of the zip code series from the transaction file.
One external output for the transaction report