B-day PM Agenda
|
Remember, when I check your activities, your conclusions count 30% of your grade. Make sure your answers are worth a whole 30%. Also, if you do not include conclusion answers, you are starting at a 70.
Update 5/14/2020
Anyone sending me a Remind message saying "Hi," "Howdy," or "Hey," will get five points added to their Task #1 grade, since that seems to be the one that most people are not doing well on.
Your last assignment has been added to your curriculum tab. It is CodeHS (big surprise, haha) through Unit Four. Your assignement is due next Thursday, May 21st, with late work due by May 29th.
Anyone sending me a Remind message saying "Hi," "Howdy," or "Hey," will get five points added to their Task #1 grade, since that seems to be the one that most people are not doing well on.
Your last assignment has been added to your curriculum tab. It is CodeHS (big surprise, haha) through Unit Four. Your assignement is due next Thursday, May 21st, with late work due by May 29th.
Update 4/16/2020
Hello, Wren!!! How's everyone today? I miss your shining faces and pleasant banter with me. Send me a Remind message just to say hi. I'd love to hear from you.
eLearning....
Ok, campers.... this is what were going to do, I think....at least this is what they tell me we're doing, I think....maybe....
Don't you love indecision? So let's talk about indecision for a second. I know everyone keeps saying these are unprecedented times....yada, yada, yada, but they really are. We all have to be flexible and try to monitor and adjust schedules, expectations, and learning styles to get done what needs to get done.
I feel we have already attained a basic level of instruction needed for an entry level class computer science class. We’ve covered two block-style programming languages, including one that used an graphical user interface (GUI). We’ve also covered two text-based languages. There are particular subjects I would have liked to cover, cybersecurity, more application programming interfaces (APIs), and binary/hexadecimal understanding, that elevate this class to the level of “honors” credit we promised to bring to you, the students. However, in general, I feel good about what we have accomplished.
Here's the important grade part....
According to the District One email, because we are a semester class, students are permitted to better their third quarter grade by four points in order to come up with their semester grade. Therefore, going forward to fourth quarter…..all eLearning tasks will be shifted to fourth quarter as a "satisfactory," "needs improvement," or "missing." Satisfactory will only occur if you have a task grade that is as high or higher than your third quarter grade. Your number grade will still be in your third quarter task list so you can see what your actual percentage is. A grade of "satisfactory" will result in a one percent increase for the semester grade. I changed them all to be “not included in final grade” tasks. That way you will get a sense of the level of completion for each task, but it won’t average anything or change a number in the “grade” column. As each task gets done as "satisfactory," that will be one additional point added to the overall grade for the class.
The first task will be Days 1 and 2 of the eLearning I’ve assigned so far. The second task will be Days 3 and 4 of the eLearning I've assigned so far. If you're done with those tasks and it doesn't give you a grade higher than your third quarter average, message me and I'll discuss with you the possibility of re-taking a CodeHS quiz. Now that we're all quarantined, CodeHS has given be the ability to reset quizzes so you can take them again, but I'm not going to do it without an effort from you. Why should you be worried about it being higher than your third quarter average? Did you read the last paragraph? That is the only way it will positively affect your semester grade.
The third task is posted on my eLearning page, http://lennoncseactc.weebly.com/elearning-b-day-pm.html. It includes some of what you had for Day 5 plus a bit more. I expect this to take two weeks of my class time allotment in your eLearning situation.
Hello, Wren!!! How's everyone today? I miss your shining faces and pleasant banter with me. Send me a Remind message just to say hi. I'd love to hear from you.
eLearning....
Ok, campers.... this is what were going to do, I think....at least this is what they tell me we're doing, I think....maybe....
Don't you love indecision? So let's talk about indecision for a second. I know everyone keeps saying these are unprecedented times....yada, yada, yada, but they really are. We all have to be flexible and try to monitor and adjust schedules, expectations, and learning styles to get done what needs to get done.
I feel we have already attained a basic level of instruction needed for an entry level class computer science class. We’ve covered two block-style programming languages, including one that used an graphical user interface (GUI). We’ve also covered two text-based languages. There are particular subjects I would have liked to cover, cybersecurity, more application programming interfaces (APIs), and binary/hexadecimal understanding, that elevate this class to the level of “honors” credit we promised to bring to you, the students. However, in general, I feel good about what we have accomplished.
Here's the important grade part....
According to the District One email, because we are a semester class, students are permitted to better their third quarter grade by four points in order to come up with their semester grade. Therefore, going forward to fourth quarter…..all eLearning tasks will be shifted to fourth quarter as a "satisfactory," "needs improvement," or "missing." Satisfactory will only occur if you have a task grade that is as high or higher than your third quarter grade. Your number grade will still be in your third quarter task list so you can see what your actual percentage is. A grade of "satisfactory" will result in a one percent increase for the semester grade. I changed them all to be “not included in final grade” tasks. That way you will get a sense of the level of completion for each task, but it won’t average anything or change a number in the “grade” column. As each task gets done as "satisfactory," that will be one additional point added to the overall grade for the class.
The first task will be Days 1 and 2 of the eLearning I’ve assigned so far. The second task will be Days 3 and 4 of the eLearning I've assigned so far. If you're done with those tasks and it doesn't give you a grade higher than your third quarter average, message me and I'll discuss with you the possibility of re-taking a CodeHS quiz. Now that we're all quarantined, CodeHS has given be the ability to reset quizzes so you can take them again, but I'm not going to do it without an effort from you. Why should you be worried about it being higher than your third quarter average? Did you read the last paragraph? That is the only way it will positively affect your semester grade.
The third task is posted on my eLearning page, http://lennoncseactc.weebly.com/elearning-b-day-pm.html. It includes some of what you had for Day 5 plus a bit more. I expect this to take two weeks of my class time allotment in your eLearning situation.
eLearning, the beginning
eLearning Days 1-5 posted. Click eLearning link in the top right corner.
I will be monitoring email as "office hours" from 10-11:30 and from 1-2:30.
I would prefer you send me Remind texts, and I monitor Remind more than just those three hours.
If you aren't signed up for Remind, please sign up by texting to 81010 the text @actcbdaypm.
eLearning Days 1-5 posted. Click eLearning link in the top right corner.
I will be monitoring email as "office hours" from 10-11:30 and from 1-2:30.
I would prefer you send me Remind texts, and I monitor Remind more than just those three hours.
If you aren't signed up for Remind, please sign up by texting to 81010 the text @actcbdaypm.
Day Nineteen and Twenty, March 11th and 13th
- Blockly due today and Engineering Notebook due today
- Tuesday: Quiz on CodeHS concepts through 2.13. This will be a programming quiz worth 55 points.
- We will work on 2.1.2/3 Dead Reckoning today and Friday.
- We'll work on 2.1.2 and the first part of 2.1.3. It is five paths (four from 2.1.2 and one from 2.1.3) for the robot. We will be using V5 Text. You can google help on C++ and use the embedded help in V5 Text.
- Any time you don't spend on 2.1.2 can be spent on CodeHS. Several people are not done with the last assignment.
Day Eighteen, March 9th
- Blockly work is due Wednesday, 3/11
- Your notebooks are also due for grading on this day for your quarterly notebook grade (20%)
- Finish 2.1.1 Blockly coding
- Activity 2.1.2/3
- We'll work on 2.1.2 and the first part of 2.1.3. It is five paths (four from 2.1.2 and one from 2.1.3) for the robot. We will be using V5 Text. You can google help on C++ and use the embedded help in V5 Text.
- We'll work on 2.1.2 and the first part of 2.1.3. It is five paths (four from 2.1.2 and one from 2.1.3) for the robot. We will be using V5 Text. You can google help on C++ and use the embedded help in V5 Text.
Day Seventeen, March 5th
- Your notebooks are due for grading on Wednesday, 3/11, for your quarterly notebook grade (20%)
- Activity 2.1.1 Blockly
- This is a block => text code translator
- Use this link instead of the one they suggest: https://blockly-demo.appspot.com/static/demos/code/index.html
- Open a word document. Use "Insert" to print out and document the four programs, both blocks and code.
- You definitely should be able to finish this activity in one day. If you get done early, you may work on CodeHS
- Developer Journal Questions are available on the sign-in table
- Don't worry, we'll get back to AppInventor, but I thought we needed a bit more of a break.
Day Sixteen, March 3rd
Finish Fun Robot Maze coding today.
Print Robot coding and document Event Handlers and Procedure.
When done....
- Thursday, I'll collect 114/5 coding, documentation, journal questions, be prepared to show me your app.
Finish Fun Robot Maze coding today.
Print Robot coding and document Event Handlers and Procedure.
When done....
- 114/5 documentation
- CodeHS
Day Fifteen, February 28th
Fun Robot Maze coding today.
Print Robot coding and document Event Handlers and Procedure.
- Due Monday by 8 am...CodeHS through 2.17
- Due Tuesday...114/5 coding, documentation, journal questions
Fun Robot Maze coding today.
Print Robot coding and document Event Handlers and Procedure.
Day Fourteen, February 26th
- Complete 1.1.4 and 1.1.5, document, journal questions for each, Due Tuesday in class
- CodeHS - The next endpoint of completion will be 2.17 (Due by 8:00 am on 3/2/20).
Day Eleven and Twelve, February 18th and 20th
- CodeHS work is now late, but it's still worth doing to improve your grades. Plus, moving forward in CodeHS requires you to know the information.
- Complete 1.1.4 and 1.1.5, document, journal questions for each
- Due Wednesday
- CodeHS
Day Ten, February 13th
2) Don't have to backspace to clear previous guess
3) Multiplayer horizontal arrangement hides while playing multiplayer secret number is
being used.
4) Horizontal arrangement re-appears when reset button is selected.
5) Secret number is displayed at the end (both for single and for multiplayer)
6) Guess button disappears and guess space is disabled if the player loses
5. The grading rubric is posted at the end of the February 7th agenda.
- All A112/3 Documentation is due.
- CodeHS through 2.11 is due tomorrow by 6pm.
- Continue working on A1.1.4 with your programming pair.
- You should finish all of A114. You may continue with A115 (Remember to change file names to reflect the new activity number and add to your Design Overview.).
- Some things I am looking for when I check off your app:
2) Don't have to backspace to clear previous guess
3) Multiplayer horizontal arrangement hides while playing multiplayer secret number is
being used.
4) Horizontal arrangement re-appears when reset button is selected.
5) Secret number is displayed at the end (both for single and for multiplayer)
6) Guess button disappears and guess space is disabled if the player loses
5. The grading rubric is posted at the end of the February 7th agenda.
Day Nine, February 11th
- All A1.1.2/3 documentation (including Developer Journal Questions) is due by the beginning of class on Thursday, February 13th.
- Even though this is not a B-day, the next section of CodeHS will be due on Friday, February 14th. All work through 2.11 will be due.
- First, you will take an A112/3 Quiz. W: drive; A1.1.3 Quiz; password: secret
- The quiz has a 20 minutes time limit.
- Type your whole C1100-### in for your student code, not just the last three numbers.
- You may use your notebooks.
- The rest of today you may work on CodeHS. CodeHS through all 2.11 activities are due Friday by 6 pm.
- However, you may feel like you need to work on other activities from this class.
- If you need to catch up on A112/3 coding or documentation or
- A114 Design Overview, you may do this.
- No other A114 work should be done.
Day Eight, February 7th
use your Initial Backlog as checklist
if your initial backlog is not a checklist, re-write it
Filling Viewer screen first? - this should be on your checklist
b. Renaming components/Naming the file - don't forget
c. Remember how to use Horizontal Arrangement? - Fill Parent
d. Some things I am looking for when I check off your app:
1. Don't have to backspace over words to enter numbers
2. Don't have to backspace to clear previous guess
3. Multiplayer horizontal arrangement hides while playing multiplayer secret number is
being used.
4. Horizontal arrangement re-appears when reset button is selected.
5. Secret number is displayed at the end (both for single and for multiplayer)
6. Guess button disappears and guess space is disabled if the player loses
e. Document..... Coding, Viewer, File list, Document Overview, Journal Questions
A114 Grading Rubric:
- All A1.1.2/3 documentation is due by the beginning of class on Thursday, February 13th.
- Even though this is not a B-day, the next section of CodeHS will be due on Friday, February 14th. All work through 2.11 will be due, however, you will have one whole day on Tuesday, February 11th in class to work on it.
- You may have until 1:00 to debug and print documentation for A112/3
- Before you begin - Global vs Local Variable, Pair Programming roles and relational operators
- A1.1.4 pointers...
use your Initial Backlog as checklist
if your initial backlog is not a checklist, re-write it
Filling Viewer screen first? - this should be on your checklist
b. Renaming components/Naming the file - don't forget
c. Remember how to use Horizontal Arrangement? - Fill Parent
d. Some things I am looking for when I check off your app:
1. Don't have to backspace over words to enter numbers
2. Don't have to backspace to clear previous guess
3. Multiplayer horizontal arrangement hides while playing multiplayer secret number is
being used.
4. Horizontal arrangement re-appears when reset button is selected.
5. Secret number is displayed at the end (both for single and for multiplayer)
6. Guess button disappears and guess space is disabled if the player loses
e. Document..... Coding, Viewer, File list, Document Overview, Journal Questions
A114 Grading Rubric:
Day Seven, February 5th
b. show Mrs. Lennon your working app
c. complete the Developer Journal Questions
d. go through A112 and A113 and make sure you have any vocabulary words you're not familiar
with written out in your notebook so you can use that during the quiz.
e. all work will be graded Thursday, February 6th.
You have until 2 to work on A112/3.
2. We will be doing 1.1.4 next. If you are ready to begin, you may start with the design overview.
Please do not go beyond the design overview because we will be going forward using pair
programming.
3. If you are done with all work, you may continue with CodeHS.
- A1.1.2/3 work is due by the beginning of class on Friday, February 7th.
- Even though this is not a B-day, the next section of CodeHS will be due on Friday, February 14th. All work through 2.11 will be due, however, you will have one whole day on Tuesday, February 11th in class to work on it.
- When done with A113, you will need to...
b. show Mrs. Lennon your working app
c. complete the Developer Journal Questions
d. go through A112 and A113 and make sure you have any vocabulary words you're not familiar
with written out in your notebook so you can use that during the quiz.
e. all work will be graded Thursday, February 6th.
You have until 2 to work on A112/3.
2. We will be doing 1.1.4 next. If you are ready to begin, you may start with the design overview.
Please do not go beyond the design overview because we will be going forward using pair
programming.
3. If you are done with all work, you may continue with CodeHS.
Day Six, February 3rd
Documentation and Developer Journal Questions for A1.1.1 and CodeHS (through 2.3.6) are due today.
Documentation and Developer Journal Questions for A1.1.1 and CodeHS (through 2.3.6) are due today.
- Discussion about abstraction
- A111 Quiz (open notes, but 20 minute time limit)
- A1.1.2 Happy Accelerometer - If you have not gotten your smiley face to move, you are a bit behind. When you are done with A1.1.2, re-save with the new activity name, A113. You will take your coding straight into A1.1.3. No screenshots need to be made at the end of A112; this will be done after A113. Everyone should get done with A113 today.
- Challenges are not part of the requirements for this activity.
- We will worry about screen shots next class.
- Journal questions ARE DUE next class.
- Challenges are not part of the requirements for this activity.
Day Five, January 30th
Documentation and Developer Journal Questions for A1.1.1 are due on Monday, February 1st. CodeHS through 2.3.6 is also due Monday.
Log in to my.PLTW.org, and AppInventor.
Go over color channels and transparency
1. Documentation on Activity 1.1.1 Digital Doodle
a. You need to get at least Challenge A done to get a 95%. Completing Challenge B & C
will give you the possibility of 100%.
b. You will only have 30 minutes to work on A111, including printing out the documentation.
c. Leave journal questions until last, so you can make sure you get everything printed you need.
d. Look back through the activity and see if there are any notes you should take. Think about it in
terms of a quiz; think....if Mrs. Lennon asked me a question on this, would I understand it?
2. Downloading AppInventor files to your P: drive
3. A1.1.2/3 Happy Accelerometer - Activity leads straight into A1.1.3, so there will not be separate
grading for A1.1.2 and therefore not a separate set of journal questions. You should at least finish with
A1.1.2 by the end of class.
a. Extracting from a zipped file/folder
b. Write out your Design Overview
c. Renaming components correctly
This is the rubric for A1.1.2/1.1.3:
Documentation and Developer Journal Questions for A1.1.1 are due on Monday, February 1st. CodeHS through 2.3.6 is also due Monday.
Log in to my.PLTW.org, and AppInventor.
Go over color channels and transparency
1. Documentation on Activity 1.1.1 Digital Doodle
a. You need to get at least Challenge A done to get a 95%. Completing Challenge B & C
will give you the possibility of 100%.
b. You will only have 30 minutes to work on A111, including printing out the documentation.
c. Leave journal questions until last, so you can make sure you get everything printed you need.
d. Look back through the activity and see if there are any notes you should take. Think about it in
terms of a quiz; think....if Mrs. Lennon asked me a question on this, would I understand it?
2. Downloading AppInventor files to your P: drive
3. A1.1.2/3 Happy Accelerometer - Activity leads straight into A1.1.3, so there will not be separate
grading for A1.1.2 and therefore not a separate set of journal questions. You should at least finish with
A1.1.2 by the end of class.
a. Extracting from a zipped file/folder
b. Write out your Design Overview
c. Renaming components correctly
This is the rubric for A1.1.2/1.1.3:
Reminders for documentation:
a. Save coding as a .png (right click in white space of "Blocks"). Open Word, change layout to
landscape, type your name at the top of the page. From "Downloads" folder, highlight the
.png file that has your coding. While it's highlighted, select "Ctrl C." Go to your Word document.
Hit "Enter" after your name. Select "Ctrl V." Your coding should show up. Print this page.
(C1100 printer) Cut and tape into your engineering notebook. Remember all of the correct
things to do with inserts. After they're are properly inserted in your notebook, annotate the Event
Handlers and any other vocabulary (color channels? transparency?)
b. Open a new Word document. Type your name at the top of the page. Use "Insert," "Screen
Shot," "Screen Clipping" to cut and paste the "Viewer" and "Components" of the Designer
screen into the Word document.
c. Open a new Word document. Type your name at the top of the page. Use "Insert," "Screen
Shot," "Screen Clipping" to cut and paste the "Name" and "Date Created" columns of MyProjects
into the Word document.
d. Answer Developer Journal Questions (you may tape in on left side and answer on right side).
These will be your conclusions questions for this activity, so make sure you answer with enough
information that you will get full credit.
a. Save coding as a .png (right click in white space of "Blocks"). Open Word, change layout to
landscape, type your name at the top of the page. From "Downloads" folder, highlight the
.png file that has your coding. While it's highlighted, select "Ctrl C." Go to your Word document.
Hit "Enter" after your name. Select "Ctrl V." Your coding should show up. Print this page.
(C1100 printer) Cut and tape into your engineering notebook. Remember all of the correct
things to do with inserts. After they're are properly inserted in your notebook, annotate the Event
Handlers and any other vocabulary (color channels? transparency?)
b. Open a new Word document. Type your name at the top of the page. Use "Insert," "Screen
Shot," "Screen Clipping" to cut and paste the "Viewer" and "Components" of the Designer
screen into the Word document.
c. Open a new Word document. Type your name at the top of the page. Use "Insert," "Screen
Shot," "Screen Clipping" to cut and paste the "Name" and "Date Created" columns of MyProjects
into the Word document.
d. Answer Developer Journal Questions (you may tape in on left side and answer on right side).
These will be your conclusions questions for this activity, so make sure you answer with enough
information that you will get full credit.
Day Four, January 28th
CodeHS work needs to be completed through the 2.3 activities by Monday, 2/3/2020. This means the activities should be done, including 2.3.6, when you arrive in class. There will be no class time on Monday, 2/3 devoted to CodeHS work.
Beginning:
1. Design Overview A1.1.1
2. Reminder for file naming and required number of versions for each activity.
3. Work on Activity 1.1.1 Digital Doodle
- Split your screen so you have 2/3 App Inventor and 1/3 PLTW
- You need to get at least Challenge A done to get a 95%. Completing Challenge B & C
will give you the possibility of 100%.
- Today will be the last day to work on A1.1.1.
To see what you will be graded on, read through the rubric at the end of the Day Three information.
CodeHS work needs to be completed through the 2.3 activities by Monday, 2/3/2020. This means the activities should be done, including 2.3.6, when you arrive in class. There will be no class time on Monday, 2/3 devoted to CodeHS work.
Beginning:
- Sign in
- Take out pen; Stow backpack under your assigned table.
- Bring pen and notebook to your computer seats.
- Log in to your computer, my.PLTW.org and App Inventor
- Grab a school phone and a cord
- Work on CodeHS until we are ready to begin. I have a little part of the activity to go over with you.
1. Design Overview A1.1.1
2. Reminder for file naming and required number of versions for each activity.
3. Work on Activity 1.1.1 Digital Doodle
- Split your screen so you have 2/3 App Inventor and 1/3 PLTW
- You need to get at least Challenge A done to get a 95%. Completing Challenge B & C
will give you the possibility of 100%.
- Today will be the last day to work on A1.1.1.
To see what you will be graded on, read through the rubric at the end of the Day Three information.
Day Three, January 23rd
Beginning:
1. From A1.1.1 - Summarize Collaborative Strategies
2. Work on Activity 1.1.1 Digital Doodle
- Quick tour of App Inventor
- Log in to App Inventor
- Split your screen so you have 2/3 App Inventor and 1/3 PLTW
- You need to get at least Challenge A done to get a 95%. Completing Challenge B & C
will give you the possibility of 100%.
Rubric for A1.1.1 Grading:
Beginning:
- Sign in
- Take out pen; Stow backpack under your assigned table.
- Bring pen and notebook to your computer seats.
- Log in to your computer and my.PLTW.org
- Do you have course unit summaries done?
1. From A1.1.1 - Summarize Collaborative Strategies
2. Work on Activity 1.1.1 Digital Doodle
- Quick tour of App Inventor
- Log in to App Inventor
- Split your screen so you have 2/3 App Inventor and 1/3 PLTW
- You need to get at least Challenge A done to get a 95%. Completing Challenge B & C
will give you the possibility of 100%.
Rubric for A1.1.1 Grading:
Day Two, January 22nd
1. Syllabus
2. Engineering Notebook notes
3. ERS and Notebook rubrics - practice using engineering notebook
4. Phone/Breaktime policy- practice using engineering notebook
5. Quick tour of the course
6. Learn activity navigation within PLTW
7. Log in to my.PLTW.org and summarize course units.
- Select the unit, then the unit "Landing Page"
- Read through the Prefaces for all of the lessons for that unit and come up with ONE 30-40
word summary of what that unit will be covering.
8. Sign up for MIT App Inventor
9. CodeHS work. Should be able to complete THROUGH 2.2 activities?
1. Syllabus
2. Engineering Notebook notes
3. ERS and Notebook rubrics - practice using engineering notebook
4. Phone/Breaktime policy- practice using engineering notebook
5. Quick tour of the course
6. Learn activity navigation within PLTW
7. Log in to my.PLTW.org and summarize course units.
- Select the unit, then the unit "Landing Page"
- Read through the Prefaces for all of the lessons for that unit and come up with ONE 30-40
word summary of what that unit will be covering.
8. Sign up for MIT App Inventor
9. CodeHS work. Should be able to complete THROUGH 2.2 activities?
Day One: January 16th
GREAT first day!
1. Scavenger Hunt
2. Name tags - rubric activity
3. Welcome letter
- Please return with a signature
- Remind sign up
4. Computer registration for username
5. Learn how to troubleshoot our own computer issues
6. Sign up for CodeHS - https://codehs.com/go/17EA0
GREAT first day!
1. Scavenger Hunt
2. Name tags - rubric activity
3. Welcome letter
- Please return with a signature
- Remind sign up
4. Computer registration for username
5. Learn how to troubleshoot our own computer issues
6. Sign up for CodeHS - https://codehs.com/go/17EA0