Iteration 1 Plan - Hamiz5401/ku-polls GitHub Wiki
Goal
A working web app that displays poll questions, allows a visitor to select a poll question and choose from a list of responses. Application correctly displays the number of "votes" for each choice in the selected poll question. Results persist across restarts of the application.
Features
- Display a page showing a list of current poll questions.
- Each poll question has a publication date (starting date) and the question is not shown before the starting date.
- Each poll question has a link to a page displaying the question and a list of choices. A visitor can select a choice and press a button to submit a vote. * His vote is recorded.
- After voting, a visitor can see the total votes for each choice on a poll question.
- Poll questions and choices are saved to a database.
- Poll questions are created using the admin interface (no custom interface yet).
Tasks
All tasks should be recorded on Project Board for Iteration 1.
- Create a task board on Github for this iteration, and enter tasks.
- Create a polls application with Question and Choice model classes (Tutorial part 2).
- Design the UI and navigation.
- Implement the view for home page and start of question detail page (Tutorial part 3)
- Implement a web form for question detail page, and back-end to handle the form submission and record a vote (Tutorial part 4)
- Write Unit Tests (Tutorial part 5)
- Add CSS styling (Tutorial part 6)
- Add at least 2 interesting questions to the application, and delete the stupid "What's up?" question.
Evaluation Critiria
- Application runs, displays list of current poll questions.
- User can select a poll question, see a list of choices, select a choice, and submit his choice. His selection is added to the "vote" count for the selected choice.
- After user submits his choice, application shows vote totals for each answer to a question.
- Application passes all unit tests.
- All navigation links work correctly.
- Application has some CSS styling and text is easy to read.
- Application has at least 2 interesting questions.
- All code committed to Github on iteration1 branch and merged into master.
Retrospective Summary
What goes according to the plan?
- The web function correctly according to the Django's tutorial
What goes wrong?
- Some task take longer than expected.
- Miss spelling occured alot which lead to some error.
What I learned?
- Some basic functionality of Django(Might need some time to review).
- Some task that look easy might take more time than expected because of bugs or other reasons.