Why choose this project topic?
The topic makes sharing a simulated bus among competing requesters without indefinite starvation a testable computer-engineering problem with visible interfaces and failure cases. Measuring waiting cycles, starvation cases and logic cost 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 waiting cycles, starvation cases and logic cost when sharing a simulated bus among competing requesters without indefinite starvation?
Choose an available development board or simulator, agree the supported interface and workload, and narrow sharing a simulated bus among competing requesters without indefinite starvation with your supervisor.
Proposed project objectives
- 01Specify the interfaces, operating assumptions and expected behaviour for sharing a simulated bus among competing requesters without indefinite starvation.
- 02Implement fixed and rotating priority arbiters, replay bounded request patterns and formally or exhaustively check stated liveness conditions.
- 03Measure waiting cycles, starvation cases and logic cost and document failures, resource limits and reproducibility.
A suggested research approach
Implement fixed and rotating priority arbiters, replay bounded request patterns and formally or exhaustively check stated liveness conditions. Keep all tests on owned, simulated or approved low-voltage equipment. Record hardware and tool versions, compare output with an independent reference, and evaluate waiting cycles, starvation cases and logic cost using normal, boundary and interrupted-operation cases.
What you will need
- HDL simulator
- Synthetic request traces
- Arbitration property specification
Keep your project scope clear
Bounded verification does not prove correctness for every unmodelled interface behaviour. 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.