Chapter 7.11 - ASSESSMENT: Non-AP Create 2

Time Estimate: 12 hours (some combination of in-class and out of class time) minimum

Follow these directions if you are taking a Non-AP CSP course. If you are taking CSP as an AP course, please go to the previous lesson for the AP Create directions.

7.11.1. Introduction and Goals

Work with a partner to design a socially useful interactive app, that demonstrates algorithms such as selection and repetition and data and procedural abstractions. As you develop your project keep track of significant errors and bugs that you encountered and how you solved or debugged them in a journal.

Please review non-AP instructions and rubric below:

7.11.2. Learning Activities

Iterative Design Thinking Process

Use an Iterative Design Thinking Process to develop your app:

Iterations

  • Iteration 1: Paper Prototype (~2 hours)

  • Iteration 2: Minimal App (~3 hours)

  • Iteration 3: Intermediate App (~3 hours)

  • Iteration 4: Enhanced App (~3 hours)

  • Iteration 5 and on: Additional Features

Design Thinking

For the Non-AP version of the Create Task, we recommend that you work with a partner using pair or buddy programming to create a socially-useful app. With your partner, follow the iterative development process in Create Task with Design Thinkingarrow-up-right. Here is what you need to turn in at each iteration.

Iteration 1: Paper Prototype

Before you start creating the app in App Inventor, you will brainstorm ideas on paper with a partner and present an elevator pitch to your class. Turn in the following:

  • Description of Problem [Empathize, Define, and Ideate]: Working in pairs, think about problems in your community and how an app might help to solve those problems or to help people in your community. Who is the target audience or users who will be using the app? What problem does the app address? How does the app address the problem?

  • Paper Prototypes [Prototype]: Create paper prototypesarrow-up-right of three different brainstorm ideas. Describe what each UI element will do.

  • Elevator Pitch: Present a short (2-3 minute) elevator pitch of your project idea to the class. The pitch could follow this template: [name of app] is a [kind of thing] for [the people who would use it or problem it would solve] that, unlike [similar apps] is able to [the major distinguishing feature of your app].

  • Feedback [Test]: Other students should provide feedback answering the following questions. Is the app presented socially useful why or why not? What is a strength of the proposed app? What suggestions do you have to improve the app?

Iteration 2: Minimal App

Working in pairs, create a minimal working app. Turn in the following:

  • Minimal app [Prototype and Test]: Build an initial prototype with minimal functions for your app with your partner.

  • Journal [Define and Ideate]: As you work, keep a journal of your development process and problems encountered and how you solved them. Complete a journal entry using this journal entry templatearrow-up-right.

Iteration 3: Intermediate

  • Intermediate App [Prototype and Test]: Iteratively add and test new features for your app, meeting the grading guidelines. For the Create 2 project, your project should use a List or a database like TinyDB for handling data, as well as procedures that you have defined, preferably with parameters, and if or loop blocks.

  • Documentation of Code: For this assignment, a well documented app means having well named components, variables, and procedures. Where appropriate, your code should contain comments that explains the various parts of your code.

  • Data: For this assignment, your app should make appropriate use of variables and lists. If data persistence is necessary for your app, you should make use of a database such as TinyDB or CloudDB.

  • Algorithms: For this assignment, your app should make appropriate use of sequence, selection, and repetition control structures including math and/or logic (in if or loop blocks) operations.

  • Abstraction: For this assignment, your app should make appropriate use of one or more programmer defined procedures to handle certain subtasks. Also, your procedures should use parameters where appropriate.

  • Journal [Define and Ideate]: Keep a journal of your development process and problems encountered and how you solved them. Complete a journal entry using this journal entry templatearrow-up-right.

Iteration 4: Advanced App

  • Advanced App [Prototype, Test]: Iteratively add and test new features for your app, meeting the grading guidelines.

  • Journal [Define and Ideate]: Keep a journal of your development process and problems encountered and how you solved them. Complete a journal entry using this journal entry templatearrow-up-right

Iteration 5: Additional Features

  • Additional Features [Prototype, Test]: Iteratively add and test new features for your app.

  • Journal [Define and Ideate]: Keep a journal of your development process and problems encountered and how you solved them. Complete a journal entry using this journal entry templatearrow-up-right.

7.11.3. Submission

When you are finished with your app, your teacher may ask you to turn in some or all of the following:

7.11.4. Grading

Your teacher may use the following Non-AP Create Performance Task Rubric arrow-up-rightor something similar to grade your Create project.

7.11.5. Resources

Last updated