Sprint 9 - CSP Objectives (Final)

10 min read

Final Project - Poway Chamber of Commerce Community Partnership

This Final Project is a community service initiative in partnership with the Poway Chamber of Commerce and Poway CTE. Your team will build a prototype website for independent non-profits and small businesses, demonstrating modern web features they may not have in their current sites.

Project Context:

Work with real businesses and non-profits in the Poway community
Build “surprise prototypes” to pitch enhanced digital solutions
Apply Computer Science Principles to authentic, real-world needs
View participating organizations: OCS Capstone Projects (CSP Filter)

Core Features Options (Choose 3 or More):

Your team should select 3 or more features that will give your specific business partner the best “wow factor” on the surprise prototype. Choose strategically based on partner needs, not just the easiest options:

User Authentication: Login/signup systems with secure session management
Database Integration: SQLite backend for data persistence
AI Integration: Chatbots, recommendations, or content generation
Social Messaging: Communication features (contact forms, messaging, notifications)
Content Management: Blogging, news posts, or dynamic content updates
Machine Learning (ML): Data analysis, prediction models, or insights using pandas
Gamification: Interactive game elements using OCS Game Engine
Modern UI/UX: Responsive design, accessibility, professional styling

You will demonstrate your skills in:

Software Engineering Practices: Planning changes, using checklists, tracking progress, writing commented code, building help documentation
Software Development Lifecycle Practices: Source control, forking, branching, building, testing, pull requests, merging/integrating
Retrospective Engineering Practices: Presentations, live reviews, demos, code reviews, revising plans
Data Types: Numbers, strings, booleans, arrays, JSON objects, SQLite tables
Operators: String operations, mathematical operations, boolean expressions
Control Structures: Iteration (loops), selection (conditionals), sequencing, try/except, .then/.catch
Input/Output: HTML5 input, validation, DOM manipulation, form handling, API requests
Procedures and Functions: Writing reusable procedures/functions with parameters and return values
Lists and Dictionaries: Managing data with lists/arrays and maps/dictionaries to handle complexity
Deployment Practices: DNS, Docker, docker-compose, nginx

This project is your opportunity to make a real impact in your community while showcasing your growth as a developer.

AP CSP Create Performance Task & PPR Status

PPR Completion Expectation

Your PPR should be substantially complete before Sprint 7. By this point, you should have:

✅ Identified your qualifying procedure (with parameter, sequencing, selection, iteration)
✅ Identified your qualifying list usage (manages complexity, could be database or map)
✅ Prepared clean screenshots (no comments, 10-point font minimum)
✅ Staged PPR to AP Digital Portfolio (or ready to submit by April 30, 2026)

Week 17 - PPR Data Structure Review

In Week 17 (Sprint 9), we will conduct a comprehensive review of AP CSP concepts related to your PPR and project code:

Review Topics:

Input/Output: Form handling, user input validation, API responses, database queries
Sequencing: Order of operations in your procedures
Selection: If/else statements, conditional logic, decision-making
Iteration: For loops, while loops, forEach, iterating through collections
Data Structures:
- Lists/Arrays: How you create, access, manipulate lists (JavaScript arrays, Python lists, SQL databases extract to Maps)
- Dictionaries/Maps: Key-value pairs (JavaScript objects, Python dicts)
- How these structures manage complexity in your code

This is NOT the PPR itself, but a conceptual review of all the programming fundamentals you’ve applied in your JavaScript and Python code. This prepares you for the AP Exam written response questions.

PPR Critical Information

Critical Deadline: PPR must be submitted as “Final” in your AP Digital Portfolio by April 30, 2026, 11:59 p.m. ET

Required PPR Code Segments

You must submit the following code segments as clear screenshots to the AP Digital Portfolio:

PPR Component	Evidence Required	Technical Requirements
Procedure/Function	Screenshot of a student-developed procedure that implements an algorithm	• Must have at least one explicit parameter • Must include sequencing, selection (if-statements), and iteration (loops) • Must be meaningfully used in your program
Procedure Call	Screenshot showing where your program calls that procedure	• Must show the actual invocation with argument(s) passed • Must be from your working program code
List Creation	Screenshot showing a list being created or populated	• Must store multiple values of the same type • Can be array, list, dictionary, or other collection • Must show initialization or data being added
List Use	Screenshot showing how that same list is used to manage complexity	• Must demonstrate list being accessed/manipulated • Must show how list simplifies program logic • Example: iterating through list, accessing elements, updating values

