What Is User Interface Design and Why It Matters

UPI Study › Courses › Software Engineering › Free lessons › Lesson 10.1 Free with a free account

What Is User Interface Design and Why It Matters

Software Engineering · Chapter 10: User Interface Design: Principles, Guidelines, and ImplementationSection 10.1 · lesson 66 of 1036 min · free with a free account

← Using Component-Level Design in Real Software ProjectsNext lesson: Rules and Guidelines for Human-Centered Interfaces →

Earn 3 college credits for Software EngineeringRecommended for credit by NCCRS · Computer Science 301 · self-paced · one payment, lifetime access
Enroll in Software Engineering · $250 →Download the syllabus (PDF)

In this lesson

The only part of a system its users ever meet - and 3 golden rules for it.

  • Define UI design, and distinguish it from architecture
  • Explain why the interface shapes how a whole system is judged
  • State and explain the 3 golden rules
  • Recognize a violation of each rule

Transcript

Everything said in the video, section by section (795 words). Read along, or search it.

User Interface Design: Principles, Guidelines, and Implementation

What Is User Interface Design and Why It Matters

Every technique covered so far shapes a system's internal quality. None of it is something a user ever sees directly. This section introduces user interface design. What it covers, why it deserves real rigor, and three golden rules that apply to almost any interface.

What Users Actually See

Exactly 1 Thing

Translating requirements into a design model. Deriving a structure chart. Organizing classes into a clean architecture. All of that shapes a system's internal quality, and none of it is visible to a user. A person using the finished system experiences exactly one thing. The interface. That means the screens, controls, messages, and interactions, standing between them and everything else that was built. A technically excellent system with a confusing interface will still feel, to the people using it, like a bad system.

Definition

What UI Design Covers

User interface design is the practice of designing how a system presents itself to, and interacts with, the people who use it. It covers the layout of information, the controls available at each moment, the feedback the system gives after an action, and the overall flow through a task. It is distinct from the system's internal architecture. Architecture determines whether the system works correctly and efficiently underneath. Interface design determines whether a person can actually understand and use it.

Figure 10.1B

The Only Part a User Meets

Here is the situation from the user's side. The user meets the interface. The screens, controls, and messages. Behind it sit the architecture, the classes and design model, and the data and structure. All of that stays permanently invisible to the user. However well it was designed, the interface is the only part of the system they ever actually meet.

Why It Matters

Not a Cosmetic Finishing Step

That is why interface design carries real, practical weight. It is not a cosmetic finishing step. A confusing interface increases training time, and increases user errors. It increases support costs. And it can cause people to abandon a system altogether, however sound the engineering underneath it is.

Golden Rule 1

Place the User in Control

Three foundational rules, often called the golden rules of interface design, apply whatever an interface looks like, or whatever platform it runs on. The first is to place the user in control. A well-designed interface responds to actions the user initiates. It does not force them through a rigid, system-dictated sequence, with no way to pause, back out, or change course. Users should feel like they are directing the interaction at every step, not being marched through it.

Golden Rules 2 and 3

Memory Load and Consistency

The second rule is to reduce the user's memory load. People have limited working memory, and a good interface does not spend it unnecessarily. Relevant information stays visible, and the interface offers recognizable cues, instead of demanding that users remember arbitrary steps. The third rule is to make the interface consistent. The same kind of action should work the same way everywhere, in terminology, visual treatment, and placement. Consistency lets something learned in one part of the interface transfer directly to every other part.

Table 10.1

The 3 Golden Rules at a Glance

Here are the three golden rules at a glance. Placing the user in control means the user directs the interaction. A common violation is a rigid sequence, with no way to go back or cancel. Reducing memory load means relevant information stays visible. A common violation is requiring users to recall details from an earlier screen. And consistency means the same action works the same way everywhere. A common violation is the same task behaving differently in different places.

Apply It

A Form With No Way Back

Let's apply that. A form requires the user to complete every field in a fixed order, with no way to skip ahead, go back, or save progress. That violates the first rule, placing the user in control. The system dictates a rigid sequence, and the user cannot pause, revise, or change course. Now think of an app or website that frustrated you recently. Which golden rule did it break? And what would changing just that one thing have done for your experience?

