Wednesday, 24 September 2014

YEAR 11 Lesson 3 FOR-LOOPS



Learning Objectives
You wil learn to:
Describe Python for loops

CLASS ACTIVITY

We will work at the following section of Using Python

http://usingpython.com/python-for-loop/

Your teacher will go through the introduction with you but your job is to carefully read the examples which have been provided before completing the challenge.

TASK 1 and HOMEWORK

Complete the Dr Love challenge.


Mục tiêu học tập
Wil bạn học cách:
Mô tả Python cho vòng
CLASS HOẠT ĐỘNG
Chúng tôi sẽ làm việc tại bộ phận sau đây của việc sử dụng Python
http://usingpython.com/python-cho-loop/
Giáo viên của bạn sẽ đi qua việc giới thiệu với bạn, nhưng công việc của bạn là để đọc kỹ các ví dụ đã được cung cấp trước khi hoàn tất thử thách.
NHIỆM VỤ 1 và Bài Làm Ở nhà
Hoàn thành thử thách Tiến sĩ tình yêu.

Posted by at

24 comments:

  1. Matthew Gavin 24 September 2014 at 13:26

    https://docs.google.com/document/d/12wJHltmu9sSfp3DKC0Cl99scBE85SpQkJv24SU9ESVU/edit?usp=sharing

    ReplyDelete
  2. Unknown26 September 2014 at 11:13

    Dr Love Project
    https://docs.google.com/document/d/12rfbMuGP1sAv_gdYxgxPMnpobwg6yncaP36cqBEYiZI/edit?usp=sharing

    ReplyDelete
    Replies
    1. Mr T1 October 2014 at 03:54

      Excellent work well done!

      1. Always add psuedocode in addition to flowcahrt
      2. Introduce each sub-section
      3.. Annotate final code with call-outs
      4. Always show cyclical development of code ie show errors and how they were solved.

      Delete
  3. Unknown27 September 2014 at 08:45

    Dr.Love Challenge
    https://docs.google.com/document/d/1JcF1leATF9o1hqPzoNe7A-sczefBSbfGT8GZzA9Uip0/edit?usp=sharing

    ReplyDelete
  4. Unknown27 September 2014 at 09:23

    dr love project:
    https://docs.google.com/document/d/1eFk4QD_xldFo5zzHHqYRF6_9gfsG8TlSmuwFqMznjkc/edit?usp=sharing

    ReplyDelete
    Replies
    1. Mr T7 October 2014 at 02:44

      Re-write checking grammar.

      Add psuedocode to tghe planning section.

      Delete
    2. Unknown8 October 2014 at 04:02

      here is the improved one
      https://docs.google.com/document/d/1eFk4QD_xldFo5zzHHqYRF6_9gfsG8TlSmuwFqMznjkc/edit?usp=sharing

      Delete
  5. Unknown28 September 2014 at 06:07

    https://docs.google.com/document/d/1UCsvzHVgH1b8eOuUZq5UtQ1npAOGhC8k9NIKayjZiAU/edit?usp=sharing

    ReplyDelete
  6. Novac28 September 2014 at 07:47

    Lachlan Bone:
    https://docs.google.com/a/gillotts.org.uk/document/d/1m_Jd8rwbQfU98seNoNPapMa4mCYFN5FixqEnElBkvjA/edit?usp=sharing

    ReplyDelete
  7. Unknown28 September 2014 at 11:17

    https://docs.google.com/document/d/1eI6And16PDQiiroz_Qvmaf_axCAl45-O6m3clNqIWbc/edit?usp=sharing

    ReplyDelete
  8. Unknown28 September 2014 at 13:51

    https://docs.google.com/document/d/1tVWYqrfRN-Fz7ZxosCGyyTiwRHHl6_zkN2wOKZyXEgY/edit

    ReplyDelete
    Replies
    1. Unknown30 September 2014 at 02:01

      https://docs.google.com/document/d/1tVWYqrfRN-Fz7ZxosCGyyTiwRHHl6_zkN2wOKZyXEgY/edit?usp=sharing

      Delete
    2. Mr T1 October 2014 at 04:07

      Scott a much better attempt.

      1. Think through the flowchart and psuedocode more clearly.
      2. Annotate your final code.
      3. Show cyclical development.
      4. Show testing results.

      Delete
  9. Unknown29 September 2014 at 09:09

    https://docs.google.com/document/d/1Pz3KnG6gPle5ilX9MoNpdCjgl5UK_VW5kXljorHBnlM/edit?usp=sharing

    ReplyDelete
    Replies
    1. Mr T1 October 2014 at 03:47

      Excellent attempt but you need to proof read your work thoroughly.

      Delete
  10. Unknown29 September 2014 at 09:37

    https://docs.google.com/document/d/1jsO2r5FqkEG29fdz_JQQo-XZRxAbqP1J96xUrKRAmuE/edit

    ReplyDelete
    Replies
    1. Mr T7 October 2014 at 02:38

      Repeat with the following improvements:

      1. Expand the planning to include detail. This should show both an algorithm/psuedocode and a flowchart.

      2. Include a How column in your testing plan

      3. Before the testing results show your code annotated explaining what each section of code does.

      4. Testing results must have a commentary.

      5. Add an evaluation which talks about the improvements that you plan to make.

      Delete
  11. Unknown29 September 2014 at 13:04

    https://docs.google.com/document/d/1LDK-fCnG8QBmMRA9wcVaeV5EWc99ua0Jalia3hgL8u8/edit?usp=sharing

    ReplyDelete
    Replies
    1. Mr T1 October 2014 at 04:17

      1. Proof read
      2. Numbers 1-9 should be in words
      3. You must layout your plans as a flowchart and psuedocode
      4. Show testing results
      5. Show annotated code
      6. Show cyclical development of code

      Delete
  12. Unknown30 September 2014 at 01:53

    https://docs.google.com/document/d/1aPI6ozrJeZiRXvLRBrwPbEPMRLiJ2Oz9D3C_ugfmlII/edit?usp=sharing

    ReplyDelete
  13. Unknown30 September 2014 at 01:55

    https://docs.google.com/document/d/1DBaDKlnFyp1wih6LftZCdS7CHY_WJFYx4hAEMv1zpao/edit?usp=sharing

    ReplyDelete
    Replies
    1. Mr T7 October 2014 at 02:22

      Re-write this after getting somebody else to proofread.

      Delete
  14. Mr T7 October 2014 at 02:20

    Sam - this is easily best work you have ever done on this course awesome! Hiowever, remember:

    1. Add psuedocode as well as an flowchart
    2, Ensure that you are more careful with the layout of the report

    ENSURE THAT THE CODE IS ANNOTATED!

    ReplyDelete
  15. Unknown8 October 2014 at 06:37

    This comment has been removed by the author.

    ReplyDelete

Subscribe to: Post Comments (Atom)