Introduction to Your Assessment

This is a creative space for you to develop and deepen your knowledge, skills, and practices through experimentation and prototyping within areas you are passionate about and/or have an aptitude for.   

Develop collaboratively, empathise with the creative processes of teammates, and connect theories and concepts with practice through practice-based inquiry. 

This assignment gives you the opportunity to perform web application development in your own direction.  

By the end of this assessment, you will familiarise yourself with using a framework to develop an application and working in a group. 

Using the following; 

1. Project Proposal and  
2. Production Plan  

Develop a prototype for the proposed web-based application. 

Requirements for the First Prototype (Work-in Progress); 

• demonstrates dynamic functionality 
• completion can either be;  
  • fully functional for half of the pages or  
  • partially functional for all of the pages  
• does not require database connectivity (hardcoding some data is acceptable). 
• runs without errors using the terminal or command prompt. 
• needs to be showcased with a video demonstration, highlighting the implemented functionality and aesthetics (include a link in your repository's readme.md file), a team member can narrate and walkthrough the audience to what is happening in the application and how the code work. 

Your project; 

• must be version controlled,  
• database connectivity would be required in the final product,
• the source files should be well-commented, appropriately formatted, stored and accessible in the github.com repository 
• may include royalty-free assets. 

Your prototype will be assessed on the following criteria:  

• Persistence - How closely your prototype aligns with the project proposal and production plan. 
• Code Practices - Code contributions are sufficient, well-formatted, DRY (Do not Repeat Yourself), follow a consistent standard, well-commented or self-documenting. A readme.md file is also required in the git, explaining the steps of how to run the application using the terminal or command prompt. 
• Technology - Frameworks and libraries mentioned in the proposal are used in the development of the application.   
• Individual Production Progress Report - The production progress report should have a maximum of 3 pages with a font size of 11 and a line spacing of 1.0. The contents of the report must include but are not limited to:   
  1. Weekly scrum meeting/team meeting minutes – Information regarding the involvement in the project of each student in the team. Stages of development, issues and roadblocks faced and how those were dealt with.   
  2. Reflection on learning in terms of technology – Any changes to the initial plan due to technical challenges should also be referred to and justified in the report.   

1. A zip file containing your team project files   
2. A .txt file containing the link to your git repository along with your team members' names, student IDs, and course code.   
3. A pdf of your Individual Production Progress Report