CS 371p

CS 371p: Object-Oriented Programming

Fall 2026: 55440 (55)
24 Aug - 7 Dec 2026
MWF 1 pm: GDC 1.304
https://gitlab.com/gpdowning-ut/cs371p/
https://www.cs.utexas.edu/~utpc/

Project #1: Collatz

Due: Wed, 9 Sep, 11:59 pm
Write a program, individually, to solve Collatz [C++23 (g++ 14.2.0, 2 sec, 512 MB, source 50 KB)].
You may not use new, delete, malloc() or free().
You may use the STL.

Rubrics

Name	Description	Points
Estimation	estimate and track time to completion
GitLab	get a GitLab account fork the public code repo (https://gitlab.com/gpdowning-ut/cs371p-collatz/) to become your private code repo (https://gitlab.com/GitLab-ID/cs371p-collatz/) give the TAs Developer access
1. GitLab Issues	enable issues here: `Settings -> General -> Visibility, project features, permissions -> Work Items` create the following issue labels here: `Manage -> Labels` (labels are case sensitive): build_files `(Blue-gray)` unit_tests `(Green-cyan)` run `(Crimson)` acceptance_tests `(Dark sea green)` hackerrank `(Titanium Yellow)` continuous_integration `(Carrot orange)` documentation `(Lavender)` ad_design `(Dark coral)` ai_criteria `(Dark coral)` create at least 30 issues with the above labels from these rubrics create at least 5 more issues for bugs and optimizations close all issues as you develop, debug, and optimize the solution	5
2. Build Files	.gitignore, ignore everything but the files listed in these rubrics .gitlab-ci.yml Makefile README.md	5
3. Unit Tests	CollatzTest.cpp create at least 15 Google Tests run astyle, a code formatter run cppcheck, a static analyzer run gcov, a coverage tool run Valgrind, a memory checker	15
4. Run	Collatz.cpp add assertions for pre/post conditions, invariants, etc. run astyle, a code formatter run cppcheck, a static analyzer do not run gcov do not run valgrind	15
5. Acceptance Tests	gpdowning-Collatz.in.txt gpdowning-Collatz.out.txt change gpdowning to your GitLab-ID create at least 75 input-output pairs `Collatz.ctd.txt`, a checktestdata schema run checktestdata, an input validator create a merge request with your input-output file pairs on https://gitlab.com/gpdowning-ut/cs371p-collatz-tests/	15
6. HackerRank	submit `Collatz.cpp` to HackerRank pass at least 2 of the 3 tests to be eligible for partial credit	15
7. Continuous Integration	show a clean build in https://gitlab.com/gpdowning-ut/cs371p-collatz/-/pipelines/ to be eligible for partial credit change gpdowning to your GitLab-ID	5
8. Documentation	create inline comments in `Collatz.cpp` specify the complexity of every function/method and the entire program in `Collatz.cpp` run doxygen on `Collatz.cpp` to produce `Collatz.html` run `git log` to produce `Collatz.log.txt` run `git rev-parse HEAD` to produce a Git SHA README.md Full Name EID GitLab ID GitLab URL GitLab Pipeline Git SHA HackerRank ID Estimated completion time Actual completion time Comments	5
9. AI Design	read Elephants, Goldfish and the New Golden Age of Software Engineering create DESIGN.md: The Problem The Technical Plan Alternatives Detailed Implementation	10
10. AI Criteria	create CRITERIA.md: reversed ranges boundaries overflow cache correctness etc. Criteria should lead to specific tests.	10
Submission	create a single PDF of README.md, DESIGN.md, and CRITERIA.md submit that PDF to Canvas

Copyright © cs371p, 1995-2026
Updated 27 Aug 2026