Now you have to take what you have learned and make simple web application from start to finish on your own as outlined in the task document.
From now on ALL your work has to be documented in your Web Application Development Log
Make sure you read all the instructions carefully and know exactly what you intend to make before starting this assessment.
This is a test to see if you can work independently and put all your knowledge into practice to make a functional web application using Python, HTML, CSS and SQL.
The project is split up into the following phases, all of which MUST be documented with the development log added below:
Design phase- design your database with an ERD and create wireframes of your website
Three sprints of development, each one consisting of:
Planning/revising sprint goals and tasks
Developing testing and commiting to github each task as you go
Deliberate end of sprint trialling with others in the class and your teacher
A Final review and reflection on the whole project at the final delivery date.
All dates for each sprint will be decided by your teacher.
You must deliver and test your application at the end of each sprint.
You will hand in your completed development log at the end for all the assessments. This will include your entire github repository and commit history.
Your teacher MUST be able to download and run your code from that repository.
This is the OFFICIAL Flask quickstart.
Everything you need to know to get you started using Flask is here.
This should be your first stop for help on anything to do with Flask.
And Don't forget it's most important sub-page:
Try it out in your own project
Distribute the Development Log any way you want (eg. Google Classroom).
All marking schedules are at the end of the development log document for your convenience.
Check in at the end of EACH phase. ie. After the Design Phase, make each kid show you the design and get it checked off before moving on. If they haven't designed it, they're not going to be able to make it. TIP: Keep it simple, they can always build complexity in but they'll get task paralysis if it's too complex.
Each sprint end should have PUBLIC testing of the application with others in the class (and you).
And at the end of sprint #2, you could pre-mark their applications as they study for the CS External on CSFieldGuide.
Software requirements:
Any Web Browser (eg Chrome, Edge, Firefox or Safari)
Visual Studio Code: https://code.visualstudio.com/
Python: https://www.python.org/downloads/
Git: https://git-scm.com/downloads
SQlite Studio (optional but worth having): https://sqlitestudio.pl/