The group decided to weigh verification strength at 90 because having a strong electronic lock is the basis of our system, and having it function correctly is core to our project. Next, we decided to put the cost and ease of installation at 70 because we want to incentivize our customers to buy and install our product without worrying extensively about the price of their home security system. We also want our system to be convenient and compact, without compromising the security of the system. To account for this, we put convenience and compactness at 60. Lastly, we want the product to look decent so that the customer's front door doesn't have its appearance ruined. For this, we put the aesthetics of our system at 30.
For the KT Decision Matrix, after calculating the Decision factors for all, we decided to use an app for unlocking in case the main system doesn't work and NFC for the main system. For the main system, NFC had a decision factor of 1310 which is higher than RFID, which had a decision factor of 1190. For the backup system, the app idea was used because the mechanical lock and keypad didn't qualify by having the most important need accounted for: verification strength. The backup designs lack the strength that our system requires in order to function safely and securely.
For the KT Evaluation Matrix, we want to compare a standard RFID reader against an NFC reader as the main scanner for our system. RFID and NFC readers both have similar odds of being damaged during transportation, so we added it under both with equal probability. The main problem we wanted to address with the tag readers was the odds of their data being accessed and manipulated from outside of the system, which we displayed in the "Getting hacked" rows. NFC readers are much more secure than RFID readers, which is reflected by having the odds of getting hacked be higher for RFID readers. In the end, our RFID reader had a threat level of 0.75, while NFC had a threat level of 0.45. As the only choice for the backup system, unlocking via the app had a score of 1.15. This is why we considered it as a backup system for one of the tag readers, as it can be useful in times when the tag reader is not.