NoSQL and Alternative Data Stores

Active learning works for handling user input because students learn best when they see immediate consequences of their code. Typing wrong data into a program makes errors real, not theoretical, so debugging becomes a concrete skill rather than abstract advice. Students remember validation and type conversion when they have to fix a crashing program in real time.

• JC 2
• Computing
• 4 activities
• 25 min–45 min

Learning Objectives

1. Identify common methods for capturing user input, such as text fields and menu selections.
2. Demonstrate how to process different types of user input, including strings and numerical data.
3. Analyze the need for input validation to prevent program errors.
4. Create a simple program that prompts for user input and responds based on that input.
5. Compare and contrast different input methods in terms of user experience and data type.

Ready-to-Use Activities

Jigsaw

⏱ 30 min·Pairs

Pair Programming: Greeting App

Pairs write a program that prompts for a user's name and age, then outputs a personalized message. Add input validation to ensure age is a number. Test with classmates, swapping roles as user and programmer.

Prepare & details

What are the limitations of relational databases?

Facilitation Tip: During the Pair Programming Greeting App, have one student act as the driver typing live code while the navigator checks for missing type conversions or empty strings.

Setup: Flexible seating for regrouping

Materials: Expert group reading packets, Note-taking template, Summary graphic organizer

• Understand
• Analyze
• Evaluate
• Relationship Skills
• Self-Management

Jigsaw

⏱ 45 min·Small Groups

Small Groups: Menu Selector

Groups build a menu-driven program for restaurant orders, using loops to handle choices until 'exit'. Include input sanitization for numbers. Demo to class and note improvements.

Prepare & details

How does a document-oriented database store data?

Facilitation Tip: For the Menu Selector, provide a starter file with placeholder options and ask groups to test each branch with invalid inputs like ‘quit’ or ‘exit’ to see which cases crash.

Setup: Flexible seating for regrouping

Materials: Expert group reading packets, Note-taking template, Summary graphic organizer

• Understand
• Analyze
• Evaluate
• Relationship Skills
• Self-Management

Jigsaw

⏱ 25 min·Whole Class

Whole Class: Input Debug Relay

Project buggy input code on screen. Class suggests fixes in turns, coding live. Vote on best solutions and run tests with volunteer inputs.

Prepare & details

When is it more appropriate to use NoSQL over SQL?

Facilitation Tip: In the Input Debug Relay, give each pair a buggy snippet and a set of test inputs; they must run the code, note the failure, and propose a fix in under two minutes.

Setup: Flexible seating for regrouping

Materials: Expert group reading packets, Note-taking template, Summary graphic organizer

• Understand
• Analyze
• Evaluate
• Relationship Skills
• Self-Management

Jigsaw

⏱ 35 min·Individual

Individual: Quiz Validator

Students extend a quiz program to accept answers via input, score them, and reprompt on errors. Share final code via shared drive for peer review.

Prepare & details

What are the limitations of relational databases?

Facilitation Tip: For the Quiz Validator, give students a rubric that checks for empty answers, non-numeric quiz scores, and negative numbers, so they learn validation by grading each other’s outputs.

Setup: Flexible seating for regrouping

Materials: Expert group reading packets, Note-taking template, Summary graphic organizer

• Understand
• Analyze
• Evaluate
• Relationship Skills
• Self-Management

Teaching This Topic

Start by modeling how input() returns strings and why int(input()) can crash if the user types ‘ten’. Avoid the trap of assuming students understand type conversion without concrete examples. Research shows that students retain debugging skills better when errors come from their own code rather than pre-written demos. Emphasize small, tested changes: fix one input case, run, repeat, instead of rewriting everything at once.

What to Expect

Successful learning looks like students writing programs that capture input, validate it, and respond appropriately without crashing. They should explain why input() returns a string, how to convert it safely, and how to loop until correct data arrives. By the end, they can handle both expected mistakes and unexpected empty entries with confidence.

Watch Out for These Misconceptions

Common Misconception

During Pair Programming: Greeting App, students may think programs accept numbers directly without conversion.

What to Teach Instead

While pairs type the greeting, have the navigator deliberately type a number like 5 instead of a name. When the program crashes, pause to rewrite the input line as name = str(input('Enter your name: ')), then show how int(input()) would fail if they tried to use the name as a number.

Common Misconception

During Menu Selector, students may overlook empty menu choices.

What to Teach Instead

Ask each group to run their menu with an empty string as input. When the program crashes, they must add a condition like if choice == '': choice = menu[0] and rerun to confirm it now handles empty inputs without failing.

Common Misconception

During Input Debug Relay, students may believe user input is safe by default.

What to Teach Instead

Give pairs a snippet that prints the user’s name directly. Have them type a name containing a SQL quote like O'Reilly. When the output breaks formatting or shows an error, they must sanitize the input by stripping quotes before printing, turning the demo into a teachable moment about injection risks.

Assessment Ideas

Exit Ticket

After Pair Programming: Greeting App, give students a code snippet that prints ‘Hello ‘ + input() + ‘!’. Ask them to write the output if the user enters 10 and explain why the output differs from entering ten.

Quick Check

During Menu Selector, ask students to list two potential problems with a program that takes a user’s age without validation, then share one way to validate the input using a loop and range check.

Discussion Prompt

After Quiz Validator, facilitate a discussion using the prompt: ‘What are three ways a user might answer a quiz question, and what challenges does each method present for the program’s input handler?’

Extensions & Scaffolding

• Challenge: Add a password field that rejects common weak passwords like ‘123456’ and loops until a secure one arrives.
• Scaffolding: Provide a template with a while loop already written and ask students to fill in only the validation condition and error message.
• Deeper exploration: Ask students to research SQL injection and modify their input handlers to strip semicolons and quotes before processing names or text fields.

Key Vocabulary

Input Prompt	A message displayed to the user, asking them to provide specific information. It guides the user on what data to enter.
Input Validation	The process of checking user-provided data to ensure it meets specific criteria before it is processed. This prevents errors and unexpected program behavior.
Data Type Conversion	Changing data from one type to another, for example, converting a string entered by a user into an integer for calculations.
String	A sequence of characters, typically representing text. User input is often initially received as a string.
Integer	A whole number, without decimals. Often required for numerical operations after user input is converted.