What is a final project for an assembly language program?
The student project consists of an assembly or mixed C and assembly language program.
The code can be written for any ARM architecture, x86 in IA32 or 64-bit code, MIPS or AVR architecture.
The student project consists of:
The proposal describes WHAT the program will do. (this step is already completed and attached on PDF below. Also, base the project off of this proposal )
The draft Progress Report shows HOW you plan to implement the code and progress to date.
The final report documents the project, including working source code and demonstration of the results.
The project draft progress report consists of:
The draft should contain as much of the material that will be in the final report (see final report below), even if just in outline form with minimal detail. The more info you include, the better the feedback you will be provided.
Report File must be in .doc, .docx or .pdf form ONLY - no rtf, zip or other file formats!
Source Code is optional but should be pasted into the report document AND provided IN SEPARATE file(s) if you have questions.
It should include at least the following:
High-level pseudocode and description to describe HOW you will implement your project code.
Diagram showing high-level design.
List of tasks you need to complete before submitting the project.
List of items you need (hardware and software) in order to debug, demonstrate and submit your project.
Revised and updated schedule.
The final project report consists of:
It must include the following in the .doc .docx or .pdf format project report:
Description of the project, and what part is done in assembly.
List the hardware, development tools, software, and other resources needed for the project
High-level pseudo-code or flowchart defining the algorithm (what the code does), including details on the part(s) written in assembly language.
ALL Source code and other files used to create the working project.
Documentation of any special items (hardware schematics, software library APIs, wiring, photos, etc.)
Tests you ran, results, and project limitations.
Screen capture of demonstration or a link to a youtube video demonstration of your project in action.
What you would do differently if you had time.
Hours spent on the project.
Source code and other required files MUST be pasted into the report document AND submitted as separate files so that your code can be compiled/assembled - submit all that is required for us to reproduce your results, otherwise, we will not consider the project as fully functional!!
Your report MUST be submitted here on Bb as a .DOC.DOCX or.PDF report file format, plus your source code files. (Please submit separate files, individually. Please do not zip them into a combined file. Thanks.)
Final project report submissions:
Projects must have at least 3 pages of 10 point font assembly code (not including comments, etc.), written solely by you.
You MUST include comments, pseudo code, and other support materials as required to document your project so that another assembly language programmer can understand how it does what it does.
Your final submission must be modular (The main function calls sub-functions or assembly subroutines), and broken into logical chunks.
You may not put the bulk of the code in one module!
You must use appropriate programming constructs such as conditional if/switch/case and for/while iteration structures in C and conditional jump/branch instructions in assembly code.
Pointers and grouped data such as arrays and structs are encouraged, and your program must make use of appropriate data structures, pointers, arrays, as appropriate, depending on the specific project.
Student Project Report - the "what" and "how"
You must define what you did and how you implemented the project. This report must define the "what" and "how":
You must document it to define what your project does (==a technical specification) and how you will implement it (==the top-level design). You also need to explain how you verified that it works (design validation and test).
The results of the testing, as well as how you tested to see that it works as specified must also be included.
List all the individual tasks, modules written, tests, and approximately how many hours it took to complete each one.
Your project final report must be turned in here on Blackboard and must include the following items:
An introductory paragraph summarizing the items below. Description of the project, and what part is done in assembly.
High-level design in pseudocode/diagram/flow chart form, showing the major module inputs, outputs, processes and how they interact.Descriptive paragraph for each top-level function explaining what's in it and how it works.
All source code for each function in C or assembly language and any other files used to create the working project.
Specific tool set used (i.e.: Windows/Eclipse with MinGW gcc compiler, or Raspbian GCC compiler, etc.)
User instructions: how to use the program with examples.
Test results and any lab notes, bugs, remaining issues.
Include the following files: .doc, .docx, or .pdf with EVERYTHING including source code pasted into ONE report document. Separately, attach all source files, (source file types include *.c *.h and others) plus anything else that would be required for me to reproduce your results.
List the hardware, development tools, software, and any special items (hardware schematics, software library APIs, wiring, photos, etc.)
Tests you ran, results, and project limitations.
Screen capture of demonstration or a link to a youtube video demonstration of your project in action.
What you would do differently if you had time.
Conclusion
Hours spent on the project