Questions? Feel free to talk with your friends in our class about this assignment, within the constraints of Academic Honesty listed below. This is not a standard cs50 assignment, so you won’t find any information about it in the cs50 forums.
Implement a website that gives the user a short survey with a series of questions. When the questions are answered, the website tells the person something about themself. For instance, “What Disney Princess are you?”
This course’s philosophy on academic honesty is best stated as “be reasonable.” The course recognizes that interactions with classmates and others can facilitate mastery of the course’s material. However, there remains a line between enlisting the help of another and submitting the work of another. This policy characterizes both sides of that line.
The essence of all work that you submit to this course must be your own. Collaboration on problems is not permitted (unless explicitly stated otherwise) except to the extent that you may ask classmates and others for help so long as that help does not reduce to another doing your work for you. Generally speaking, when asking for help, you may show your code or writing to others, but you may not view theirs, so long as you and they respect this policy’s other constraints. Collaboration on quizzes and tests is not permitted at all. Collaboration on the final project is permitted to the extent prescribed by its specification.
Below are rules of thumb that (inexhaustibly) characterize acts that the course considers reasonable and not reasonable. If in doubt as to whether some act is reasonable, do not commit it until you solicit and receive approval in writing from your instructor. If a violation of this policy is suspected and confirmed, your instructor reserves the right to impose local sanctions on top of any disciplinary outcome that may include an unsatisfactory or failing grade for work submitted or for the course itself.
- Communicating with classmates about problems in English (or some other spoken language).
- Discussing the course’s material with others in order to understand it better.
- Helping a classmate identify a bug in his or her code, such as by viewing, compiling, or running his or her code, even on your own computer.
- Incorporating snippets of code that you find online or elsewhere into your own code, provided that those snippets are not themselves solutions to assigned problems and that you cite the snippets’ origins.
- Reviewing past years’ quizzes, tests, and solutions thereto.
- Sending or showing code that you’ve written to someone, possibly a classmate, so that he or she might help you identify and fix a bug.
- Sharing snippets of your own solutions to problems online so that others might help you identify and fix a bug or other issue.
- Turning to the web or elsewhere for instruction beyond the course’s own, for references, and for solutions to technical difficulties, but not for outright solutions to problems or your own final project.
- Whiteboarding solutions to problems with others using diagrams or pseudocode but not actual code.
- Working with (and even paying) a tutor to help you with the course, provided the tutor does not do your work for you.
- Accessing a solution to some problem prior to (re-)submitting your own.
- Asking a classmate to see his or her solution to a problem before (re-)submitting your own.
- Decompiling, deobfuscating, or disassembling the staff’s solutions to problems.
- Failing to cite (as with comments) the origins of code, writing, or techniques that you discover outside of the course’s own lessons and integrate into your own work, even while respecting this policy’s other constraints.
- Giving or showing to a classmate a solution to a problem when it is he or she, and not you, who is struggling to solve it.
- Looking at another individual’s work during a quiz or test.
- Paying or offering to pay an individual for work that you may submit as (part of) your own.
- Providing or making available solutions to problems to individuals who might take this course in the future.
- Searching for, soliciting, or viewing quiz questions or answers prior to taking the quiz.
- Searching for or soliciting outright solutions to problems online or elsewhere.
- Splitting a problem’s workload with another individual and combining your work (unless explicitly authorized by the problem itself).
- Submitting (after possibly modifying) the work of another individual beyond allowed snippets.
- Submitting the same or similar work to this course that you have submitted or will submit to another.
- Using resources during a quiz beyond those explicitly allowed in the quiz’s instructions.
- Viewing another’s solution to a problem and basing your own solution on it.
Your work on this problem set will be evaluated along four axes primarily.
To what extent does your code implement the features required by our specification?
To what extent is your code consistent with our specifications and free of bugs?
To what extent is your code written well (i.e., clearly, efficiently, elegantly, and/or logically)?
To what extent is your code readable (i.e., commented and indented with variables aptly named)?
There is a Flask tutorial here you might find useful.
As always, we’ll begin the setup process for this problem by logging into cs50.io and executing:
Create a new folder called personality. Within this folder create application.py and a folder called templates where you will store your HTML files. Create an index.html file as well. You can have one or more result html files, and you can name them whatever you like.
Design and implement a program, personality, that, gives the user a survey and returns some information about the person.
- Implement your program in a file called application.py in a directory called personality.
- Your program generate a website with a survey using index.html.
- Your survey should ask the user’s name, and use it on the results page.
- Your survey should have at least 4 questions. At least 3 should be multiple choice, and one should use a list of checkboxes where more than one checkbox can be selected.
- You may assume that the user will answer every question
- Your program should redirect to a new webpage with the result to the survey.
- The result MUST be determined based on the answers. The same result can NOT happen every time. You can NOT use a random number generator or other random results
- Your design should look good. Use images! Cite any images you find online.
$ cd personality
$ flask run
Then open the link and take the quiz!
Take the survey several times to make sure it works as intended.
Have your friends take your personality test. You might learn something about them!
Turning it In
When you’re done, submit your work by navigating to the personality folder and using submit50.