SNHU CS-499: Computer Science Capstone
CS-499 is the final course of SNHU's CS program: you select artifacts from earlier courses and enhance them in three categories (software design and engineering, algorithms and data structures, and databases), assembling everything into a professional ePortfolio with a code-review video and a self-assessment.
Fennie is independent and not affiliated with Southern New Hampshire University. This is an unofficial study guide.
What makes it hard
There's no new material; the difficulty is scope management and writing. Students routinely over-promise enhancements in week 1 and drown by week 5, and the narratives explaining how each enhancement demonstrates a course outcome are graded as seriously as the code itself.
What you'll cover
- • Artifact selection and enhancement planning
- • Software design and engineering enhancement
- • Algorithms and data structures enhancement
- • Database enhancement
- • Code review
- • Professional self-assessment and ePortfolio
The CS-499 study guide
How to study for SNHU CS-499, step by step.
- 1
Pick artifacts you understand completely
Choose projects you could explain line by line, not the most impressive ones. The code review video and narratives require deep familiarity, and relearning an old project burns weeks you don't have.
- 2
Scope enhancements you can finish by week 3 of planning
The classic CS-499 failure is over-promising in the plan and drowning mid-term. A modest enhancement done well and explained clearly outscores an ambitious one left half-built.
- 3
Script the code review before recording
The video walkthrough is graded on analysis (existing weaknesses and planned improvements), not production value. A written outline keeps it complete and under control.
- 4
Write each narrative the same week as the enhancement
The narratives connecting your work to course outcomes are half the deliverable. Drafting them while the decisions are fresh produces better writing in half the time.
Today
Today's CS-499 plan
What a Fennie Daily Plan looks like for CS-499. 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 SNHU CS-499 hard?
It's more a project-management test than a technical one: no new concepts, but three enhancements plus substantial writing in 8 weeks. Students who scope modestly and start the narratives early consistently report a smooth term.
What do you do in the CS-499 capstone?
You enhance artifacts from earlier courses in three categories (software engineering, algorithms and data structures, and databases) and present them in an ePortfolio with a recorded code review and a professional self-assessment.
Can I use one project for all three CS-499 enhancements?
Yes, a single artifact can be enhanced across all three categories, and many students do exactly that. The requirement is demonstrating each category's outcomes, not using three separate projects.
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.