CMST 290 at the University of Maryland Global Campus introduces the code behind interactive digital media, written for designers rather than programmers.
UMGC describes it as an introduction to the principles, practices, techniques and theories that govern the use of scripting and programming languages in the design and development of interactive digital media.
The objective is to use proven scripting and programming theory to support digital media design for print, web and mobile devices. Projects involve modifying existing scripting languages and HTML code as well as conducting a usability review.
It is a 3-credit course, and UMGC lists it in certificate programs such as Augmented and Virtual Reality Design. For many design students it is the first time they read and change code, which is the main hurdle.
Course at a Glance
| Item | Details |
|---|---|
| University | University of Maryland Global Campus (UMGC) |
| Course code | CMST 290 |
| Credits | 3 |
| Subject area | Web and digital design |
| Project types | Modifying scripts and HTML code; a usability review |
| Typical work | Code modification projects with short design explanations |
What CMST 290 Covers
| Topic | What it means in practice |
|---|---|
| Scripting and programming principles | Variables, conditions, loops, functions and events |
| HTML | The structure of web pages and how scripts attach to them |
| Interactive digital media | Responding to clicks, input and other user actions |
| Design for print, web and mobile | How code supports layouts across different outputs |
| Usability review | Evaluating how easily people can use an interactive product |
Key Concepts Explained
Reading Code Before Changing It
Because projects involve modifying existing code, the first skill is reading it. Identify what each block does, which elements it affects and what triggers it, then make one change at a time.
Example: A script changes a button's color when clicked. To make it also show a message, find the click handler function, add one line that sets a paragraph's text, save, reload and test before making any other change.
Events
Interactive media responds to events: clicks, key presses, page loads or form submissions. Code "listens" for an event and runs a function when it happens.
Separation of Structure, Style and Behavior
HTML holds the structure, CSS the appearance and scripts the behavior. Keeping them apart makes code easier to change and debug.
Example: Rather than writing colors inside a script, the script adds a class such as active to an element, and the CSS file defines what active looks like. A designer can then restyle it without touching the script.
Conducting a Usability Review
UMGC names a usability review as part of the project work. A simple, credible review follows these steps:
- Define the main tasks a user should be able to complete.
- Ask a few people to try those tasks while you observe without helping.
- Note where they hesitate, make errors or give up.
- Check against recognized principles, such as Nielsen's usability heuristics.
- Recommend specific, prioritized changes.
Report what you observed, not just opinions, and link each recommendation to a finding.
Typical Assignments and How to Approach Them
| Assignment type | What it tests | How to approach it |
|---|---|---|
| HTML modification | Structure and markup | Validate the page after each change |
| Script modification | Scripting logic | Use the browser console to spot errors |
| Interactive feature | Events and behavior | Test on desktop and mobile widths |
| Usability review | Evaluation | Base findings on observed tasks |
Scripting Basics for Designers
You do not need to become a programmer, but a handful of ideas appear in almost every script you will modify:
- Variables store values, such as a score or a user's name.
- Conditions (if and else) choose between actions.
- Loops repeat actions, such as building a list of items.
- Functions group steps under a name so they can be reused.
Example: A quiz script stores the score in a variable, uses a condition to check each answer and calls a function to show the result. Changing the pass mark means editing one value, once you can see where it lives.
Where Students Get Stuck
- Small syntax errors. A missing bracket or quote can stop a whole script; the console shows the line.
- Changing too much at once. Change and test one thing at a time.
- Caching. Hard-refresh the browser if changes do not appear.
- Opinion-based reviews. Usability findings need evidence from users or heuristics.
Study Tips for CMST 290
- Use a code editor with syntax highlighting.
- Comment each change you make with a short note.
- Keep a backup of the original files.
- Practice explaining what a piece of code does in plain English.
How We Help with CMST 290
Send the project instructions, starter files, your current code and any feedback. A writer with web and interactive design experience can explain code line by line, help you find errors, prepare a model of a comparable modification, or edit your usability review.
GradeEssays is independent of the University of Maryland Global Campus. Our help is for learning; the work you submit must be your own under UMGC's academic integrity policy.
Make Your CMST 290 Project Interactive
Share the brief, code and feedback. We explain the scripting and model a clean, working version.
Start My Interactive Design HelpFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
It is a 3-credit course.
UMGC presents it as an introduction, so it is designed for students new to scripting in design.
UMGC says projects involve modifying existing scripting languages and HTML code and conducting a usability review.
UMGC describes digital media design for print, web and mobile devices.
An evaluation of how easily people can use a product, based on observing users and checking design principles.
Yes. We explain what each part does so you can modify it yourself.