PPR Formatting & Submission Rules

Critical Rules (Failure to follow may result in lost points or unscorable submission):

✅ DO:

Use clear screenshots with at least 10-point font size
Ensure code is readable and properly formatted
Keep screenshots focused on relevant code segments
Submit by April 30, 2026, 11:59 p.m. ET deadline

❌ DO NOT:

Include any code comments in your PPR screenshots
Include your name or any personally identifying information
Use blurry or low-quality screenshots
Include unnecessary code outside the required segments

Technical Standards Checklist

To score full points on the exam questions, ensure your code meets these standards:

Procedure Requirements:

✅ Has at least one explicit parameter (not just empty parentheses)
✅ Contains sequencing (multiple lines of code executed in order)
✅ Contains selection (if/else statements or conditional logic)
✅ Contains iteration (for loop, while loop, or forEach)
✅ Returns a value or produces a meaningful side effect

List Requirements:

✅ Stores multiple values (not just a single variable)
✅ Is accessed using an index or key
✅ Manages complexity (simplifies program compared to not using a list)
✅ Is meaningfully used (not just for display purposes)

Example of Managing Complexity with Lists:

Without List: Would need separate variables (score1, score2, score3…) and repetitive code
With List: Single list structure (scores = []) with loop to process all values efficiently

Timeline of Key Events

Event	Purpose/Details	Date
April 13: Initial Prototype	Working prototype ready for initial engagement	Beginning of Sprint 8
April 13: Data Structure Review	Individual review Input/Output, Sequencing, Selection, Iteration, Lists/Arrays, Dictionaries/Maps, with instructor.	April 8, 2026
April 15: Prototype Demo	Demo Chamber of Commerce prototype to instructor	April 15, 2026
April 15-24: Chamber/CTE Pitch	Present working prototypes to Poway Chamber of Commerce and CTE	April 15-24, 2026 Del Norte HS A101, Periods 3 & 4
Sprint 8-9: Prototype Refinement	Incorporate Chamber/CTE feedback, build 3+ features (Login, Database, AI, Social Messaging, Blogging, ML, Gamify, UI/UX)	Ongoing Sprint 9
April 30: PPR Submission Deadline	PPR submitted as “Final” to AP Digital Portfolio	April 30, 2026, 11:59 p.m. ET
May 12-16: AP CSP Exam	AP Computer Science Principles Exam (reference your PPR during written responses)	May 12-16, 2026
May 18-22: Community Non-Profit Pitch	Pitch surprise innovation ideas to community non-profits (outside classroom)	May 18-22, 2026
May 27: N@tM Showcase	Final pitch to community and parents at Night at the Museum	May 27, 2026 (Wednesday), 6pm
Finals Week: Final Presentations	Monday: Present LinkedIn page, Blog portfolio, and Analytics Final Day: Instructor completes final grading	Finals Week (Week 36)

Project Planning - Chamber of Commerce Community Project

CSP Course Timeline

Sprints 7 (Weeks 25-33): Chamber Project Initial Dev, Data Structures 1 (DS1) & PPR Development

Learn foundational data structures (lists, dictionaries, procedures with algorithms)
Build and finalize PPR-qualifying code
Submit PPR to AP Digital Portfolio (deadline: April 30, 2026)
Begin Chamber of Commerce community project planning
Sprint 8 Milestone: Create initial engagement prototype to share with Chamber of Commerce / CTE partners

Sprint 8-9 (Weeks 34-36): Chamber of Commerce Prototype & Community Presentations

PRIMARY FOCUS: Build surprise prototypes for Poway Chamber of Commerce / CTE partners
April 15-24: Pitch working prototypes to Chamber/CTE at Del Norte HS (A101, periods 3 & 4)
Week 17: PPR Data Structure Review (Input/Output, Sequence, Selection, Iteration, Lists, Maps)
Sprint 9: Implement 3+ features based on partner needs
May 18-22: Pitch innovation ideas to community non-profits (outside classroom)
Finals Week: N@tM showcase presentation

Sprint 9 Project Presentation

Core Objective: Build a surprise prototype website for a Poway Chamber of Commerce / CTE partner (non-profit or small business).

Feature Requirements (choose 3 or more):

