SNHU CS-319: UI/UX Design and Development
CS-319 covers user interface and user experience design: user-centered design principles, personas, wireframes, and prototypes. The term-long project has you design the interface for a mobile application, and many students carry that design forward into CS-360 to actually build it.
Fennie is independent and not affiliated with Southern New Hampshire University. This is an unofficial study guide.
What makes it hard
There's little coding, which surprises CS students. The work is design artifacts and written justification, and rubrics expect every design choice tied to a user need rather than personal taste. Students who skip the persona and research steps produce attractive screens that lose points for lacking documented user-centered reasoning.
What you'll cover
- • User-centered design principles
- • Personas and user research
- • Wireframing and storyboards
- • Prototyping
- • Usability and accessibility
- • Design documentation
The CS-319 study guide
How to study for SNHU CS-319, step by step.
- 1
Take the personas seriously in the early weeks
Every later design decision is supposed to trace back to a documented user need. Thin personas in week 2 make week 6's justification paragraphs impossible to write convincingly.
- 2
Justify every design choice in writing as you make it
Keep a running log of why each screen looks the way it does and which user need it serves. The rubrics grade reasoning, and reconstructing it later never reads as well.
- 3
Learn the vocabulary precisely
Graders look for correct use of design terms: affordance, visual hierarchy, accessibility, usability heuristics. A small glossary reviewed weekly covers most of the conceptual content.
- 4
Design for the CS-360 handoff
Many students build their CS-319 design in CS-360 the next term. A clean, realistic design now saves you from re-architecting screens when you have to implement them in Android Studio.
Today
Today's CS-319 plan
What a Fennie Daily Plan looks like for CS-319. Yours is built from your own syllabus and adapts every day to your deadlines and progress.
First plan free, no card required. Fennie is independent and unaffiliated with your school.
FAQ
Is CS-319 a coding class?
Mostly no. You produce design artifacts (personas, wireframes, prototypes) and written justification rather than working code. CS students often find the writing load the surprising part.
Is SNHU CS-319 hard?
It's one of the lighter CS courses in workload, but the rubrics are strict about user-centered reasoning. Designs justified by personal taste instead of documented user needs lose points regardless of how good they look.
Does CS-319 connect to CS-360?
Often, yes. Many students design a mobile app interface in CS-319 and then implement it in CS-360. Designing something realistic to build makes the follow-on course noticeably smoother.
More SNHU courses
CS-210: Programming Languages
CS-210 introduces C++ and compares how different languages handle the same problems, sitting early in SNHU's CS core after IT-140 and IT-145. The signature project is the Corner Grocer item-tracking program, which reads a file and reports item frequencies using maps.
CS-250: Software Development Lifecycle
CS-250 covers the software development lifecycle with a heavy focus on Agile and Scrum: roles, ceremonies, user stories, and how requirements become working software. There's little programming; assignments are mostly written analyses of a case-study development team.
CS-300: Data Structures and Algorithms: Analysis and Design
CS-300 is SNHU's data structures course in C++: vectors, linked lists, hash tables, and binary search trees, plus Big-O runtime analysis. It builds to the ABCU advising program project, where you choose a data structure, justify it with runtime analysis, and implement a course-catalog loader and printer.
CS-320: Software Test, Automation QA
CS-320 teaches software testing in Java: unit tests with JUnit, requirements-based test design, and basic QA strategy. Across the term you build and test three small services (contact, task, and appointment), then reflect on your testing approach in a final summary.