Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: THEend8_
Change Log
1. Added a FAQ item about progressing without completing lab 3.
2. Removed searching by subject only since it was not implemented in lab 3 - Nov 14
Objectives:
A. Learn how to use Angular to develop the front-end for a web application
B. Create a client (front-end) interface using Angular for interacting with the API that was designed in
lab 3
In this lab, you will implement a front end with Angular, that uses the server API for a time table query
application that was developed in lab 3. Accessing the application using a public URL is mandatory. You may
use Amazon EC2 or your own server for a public URL. You may use a local installation of Node.js for
development purposes.
Workflow:
1. Create a new private Git repository on Github called “se3316-xxx-lab4” (all lowercase) where “xxx”
is your Western email ID (without @uwo.ca part).
2. Clone that repository on your workstation/laptop to create a local working directory.
3. Deploy on the server using Git.
4. Make frequent and meaningful commits and push your project to Github.
Submission Instructions:
Please carefully read the instructions and strictly follow them. Your grade depends on it.
1. Use a proper “.gitignore” file so that only the files that you edit are in your repository.
2. Make frequent commits with an appropriate commit message.
3. Ensure that you understand the principles behind your code.
4. Ensure that Github contains the latest version of your code.
5. Copy the output of command “git log” and paste that onto the submission page (Assignments
section) on Owl.
6. Download your repository as a zip file from Github and submit as an attachment. Please do not zip
the folder on your computer as it contains a large amount of extraneous files.
7. Ensure that your Github repository is shared with TAs.
8. Demonstrate your lab (on a public URL) before the demonstration deadline. You may set up the
public URL after submission on Owl. As long as the changes only involve deployment issues, it is
acceptable.
Penalties will apply for not following the naming convention or any of the submission steps.
Rubric (out of 100):
See the requirements for front-end and back-end for marks allocated for implementation.
1. No input sanitization: -10 for each occurrence.
2. Code management with Git
a. Less than 10 commits: -20
b. No meaningful commits: up to -10
c. No meaningful commit messages: up to -5
d. Not using a proper .gitignore file to ignore images: -5
e. Not using Git pull to deploy code to server: -5
3. Logistics
a. Repository name not in required format: -5
b. No zip file: not graded
c. Code is not attached as a zip file or it contains content that is not in the Git repository or is 1
missing content that is in the repository: -10
Preparation - Learning Angular