| Week 1 |
Project setup |
2h |
| Week 1 |
Twitter Developer Account(mails) |
2h |
| Week 2 |
First Connection with Twitter |
1h |
| Week 2 |
Preparation of the questions |
1h |
| Week 3 |
Git documentation is prepared |
30m |
| Week 3 |
Functional requirements are prepared |
2h |
| Week 3 |
2 mockups are prepared |
30m |
| Week 3 |
SPA is set up |
30m |
| Week 4 |
Django is set up |
3h |
| Week 4 |
Non-functional requirements and a scenario are prepared |
1h |
| Week 5 |
Getting first tweet |
3h |
| Week 5 |
Login/register page |
5h |
| Week 6 |
Dashboard(frontend) |
5h |
| Week 6 |
Postgresql implementation and saving user into DB |
8h |
| Week 7 |
Logging all search result into DB |
6h |
| Week 7 |
NLTK analysis |
10h |
| Week 8 |
Sentiment analysis implementation |
5h |
| Week 8 |
Tagme and entity linking |
10h |
| Week 9 |
WordCloud and BarChart |
6h |
| Week 9 |
Tweet list with sentiment |
9h |
| Week 10 |
History page implementation |
6h |
| Week 10 |
Deployment with Heroku |
7h |
| Week 11 |
Deployment with Heroku |
6h |
| Week 11 |
Design fixes |
7h |
| Week 12 |
Bug fixing |
6h |
| Week 12 |
Project Plan |
7h |