CSC4902: Computer Science Capstone 2

CSC4902 is the second and final Capella University computer science capstone, taken in your last quarter to complete the client project begun in CSC4900.

The catalog says students continue to apply knowledge and skills from other courses as they complete a project that benefits an organization, community or industry.

The description again refers to the proposal (project description, deliverables, completion dates and associated learning) and to executing it once approved, completing deliverables for the client and producing a final product.

It is a 6-credit course for BS in Computer Science students only, must be taken in the final quarter, cannot be met by transfer or prior learning credit, and has CSC4900 as its prerequisite.

Completing the Deliverables

Start the quarter by comparing where the project stands with the approved proposal. Each deliverable is either done, in progress or at risk, and the plan for the quarter follows from that.

Changes are normal in real projects. What matters is that they are agreed, explained and reflected in your final documentation, not hidden.

Testing and Evidence

Pacing the Final Quarter

• Plan to finish building well before the end of the quarter, leaving the final weeks for testing, fixes and documentation.
• Book client review sessions early; their availability may be limited.
• Write the final report alongside the build, updating it at each milestone.

Typical Work and How to Approach It

Where Students Get Stuck

• Last-minute features. New features late in the quarter introduce bugs. Freeze scope in time to test.
• Thin testing. "It works" is not evidence. Document what you tested and the results.
• Weak reflection. Be specific about what you learned, what went wrong and what you would change.
• Hand-over gaps. The client needs instructions to run and maintain the product after you leave.

Presenting the Final Product

Whether your instructor asks for a recorded demonstration, slides or a written walkthrough, the same structure works well for a technical project with a real client.

1. The problem: who the client is and what was not working.
2. The solution: what you built, in one or two sentences.
3. The demonstration: one realistic user journey from start to finish.
4. The evidence: test results and client feedback.
5. Reflection and next steps: what you learned and what future work you recommend.

Rehearse the demonstration with fresh data and a backup recording, in case something fails live. Keep technical depth for questions; most audiences want to see the product solving the problem.

Tips for the Final Quarter

• Fix the most serious bugs first; cosmetic issues can wait.
• Ask someone unfamiliar with the project to follow your user guide and note where they get stuck.
• Keep a running list of known issues so the final report is honest and complete.
• Back up the code and documentation in more than one place.

Writing the Reflection on Learning

The CSC4900 proposal listed the learning the project would involve, so the final reflection should answer it directly. Compare what you planned to learn with what actually happened.

• Name the program skills you relied on most, with one concrete moment for each.
• Describe a problem you did not expect and how you solved it.
• Explain one decision you would make differently, and why.
• Note what the client relationship taught you about requirements and communication.

Specific, honest reflection is more persuasive than claims of a flawless project.

How We Help with CSC4902

Send the instructions, scoring guide, approved proposal, current documentation and any feedback. A tutor can help you prioritize remaining work, review your code and tests, give feedback on the final report and reflection, and edit your presentation script. Our capstone project help guide covers general structure.

GradeEssays is independent of Capella University. We do not complete capstone work for submission; we tutor, review and edit so that the project stays your own under Capella's academic honesty policy. Orders include free revisions within the scope of your original request and a full refund if late.