During the lecture, Mr Japit Sionggo went through with us on what should we be expected from the second half of the FYP:-
1. Presentation - What we learnt, Research, Live Demo, PowerPoint for the project
2. Implementation: Software product quality. Needs to meet all preliminary requirements. Whatever we say we must deliver in order to meet the requirements. If not possible, replace with another method.
3. Test Logs: what's the error, who is going to fix it, how are you going to fix it. cannot be all passed. don't print out test logs. can only be in your CD. only test plan on technical manual
4. Configuration Management: Versioning of All documents and prototypes. Version Control.
5. Change control
6. Risks assessment
7. By week 19 everything work properly if possible.
After that, we had our first prototype demo with Mr Tan.
Below are the suggestions / feedbacks he gave to us: -
1. What happens if the USB is pulled out?
2. User friendly in terms of RSA. How to send the keys?
-> Lesser things to do for users - checkbox might be good?
3. Can the attacker clone the USB? Can we make the attack to be difficult ? How to prevent cloning?
4. Function for recovery? Options for users to recover their encrypted data if they lost the USB.
5. If folder is big? -> We will implement multithreading
6. 3 times incorrect password and the file is wiped is a danger to the user.
Perhaps forensic tools for users before wiping?
7. SMS or email if possible .
8. One time pad: research more on how scalability. Especially for big files -> Advise users not to use this for big files.
10. How reliable our program is?
11. Perhaps let users to choose what factor they want to use: SMS/email/password
After the demo, we gathered to go through our proposal again to see our progress.
Priorities Function to implement: Insert USB Drive to get its USB Key (or can be done semi-independently of the USB drive if the USB key is known by the user and manually keyed in as well)
To do List for individual member:
EnQi - To update/reorganize all documentation, create the base for test logs report
Jose and WeiJie - To continue to progress on the coding.
1. Presentation - What we learnt, Research, Live Demo, PowerPoint for the project
2. Implementation: Software product quality. Needs to meet all preliminary requirements. Whatever we say we must deliver in order to meet the requirements. If not possible, replace with another method.
3. Test Logs: what's the error, who is going to fix it, how are you going to fix it. cannot be all passed. don't print out test logs. can only be in your CD. only test plan on technical manual
4. Configuration Management: Versioning of All documents and prototypes. Version Control.
5. Change control
6. Risks assessment
7. By week 19 everything work properly if possible.
After that, we had our first prototype demo with Mr Tan.
Below are the suggestions / feedbacks he gave to us: -
1. What happens if the USB is pulled out?
2. User friendly in terms of RSA. How to send the keys?
-> Lesser things to do for users - checkbox might be good?
3. Can the attacker clone the USB? Can we make the attack to be difficult ? How to prevent cloning?
4. Function for recovery? Options for users to recover their encrypted data if they lost the USB.
5. If folder is big? -> We will implement multithreading
6. 3 times incorrect password and the file is wiped is a danger to the user.
Perhaps forensic tools for users before wiping?
7. SMS or email if possible .
8. One time pad: research more on how scalability. Especially for big files -> Advise users not to use this for big files.
10. How reliable our program is?
11. Perhaps let users to choose what factor they want to use: SMS/email/password
After the demo, we gathered to go through our proposal again to see our progress.
Priorities Function to implement: Insert USB Drive to get its USB Key (or can be done semi-independently of the USB drive if the USB key is known by the user and manually keyed in as well)
To do List for individual member:
EnQi - To update/reorganize all documentation, create the base for test logs report
Jose and WeiJie - To continue to progress on the coding.
Comments
Post a Comment