:white_check_mark: input :white_check_mark: program functionality :white_check_mark: output :white_check_mark: describes overall purpose of the program :white_check_mark:describes what functionality of the program is demonstrated in the video:white_check_mark: describes the input and output of the program demonstrated in the video
1
1
Data Abstraction
:white_check_mark: includes two program code segments: :white_check_mark:one shows how data has been stored in this list (or other collection type). :x: other shows the data in this same list is used as part of fulfilling the program’s purpose. :white_check_mark: identifies name of variable representing list being used :white_check_mark: describes what the data contained in this list is representing in the program.
0
0
Managing Complexity
:x: includes a program code segment that shows a list being used to manage complexity in the program. :x:explains how the named selected list manages complexity in the program code by explaining why the program code could not be written, or how it would be written differently, without using this list.
0
0
Procedural Abstraction
:white_check_mark: has two program code segments: :white_check_mark: one showing a student-developed procedure with at least one parameter that has an effect on the functionality of the procedure. :white_check_mark: other showing where the student-developed procedure is being called. :x: describes what the identified procedure does and how it contributes to the overall functionality of the program.
0
0
Algorithm Implementation
:white_check_mark: includes a program code segment of a student-developed algorithm that includes :white_check_mark: sequencing :white_check_mark: selection :white_check_mark: iteration :white_check_mark: explains in detailed steps how the identified algorithm works in enough detail that someone else could recreate it.
1
1
Testing
:white_check_mark: describes two calls to the selected procedure identified in written response 3c. Each call must pass a different argument(s) that causes a different segment of code in the algorithm to execute. :white_check_mark: describes the condition(s) being tested by each call to the procedure. :white_check_mark: identifies the result of each call.
1
1
Reflection 1
What I learned in this submission is that you have to be really specific in answering and meeting the criteria in your wording. For example, for Procedural Abstraction, the person did not get the point for explaining how the procedure contributes to the overall program. However he did state that "it allows for the program to execute smoothly," it isn't an in-depth and good enough explanation to get the point, therefore he loses the entire point.
Grading of Submission 2
Reporting Category
Requirements
Student Score
College Board Score
Program Purpose and Function
:white_check_mark: input :white_check_mark: program functionality :white_check_mark: output :white_check_mark: describes overall purpose of the program :white_check_mark:describes what functionality of the program is demonstrated in the video:white_check_mark: describes the input and output of the program demonstrated in the video
1
1
Data Abstraction
:white_check_mark: includes two program code segments: :white_check_mark:one shows how data has been stored in this list (or other collection type). :white_check_mark: other shows the data in this same list is used as part of fulfilling the program’s purpose. :white_check_mark: identifies name of variable representing list being used :white_check_mark: describes what the data contained in this list is representing in the program.
1
1
Managing Complexity
:white_check_mark: includes a program code segment that shows a list being used to manage complexity in the program. :white_check_mark: explains how the named selected list manages complexity in the program code by explaining why the program code could not be written, or how it would be written differently, without using this list.
1
1
Procedural Abstraction
:white_check_mark: has two program code segments: :white_check_mark: one showing a student-developed procedure with at least one parameter that has an effect on the functionality of the procedure. :white_check_mark: other showing where the student-developed procedure is being called. :white_check_mark: describes what the identified procedure does and how it contributes to the overall functionality of the program.
1
1
Algorithm Implementation
:white_check_mark: includes a program code segment of a student-developed algorithm that includes :white_check_mark: sequencing :white_check_mark: selection :white_check_mark: iteration :white_check_mark: explains in detailed steps how the identified algorithm works in enough detail that someone else could recreate it.
1
1
Testing
:white_check_mark: describes two calls to the selected procedure identified in written response 3c. Each call must pass a different argument(s) that causes a different segment of code in the algorithm to execute. :white_check_mark: describes the condition(s) being tested by each call to the procedure. :white_check_mark: identifies the result of each call.
1
1
Reflection 2
I agree with CollegeBoard in regards to the grading they gave this submission. I believe that his writing portion was very descriptive and specific enough so that he could secure all the points. I also like how he references the video in his writing so that he can also explain how the video and the coding are co-joined, and helps to visualize other than just his words. This is one that I will look back to when doing our project, to make sure that we submit a final product similar to the quality of this person's project.
Grading of Submission 3
Reporting Category
Criteria
What score I give them
College Board Score
Program Purpose and Function
:white_check_mark: input :white_check_mark: program functionality :white_check_mark: output :white_check_mark: describes overall purpose of the program :white_check_mark:describes what functionality of the program is demonstrated in the video:white_check_mark: describes the input and output of the program demonstrated in the video
1
1
Data Abstraction
:white_check_mark: includes two program code segments: :white_check_mark:one shows how data has been stored in this list (or other collection type). :x: other shows the data in this same list is used as part of fulfilling the program’s purpose. :x: identifies name of variable representing list being used :x: describes what the data contained in this list is representing in the program.
0
0
Managing Complexity
:white_check_mark: includes a program code segment that shows a list being used to manage complexity in the program. :x:explains how the named selected list manages complexity in the program code by explaining why the program code could not be written, or how it would be written differently, without using this list.
0
0
Procedural Abstraction
:white_check_mark: has two program code segments: :x:one showing a student-developed procedure with at least one parameter that has an effect on the functionality of the procedure. :x: other showing where the student-developed procedure is being called. :x: describes what the identified procedure does and how it contributes to the overall functionality of the program.
0
0
Algorithm Implementation
:white_check_mark: includes a program code segment of a student-developed algorithm that includes :white_check_mark: sequencing :white_check_mark: selection :x: iteration :x: explains in detailed steps how the identified algorithm works in enough detail that someone else could recreate it.
0
0
Testing
:white_check_mark: describes two calls to the selected procedure identified in written response 3c. Each call must pass a different argument(s) that causes a different segment of code in the algorithm to execute. :white_check_mark: describes the condition(s) being tested by each call to the procedure. :white_check_mark: identifies the result of each call.
1
0
Reflection 3
In submission 3, I gave a point for the Testing category, whereas CollegeBoard did not. I thought it meet the criteria, but after looking at CollegeBoard's explanation, I realized that they described two calls from the specified procedure, but the didn't describe two calls TO the specified procedure. In my project, I will be sure to be very specific when doing the testing category, and make sure that I do it correctly in terms of what the criteria is stating.
Grading of Submission 4
Reporting Category
Requirements
Student Score
College Board Score
Program Purpose and Function
:white_check_mark: input :white_check_mark: program functionality :white_check_mark: output :white_check_mark: describes overall purpose of the program :white_check_mark:describes what functionality of the program is demonstrated in the video:white_check_mark: describes the input and output of the program demonstrated in the video
1
1
Data Abstraction
:white_check_mark: includes two program code segments: :white_check_mark:one shows how data has been stored in this list (or other collection type). :white_check_mark: other shows the data in this same list is used as part of fulfilling the program’s purpose. :white_check_mark: identifies name of variable representing list being used :white_check_mark: describes what the data contained in this list is representing in the program.
1
1
Managing Complexity
:white_check_mark: includes a program code segment that shows a list being used to manage complexity in the program. :white_check_mark: explains how the named selected list manages complexity in the program code by explaining why the program code could not be written, or how it would be written differently, without using this list.
1
1
Procedural Abstraction
:white_check_mark: has two program code segments: :white_check_mark: one showing a student-developed procedure with at least one parameter that has an effect on the functionality of the procedure. :white_check_mark: other showing where the student-developed procedure is being called. :white_check_mark: describes what the identified procedure does and how it contributes to the overall functionality of the program.
1
1
Algorithm Implementation
:white_check_mark: includes a program code segment of a student-developed algorithm that includes :white_check_mark: sequencing :white_check_mark: selection :white_check_mark: iteration :white_check_mark: explains in detailed steps how the identified algorithm works in enough detail that someone else could recreate it.
1
1
Testing
:x: describes two calls to the selected procedure identified in written response 3c. Each call must pass a different argument(s) that causes a different segment of code in the algorithm to execute. :x: describes the condition(s) being tested by each call to the procedure. :x: identifies the result of each call.
0
0
Reflection 4
I thought this person did a really good job, and after learning how to grade the testing category from submission 3, I realized that this person's testing category was done very poorly. They didn't describe the specific arguments and they described the code segments rather than the result of the call. Again, I will make sure I really take my time with this part of the project, as I see many miss this for kind of doing it right, but miss parts to it which makes them lose the whole point.
Grading of Submission 1
:white_check_mark: program functionality :white_check_mark: output :white_check_mark: describes overall purpose of the program :white_check_mark:describes what functionality of the program is demonstrated in the video:white_check_mark: describes the input and output of the program demonstrated in the video
Reflection 1 What I learned in this submission is that you have to be really specific in answering and meeting the criteria in your wording. For example, for Procedural Abstraction, the person did not get the point for explaining how the procedure contributes to the overall program. However he did state that "it allows for the program to execute smoothly," it isn't an in-depth and good enough explanation to get the point, therefore he loses the entire point.
:white_check_mark: program functionality :white_check_mark: output :white_check_mark: describes overall purpose of the program :white_check_mark:describes what functionality of the program is demonstrated in the video:white_check_mark: describes the input and output of the program demonstrated in the video
Reflection 2 I agree with CollegeBoard in regards to the grading they gave this submission. I believe that his writing portion was very descriptive and specific enough so that he could secure all the points. I also like how he references the video in his writing so that he can also explain how the video and the coding are co-joined, and helps to visualize other than just his words. This is one that I will look back to when doing our project, to make sure that we submit a final product similar to the quality of this person's project.
Grading of Submission 3
:white_check_mark: program functionality :white_check_mark: output :white_check_mark: describes overall purpose of the program :white_check_mark:describes what functionality of the program is demonstrated in the video:white_check_mark: describes the input and output of the program demonstrated in the video
Reflection 3 In submission 3, I gave a point for the Testing category, whereas CollegeBoard did not. I thought it meet the criteria, but after looking at CollegeBoard's explanation, I realized that they described two calls from the specified procedure, but the didn't describe two calls TO the specified procedure. In my project, I will be sure to be very specific when doing the testing category, and make sure that I do it correctly in terms of what the criteria is stating.
:white_check_mark: program functionality :white_check_mark: output :white_check_mark: describes overall purpose of the program :white_check_mark:describes what functionality of the program is demonstrated in the video:white_check_mark: describes the input and output of the program demonstrated in the video
Reflection 4 I thought this person did a really good job, and after learning how to grade the testing category from submission 3, I realized that this person's testing category was done very poorly. They didn't describe the specific arguments and they described the code segments rather than the result of the call. Again, I will make sure I really take my time with this part of the project, as I see many miss this for kind of doing it right, but miss parts to it which makes them lose the whole point.