ArticleslgStudy

computer science

IBM Common User Access

IBM Common User Access is a computer science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand IBM Common User Access rather than just read about it. In short: Common User Access (CUA) is a standard for user interfaces to operating systems and computer programs. It was developed by IBM and first published in 1987 as part of their Systems Application Architecture.

Key takeaways

  • IBM Common User Access belongs to computer science; place it in that map before memorising details.
  • Learn the definition first, then one example that makes the definition concrete.
  • Connect IBM Common User Access to a quantity you can measure, compute or draw — that is where exam questions come from.
  • Reproduce the core statement of IBM Common User Access from memory before moving on to harder problems.

Reference excerpt

Common User Access (CUA) is a standard for user interfaces to operating systems and computer programs. It was developed by IBM and first published in 1987 as part of their Systems Application Architecture. Used originally in the MVS/ESA, VM/CMS, OS/400, OS/2 and Microsoft Windows operating systems, parts of the CUA standard are now implemented in programs for other operating systems, including variants of Unix. It is also used by Java AWT and Swing.

Motivations and inspirations IBM wanted a standard way to interact with text-based user interface software, whether the screen was a dumb terminal connected to a mainframe or a PS/2 with VGA graphics. CUA was a detailed specification and set strict rules about how applications should look and function. Its aim was in part to bring about harmony among DOS applications, which until then had independently implemented different user interfaces. For example, to open a file:

In WordPerfect, the command to open a file was F7, 3. In Lotus 1-2-3, a file was opened with / (to open the menus), F (for File), R (for Retrieve). In Microsoft Word, a file was opened with Esc (to open the menus), T (for Transfer), L (for Load). In WordStar, ^ K D (to get to the Opening Menu), followed by D. In emacs, a file is opened with Ctrl+x followed by Ctrl+f (for find-file). In vi, use Esc to allow commands, then :espace. to open the file browser. F1 was often the help key (such as Volkswriter (1982)), but in WordPerfect, help was on F3 instead. Some programs used Esc to cancel an action, while some used it to complete one; WordPerfect used it to repeat a character. Some programs used End to go to the end of a line, while some used it to complete filling in a form. Ins sometimes toggled between overtype and inserting characters, but some programs used it for "paste". Some program had to be learned individually, and its user interface memorized. It was a sign of expertise to have learned the UIs of some applications, since a novice user facing a new program would find their existing knowledge of a similar application either of no use or a hindrance to understanding. Learned behavior might need to be unlearned for an application. The detailed CUA specification, published in December 1987, is 328 pages long. It has similarities to Apple Computer's detailed human interface guidelines (139 pages). The Apple HIG is a detailed book specifying how software for the 1984 Apple Macintosh computer should look and function. When it was first written, the Mac was new, and graphical user interface (GUI) software was a novelty, so Apple took great pains to ensure that programs would conform to a single shared look and feel. CUA had a similar aim, but it faced the more difficult task of trying to impose this retroactively on an existing, thriving but chaotic industry, with the much more ambitious goal of unifying all UI, from personal computers to minicomputers to mainframes; and supporting both character and GUI modes, and both batch and interactive designs. By comparison, the Apple HIG only supported interactive GUI on a standalone personal computer. CUA also attempted to be a more measurable standard than the Apple HIG and had large sections formatted as checklists to measure compliance.

Description The CUA contains standards for the operation of elements such as dialog boxes, menus and keyboard shortcuts that have become so influential that they are implemented today by many programmers who have never read the CUA. Some of these standards can be seen in the operation of Windows itself and DOS-based applications like the MS-DOS 5 full-screen text editor edit.com. CUA hallmarks include:

All operations can be done with either the mouse or the keyboard; If applicable to the page/screen in question F5 provides a refresh function; Menus are activated/deactivated with the F10 key; Menus are opened by pressing the Alt key plus the underlined letter of the menu name; Menu commands that require parameters to proceed are suffixed with an ellipsis ("…"); Options are requested using secondary windows (often called dialog boxes); Options are divided into sections using notebook tabs; Navigation within fields in dialog boxes is by cursor key; navigation between fields is by pressing the Tab ↹ key; ⇧ Shift+Tab ↹ moves backwards; Dialog boxes have a 'Cancel' button, activated by pressing the Esc key, which discards changes, and an 'OK' button, activated by pressing Return, which accepts changes; Applications have online help accessed by a Help menu, which is the last option on the menu bar; context sensitive help can be summoned by F1; The first menu is to be called 'File' and contains operations for handling files (new, open, save, save as) as well as quitting the program; the next menu 'Edit' has commands for undo, redo, cut, copy, delete, paste commands; The Cut command is ⇧ Shift+Del; Copy is Ctrl+Ins; Paste is ⇧ Shift+Ins; The size of a window can be changed by dragging one of the 8 segments of the border. CUA not only covers DOS applications, but is also the basis for the Windows Consistent User Interface standard (CUI), as well as that for OS/2 applications — both text-mode and the Presentation Manager GUI — and IBM mainframes which conform to the Systems Application Architecture. CUA was more than just an attempt to rationalise DOS applications — it was part of a larger scheme to bring together, rationalise and harmonise the overall functions of software and hardware across IBM's entire computing range from microcomputers to mainframes. The third edition of CUA took a radical departure from the first two by introducing the object-oriented workplace. This changed the emphasis of the user's interactions to be the data (documents, pictures, and so on) that the user worked on. The emphasis on applications was removed with the intention of making the computer easier to use by matching users' expectations that they would work on documents using programs (rather than operating programs to work on documents).

… excerpt ends here. Continue reading the full article.

Worked examples

Example 1 — a first encounter with IBM Common User Access

Start with the simplest possible case. Write down what IBM Common User Access claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In computer science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to IBM Common User Access before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about IBM Common User Access ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of IBM Common User Access

In research
IBM Common User Access appears in computer science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry
Engineering practice reuses IBM Common User Access in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom
IBM Common User Access is common in secondary-school and first-year university syllabi. It links to neighbouring topics Human–computer interaction, IBM software, OS/2 technology, so understanding it makes those chapters shorter.
In everyday life
Look for IBM Common User Access outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.
Ask Teacher Smith questions about this articleOpens your AI tutor with a question about “IBM Common User Access” →

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study IBM Common User Access in 20 minutes

  1. Read the reference excerpt below once, without taking notes.
  2. Close the page and write down what IBM Common User Access means in your own words.
  3. Compare your version with the excerpt and mark what you missed.
  4. Work through the three examples above with pen and paper.
  5. Explain IBM Common User Access out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is IBM Common User Access in simple terms?

Common User Access (CUA) is a standard for user interfaces to operating systems and computer programs. It was developed by IBM and first published in 1987 as part of their Systems Application Architecture.

Why does IBM Common User Access matter?

Because it connects several computer science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study IBM Common User Access?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on IBM Common User Access.

Tags

  • Human–computer interaction
  • IBM software
  • OS/2 technology
  • User interface techniques

Keep exploring