6 MENU STRUCTURES (菜单结构)
原文
Problem description
An application has the following menu structure.
[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-8FEhzJV7-1659677976723)(C:\Users\wubf\AppData\Roaming\Typora\typora-user-images\image-20220803151146202.png)]
Clicking Client data brings up:
How should the activation of the several transactions, like Add new client, through the dropdown menus be counted?
Discussion
The stepwise activation, menu structure, of a transaction (first Administration, then Client data) is not counted as a user transaction. The full menu path however, is counted as one additional data element type for the underlying functions (Retrieve, Add new, Edit, Delete).
Solution
Do not count the menu structure.
翻译
问题描述
应用程序具有以下菜单结构。
单击客户端数据会显示:
如何计算通过下拉菜单激活多个事务(如添加新客户端)的功能点?
讨论
事务(首先是管理,然后是客户端数据)的逐步激活、菜单结构不算作用户事务。但是,完整菜单路径被视为基础功能(检索、添加新的、编辑、删除)的一种附加数据元素类型。
解决方案
不计算菜单结构的功能点