You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
25 lines
1.6 KiB
25 lines
1.6 KiB
7 months ago
|
Task Overview:
|
||
|
|
||
|
Objective: Develop a basic prototype of an online voting system where a member casts a vote and the system checks against a list of eligible members to ensure they are allowed to vote and restrict them to a single vote.
|
||
|
|
||
|
Components of the Task:
|
||
|
|
||
|
System Design:
|
||
|
Design the architecture of the voting system including data models and system components.
|
||
|
Document the system design briefly, outlining key components such as the front-end interface, back-end services, and the database schema.
|
||
|
Coding:
|
||
|
Develop a simple front-end interface where members can cast their vote. This can be a basic web form capturing the vote.
|
||
|
Implement back-end logic in a chosen programming language to process the vote, including checking against a list of members to verify eligibility.
|
||
|
Write code to ensure that each member can only vote once.
|
||
|
Database Management:
|
||
|
Create a simple database schema to store member information and votes.
|
||
|
Write a database query to check if a member is eligible to vote and to record the vote.
|
||
|
Security Implementation:
|
||
|
Discuss or implement basic security measures to protect the voting process and member data.
|
||
|
Version Control:
|
||
|
Use a version control system like Git to manage the code for the task. Provide access to the repository so that the interviewers can review the commit history.
|
||
|
Testing and Quality Assurance:
|
||
|
Develop basic unit tests or integration tests to ensure the functionality of the voting process.
|
||
|
Documentation:
|
||
|
Provide brief documentation on how to set up and run the system, including any necessary steps to install dependencies or configure the environment.
|