CMST 308 at the University of Maryland Global Campus teaches a user-centered design process that ends in a working prototype backed by usability data.
UMGC describes it as a hands-on, project-based introduction to user experience (UX) and user interface (UI) design, including design thinking and the basic practices of user experience, interface and interaction design.
The focus is a user-centric, systematic, data-driven process of research, concept generation, prototyping and refinement. The goal is to evaluate user interfaces and create a working prototype using industry-standard techniques guided by usability data.
It is a 3-credit course in UMGC's Web and Digital Design pathway. Students often rush to visual design; the course rewards evidence from users at every step.
Course at a Glance
| Item | Details |
|---|---|
| University | University of Maryland Global Campus (UMGC) |
| Course code | CMST 308 |
| Credits | 3 |
| Format | Hands-on, project-based |
| Main output | A working prototype guided by usability data |
| Typical work | User research, wireframes, storyboards, prototypes and usability evaluations |
What CMST 308 Covers
| Topic (UMGC) | What it means in practice |
|---|---|
| Design thinking | Empathise, define, ideate, prototype and test, repeated |
| Human-computer interaction | How people perceive and use interfaces |
| User research | Interviews, surveys, observation and personas |
| Measuring interface quality | Task success, time on task, errors and satisfaction |
| Wireframing and prototyping | From low-fidelity sketches to interactive prototypes |
| Virtual experiences and storyboarding | Planning interactions and user journeys visually |
| Career paths | UX and UI roles and the skills they require |
Key Concepts Explained
Problem Statements and Personas
Research becomes useful when it is turned into a clear problem statement. Personas summarize the needs and behaviors of key user groups, based on real findings rather than guesses.
Example: After interviewing six commuters, you write: "Daily bus riders need to know whether the next bus is on time before they leave home, because a missed connection can make them late for work." Every later design choice can be checked against that need.
Fidelity
Low-fidelity wireframes test structure and flow cheaply. High-fidelity prototypes test visual detail and interaction. Changing structure late is expensive, so test early with rough versions.
Usability Metrics
UMGC emphasizes measuring interface quality. Common measures include task success rate, time on task, error count and a satisfaction score such as the System Usability Scale (SUS).
Example: Five testers try to set a trip alert. Three succeed on the first prototype. After moving the alert button to the main screen, all five succeed and average time falls. Report both rounds to show data-driven refinement.
From Research to Prototype
- Research: interview or survey real users and observe current behavior.
- Define: write personas and a problem statement.
- Ideate: sketch several concepts before choosing one.
- Storyboard and wireframe: map the journey and screen structure.
- Prototype: build an interactive version in an industry-standard tool.
- Test and refine: run usability tests, measure, change and retest.
Document each stage with artifacts and short explanations; together they form a UX case study.
Typical Assignments and How to Approach Them
| Assignment type | What it tests | How to approach it |
|---|---|---|
| User research plan | Research design | Set goals, questions and participants |
| Personas and journeys | Synthesis | Base every detail on findings |
| Wireframes and storyboards | Structure and flow | Start low-fidelity |
| Prototype | Interaction design | Make the core tasks fully clickable |
| Usability evaluation | Measurement | Use defined tasks and metrics |
Running a Usability Test Session
Usability data guides the prototype in CMST 308, so the quality of your sessions matters. A simple session plan:
- Welcome the participant and explain that you are testing the design, not them.
- Ask them to think aloud as they work.
- Give realistic tasks without hints, such as "Set an alert for your morning bus".
- Record success, time, errors and comments for each task.
- Finish with a short questionnaire, such as SUS, and an open question.
Resist helping when participants struggle; the struggle is the data.
Where Students Get Stuck
- Designing for yourself. Ground decisions in user data.
- Leading questions in research. Ask about past behavior, not hypothetical preferences.
- Polishing too early. Test rough versions first.
- Testing without metrics. Define tasks and measures before sessions.
Study Tips for CMST 308
- Recruit testers early; even a few sessions reveal major problems.
- Record findings in a simple spreadsheet so patterns stand out.
- Keep every version of your wireframes to show iteration.
- Write your case study as you go, not at the end.
How We Help with CMST 308
Send the project brief, your research notes, wireframes or prototype link and any feedback. A writer with UX experience can help you plan research and usability tests, structure personas and journey maps, critique a prototype, or edit your case study and design rationale. Our case study writing guide covers structure.
We never invent research data: findings must come from your own users. GradeEssays is independent of the University of Maryland Global Campus, and the work you submit must be your own under UMGC's academic integrity policy.
Make Your CMST 308 Project User-Centered
Share the brief, research and prototype. We help you structure research, testing and a clear design rationale.
Start My UX Design HelpFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
It is a 3-credit course.
Yes. UMGC describes it as a hands-on, project-based introduction to UX and UI design.
UMGC's stated goal is to evaluate user interfaces and create a working prototype guided by usability data.
UX covers the whole experience of using a product; UI is the visual and interactive layer people touch.
UMGC refers to industry-standard techniques; your section may specify a tool.
No. Research must come from real users. We help you plan, analyze and write it up.