Conceptual modeling for user interface development

From MaRDI portal





Since the early 1950s many YADAs (Yet Another Descriptive Approach) have been proposed to describe computing system, simulation system or information systems. The approach presented in this book is ``Entity Relationship Modeling of Information Artifacts (ERMIA) which uses diagram elements (consisting of specific shapes), undirected lines and annotations to represent the system being modeled. ERMIA is a ``course grained or high level, descriptive approach. The specific emphasis is on user interface development, but few computer interface examples are given. Among the ERMIA examples presented in this book are: (1) stove top controls, (2) an appointment book, (3) a digital alarm clock, (4) an ATM, (5) a library, (6) a theorem prover, (7) a telephone network (more correctly a telephone book). Exception handling is a big part of interface development. The examples presented assume that correct user actions occur. How to indicate recovery from actions such as inserting the wrong card into an ATM or pressing the wrong ATM key or indicating when the ATM is out of cash or any way to indicate the conditionals that make up systems are minimized or avoided. Representing conditional actions is necessary if interface requirements are to be described adequately during design and development stages. If learning ERMIA is a goal, the book does provide a good step by step introduction to ERMIA. It contains 15 exercises, a short bibliography and a short index. If ERMIA is to avoid being a YADA it will have to show its prowess on some reasonably sized interface problems.












This page was built for publication: Conceptual modeling for user interface development

Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q4255383)