Key Terms

The Vocabulary of This Section

Let's lock in the key terms. User interface design is the practice of designing how a system presents itself to, and interacts with, the people who use it. The interface is everything a user directly sees, clicks, reads, and reacts to, as distinct from the internal architecture. The golden rules of interface design are user control, reduced memory load, and consistency. User control means the user directs the interaction. And consistency means the same kind of action works the same way throughout.

Key Takeaways

What to Carry Forward

To pull this together. User interface design shapes how a system presents itself to users, and it is distinct from the internal architecture. The interface is the only part of a system users ever meet, which is why it shapes how the whole system is judged. Placing the user in control means the user directs the interaction. Reducing memory load means keeping relevant information visible. And consistency means the same kind of action works the same way everywhere.

About Software Engineering at UPI Study

Software Engineering (Computer Science 301) is a self-paced online course of 103 video lessons in 15 chapters, from process models and agile to requirements, design, user interfaces, reliability, security and project management. It carries a NCCRS credit recommendation for 3 semester credits.

Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Enroll now → Course details Download the syllabus All Computer Science courses Every course with PRO →

Compare: Software Engineering vs Systems Analysis

Why take it here

Why students take Software Engineering with UPI Study

How professional software gets builtSoftware Engineering covers how teams turn requirements into working, maintainable software: process models, agile, requirements, design, testing, reliability and project management. It is a core course in computer science and software degrees.
Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.
Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.
Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.
Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.
130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Where the credit goes

Universities that work with NCCRS

Software Engineering carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Thomas Edison State UniversityThomas Edison State UniversitySigned partnerUniversity of the PeopleUniversity of the PeopleSigned partnerCharter Oak State CollegeCharter Oak State CollegeSigned partnerStrayer UniversityStrayer UniversitySigned partnerColumbia Southern UniversityColumbia Southern UniversitySigned partnerIndiana TechIndiana TechSigned partnerPenn StatePenn StateWorks with NCCRSSouthern New Hampshire UniversitySouthern New Hampshire UniversityWorks with NCCRSSUNYSUNYWorks with NCCRS +many more cooperating universitiesFind my college →

Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.

FAQ

Questions students ask us

About What Is User Interface Design and Why It Matters

What is user interface design?
User interface design is the practice of designing how a system presents itself to, and interacts with, the people who use it. It covers the layout of information, the controls available at each moment, the feedback after an action, and the overall flow through a task. It is distinct from internal architecture, which determines whether the system works correctly underneath, while UI design determines whether people can understand and use it.
What are the three golden rules of user interface design?
The three golden rules, associated with Theo Mandel, are: place the user in control, reduce the user's memory load, and make the interface consistent. User control means the user directs the interaction rather than being forced through a rigid sequence. Reducing memory load means keeping relevant information visible and offering recognizable cues. Consistency means the same kind of action works the same way everywhere, so learning transfers across the interface.
Why does user interface design matter so much for a software system?
The interface is the only part of a system a user ever meets, so it shapes how the whole system is judged. The architecture, classes, and data structures behind it stay invisible. A technically excellent system with a confusing interface still feels like a bad system, and it can increase training time, user errors, and support costs, or lead people to abandon it entirely. UI design is not a cosmetic finishing step.
What are examples of violating the golden rules of interface design?
A form that forces every field in a fixed order with no way to skip, go back, or save progress violates placing the user in control. Requiring users to recall details from an earlier screen violates reducing memory load. Having the same task behave differently in different parts of an application violates consistency. Each violation makes users work harder than the interface should require.

About the Software Engineering course

How many college credits is Software Engineering?
Software Engineering (Computer Science 301) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
How much does Software Engineering cost and what is included?
$250, paid once, with lifetime access: all 103 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. Students who want several courses choose UPI Study PRO instead.
Which universities accept UPI Study credits?
UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.
How long does Software Engineering take?
It is self-paced with no deadlines. The 103 lessons total about 11 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.
How are the exams done?
Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.
How do my credits reach my college?
When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

Ready for the full course? Earn 3 credits in Software Engineering.

103 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.

Enroll in Software Engineering →Download the syllabusEvery course with PRO →
Software Engineering
3 credits · NCCRSEnroll →