Assessment

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:

1. Design phase- design your database with an ERD and create wireframes of your website

2. Three sprints of development, each one consisting of:

   1. Planning/revising sprint goals and tasks

   2. Developing testing and commiting to github each task as you go

   3. Deliberate end of sprint trialling with others in the class and your teacher

3. 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.

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

• A Website for your favourite sports team and the players to help promote the team to others

•  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

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

• A Character Database (eg Marvel Heroes or LoL) to help players find more information and statistics on their favourite characters

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

• 
  

Write down your final decision in your Development Log

Once you have researched and decided you need to create the initial design for your application and recorde them in your Development Log. 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.

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 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.

Each sprint testing, review, planning and refinements must be recorded in your Development Log.

Part 4- A Final Review

Once all of your development is complete, you’ll need to complete a final review in your Development Log. This allows you to discuss how planning, testing and trialling 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.