D2: Evaluate Success based on Design Specifications

D3: Explain Improvements


D2

RUBRIC

7 - 8

critically evaluates the success of the solution against the design specification based on authentic product testing

5 - 6

explains the success of the solution against the design specification based on relevant product testing

3 - 4

outlines the success of the solution against the design specification based on relevant product testing

1 - 2

states the success of the solution

Note: The highlighted terms above are defined here:MYP Command Terms

EXEMPLAR

Mark Band 7 - 8  critically evaluates the success of the solution 

Mark Band  5-6 explains the success of the solution


Below are examples used outside of the planner in a presentation 

D2 exemplar.pdf

D3

RUBRIC

7 - 8

explains how the solution could be improved

5 - 6

describes how the solution could be improved

3 - 4

outlines how the solution could be improved

1 - 2

not applicable

Note: The highlighted terms above are defined here:MYP Command Terms

D4

RUBRIC

7 - 8

explains the impact of the product on the client/target audience

5 - 6

explains the impact of the solution on the client/target audience, with guidance

3 - 4

outlines the impact of the solution on the client/target audience

1 - 2

not applicable

Note: The highlighted terms above are defined here:MYP Command Terms

Level 2 EXEMPLAR

Mark band 7-8  explains how the solution could be improved

Mark band  5-6  describes how the solution could be improved


Below are examples used outside of the planner in a presentation 

Approaches to learning

Measuring Success

Measuring the success of your product or solution is an important step of the design cycle. Once you identify what went well, you can reflect on what did not go well and work to fix that in the next iteration.

Reasons or Causes for Improvements

Evaluating Reason or Causes