How xuej41/cpp-projects works
Main Components
a. Project Categories
• Laboratory Assignments (Lab0-Lab4)
• Programming Practice Assignments (PPA1-PPA3)
• Competitive Programming Solutions (DMOJ_CP_Questions)
• Course Project (Final_Course_Project)
b. Key Architectural Patterns
• Each lab/assignment follows a consistent structure with testing frameworks
• Modular design with separate header (.h) and implementation (.cpp/.c) files
• Automated testing infrastructure (GitHub Classroom integration)
Educational Labs Section
• Labs 0-4 as individual modules
• Each lab should have connections to:
• Source files (Questions.c/h)
• Test infrastructure (testCases.c)
• Build system (makefile)
• Automation (.github/classroom)
Programming Practice Assignments Section
• PPA1-3 modules
• Common components:
• MacUILib (shared library)
• Main implementation files
• Build configuration
Final Course Project Section
• Game architecture:
• Core Components (GameMechs, Player)
• UI Layer (MacUILib)
• Object Management (objPos, objPosArrayList)
• Test Suite connection
Competitive Programming Section
• Solutions by algorithm type:
• Graph Algorithms (BFS, DFS)
• Data Structures (Segment Trees, Bitset)
• Contest Solutions (CCC)
Important Details to Capture
• GitHub Classroom Integration:
• Automation workflow
• Autograding configuration
• Test case execution flow
• Build System:
• Makefile relationships
• Compilation dependencies
• Test execution paths
• Common Libraries:
• MacUILib usage across PPAs
• Shared utility functions
• Testing frameworks
Level 1 (Top): Main project categories
Level 2: Individual projects/assignments
Level 3: Component files and relationships
Level 4 (Bottom): File-level dependencies