BrainDump - Flash Cards Simplified
By John Huynh
Problem: There are a myriad of games and learning aids for developing students, but are there tools for older students? It is ironic that, as the breadth and difficulty of learning increases, there is a reduction in learning aids. That is not to say that there arenít good learning aids. The problem is that the robust nature of the available programs renders them confusing to the uninitiated. Learning how to use these study aids would subtract from the already limited time available for studying.
Solution: My solution is to create an application that emulates flash cards. Flash cards is a powerful method of studying because it not only triggers thinking through questions, but the creation of the cards itself requires the students to study in the tradition sense. Also, flash cards provide a quick way of recording and retrieving previous information.
Description: Brain Dump is a simple and intuitive study tool for students studying advanced topics. I will approach this goal by promoting study through the transfer of time from prepping the study material to actually studying. You may argue that the creation of the study materials is a key part in studying. I agree that the procuring of information for the study materials is a key part of studying; however, students should not be spending hours converting that information into useful study tools.
Target: I would like the project to apply to students of all ages in all fields. However, my main targets will be high school and college students. This decision was made because I believe students in high school and college are more tech-savvy and will be more likely to make use of our application.
April 7-14 Decide on underlying data structure to represent Decks and Cards. Implement rough iteration of BrainDump UI based on the web version of BrainDump.
April 14-21 Finish data structure conceptualization. Begin implement searching, sorting, creation, and editing of cards and deck functionality. Reiterate UI development.
April 21-28 Continue functionality development and begin developing final UI design.
April 28-May 5 Wrap up UI and functionality. Draft up usability test criteria, find subjects, and receive critique/suggestions. Implement feasible suggestions. Show app to class.