Overview
ISO/IEC 18021:2002 specifies user interface functions for management of database communications on mobile tools (MBT) operating in a client–server model. It applies to MBT clients (e.g., PDAs, smart phones, electronic organizers, palm-sized PCs) that interchange data with an MBT server. The standard defines two core UI functions: (1) obtaining user approval before database updates or data transmission, and (2) providing feedback (success or failure) after a database operation. Adoption improves interoperability, user control and reliability when mobile devices perform database operations over sometimes unreliable links (for example, wireless).
Key topics and requirements
- User approval UI
- Prior notice to users before an MBT client's database is updated remotely or when local data will be transmitted.
- Mechanisms for granting or refusing approval and for configuring operation parameters.
- Feedback UI
- Clear success messages after updates or transmissions.
- Failure notifications with both general and detailed reasons, plus acknowledgement controls.
- Screen content and layout
- Specification of required screen contents (non-scrollable “consistent area”, labels, acknowledgement elements) that MBT clients must present before and after database operations to conform.
- Conformance
- A system conforms if it provides the screen contents described in specified clauses before execution and the described success/failure feedback after execution.
- Informative annexes
- Examples and guidance for database operation screens, sample applications, basic screen presentation, and technical information (PDX tags for screen description and P4script for database operation scripting).
Practical applications and users
Who benefits from ISO/IEC 18021:
- Mobile application and UI designers - to design consistent approval and feedback dialogs for mobile database syncs.
- Mobile OS and embedded-device developers - to implement standard client-side screens and flow for database communications.
- Product managers & usability specialists - to ensure user control, security and predictable behaviour across devices.
- QA and compliance teams - to verify conformance and interoperability across MBT clients and servers.
- Enterprise mobility architects - to standardize server-client interactions and improve user trust when syncing sensitive data.
Practical benefits:
- Improved usability, security (user approval controls), and reliability (clear success/failure feedback) for mobile database operations.
- Better interoperability across diverse MBT implementations.
Related standards
- ISO 9241-10 (ergonomic dialogue principles) is cited as a key reference for usability and dialogue design.