AP CS PD 1.3 Week 4.pptx

AP CSP

1. Week 4 AP College Board

2. Big Idea 1 Lesson Objectives: I can develop a program using a development process. I can design a program and its user interface. Success Criteria: Lesson 1 :Be Able to determine and design appropriate method or approach to achieve the purpose. Lesson 2: Be Able to explain how a code segment or program functions. Lesson 3: Be Able to explain how collaboration effects the program development. Lesson 4: Be Able to acknowledge the intellectual properties of others

3. Big Idea 1 A development process can be ordered and intentional , or exploratory in nature. A development process that is incremental is one that breaks the problem into smaller pieces and makes sure each piece works before adding it to the whole. A development process that is iterative requires refinement and revision based on feedback, testing, or reflection throughout the process. This may require revisiting earlier phases of the process. 4

4. Big Idea 1 Investigation  The design of a program incorporates investigations to determine its requirements. Most programs are designed to be u sed by people other than the programmers. To meet the needs of the users, the investigation must identify the program constraints as well as the concerns and interests of people who will use the program. Some ways investigations can be performed are: 5

5. Choosing a Method for Collecting Feedback 6

6. Big Idea 1 Design Phase  The design phase of a program may include: ■​Brainstorming ■​Planning and storyboarding ■​Organizing the program into modules and functional components ■​Creating diagrams that represent the layouts of the user interface ■​Developing a testing strategy for the program  7

7. Collaborative Activity – 1 Map the following scenario to the design process. Planning a garden that meets specific design objectives, then plant and tend the garden. At the end of the growing season, iterate the design to improve it for the next season based on how the garden was or was not successful in meeting the objectives. 8

8. Collaborative Activity – 2 Implement the design process on the following scenario: Analyzing the five most popular social media platforms for teens, then predict and design a new platform based on existing trends and past trajectory of change. 9

9. Lesson Objectives: I can develop a program using a development process. I can design a program and its user interface. Success Criteria: Lesson 1 :Be Able to determine and design appropriate method or approach to achieve the purpose. Lesson 2: Be Able to explain how a code segment or program functions. Lesson 3: Be Able to explain how collaboration effects the program development. Lesson 4: Be Able to acknowledge the intellectual properties of others

10. Big Idea 1 Program documentation Program documentation is a written description of the function of a code segment, event, procedure, or program and how it was developed. Program documentation helps in developing and maintaining correct programs when working individually or in collaborative programming environments. 11

11. Big Idea 1 Programmers should document a program throughout its development. Documentation helps the programmer remember what he or she was thinking, or the collaborative partners were thinking at the time they were programming. Comments are a form of program documentation written into the program that do not affect how the program runs. Comments do not affect the run speed of a program. Python, for example, uses # for comments. 12

12. Big Idea 1 13

13. 14 Essential Knowledge It is important to acknowledge any code segments that were developed collaboratively or by another source.

14. Big Idea 1 15 How is a program deve l oped?

15. Big Idea 1 While documentation is an important place to give credit: Many projects use comments within the programming language to give credit. This is an important part of the development of the program. When developers find a bug (or an error in a program), they need to be able to determine who can/should fix the problem. This may be most useful after a program is completed, and users find additional bugs. 16 Documentation

16. Big Idea 1 Many times, developers use code segments, procedures, algorithms, are written by others. These other individuals are not necessarily a part of the project, but they still deserve to be credited . This is like quoting someone in a research paper or article. Any code segments, procedures, algorithms are considered intellectual property of the author . The program documentation should include the author's name and the source of any code segments being used. This portion of the documentation may resemble a bibliography, or a works cited page in a research paper. 17 Documentation Rules

17. 18 All the following require crediting the original author(s) and/or source in program documentation except? Use of code segment(s) from another program written by someone else in a program you are writing. Use of your own original code segments in a program you are writing. Use of an algorithm written by someone else in a program you are writing. Use of code segments you collaborated on with others in a program you are writing. Exit Slip Big Idea 1

18. Collaborative Activity – 1 Map the following scenario to the documentation process. Documenting the ‘important’ stories from your family (immediate or extended), focusing on older generations first. Help your family tell their story by telling all of their individual stories, then come up with a way to ‘publish’ that story (likely only sharing it with the family itself). 19

19. Lesson Objectives: Lesson 4: I can d escribe the purpose of a code segment or program by writing documentation. Success Criteria: Lesson 4: Be Able to acknowledge the intellectual properties of others

20. 21

21. 22

22. 23 Lesson Objectives: Lesson 4: I can d escribe the purpose of a code segment or program by writing documentation. Success Criteria: Lesson 4: Be Able to acknowledge the intellectual properties of others

23. 24

24. 25

25. 26

26. 27

27. 28