C867 / JYM2 Class Roster - Completion Guide
WGU C867 / JYM2
TASK 1 - CLASS ROSTER
Rubric-Aligned Completion Guide & C++ Project Template
Purpose: This document is a detailed learning and completion aid for the C867 Class Roster
performance assessment. It is intentionally not a ready-to-submit assessment: student-specific
information and several key implementation sections remain marked TODO so you can
complete and understand your own work.
2026 Edition | Clear six-file architecture | Validation checklist | Expected-output guide
Project Language Primary Concepts
C867 Scripting and C++ OOP, parsing, arrays of
Programming - Applications pointers, validation, dynamic
memory
Rubric-aligned learning aid - verify against the current WGU task page before submission
, C867 / JYM2 Class Roster - Completion Guide
1. Use This Guide Correctly
The assessment requires you to demonstrate your own C++ skills. Use this guide to understand the
required architecture, build your project, test it, and check it against the rubric. Replace every
bracketed placeholder and complete every TODO yourself.
Important: Do not submit this PDF as the performance assessment. Your assessment deliverable
is your own C++ project/source files in the format required by the current WGU task page.
Publicly available copies of the Class Roster instructions consistently describe a six-file project:
degree.h, student.h, student.cpp, roster.h, roster.cpp, and main.cpp. They also require a
DegreeProgram enumeration, Student and Roster classes, student-data parsing, invalid-email
detection, average-days calculation, degree filtering, removal testing, and dynamic-memory cleanup.
2. Rubric-to-File Map
Rubric Area What You Must Demonstrate Primary File(s)
A Replace the fifth student record main.cpp
with your personal data.
B Create exactly the required six Project structure
C++ source/header files.
C Define DegreeProgram with degree.h
SECURITY, NETWORK,
SOFTWARE.
D Student data members, getters, student.h / student.cpp
setters, constructor, print().
E Roster pointer array, parsing, roster.h / roster.cpp
add/remove, print functions.
F Demonstrate the required calls main.cpp / roster.cpp
in main() and cleanup.
G Professional naming, All files / console output
formatting, comments,
readable output.
3. Recommended Project Folder
C867_ClassRoster/
|
|-- degree.h
|-- student.h
|-- student.cpp
|-- roster.h
Rubric-aligned learning aid - verify against the current WGU task page before submission
, C867 / JYM2 Class Roster - Completion Guide
|-- roster.cpp
`-- main.cpp
Do not add legacy subclass files such as SecurityStudent, NetworkStudent, or SoftwareStudent unless
your current WGU rubric explicitly asks for them. Older versions of C867 used a different
architecture.
Rubric-aligned learning aid - verify against the current WGU task page before submission
WGU C867 / JYM2
TASK 1 - CLASS ROSTER
Rubric-Aligned Completion Guide & C++ Project Template
Purpose: This document is a detailed learning and completion aid for the C867 Class Roster
performance assessment. It is intentionally not a ready-to-submit assessment: student-specific
information and several key implementation sections remain marked TODO so you can
complete and understand your own work.
2026 Edition | Clear six-file architecture | Validation checklist | Expected-output guide
Project Language Primary Concepts
C867 Scripting and C++ OOP, parsing, arrays of
Programming - Applications pointers, validation, dynamic
memory
Rubric-aligned learning aid - verify against the current WGU task page before submission
, C867 / JYM2 Class Roster - Completion Guide
1. Use This Guide Correctly
The assessment requires you to demonstrate your own C++ skills. Use this guide to understand the
required architecture, build your project, test it, and check it against the rubric. Replace every
bracketed placeholder and complete every TODO yourself.
Important: Do not submit this PDF as the performance assessment. Your assessment deliverable
is your own C++ project/source files in the format required by the current WGU task page.
Publicly available copies of the Class Roster instructions consistently describe a six-file project:
degree.h, student.h, student.cpp, roster.h, roster.cpp, and main.cpp. They also require a
DegreeProgram enumeration, Student and Roster classes, student-data parsing, invalid-email
detection, average-days calculation, degree filtering, removal testing, and dynamic-memory cleanup.
2. Rubric-to-File Map
Rubric Area What You Must Demonstrate Primary File(s)
A Replace the fifth student record main.cpp
with your personal data.
B Create exactly the required six Project structure
C++ source/header files.
C Define DegreeProgram with degree.h
SECURITY, NETWORK,
SOFTWARE.
D Student data members, getters, student.h / student.cpp
setters, constructor, print().
E Roster pointer array, parsing, roster.h / roster.cpp
add/remove, print functions.
F Demonstrate the required calls main.cpp / roster.cpp
in main() and cleanup.
G Professional naming, All files / console output
formatting, comments,
readable output.
3. Recommended Project Folder
C867_ClassRoster/
|
|-- degree.h
|-- student.h
|-- student.cpp
|-- roster.h
Rubric-aligned learning aid - verify against the current WGU task page before submission
, C867 / JYM2 Class Roster - Completion Guide
|-- roster.cpp
`-- main.cpp
Do not add legacy subclass files such as SecurityStudent, NetworkStudent, or SoftwareStudent unless
your current WGU rubric explicitly asks for them. Older versions of C867 used a different
architecture.
Rubric-aligned learning aid - verify against the current WGU task page before submission
