Brief Description

In this lesson, students will discuss what appropriate behaviors are needed to be ”good” computer users. They will then generate a chart of computer expectations, which can then be hung in the classroom - using Word. The chart will then be shared & discussed with their parents at either a Net Buddy Nite or in a handout at home with their parent (if they are unable to attend a Net Buddy Nite).

Standards and Frameworks

Technology Standards

2T-F1. Demonstrate respect for other students while using technology
2T-R1. Work cooperatively and collaboratively when using technology in the classroom. 2T-R2. Practice responsible use of technological devices.
Academic Standards
2SS-R1. Describe how a good citizen conducts oneself, with emphasis on: why we have expectations and the consequences when we disregard them.
Objectives

Academic

Technological Pre-Requisite Technology Skills Materials

Computer, AverKey, Chart paper, printer

Accommodations for Special Needs

All of my students have special needs. Many have behavioral goals and objectives as well as academic. This lesson was developed to target both areas. Students will work both cooperatively during the course of this lesson. They will be available to support each other in both academic & technology tasks required within this lesson. Extended time & flexible scheduling will be provided if needed.

Procedures
Students attend the Learning Lab for 60 min time blocks / 4 days a week
This activity takes approximately two to three class sessions to complete.

  1. Students need to understand that certain expectations must be met in a classroom when they are using the computer.  They need to know that it is expected that they take turns, respect each other’s work, respect the computer and be responsible when using it. In order to learn these ideas, the teacher will need to role play both positive & negative behavioral choices. The class will observe the teacher act various situations & discuss what might be accepatble or not with what they observe. You, as the teacher will pretend to work on the computer and have the students raise their hands if they see something wrong.
  2. The role plays should involve the students as much as possible. The ideas to be conveyed through role play include, but are not be limited: no food & drinks on/near the computers, treating the keyboard, etc. with care (no rough handling/banging), avoid moving computers & computer stations without teacher/adult help/permission, not to force disks or CDs into trays or slots, remembering to not touch electrical outlets, etc. Most of these are safety issues. You, as the teacher, will go through various role plays & should write down the expectation (in their language/phrasing) that goes with each situation acted out on the board or chart paper. The goal is to get the students to say what they should be expected to do when they use computers in the classroom. Be sure to ask why they think their expectation is good. Try to keep the expectations fairly simple and broad. Don't have rules so narrow that they begin to think of all the exceptions.
  3. Students need to recognize that there are a limited number of computers in a classroom and they must learn to take turns. To demonstrate this point, have a student volunteer come up and pretend that they want to use the computer. Play the part of the student who is less than cooperative & won’t take turns. They need to see how it look to others. After the role play, ask the students what is wrong with your behavior? Have them discuss what would have been a better way to have dealt with the situation.  Everyone likes to be on the computer, but they need to think what would be fair for all. Ask how they could resolve this problem in a fair manner? How can you take turns at the computer? Write down possible solutions for them to refer to later.
  4. Students also need to understand that they need to demonstrate respect for each other's work. Again act out a situation where someone either alters or deletes another student's work. They need to think of how it would make them feel to have their work eliminated  or just not valued by their classmates.  Have them think of posible options of what to do if  they should find someone’s work left on the computer? Should they ever delete anything without asking first?  Write their possible solutions on the board.
  5. Now have them go back over the list developed. Have them decide if the list developed covers our classoom's needs. Have them help make any changes necessary. Try to end up with six or so expectations.
  6. The next step is to use technology to make a chart of these rules. Explain that you will divide the class into pairs. Have each pair be responsible for making a sign that will explain one of the rules the class developed.
  7. Work through this process with the group first. Use think-aloud strategies to show how you would create a rule sign.
  8. Use the AverKey to project your work so the students can see.
  9. Next, use this URL to visit a site that has numerous links for clipart. Show them how to use the clip art links to find a picture to help explain an expectation.  Show them how to import the picture into Word and then type in the words below.
  10. My groupings are smaller so I can have all of my groups work at the same time if I pair them up. If this isn't the case for you, have each pairing work on this project during center time. Plan to move about and facilitate this process with the various groups. Continually remind them to use the CUPS process ( U- for Understanding is the most important. C = Capitals, U = Understanding, P = Punctuation,  S = Spelling.  Help them to create the sign and print it out.
  11. Display the signs by the computer center for Net Buddy Nite.  Go through each sign with class and discuss what each sign means.  If students are unable to attend Net Buddy Nite, you may wish to send a copy home for the child to discuss with their parents.
Assessment

The students will be assessed individually and as a group through a checklist.

Teacher Name: Barbara Peers Robeson
Site: Donaldson
Date Submitted: April 15, 2002