Select features strategically to maximize impact for your specific business partner. Choose the combination that will best impress your customer:

User Authentication: Login/signup system with session management
Database Integration: SQLite backend for persistent data storage
AI Integration: Chatbot, content generation, or intelligent recommendations
Social Messaging: Contact forms, notification system, or messaging features
Blogging/CMS: Dynamic content management system for news/updates
Machine Learning (ML): Data analysis, predictions, or insights using pandas
Gamification: Interactive game elements using OCS Game Engine
Modern UI/UX: Responsive design, accessibility features, professional styling

Project Deliverables:

Create Issues describing features, assignments, expected goals, and stretch goals
Build Help/Documentation in your blog to guide future engineers
Develop Individual Blog showcasing:
- Design documents for your Chamber of Commerce prototype
- Technical implementation details (databases, APIs, authentication)
- PR and commit history highlighting individual contributions
- How you applied AP CSP concepts (procedures, lists, algorithms) to real-world needs
  Sprint 9 Development Milestones

PPR Data Structure Review

Comprehensive CSP Concept Review with instructor:
- Input/Output operations, Sequencing in procedures/functions
- Selection (conditionals, if/else logic), Iteration (loops: for, while, forEach)
- Data Structures: Lists/Arrays and Dictionaries/Maps/Objects (JavaScript/Python)
- How these structures manage complexity in your projects

April 15-24 - Chamber/CTE Pitch:

Location: Del Norte HS A101, Periods 3 & 4
Deliverable: Pitch companies you plan to surprise with working prototype and innovation ideas
Required: Demonstrate core features, explain business value, gather feedback

Sprint 9 Development (Weeks 34-36):

Feature Integration: Implement 3+ chosen features (AI, messaging, auth, blogging, ML, gamify, etc.)
Database Implementation: Setup SQLite, implement backup/restore
Testing: Unit tests, functionality validation, edge case testing
UI/UX Polish: Responsive design, accessibility, professional styling

May 18-22 - Community Non-Profit Pitch:

Location: Outside classroom (community partner sites)
Impact Story: Highlight community value and real-world application of CSP concepts
UI/UX Polish: Responsive design, accessibility, professional styling- Demonstration: Show all implemented features, explain technical decisions

Final Presentation: Pitch prototype to community partners at Night at the Museum

Finals Week - N@tM Showcase:

Final Deliverables & Blog

Throughout Sprint 7-9, you will update your kanban boards and team/project blog to support implementation and communication of your Chamber of Commerce community prototype, technical, and AP CSP competency. Your blog will serve as the central point for communication with your instructor and demonstrate your real-world application of computer science principles.

Important Note on PPR:

PPR should already be drafted and prepared to submit to AP Digital Portfolio (deadline: April 30, 2026)
Your blog can reference PPR code but focus primarily on Chamber of Commerce project
Week 17 review will cover all CSP data structure concepts (not PPR submission itself)

AP Exam Preparation: Your PPR will be available to you during the AP Exam. You will answer four written response questions about:

Your procedure’s purpose and functionality
How your procedure implements an algorithm with sequencing, selection, and iteration
How you use a list to manage complexity in your program
The overall purpose and functionality of your program

Team Blog Requirements:

Chamber of Commerce Project Documentation:
- Partner organization background and needs assessment
- Design documents showing system architecture, data flow, and feature plans
- Technical implementation details (authentication, database schema, AI integration, etc.)
- Screenshots/videos demonstrating key features (login, data management, AI, messaging, blogging)
- Explanation of how AP CSP concepts apply to your solution
Code Highlights: Explain key programming decisions and techniques
- Procedures/functions you created with parameters and algorithms
- How you use lists/dictionaries to manage data complexity
- Input/output handling, iteration, and selection logic
Testing Documentation: Show test cases, validation, debugging process
Contribution Evidence: PR and commit history showing individual work
PPR Reference (if needed): Link to your PPR code segments with explanations

N@tM Presentation Focus: Your N@tM presentation should emphasize:

Community Impact: How your prototype helps the partner organization
Technical Innovation: Modern features you implemented (AI, auth, database, messaging)
Real-World Application: How you applied CSP principles to solve authentic problems
Surprise & Pitch: Demonstrate features the partner may not have considered
Team Collaboration: Show how your team worked together to deliver value

Computer Science Principles