Deadline and submission
Deadline: 2017-12-06 07:30
Submit: Submit your assignment by doing a release on GitHub named “v1.0″. In case of changes after a released version please use incremental version numbers, i.e. “v1.1″, “v1.22 etc.
After performing this assignment you will fulfill the three goals described in the course syllabus:
- Describe a web browsers different internal components and their interactions including browser security mechanisms
- Store and with asynchronous communication, transfer data with for the task appropriate data format
This examination is worth 3 credits (3hp).
The quiz application
This examination will focus on asynchronous communication agains an external RESTful web services through asynchronous calls. The backend (server-side code) of this assignment will be given and your job is to write the client-side code.
- Do the excercises at A and B level. (at least)
- Read the chapters in the book for this part.
- Make sure Node and NPM is installed on your computer.
- Use Git to clone down your examination-repo. It should be something like
git clone https://github.com/[COURSECODE]/[USERNAME]-examination-2.git
Pull down the files from our examination repo (be sure to do this in the right directory)
git pull https://github.com/[COURSECODE]/examination-2.git
This repo should include a boilerplate for the assignment with the same stuff that you have been using in the exercises. Se README.md-file for instructions on how to install.
- Start writing your code in this repo and do your commits as usually.
Any attempt to plagiarism or other way of cheating will be reported to the university discipline board
About the assignment
You should create an client application in which the user can answer, by the server given, quiz-questions. The user must do this in a certain time. If the user gives the correct answer, the application will take the user to the next question. If the user give the wrong answer or didn´t in time the quiz is over.
You are responsible for the presentation of the questions (retrived from the server), the handling of the client application logic and the user interface. The user shouldn't have any problem to understand the UI. Keep it simple, keep it beautiful.
At the start of the game the user should be able to write a nickname she/he wants in the quiz game. The game must have a timer that gives the user a maximum of 20 seconds to answer each question. If the user doesn´t answer during the time or the user answer wrong it is game over and the user should be able to start the game over.
If the user answer all of the questions correctly the game should record the users total time and present this in a high-score list with the five fastest times. The high-score will be saved in the browsers Web Storage.
The questions and answers
The questions will be public to the client application through a RESTful Web API. The first question (starting point of the application) is at the URL:
You can find the source code of the server at the GitHub repo:
, that is if you are interested in running the server by you self [optional, but good training].
The response of the API will tell you what kind of question you should show to the user and where to send the answers. In other word, you have to analyze the response from the server to know how to display the questions and how to send new requests for answering the questions. Hyperlink is provided by the server response in a RESTful way. The server responses will also give clues about what HTTP-methods to use and how to send the answers back.
The server will put out two different types of questions. Simple text questions and questions with alternatives where the user should answer with the right key "alt1", "alt2" etc. You can watch the server responses and decide what is what. Questions with alternatives should be presented with html radio buttons. The user should not need to write anything on thoose questions.
The last question answered will not return any new link to a new question and that means that the quiz is over.
Create a release tag at github to indicate that you are ready for examination. Book a time for oral exam.
- It should be easy for the user to understand the application and how to use it.
- The application must be able to handle the different types of questions/answers that the server provide/handle.
- For every question there should be a timer counting down from 20 seconds to 0 seconds.
- The client application should also keep track of the total time the user takes to answer all the questions.
- The user should be able to choose a nickname at the start of the game that will be used in the high-score list.
- Application should use Web Storage to store a high-score list which presents the five fastest total times (on that specific client) at the end of the game. At least nickname and total time should be present.
- Your applications shall be able to handle any number of questions as well as different numbers of alternatives to questions.
Before you start writing code think about:
- How to present the question the user should answer?
- How to get the answer from the user and how to send it back to the server?
- Be sure to tell the server that the POST-request is a "application/json"-request by setting the "Content-type" of the HTTP-header (check up the XMLHttpRequest object and setRequestHeader or fetch api)
- Decide if you want to use XMLHttpRequest or the Fetch API
Best of luck!
The examination will be done as an oral hearing where you get a couple of theoretical questions from this part (Lecture 2 to 4) and also show your practical assignment. You can´t book a time for oral hearing before you are ready with the assignment and have done a release on GitHub.
The hearing will take place over Slack (distance learning students) or in the staff offices on the third floor of Kalmar Nyckel (Campus students)
- Slack. Meetup: The slack-channel for the course.