WGU D288: Back-End Programming
D288 is the project course where WGU software students build a real back end: a Spring Boot REST application wired to a provided MySQL database and Angular front end, developed in the WGU lab environment with IntelliJ. It's assessed as a performance assessment, not an exam.
Fennie is independent and not affiliated with Western Governors University. This is an unofficial study guide.
What makes it hard
This is most students' first time connecting all the layers (entities, repositories, REST controllers, and a front end they didn't write), and the orientation cost is real. The lab environment and database setup eat early hours, and submissions get returned for missing rubric requirements like validation rules more than for broken endpoints.
What you'll cover
- • Spring Boot and REST APIs
- • JPA entities and repositories
- • MySQL integration
- • Working with a provided Angular front end
- • Data validation
- • Lab environment and IntelliJ workflow
The D288 study guide
How to study for WGU D288, step by step.
- 1
Turn the rubric into a checklist first
Every entity, endpoint, and validation rule the PA requires is in the rubric. Listing them before coding is the difference between one submission and three.
- 2
Get the lab environment and database running early
The provided MySQL database and IntelliJ lab setup are the course's known time sink. Verify you can run the starter and hit the database before planning anything else.
- 3
Trace how the front end calls the back end
Spend a session following one request from the Angular UI to the database and back. Once that path is clear, every remaining requirement is a variation on it.
- 4
Build one layer at a time and verify
Entities first, then repositories, then controllers, confirming each layer works before stacking the next. Debugging all three at once is how the project sprawls.
- 5
Check validation rules, then submit early
The easily-missed rubric items are the validation requirements. Audit them line by line and submit. Revisions are free and feedback is fast.
Today
Today's D288 plan
What a Fennie Daily Plan looks like for D288. 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 WGU D288 hard?
It's a meaningful step up. You wire Spring Boot, MySQL, and a provided Angular front end together for the first time. The difficulty is orientation and setup; the required code is reasonable once the layers make sense.
How long does D288 take?
Commonly 3-6 weeks. Getting the lab environment and database connection working in the first few days is the biggest predictor of a fast finish.
Is the D288 assessment an exam?
No. It's a performance assessment: you submit a working Spring Boot application that meets the rubric. Validation rules are the most commonly missed requirements.
More WGU courses
D287: Java Frameworks
D287 moves from core Java into Spring Boot: you take a provided starter application and extend it to meet business requirements, working with MVC structure, controllers, and templates. It's assessed as a performance assessment: a working project submission, not an exam.
D386: Hardware and Operating Systems Essentials
D386 grounds WGU's software engineering students in how machines run their code: computer architecture, memory and storage technologies, operating system functions, virtualization, RAID, and cloud and networking basics. It ends in an OA.
D387: Advanced Java
D387 caps WGU's Java sequence with a performance assessment: you extend a Spring Boot back end with an Angular front end to add multithreaded language translation and currency display, then containerize the app with Docker and document a cloud deployment plan, all through a GitLab pipeline.
D480: Software Design and Quality Assurance
D480 covers software design and QA practice through two scenario-based performance assessment tasks: a software design plan responding to a business ticket, and a quality assurance test plan for the proposed change. It's writing-heavy: documents, not code.