Reference no: EM133781820 , Length: word count:4000

Web Application Development Application Project

Assignment Brief

As part of the formal assessment for the programme you are required to submit a Web Application Development assignment. Please refer to your Student Handbook for full details of the programme assessment scheme and general information on preparing and submitting assignments.

Learning Outcome 1: Discuss and evaluate web application server technologies and deployment strategies.

Learning Outcome 2: Critically assess the concepts of client and server, and how a 3-tier architecture supports the development of client-server-based applications.

Learning Outcome 3: Build a web application that combines client-side and server-side technologies to assemble a non-trivial web application.

Discipline Expertise: Knowledge and understanding of chosen field. Possess a range of skills to operate within this sector, have a keen awareness of current developments in working practice being well positioned to respond to change.

Guidance

Your assignment should include: a title page containing your student number, the module name, the submission deadline and the exact word count of your submitted document; the appendices if relevant; and a reference list in AU Harvard system(s). You should address all the elements of the assignment task listed below. Please note that tutors will use the assessment criteria set out below in assessing your work.

Assignment Tasks
For this assignment you will be submitting both a software artefact and a report.

Task 1 - Application Development

Develop a functioning prototype web application in HTML, CSS, PHP, JavaScript, and SQL for the following scenario:

Create a web interface with a simple content management system, from scratch, for an interactive short training or educational course.

You are free to choose the subject of the course. It can be anything from skateboarding to systems architecture, pottery to interplanetary exploration, and so on. You should include a programme summary, individual lessons and some form of testing or assessment.

The course must be at least 6 lessons long and have an admin interface to allow editing, adding, and removal of content.

Your interface may be a multi-page or single-page application, but it must be driven by content from a database. You do not have to attempt to implement user accounts or any authentication but may if you wish. (Also be sure not to include any actual user's personal data in the demo content.)

You may also include further functionality at your discretion (Your lessons can be as simple as an iLearn lesson, or interactive like SQL Bolt, It is not recommended that you attempt to build something as complex as a course on tryhackme.com or similar, as that would be going far beyond the learning expectations of this module).

Your application MUST demonstrate multiple user interactions that invoke each of the following database operations at least once:

Select
Insert
Update
Delete

You MUST build the application from scratch using the languages specified.

You MUST NOT use any HTML, CSS, PHP or JavaScript frameworks, libraries, or templating solutions to create your application (i.e. No Bootstrap, React, Tailwind, Laravel, Wix, etc.).

You MUST NOT deep-link images, video, audio or any other assets from 3rd party websites. Any media content included MUST be hosted under the COM6011 directory or its subdirectories.

You MUST NOT violate the licensing agreements of any content included in your application. Any assets copied or downloaded from 3rd parties and included in the application must be free to use and the licensing agreement included as an appendix.

Your application should not be a simple copy of any readily available online tutorial. Where you do use any such content it should be properly referenced in both the source code of your app, via a comment, and in the references section of your report. If large portions of your submission are found to be comprised of code which is available as part of an online tutorial it will be disregarded as non-original and may be considered an act of academic misconduct.

Evidence for the grading of this task will be supplemented by the code provided as appendices to your report from task 2.

Task 2 - Report
Your report should be composed of the following sections: Cover page:

A standard Arden assignment cover page Table of contents
A table of contents for your report, including page numbers

Introduction
The primary web address (URL) of your web application and any interfaces not immediately accessible via links from the primary address (e.g. a secondary interface for administrators)
An approximately 300 word description of your application and its functionality. You may include screenshots of the application.
Application structure
A 400 word explanation of the structure of the application in the context of an n-tier/n-layer architecture. Provide lists/diagrams that explain the file and directory structure and how the various component parts interact with each other.
Remember that this is specific to your application structure, not about n- tier architecture in general, DO NOT include generic descriptions or definitions of terminology, you may assume that the assessor already understands the concepts.

Critical review and recommendations
500 words critically appraising your work in terms of its architecture, code structure, functionality, usability, accessibility and making recommendations for future improvements.

References
A full list of sources utilised and cited in the creation of your application, including other's source code, in the AU Harvard style.

Appendices
A full copy of all source code including:
SQL statements
HTML
CSS
PHP
JavaScript
Feel free to break this into multiple lettered appendices.

Any 3rd party content license agreements