Rubric for Project #2
Description
Rubric References (How our project is academically alligned)
This rubric is synthesized from college-level game development and CS capstone rubrics, including:
-
Texas A&M University – Computer Game Development Project Rubric
https://people.engr.tamu.edu/schaefer/teaching/443_Fall2013/Project1_Grading_Rubric.pdf -
UMBC – CMSC 493 / ART 485 Game Prototype Evaluation
https://userpages.cs.umbc.edu/olano/class/493-25-2/proto.html -
STEM Minds – Video Game Design Rubric
https://www.stemminds.com/wp-content/uploads/2021/03/VGD-Rubric.pdf -
University of Iowa – Game Design & Capstone Framework
https://ames.team/wp-content/uploads/2025/05/2025-game-rubric.pdf
Capstone-Aligned Game Development Rubric (combination of rubrics from the above sources)
| Category | College Capstone Project Expectation | Our Project’s Technical Connections |
|---|---|---|
| Technical Implementation & Code Quality | Clean, modular, and maintainable code; core systems implemented correctly and reliably | Object-oriented programming (classes, inheritance, encapsulation), modular architecture, separation of concerns, reusable components |
| Systems Design & Engineering Depth | Multiple systems interact cohesively; design supports scalability and iteration | System architecture design, interface-based communication, dependency management, controlled coupling |
| Theme Integration & Design Intent | Horror theme meaningfully shapes mechanics, pacing, and player decisions | State machines, event-driven programming, timing systems, data-driven behavior control |
| Gameplay & Player Experience | Intuitive controls, clear objectives, balanced difficulty, and smooth transitions | Input handling, UI state management, feedback loops, control flow, transition logic |
| Performance, Stability & Debugging | Stable performance with minimal bugs; edge cases handled | Algorithmic efficiency, memory management awareness, profiling, debugging strategies, error handling |
| Documentation & Technical Communication | Systems and design decisions clearly explained | Technical writing, code documentation, design diagrams, explanation of algorithms and architecture (we will add comments!) |
Professional and Career Relevance
This project is intentionally structured to align with the skills and practices expected in software engineering, game development, and technical roles. By completing a capstone guided by this rubric, the team gains experience that directly translates to industry expectations.
From an employer perspective, this project demonstrates:
-
Object-Oriented Programming and Architecture
The use of OOP principles (encapsulation, inheritance, modular design) mirrors how production software and game engines are built and maintained. -
Systems Thinking and Engineering Tradeoffs
Designing interacting systems (game state, AI, progression, UI) shows the ability to reason about complexity, scalability, and maintainability—key skills in large codebases. -
Problem Solving and Debugging
Performance optimization, bug fixing, and edge-case handling reflect real-world engineering workflows, not toy assignments. -
Clear Technical Communication
Documentation, design explanations, and readable code prepare the team to clearly explain technical decisions during interviews and design reviews. -
Project Ownership and Iteration
Building a complete, working system from concept to implementation demonstrates initiative, accountability, and the ability to iterate on feedback—traits employers consistently value.
When meeting with future employers, this project serves as a concrete discussion artifact:
- Code can be walked through to explain architecture and design decisions
- Systems can be discussed in terms of tradeoffs and constraints
- Gameplay mechanics can be framed as engineering solutions, not just creative ideas
Overall, this capstone positions the team with a portfolio-ready project that reflects real-world development practices, making it easier to communicate technical competence, teamwork, and problem-solving ability in professional settings.