Individualized Long‐Term Project

Introduction

This is an individual project (not a team-based project). You will be finding a large dataset of information online and analyzing the data looking for insights within the data. By the end of the project, you will be expected to visualize the data in a non-standard way (see the D3 website for ideas). To complete this task you will want to use one of the following programming languages: JavaScript or Python.

By the deadline, this project must include the following:

• The use of a large dataset, and
• Tools to help you analyze and work with that dataset, and
• A non-standard visualization of the data that you are analyzing, and
• Demonstrate all the concepts in the success criteria (bottom of the page).

Step 1 (Program Planning)

Brainstorm and create a plan for:

• What dataset you have found and will work with, and
• Why you chose this dataset, and
• What insights you are hoping to propagate from the data, and
• How you are going to demonstrate the learning goals (see bottom of this page) to your teacher, and
• How you plan to complete your research and compilation of data, and
• How you will use your time throughout the course to make complete this project during class time, and
• A timeline of when you envision demonstrating the learning goals to the teacher (of which, at least half must be demonstrated at least two weeks before midterm) - see your teacher for exact deadlines.

Discuss the plan with your teacher before the end of the third week of class. See your teacher for an exact date.

Resources

Sample tools that could help you complete this include:

• ObservableHQ (JavaScript), or
• D3.js (JavaScript), or
• Numpy (Python), or
• etc.

Step 2 (Program Creation)

Create the planned/discussed product. See your teacher for your due date(s).

Present/Demonstrate Your Work

Throughout the semester, based on the teacher-assigned created, you and your teacher will have meetings to go through your work. During these meetings, you will be having an interactive discussion with your teacher about your work in a one-on-one manner where you demonstrate your knowledge of the success criteria. Be prepared to answer follow-up questions.

Citations and Research Notes

Complete the following regarding citations:

• Cite any sources used using IEEE format.
• Cite all images used. You can provide a list of hyperlinks to the images used or embed them into your work.
• Keep a copy of your sources used, as they might be requested at some point.

Overarching Learning Goal(s) and Success Criteria

The Overarching Learning Goal(s) for this include 📙 Data Structures and Algorithms.

A second follow-up evaluation may be performed based on the initial evaluation, at the teacher's discretion.

Success Criteria	Look Fors	Feedback Opportunity
📙 I can use integer division in computer programs.	To be co-created.	Feedback can be requested up until two days before the deadline.
📙 I can use resultant remainders in computer programs.	To be co-created.	Feedback can be requested up until two days before the deadline.
📙 I can complete type conversions.	To be co-created.	Feedback can be requested up until two days before the deadline.
📙 I can decompose a problem into modules, classes, or abstract data types using an object-oriented design methodology (using classes, methods, etc. using UML, etc.).	To be co-created.	Feedback can be requested up until two days before the deadline.
📙 I can apply the principle of reusability in program design (use of inheritance).	To be co-created.	Feedback can be requested up until two days before the deadline.
📙 I can create a modular program that is divided among multiple files.	To be co-created.	Feedback can be requested up until two days before the deadline.
📙 I can read from, and write to, an external file (i.e. database, API, text file, binary file, etc.).	To be co-created.	Feedback can be requested up until two days before the deadline.
📙 I can use one-dimensional arrays of compound data types (i.e. objects)	To be co-created.	Feedback can be requested up until two days before the deadline.
📙 I can compare the efficiency of sorting algorithms, using run times and computational complexity analysis.	To be co-created.	Feedback can be requested up until two days before the deadline.
📙 I can compare the efficiency of linear and binary searches, using run times and computational complexity analysis.	To be co-created.	Feedback can be requested up until two days before the deadline.
📙 I can design a simple and efficient recursive algorithm.	To be co-created.	Feedback can be requested up until two days before the deadline.
📙 I can create fully documented program code according to industry standards.	To be co-created.	Feedback can be requested up until two days before the deadline.
📙 I can work independently, using support documentation, to resolve syntax issues during software development.	To be co-created.	Feedback can be requested up until two days before the deadline.