Day 14: Collaborative Program Development - Day 2

Learning Objectives

• CRD-2.E: Develop a program using a development process.
• CRD-2.F: Design a program and its user interface.
• CRD-2.G: Describe the purpose of a code segment or program by writing documentation.
• CRD-2.J: Identify and correct errors in algorithms and programs, including error discovery through testing.

Essential Questions

• How do we translate program requirements into effective designs?
• How can we create and test prototypes to improve our program?

Materials Needed

• Design document templates
• Wireframing tools/templates
• Prototyping materials/tools
• Testing plan templates
• Project documentation templates

Vocabulary

• Prototype
• Wireframe
• Storyboard
• Algorithm design
• Test plan
• Design documentation

Procedure (50 minutes)

Opening (5 minutes)

1. Review and Connection (5 minutes)
   • Teams briefly share their project ideas and requirements
   • Address any common questions or challenges
   • Set goals for today's design and prototyping work

Main Activities (35 minutes)

2. Program Design (15 minutes)

   • Teams create detailed designs for their programs:
     • User interface wireframes/mockups
     • User interaction storyboards
     • Program structure/components
     • Algorithms for key functionality
   • Teams document design decisions and rationale
   • Teams connect design elements to specific requirements

3. Initial Implementation/Prototyping (15 minutes)

   • Teams create initial prototypes based on their designs
   • Prototypes can be:
     • Paper prototypes
     • Digital wireframes
     • Pseudocode for key algorithms
     • Simple interactive mockups
   • Teams document implementation decisions

4. Testing and Debugging Planning (5 minutes)

   • Teams develop testing strategies:
     • Test cases for key functionality
     • User testing protocols
     • Error identification and correction procedures
   • Teams anticipate potential errors and plan debugging approaches

Closing (10 minutes)

5. Design Documentation (7 minutes)

   • Teams compile and organize their design documentation including:
     • Program purpose and requirements summary
     • UI designs and wireframes
     • Algorithm descriptions
     • Testing plans
     • Implementation notes
   • Teams ensure documentation is clear and complete

6. Preview Final Day (3 minutes)

   • Explain that next class will focus on project presentations and unit review
   • Outline presentation expectations
   • Remind teams to finalize all documentation

Assessment

• Design Documentation: Quality and completeness of program design
• Prototype: Functionality and alignment with requirements
• Testing Plan: Thoroughness of test cases and debugging strategies

Differentiation

For Advanced Teams

• Encourage more sophisticated prototypes
• Suggest consideration of edge cases in testing
• Challenge them to document alternative design approaches considered

For Struggling Teams

• Provide more structured design templates
• Offer simplified prototyping approaches
• Give additional guidance on testing strategies

Homework/Extension

• Refine program design based on feedback
• Enhance prototypes if time allows
• Prepare for project presentation
• Complete any unfinished documentation

Teacher Notes

• Monitor team progress and provide targeted assistance
• Ensure all team members are contributing to the design process
• Emphasize the connection between requirements and design elements
• Remind students that documentation quality will be part of assessment
• Encourage teams to focus on quality over quantity in their designs