Why choose this project topic?
The topic makes testing application behaviour when a fictional key-storage device rejects requests a testable computer-engineering problem with visible interfaces and failure cases. Measuring incorrect acceptance, error recovery and interface coverage helps a student compare design alternatives and explain how resource constraints affect the proposed implementation.
How do the selected hardware or embedded-software choices affect incorrect acceptance, error recovery and interface coverage when testing application behaviour when a fictional key-storage device rejects requests?
Choose an available development board or simulator, agree the supported interface and workload, and narrow testing application behaviour when a fictional key-storage device rejects requests with your supervisor.
Proposed project objectives
- 01Specify the interfaces, operating assumptions and expected behaviour for testing application behaviour when a fictional key-storage device rejects requests.
- 02Build a mock device API with dummy keys, exercise timeout and permission errors and verify that sensitive operations fail closed.
- 03Measure incorrect acceptance, error recovery and interface coverage and document failures, resource limits and reproducibility.
A suggested research approach
Build a mock device API with dummy keys, exercise timeout and permission errors and verify that sensitive operations fail closed. Keep all tests on owned, simulated or approved low-voltage equipment. Record hardware and tool versions, compare output with an independent reference, and evaluate incorrect acceptance, error recovery and interface coverage using normal, boundary and interrupted-operation cases.
What you will need
- Mock secure-element API
- Dummy key identifiers
- Application test harness
Keep your project scope clear
The emulator does not provide tamper-resistant key storage or certify cryptographic security. Project writing does not supply working firmware or manufactured hardware.
Computer Engineering project chapter outline
Use this outline as a starting point. You can edit the chapter titles to match your department’s format during setup.
- Chapter 1Introduction
- Chapter 2Literature Review
- Chapter 3System Analysis and Design
- Chapter 4System Implementation and Testing
- Chapter 5Summary, Conclusion and Recommendations
Turn this topic into your own final year project.
Your title, department, research question and outline are ready. Add your institution, personalise the details and continue to your project workspace.
Generate the Complete Project Generation uses your word balance. Review the draft and supply your own verified research findings.