March 30 2016 Lesson Notes: Difference between revisions
Line 29: | Line 29: | ||
How will students demonstrate that they have achieved the lesson objective? | How will students demonstrate that they 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 == |
Revision as of 11:35, 1 April 2016
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]
March 30 2016
Objectives[edit]
- 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]
Describe what kinds of hands-on/minds-on activities students will be doing?
Explain[edit]
List higher order thinking questions which teachers will use to solicit student explanations and help them to justify their explanations.
Extend[edit]
Describe how students will develop a more sophisticated understanding of the concept.
Evaluate[edit]
How will students demonstrate that they 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]
None.
As a computer scientist, you have[edit]
- 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.).