Report for MIPS code

I need a full report for my MIPS code baseed on the requerments asked.

This final report will be the version with final details and code.

This submission MUST include ALL of your final project code!

This submission should include:

1. The signed declaration that the work you’re submitting is your own original work
2. A high level description of your program
3. A list of the core functions and operations of your project
4. A high level description of the code, written in C or pseudo code or flow chart format
5. Summary of the tests you’ve performed on your code and examples of the test results
6. The results should include screen shots, or links to audio/video recordings on Youtube or shared Google files, as appropriate
7. Summary of all tasks that were completed by the time the final report was due
8. List of tasks that could not be completed by the due date
9. Conclusion, stating what you’d do differently if you had it to do over again
10. Estimated total time to complete the project, in hours.
11. At the end of the draft report, you must include ALL the code with comments (formatted in the style of the MIPS code samples) you’ve written to date, pasted into the draft report file, plus:

Any supplementary files that would be needed to reproduce your test results. This should include anything you used to create and test your project and may include supporting .h files, supporting C code, spreadsheets, Matlab scripts, data files, etc.

Submit the current version of your code in .C and .asm file(s).

Your C and MIPS code should compile/assemble and execute without errors, even if it isn’t fully functional.

You are required to submit at least 3 files:

1. The report in .doc .docx or .pdf file format including the file extensions in the name. The .c and .asm code MUST be pasted into the end of the report document to receive credit!
2. The current version of your C code in .c and any optional .h files
3. The current version of your MIPS assembly source code as one or more .asm file(s).

Any other files required to reproduce your results, such as spreadsheets, Matlab scripts, data files or anything else used to create and test your project code.

Your MIPS code must include at least the following items to receive a passing grade:

• Conditional branches, equivalent to C if-else
• Nested Loops equivalent to C while(), for() or do-while()
• Use of a 2-D array
• Use of the stack to store the $ra (return address) register

Additional methods and more extensive operations, the use of advanced features such as sound, floating point, bitmap graphics, and storing local variables on the stack or recursive functions will receive additional points.

The report must document the structure of your final project, written in C and assembly with comments and any prototype functions that define arguments and return values. List limitations due to I/O and other features that were not complete.

This report and code should include the high level definition and pseudocode plus your final project MIPS assembly code FORMATTED in the style used in the MIPS code examples. By the time you complete the MIPS code, it must embody the basic logic and algorithms described above.

Once you have submitted the final report here, please schedule your 10-minute one-on-one meeting to discuss your project with the instructor.

Please prepare for the meeting by making sure you:

• Have the development environment(s) you need to demo your program operation
• Have your final report open and ready to show
• Have your SDSU or other government issued Photo ID with you

Have a working webcam or phone camera that works with zoom

In the meeting you will be asked to describe and demonstrate your project operating, and to discuss your code.

9/19/24, 11:06 AM
Project – FINAL Report
Project – FINAL Report
Due Apr 24, 2023 by 11:59pm
Points 500
Submitting a text entry box, a website url, a media recording, or a file upload
This final report will be the version with final details and code.
This submission MUST include ALL of your final project code!
This submission should include:
1. The signed declaration that the work you’re submitting is your own original work
2. A high level description of your program
3. A list of the core functions and operations of your project
4. A high level description of the code, written in C or pseudo code or flow chart format
5. Summary of the tests you’ve performed on your code and examples of the test results
6. The results should include screen shots, or links to audio/video recordings on Youtube or shared
Google files, as appropriate
7. Summary of all tasks that were completed by the time the final report was due
8. List of tasks that could not be completed by the due date
9. Conclusion, stating what you’d do differently if you had it to do over again
10. Estimated total time to complete the project, in hours.
11. At the end of the draft report, you must include ALL the code with comments (formatted in the style of
the MIPS code samples) you’ve written to date, pasted into the draft report file, plus:
12. Any supplementary files that would be needed to reproduce your test results. This should include
anything you used to create and test your project and may include supporting .h files, supporting C
code, spreadsheets, Matlab scripts, data files, etc.
Submit the current version of your code in .C and .asm file(s).
Your C and MIPS code should compile/assemble and execute without errors, even if it isn’t fully
functional.
You are required to submit at least 3 files:
1. The report in .doc .docx or .pdf file format including the file extensions in the name. The .c and .asm
code MUST be pasted into the end of the report document to receive credit!
2. The current version of your C code in .c and any optional .h files
3. The current version of your MIPS assembly source code as one or more .asm file(s).
Any other files required to reproduce your results, such as spreadsheets, Matlab scripts, data files or
anything else used to create and test your project code.
Your MIPS code must include at least the following items to receive a passing grade:
https://sdsu.instructure.com/courses/123559/assignments/863448
1/2
9/19/24, 11:06 AM
Project – FINAL Report
Conditional branches, equivalent to C if-else
Nested Loops equivalent to C while(), for() or do-while()
Use of a 2-D array
Use of the stack to store the $ra (return address) register
Additional methods and more extensive operations, the use of advanced features such as sound,
floating point, bitmap graphics, and storing local variables on the stack or recursive functions will receive
additional points.
The report must document the structure of your final project, written in C and assembly with comments
and any prototype functions that define arguments and return values. List limitations due to I/O and other
features that were not complete.
This report and code should include the high level definition and pseudocode plus your final project
MIPS assembly code FORMATTED in the style used in the MIPS code examples. By the time you
complete the MIPS code, it must embody the basic logic and algorithms described above.
Once you have submitted the final report here, please schedule your 10-minute one-on-one meeting to
discuss your project with the instructor.
Please prepare for the meeting by making sure you:
Have the development environment(s) you need to demo your program operation
Have your final report open and ready to show
Have your SDSU or other government issued Photo ID with you
Have a working webcam or phone camera that works with zoom
In the meeting you will be asked to describe and demonstrate your project operating, and to discuss your
code.
*Please note that the final report and code will be subject to checks for plagiarism, so be sure to clearly
mark anything you did not personally write, and include citations to indicate where that material came
from to avoid the academic and punitive sanctions which are consequences of plagiarism
(https://newscenter.sdsu.edu/student_affairs/srr/cheating-plagiarism.aspx) as defined in the rules defined
in the SDSU catalog, and SDSU’s student rights and responsibilities
(https://newscenter.sdsu.edu/student_affairs/srr/academic-dishonesty.aspx) , as well as the student-
teacher contract.
https://sdsu.instructure.com/courses/123559/assignments/863448
2/2