ASSESSMENT TASK

Flask-Based (Python) web application

You will be given an incomplete Flask-Based (Python) web application. Your task is to finish off the incomplete application. This will consist of completing the following sub-tasks:

1)    Interface personalisation. [15%]

2)    Lab-assisted tasks. [35%]

3)    Self-worked task.  [35%]

4)    Reflective Journal. [15%]

Interface Personalisation

Restyle the website interface (web page) to a different design than the one given. Use PARC and Colour Harmony Schemes to help you achieve this.

Lab-assisted Tasks

There will be a number of development tasks e.g. the calculator and journal sections that will come with lab guides to help you build them. Where possible Selenium IDE tests will be provided to assist in building these sections. The sections will be marked on completed functionality i.e. how many tests are passed.

Self-worked Task

You should complete a Thought of The Day section that randomly displays a thought from a list (stored in a JSON file on the server) whenever a user visits the page. It should include an admin section that:

1)    Displays the complete list of thoughts.

2)    Displays the details of a single thought selected from the list.

3)    Allows new thoughts to be added to a list and stored on the server.

4)    Allows thoughts to be deleted from the list.

5)    Is styled according to your interface personalisation.

6)    Uses JSON for communication between the client-side and the API on the server.

This section will be also marked on completed functionality.

Reflective Journal (Appendix A + JSON File)

You will demonstrate a professional approach by keeping a reflective journal of your progress. Each weekly entry should include the Status of Tasks that have been worked on that week. It should show those completed and the status of other tasks you were progressing during that week e.g.

“Calculator addition and subtraction finished and working, multiplication started.”

In the Reflection/Action column you can write comments about the tasks as you do them. This is a short reflective review, of 150 words maximum, per week. For example, consider questions like

1.    What you have been working on and progress made.

2.    What went well, and how you dealt with issues arising.

3.    What you learnt by completing the tasks

4.    What you still do not understand

5.    What you would do better next time.

6.    What LSEPI (Legal, Social, Ethical and Political Issues) or security issues might impact your work.

7.    Sources of knowledge utilized.

It maybe that sometimes you say very little, e.g. “all tests passed successfully” and for other tasks you want to write more e.g.: “struggled with the file writing as I could not figure out how to append to an open file and kept overwriting the original data, I now know I need to alter the File writing object and set append to true”. You should also consider any actions you need to complete to help you improve your programming, e.g. “email tutor to ask for help”, “find more tasks to help me understand while loops” etc.

***Note: To start with you can use the attached Reflective Journal form (Appendix A) to record journal entries but once the journal section of the assignment tasks has been completed you should transfer all entries to the journal.json file contained within the application.

Submission Format

Your submission should be:

1.    A single zip file containing your completed app uploaded to the large file submission link.

2.    A copy of the journal.json file, containing your personal journal entries, uploaded to the Turnitin submission link.

These should be uploaded to Brightspace by the Submission Due Date and time (see above).

Marking Criteria

A guide to marking criteria is supplied in Appendix B.

Feedback

A mark sheet based on the table in Appendix B will be used. This will be completed by the marker and submitted for you to review on Brightspace. 

INTENDED Learning Outcomes (ILOs)

This assignment tests your ability to:

1.    Design and implement solutions to simple problems using appropriate software languages.

2.    Demonstrate an understanding of the importance of developing software in an ethical, secure, and professional manner.

3.    Demonstrate the appropriate use of data structures in simple programs.

4.    Test and debug a given program by using a suitable testing strategy