Skip to content

Latest commit

 

History

History
55 lines (49 loc) · 3.55 KB

README.md

File metadata and controls

55 lines (49 loc) · 3.55 KB
Raw

Project Description

Frontend Technologies allowed - Angular for dynamism and SPA and any technologies/framework allowed for frontend design. Backend Technologies allowed - NodeJs, ExpressJS, MongoDB, SocketIO, WebSockets.

Features of the platform -

  1. User management system
  2. User Test management system 3) User Test taking system
  3. Test listing admin
  4. User analytics in admin panel.

  1. User Management System -

    • User should be able to sign up using email, gmail.
    • User should be able to login to the system through email and password combination or using Gmail
    • Forgot password functionality should be there to reset password.

  2. User Testing management system -

    • Once the user logs into the system, he should see a dashboard containing the statistics of all tests he has taken. The statistics may include the number of tests taken, average score and percentage growth etc. You are free to think and use more metrics, graphs etc.
    • Dashboard should also contain the lists of tests the user has taken and every item in this list should be clickable.On clicking this item, a Test Result view should open which contains the details of test result.
    • There should be a “take a test” option in menu from which user can go to test taking page.
    • On test taking page, user should see a list of tests he can appear for along with a button to start that test.

  3. User test taking system -

    • Once user starts the test, he should first see an instructions screen containing. It may also contain the rules of the test.
    • Once the user reads the instructions and accepts the rules (single accept button), The test timer will start and the screen should display the test questions and options associated with it.
    • User should be able to choose only one option as answer for every question.
    • The test should have a time limit. The test window must automatically close once the timeout occurs irrespective of how many questions have been answered. The system should submit the answers automatically.
    • If the user completes the test before the time ends, he should see a submit window which will submit his all answers. In case of timeouts, this window must appear automatically.
    • The system must keep a track of how much time a user is taking for answering each question. Your models should be designed accordingly. Hint - questions and their options should be stored in one model which is not user dependent, whereas the answers should be stored with both testId and user details because the answers are related to users.
    • You may use socketio, ws or similar modules for live tracking the user progress.
    • On submission of test, show the result to student. Tell him the number of correct answers and percentage of marks obtained.

  4. Test listing Admin

    • Admin should be able to create tests in the system
    • Each test should have a set of questions, each question containing at least 4 options and overall time limit of the test.
    • Admin should be able to create, edit, delete and view any tests, question or option.
    • While creating options for any question, admin should be able to set a correct answer. This answer (flag) will actually help in automating the test evaluation process.

  5. User analytics in admin

    • Admin should be able to view details of users registered in the system .
    • Admin should be able to view overall performance of the user in all his tests.