| Author | Message | ||
     Janani |
Hi, I have an 'Add' transaction which has many command buttons like 'save', 'cancel', 'next', previous, verify. should i count each command button as a DET for this transaction. specifically should i count 'cancel' button. Thanks, Janani | ||
| Nandakumar Balasubramaniam |
A cancel functionality is mostly expected to ignore the user input made in the user interface. Such transactions do not end up in any update to any ILF. Assuming your 'Cancel' transaction also falls under this category, the 'Cancel' button shall not be counted. Next and Previous are navigational options hence wont be counted. Save can be counted as an elementary process (EI) Nanda | ||
| Charley Tichenor |
If you have many navigational aids, you may want to consider counting them under GSG #7. Also, it is not clear to me what "verify" means. This might be an elementary process in itself, or may not be. | ||
| Deepak Kumar J |
According to IFPUG counting rules each command button would be counted as a data element for the action it invokes. For example, a simple application to capture the distributor details such as Name, Address, City, State, Zip, Phone Number, and Fax Number. This would represent seven fields or (seven data elements) and the add command button would represent the eighth data element. In short, the “add” external input represent a one external input with eight data elements, similarly for the “change” external input represents another external input with eight (seven data elements plus the “change” command button). Hope this clears your doubt. | ||
| Maxim Rusakov Username: Maximrusakov Post Number: 14 Registered: 04-2010 |
according to CPM 4.3 Part 2 7-14: "Count only one DET per transactional function for the ability to initiate action(s) even if there are multiple means to do so" As a result, I assume you should count only 1 DET. |
