March 30 2016 Lesson Notes: Difference between revisions
No edit summary |
No edit summary |
||
(10 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
These are the lesson notes for a class meeting. You will find links, homework, and other information about our class meeting here. If you missed a class, or you want to review what we did in a class, this is the right page for you! | These are the lesson notes for a class meeting. You will find links, homework, and other information about our class meeting here. If you missed a class, or you want to review what we did in a class, this is the right page for you! | ||
== Date == | == Date == | ||
''When was this lesson delivered?'' | |||
March 30 2016 | March 30 2016 | ||
== | == Objectives == | ||
''What are we going to learn today?'' | |||
* You will review [[conditionals]] and [[abstraction]]. You will do this through the [[date fashion]] problem set. | |||
* You will review your project on our design project. All of you will work on your design project. | |||
== Explore == | == Explore == | ||
''What kinds of hands-on/minds-on activities will we be doing?'' | |||
== Explain == | == Explain == | ||
''What are some higher order thinking questions I will use to solicit explanations and help you to justify your explanations?'' | |||
== Extend== | == Extend== | ||
''How will you develop a more sophisticated understanding of the concept?'' | |||
== Evaluate == | == Evaluate == | ||
How will | ''How will you demonstrate that you have achieved the lesson objective?'' | ||
* students will receive a formative assessment for their problem set work. [[Media:Problem-setrubric.pdf|Please click here to see how you will be graded]] | |||
== Homework == | == Homework == | ||
''What is your homework and when is it due?'' | |||
* We must work on our design project. Everyone is required to respond to Mr. MacKenty's feedback on the discussion page for your project. This homework is due at the start of our next class. | |||
== As a computer scientist, you have == | == As a computer scientist, you have == | ||
''These are the characteristics every computer scientist works towards.'' | |||
* Confidence in dealing with complexity | * Confidence in dealing with complexity |
Latest revision as of 12:43, 1 April 2016
![](/images/f/f7/Plan.png)
These are the lesson notes for a class meeting. You will find links, homework, and other information about our class meeting here. If you missed a class, or you want to review what we did in a class, this is the right page for you!
Date[edit]
When was this lesson delivered?
March 30 2016
Objectives[edit]
What are we going to learn today?
- You will review conditionals and abstraction. You will do this through the date fashion problem set.
- You will review your project on our design project. All of you will work on your design project.
Explore[edit]
What kinds of hands-on/minds-on activities will we be doing?
Explain[edit]
What are some higher order thinking questions I will use to solicit explanations and help you to justify your explanations?
Extend[edit]
How will you develop a more sophisticated understanding of the concept?
Evaluate[edit]
How will you demonstrate that you have achieved the lesson objective?
- students will receive a formative assessment for their problem set work. Please click here to see how you will be graded
Homework[edit]
What is your homework and when is it due?
- We must work on our design project. Everyone is required to respond to Mr. MacKenty's feedback on the discussion page for your project. This homework is due at the start of our next class.
As a computer scientist, you have[edit]
These are the characteristics every computer scientist works towards.
- Confidence in dealing with complexity
- Persistence in working with difficult problems
- Tolerance for ambiguity
- The ability to deal with open-ended problems
- The ability to communicate and work with others to achieve a common goal or solution
Standards[edit]
- Apply analysis, design, and implementation techniques to solve problems (e.g., use one or more software lifecycle models).
- Describe a software development process used to solve software problems (e.g., design, coding, testing, verification).
- Use collaborative tools to communicate with project team members (e.g., discussion threads, wikis, blogs, version control, etc.).