JSAL prepared a design change document and provided a copy to the client (the capstone professors). The document provided the changes desired by the client to include a write-in feature within the firmware of eVote. The document also pointed out that additional funds may be necessary due to the added feature, but due to time constraints, the feature will be completed by clocking in additional hours and this will be reflected in future progress reports.
The keyboard was successfully integrated with the microprocessor and was able to navigate between two different screens. The security of the database data has also progressed to finding a 128 bit encryption method that uses a password that will be used to decrypt the database parameters when being called upon in the administrator program.
The screen for the write-in has been designed and implemented, but the navigational code has yet to be implemented and will be worked on after the progress report presentation.
The screens of eVote have been implemented except for the ballots for the governor and resident commisioner which will be worked on after the progress report due to the fact that these screens have images on them that require additional work to calculate their pixel positions.
lunes, 27 de octubre de 2008
jueves, 23 de octubre de 2008
LCD Screens, Navigation keypad and Database security
The team is working with the tasks for the second phase of the project. Laura is working with the write-in screen. In order to design the screen, a table is being used to establish the coordinates in which a letter will appear. Javier is working with the screens for voting. These screens include language selection, integral or mixed voting selection as well as write in option selection. Angel is working with the encryption and decryption of the information stored in the database. Sylvia is working with the keypad for navigation. Yesterday Sylvia and Javier tested the keypad to look at the output voltage from each of the pressed keys. The keypad regulates the input voltage to have an output voltage of 3V. Therefore, there is no need to have a voltage regulator. Sylvia, Javier and Laura are working with dependent modules from one another; therefore before start working the design was discussed.
Below a picture of the keypad testing
lunes, 20 de octubre de 2008
Lcd screens and navigation
During the day the team discussed feedback from friday's happy hour sessions. The day's work revolved around:
1. "Write-In" in-depth design : Write in screen has been designed and code is currently being made for displaying it on the LCD
2. Language selection in-depth design: Design began for the way in which the program handles language selection on the code level
3. Overview of Keyboard navigation
4. LCD matrix table (Excel): This table is being used to design the different screens (see image below)
miércoles, 15 de octubre de 2008
sábado, 11 de octubre de 2008
LCD Updates
The LCD is now working!
After various days, it was observed that the initialization code was affected by the reset process. After the reset process was removed the LCD started working, but still had problems due to the voltage supply. The cables were not making the correct contact with the circuit and the power supply. After resolving the issue with the cables, the LCD worked.
Below some pictures of the LCD working.
After various days, it was observed that the initialization code was affected by the reset process. After the reset process was removed the LCD started working, but still had problems due to the voltage supply. The cables were not making the correct contact with the circuit and the power supply. After resolving the issue with the cables, the LCD worked.
Below some pictures of the LCD working.
jueves, 9 de octubre de 2008
Risk: Possible Change in Computers
We have been informed that the computers in room S-123 might be changed on friday or early next week.
We have made backups of our code and database in order to prevent any loss of information.
Also, we have informed the Help@ECE staff that the new computers will require the installation of: MySQL Server & Tools, MyODBC Driver 3.51, TortoiseSVN, Visual Studio 2008, and the BarCode font.
All the development plans have been made assuming Windows XP will be the OS used, so if these new computers have Windows Vista we might have to run our applications in a virtual machine with XP in order to avoid any issues.
We have made backups of our code and database in order to prevent any loss of information.
Also, we have informed the Help@ECE staff that the new computers will require the installation of: MySQL Server & Tools, MyODBC Driver 3.51, TortoiseSVN, Visual Studio 2008, and the BarCode font.
All the development plans have been made assuming Windows XP will be the OS used, so if these new computers have Windows Vista we might have to run our applications in a virtual machine with XP in order to avoid any issues.
Database Design Changes
Through out this phase there have been unplanned changes to the evote database. The Position table was removed since it wasn't vital and the information could be stored in a different table. This table might make coding efficient in the Raven version but for the Sparrow version it is not necessary.
Today, a column called "Barcode" was added to the candidate table . This field will store the text to be converted to the printed receipt.
A history table was added to associate a an official to a voter. This way, should there be any problems with a voter or an official, related people can be identified.
The kiosk table was given an additional identification number to make the voting experience better for voters and officials. The kID field is unique for every kiosk, so in a real life scenario every kiosk in the area using the system will have a different number. This number would only be useful when looking at the kiosks from an outside perspective. In the voting units, the officials and voters need local identification number that will make it easy for them to know where a voter has to go.
Today, a column called "Barcode" was added to the candidate table . This field will store the text to be converted to the printed receipt.
A history table was added to associate a an official to a voter. This way, should there be any problems with a voter or an official, related people can be identified.
The kiosk table was given an additional identification number to make the voting experience better for voters and officials. The kID field is unique for every kiosk, so in a real life scenario every kiosk in the area using the system will have a different number. This number would only be useful when looking at the kiosks from an outside perspective. In the voting units, the officials and voters need local identification number that will make it easy for them to know where a voter has to go.
Suscribirse a:
Entradas (Atom)