You must decide on a Web Application purpose and end user. This should be kept fairly simple to begin with but have the potential to grow. Examples might include:

• A Website for your favourite sports team and the players to help promote the team to others that users can rate players

•  A simple food shop ordering system for customers to make orders (like Dominoes©!)

• A Video Game rating and review database to help game buyers make informed decisions where users can add their own reviews.

• A PC Parts database to help buyers create and cost a new PC Build

• A Quiz program to help students study for a subject at school and make their own questions to help their learning

At Level 3 it is expected that your application does more than just "Read" data. It Should also provide the user with some way to Update, Edit or Delete the Data. This is commonly achieved through "Admin" interfaces within the site or sites that have user generated information.

Part 2- Design

Once you have researched and decided you need to create the initial design for your application. This includes:

1. Entity Relationship Diagram for the Data. This will include the tables, fields and data types as well as any Primary Keys or Foreign Keys. Keep the initial design simple! It can and will get more complex as the project continues. However, at Level 3 you are expected to end up with at least one many-to-many relationship within your design.

2. Wireframes of the Front End Design. Draw sketches of what the page(s) will look like. Where will the header be? What size and position will the images be? This gives you an idea of what is needed when you start development. 

3. Consider the Relevant Implications. Before beginning, you must show you understand the relevant implications for making this application. Examples of relevant implications include: social, cultural, legal, ethical, intellectual property, privacy, accessibility, usability, functionality, aesthetics, sustainability and future proofing, end-user considerations, and health and safety. Explain a few that you think are important and and say why you might be concerned about them before developing your app.

Part 3- Planning and Development

You will now complete 3 sprints of approximately 4 weeks each. Your teacher will decide on the number of sprints, sprint length and delivery dates for testing.

Each sprint will have:

1. Project planning and goal setting at the beginning. The design can be refined and goals adjusted at this stage.

2. Ongoing testing/trialling of tasks as you develop them. Are tasks fully functional before moving on to the next task? Commit your code regularly once each task is complete and functional. A testing table has to be filled out in your development. Note that higher marks require comprehensive testing.

3. Formal testing/trialling WITH OTHERS at the end of each sprint. This includes all data integrity testing (does the query return the right data? Does the python code process and serve it to the html correctly? Does the right data appear in the right place on the page/html? Is it readable, does it follow HCI conventions?)

4. Sprint review, sometimes called retrospectives, to help ensure that the testing informs the next sprint. These reviews will help you to adjust your plan for the next sprint so you make a more refined application.

How will users interact with your Web Application? 

Options include: 

• Deploying it live to pythonanywhere.com 

• Share your GitHub repository, including a readme.md with instructions on how to set up and use the site and a requirements.txt so others can easily try it out.

Once all of your development and testing is complete, you’ll need to complete a final review in your Development Log. This allows you to discuss how planning, testing and trialing led to the development of a high-quality digital technologies outcome and how your application addressed the relevant implications that you explained at the beginning. This is required for higher marks in some of the assessments.