ISO IEC 18021 pdf download – Information technology — User interfaces for mobile tools for management of database communications in a client-server model

ISO IEC 18021 pdf download – Information technology — User interfaces for mobile tools for management of database communications in a client-server model
5 Description of contents in MBT database operation screens5.1 General
When the MBT database operation is executed, the MBT client shall provide the screen contents described in subclauses 5.2,5.3,and 5.4.
Regarding the support of cultural and linguistic adaptability requirements，message numbers specified in thisstandard shall be used to preserve data interoperability among applications in different natural languages. Themessages may be modified or adapted in any natural language. However, the resulting changes shall respect thefunction defined in this clause to which the messages applies.
Communication between components (the MBT client and the MBT server) shall always use one of the messagenumbers.
Note: General messages of sample application corresponding to all example message numbers refer to Annex B. lt isunderstood that in the future graphics,vice messages, sounds could be used as the representation for the user. Should it bethe case, message numbers shall always be used for data interoperability between components (the MBT client and the MBTserver)-
The system should have the capability to disable the notification upon the request of the user.
5.2 User approval or disapproval
5.2.1 Prior notice
The MBT client shall inform the user in advance that
– the MBT database operation will be executed.(Note: Example message number 0100)when appropriate, the MBT client shall inform the user in advance that
the MBT client’s database will be updated by the MBT server application.(Note:Example message number0111)
the MBT server’s database will be updated by the MBT server application.(Note:Example message number0121)
data in the MBT client’s database will be transmitted to the MBT server.(Note: Example message number0131)
5.2.2 Granting or refusing approval
The MBT client shall provide an on-screen button, a fixed button outside of the display screen, or similar control asthe means for:
granting approval for the MBT server application to execute the MBT database operation,- refusing approval for the MBT server application to execute the MBT database operation.
When the user grants approval, the MBT database operation shall be executed.
When the user refuses approval, the MBT database operation shall not be executed and another screen contentshall be displayed.
The MBT client shall ensure an exclusive choice between granting and refusing approval for an MBT databaseoperation, by providing radio buttons,select buttons, or the like.
The buttons for granting and refusing approval for the MBT database operation should always be displayed on thescreen in a consistent area without being removed by scroling or any other navigation by the user. Those buttonsshould be aid out side by side.
5.2.3 Parameter setting
The MBT client may provide a text input area, check buttons, a selectable menu, or similar control, as the meansfor setting the MBTdatabase operation parameters, if necessary for executing an MBT database operation. lf theuser sets those MBT database operation parameters, the parameters shall be used by the MBT server applicationto execute the corresponding MBT database operation.The means for setting the MBT database operationparameters should be displayed on the screen.
5.3 Feedback to the user (success)5.3.1 Notice of successful completionThe MBT client shall inform the user that:
– the MBT database operation has been completed successfully.(Note:Example message number o200).When appropriate, the MBT client shall inform the user that;
the MBTclient’s database has already been updated by the MBT server application.(Note: Example messagenumber 0211).
the MBT server’s database has already been updated by the MBT server application.(Note:Examplemessage number 0221).
data in the MBT client’s database has already been transmitted to the MBT server.(Note: Example messagenumber 0231).
5.3.2 User acknowledgement of successful completion
The MBT client shall provide an on-screen button, a fixed button outside of the display screen, or similar control,as the means for acknowledging the successful completion of an MBT database operation,
After the user has acknowledged the successful completion of the operation, another screen content shall bedisplayed.
The button for acknowledging the successful completion of the MBT database operation should always bedisplayed on the screen in a consistent area without being removed by scrolling or any other navigation by theuser.