CS471: Computer Science Pedagogy - CS4All and UDL (100 Points)
Assignment Goals
The goals of this assignment are:- Understand the principles of Universal Design for Learning (UDL)
- Understand the goals and strategies of Computer Science for All (CS4All)
- Apply UDL and CS4All principles to lesson planning in computer science
Background Reading and References
Please refer to the following readings and examples offering templates to help get you started:- Universal Design for Learning (UDL) - CAST
- Computer Science for All (CS4All)
- Promoting Effective Computing Pedagogy
- CS for ALL: Teaching All Computational Thinking through Inclusion and Collaboration (TACTIC)
- https://csteachers.org/improving-accessibility-in-the-classroom-with-the-udl4cs-interactive-table/
The Assignment
Applying UDL and CS4All to Lesson Planning
Overview
In this assignment, you will explore how the principles of Universal Design for Learning (UDL) and the Computer Science for All (CS4All) movement can be applied to make computer science education more accessible, engaging, and equitable.
Reflect on each of the 9 elements of the UDL framework, and the 12 Principles of Computing Pedagogy. Think about how they could be used to truly bring computing to all learners: across gender and other underrepresented axes, to other disciplines, and/or across all grade levels. Your report does not need to address every one of these ideas. Instead, you should form a thesis addressing what you believe is the most important change that needs to happen in the next 10 years to improve and facilitate access to computing education. Support your claim with relevant research literature, and frame your ideas within these existing frameworks. What should computing education look like for the next generation so that it represents and improvement over your own experiences?
You will reflect on these principles and write a report discussing how they could be integrated into your own lesson planning.
I highly encourage you to explore the Project TACTIC webpage from the University of Florida, which was a multi-year project to understand the specific needs for and to develop inclusivity in computing education for students with disabilities or at risk. You will find their recommendations highly relevant to your exploration. I recommend that you incorporate and cite their findings in your report. Additionally, the CSTA UDL4CS interactive table and presentations offer tangible suggestions about how to put these ideas into practice.
Instructions
Read the provided materials on UDL and CS4All to understand the core principles and goals of each framework.
In a written report, address the following:
- Summary of UDL principles and how they can enhance accessibility and engagement in CS lessons.
- Summary of CS4All goals and pedagogical principles, and how they promote equity in CS education.
- Discussion of how UDL and CS4All principles align, and could be integrated into a CS lesson plan.
- Concrete examples of how you could apply these principles to make your own CS lesson plan more accessible, engaging, and equitable.
- Properly cite at least 5 sources on UDL and CS4All in your report.
Design Questions to Help You Begin
Please answer the following questions in your README file before you begin writing your program.- What are the key principles of Universal Design for Learning (UDL)?
- What are the goals and strategies of Computer Science for All (CS4All)?
- How can UDL and CS4All principles be applied to lesson planning in computer science?
Submission
In your submission, please include answers to any questions asked on the assignment page in your README file. If you wrote code as part of this assignment, please describe your design, approach, and implementation in your README file as well. Finally, include answers to the following questions:- Describe what you did, how you did it, what challenges you encountered, and how you solved them.
- Please answer any questions found throughout the narrative of this assignment.
- If collaboration with a buddy was permitted, did you work with a buddy on this assignment? If so, who? If not, do you certify that this submission represents your own original work?
- Please identify any and all portions of your submission that were not originally written by you (for example, code originally written by your buddy, or anything taken or adapted from a non-classroom resource). It is always OK to use your textbook and instructor notes; however, you are certifying that any portions not designated as coming from an outside person or source are your own original work.
- Approximately how many hours it took you to finish this assignment (I will not judge you for this at all...I am simply using it to gauge if the assignments are too easy or hard)?
- Your overall impression of the assignment. Did you love it, hate it, or were you neutral? One word answers are fine, but if you have any suggestions for the future let me know.
- Using the grading specifications on this page, discuss briefly the grade you would give yourself and why. Discuss each item in the grading specification.
- Any other concerns that you have. For instance, if you have a bug that you were unable to solve but you made progress, write that here. The more you articulate the problem the more partial credit you will receive (it is fine to leave this blank).
Assignment Rubric
| Description | Pre-Emerging (< 50%) | Beginning (50%) | Progressing (85%) | Proficient (100%) |
|---|---|---|---|---|
| Summary of UDL Principles (20%) | Fails to summarize UDL principles or provides incorrect information. | Provides a basic summary of UDL principles but lacks detail on how they enhance accessibility and engagement in CS lessons. | Provides a clear summary of UDL principles and some insight into how they enhance accessibility and engagement in CS lessons. | Provides a comprehensive and insightful summary of UDL principles, clearly explaining how they enhance accessibility and engagement in CS lessons. |
| Summary of CS4All Goals and Pedagogical Principles (20%) | Fails to summarize CS4All goals and principles or provides incorrect information. | Provides a basic summary of CS4All goals and principles but lacks detail on how they promote equity in CS education. | Provides a clear summary of CS4All goals and principles and some insight into how they promote equity in CS education. | Provides a comprehensive and insightful summary of CS4All goals and principles, clearly explaining how they promote equity in CS education. |
| Integration of UDL and CS4All Principles into Lesson Planning (20%) | Fails to discuss integration or provides incorrect information. | Discusses integration but lacks clarity or concrete examples. | Provides clear discussion of integration with concrete examples but could be more comprehensive. | Provides clear, comprehensive, and insightful discussion of integration with concrete examples, aligning UDL and CS4All principles in a CS lesson plan. |
| Thesis and Support with Relevant Research Literature (20%) | Lacks a clear thesis or fails to support it with relevant research literature. | Presents a thesis but lacks strong support with relevant research literature. | Presents a clear thesis and supports it with relevant research literature but could be more insightful or comprehensive. | Presents a clear, insightful, and comprehensive thesis, strongly supported with relevant research literature, addressing the future of computing education. |
| Overall Clarity, Organization, and Citation (20%) | Report is disorganized, lacks clarity, and fails to properly cite sources. | Report has basic organization and clarity but lacks proper citation or could be more polished. | Report is well-organized and clear, with proper citation, but could be more polished or insightful. | Report is well-organized, clear, and polished, with proper citation, logical flow, and coherent presentation. |
Please refer to the Style Guide for code quality examples and guidelines.