3.5 Basic Troubleshooting
Candidates troubleshoot basic software and hardware problems common in digital learning environments. (PSC 3.5/ISTE 3e)
Artifact: Ecology Lesson Plan
Reflection:
The Internet lesson plan created to address the content standards and technology standards of students in a culminating lesson plan that uses research-based learner-centered strategies, authentic learning tasks, as well as differentiation to address the varying learners in the classroom. As a portion of the lesson plan, there was also a management component that required me to address potential issues that may arise and how I would go about troubleshooting these problems. I outlined several potential issues that could have happened and then how I would address these problems. I created this Internet lesson plan independently and implemented the lesson plan successfully with my students.
Standard 3.5 sets the foundation for troubleshooting basic software and hardware problems. This artifact demonstrates my ability to create an entire lesson plan and prepare for potential troubleshooting issues in advance. In addition, once these issues did arise, I was able to easily troubleshoot these basic software and hardware problems. As part of the implementation of this lesson plan, I had to troubleshoot basic problems such as students being unable to login, laptop batteries running low, and not have enough computers. There was also an additional problem I had to troubleshoot in that the program I had chosen to use was blocked by the school Wi-Fi and students could not create accounts. Through troubleshooting this problem, I discovered that the Wi-Fi only blocked the creation of accounts, if a student already had an account he or she could use the program.
The creation of this Internet lesson plan and the section on troubleshooting was very beneficial to me in that I had to plan ahead and have alternate plans should troubleshooting issues arise. In the past when I create lesson plans, I do not always think ahead in terms of issues that may occur and how I will solve them. This lesson plan creation encouraged me to plan ahead in terms of troubleshooting for all lesson plans I create moving forward. In doing this lesson plan differently, I would not set particular software as the choices. In this manner, students have the option of choice and it also allows for more flexibility should a problem occur with the Wi-Fi and not being able to access a designated site.
This lesson plan was quite beneficial to student learning in that students had to create their own websites, videos, or blogs using mostly unfamiliar technology. I had to troubleshoot during the course of the lesson but students also had to troubleshoot their own minor problems as they worked through the creation of their chosen assignment. The impact of the students was assessed in several ways. First, the rubric for the lesson plan assessed their general ability to create a website, video, or blog. Additionally, their ability to troubleshoot minor problems was further assessed when using similar technology on later assignments and students being able to easily create additional projects for submission.
The Internet lesson plan created to address the content standards and technology standards of students in a culminating lesson plan that uses research-based learner-centered strategies, authentic learning tasks, as well as differentiation to address the varying learners in the classroom. As a portion of the lesson plan, there was also a management component that required me to address potential issues that may arise and how I would go about troubleshooting these problems. I outlined several potential issues that could have happened and then how I would address these problems. I created this Internet lesson plan independently and implemented the lesson plan successfully with my students.
Standard 3.5 sets the foundation for troubleshooting basic software and hardware problems. This artifact demonstrates my ability to create an entire lesson plan and prepare for potential troubleshooting issues in advance. In addition, once these issues did arise, I was able to easily troubleshoot these basic software and hardware problems. As part of the implementation of this lesson plan, I had to troubleshoot basic problems such as students being unable to login, laptop batteries running low, and not have enough computers. There was also an additional problem I had to troubleshoot in that the program I had chosen to use was blocked by the school Wi-Fi and students could not create accounts. Through troubleshooting this problem, I discovered that the Wi-Fi only blocked the creation of accounts, if a student already had an account he or she could use the program.
The creation of this Internet lesson plan and the section on troubleshooting was very beneficial to me in that I had to plan ahead and have alternate plans should troubleshooting issues arise. In the past when I create lesson plans, I do not always think ahead in terms of issues that may occur and how I will solve them. This lesson plan creation encouraged me to plan ahead in terms of troubleshooting for all lesson plans I create moving forward. In doing this lesson plan differently, I would not set particular software as the choices. In this manner, students have the option of choice and it also allows for more flexibility should a problem occur with the Wi-Fi and not being able to access a designated site.
This lesson plan was quite beneficial to student learning in that students had to create their own websites, videos, or blogs using mostly unfamiliar technology. I had to troubleshoot during the course of the lesson but students also had to troubleshoot their own minor problems as they worked through the creation of their chosen assignment. The impact of the students was assessed in several ways. First, the rubric for the lesson plan assessed their general ability to create a website, video, or blog. Additionally, their ability to troubleshoot minor problems was further assessed when using similar technology on later assignments and students being able to easily create additional projects for submission.