Formal Project Report Format/Specifications

Formal Project Report Format/Specifications 

*All sections of this report must be computer generated to be considered in the grading process 

Page One: 

Title page - This should include: 

A Course name and number 

B. Date submitted / date due 

C. Name of faculty member(s) and their associated department 

D. Name of the project 

E. Name of the preparer 

Page Two: 

Project Objective 

You are to describe the purpose or objective of the course project. This should be a 

brief but complete statement of what you intend to design and prototype. A bulleted list 

of design criteria should be included. Be sure to classify hard, soft, or firm requirements. 

Parts List 

List all parts used, including name, manufacturer’s part numbers, and quantity for the 

project. Use a table and be sure to provide a table number and description in a similar 

format to a standard textbook. 

Page Three and beyond: 

• Theory 

A brief section is to be included which should detail any theoretical foundation of the 

project. Start by explaining the theory behind the real time operating system used. Be 

sure to detail “hard”, “soft”, and “firm” requirements, deadlocks, priority inversion, task 

synchronization, and other “real-time” terminology required to understand your project. 

Then in a new paragraph, detail the theory of operation of the interfacing circuitry used 

in the project and how it connects to the microprocessor. Then explain the technical 

details of the microprocessor used and how they relate to the project. 

• Hardware/Interface 

Detail the hardware interfacing circuitry and other important circuitry included in the 

project. Give each unique hardware interface its own section within this section. 

Schematics are an essential part of any engineering work and should be included in 

each hardware-interfacing section. The last section within this section should include 

final schematic and explain how it all comes together at the hardware level. Then the 

use of Ultiboard should be explained and the final Ultiboard drawing should be inserted. 

Submitted drawings are to be neat and clearly labeled with both figure numbers and 

descriptions similar to the format of a standard textbook. All schematics and other 

drawings MUST be computer generated. 

• Procedure/Data Collection 

Detail briefly, the procedure used for designing, programming, and prototyping the 

project. Include the lab activity which involved testing each portion of the project. Must 

be a clear bulleted list that provides the steps involved in completing the project. Use a 

new bulleted list for each part of the procedure. In other words, make a list for 

designing, a new list programming and setting up the development environment, and a 

new list for prototyping and testing. Be sure to clearly label each list. 

• Calculations 

Include ALL pertinent computations as part of your report. You must give a sample 

calculation for each unique relationship used in the project. Label each calculation 

according to the quantity that is being solved. Do not label calculations based on parts 

or sections of a lab activity. For example label an equation “Ohm’s law” instead of “Part 

I” even if ohm’s law was used in part one of the lab activity. After the label, be sure to 

show the transfer function or formula and then under that show the numbers plugged 

into that transfer function or formula followed by the answer. How well you present 

your calculations is considered greatly in grading. Make them make sense and present 

them in a clear, orderly fashion. This section MUST be computer generated. Also 

copy and paste the results of Labrosse’s RAM calculator after you have tailored it to 

comply with your configurations. 

Formal Project Report Format RAF 9/27/07

• Scheduling Theory 

Detail steps involved in Rate Monatomic Scheduling or Extended Rate Monatomic 

Scheduling and the results of the steps taken. Conclude this section with a table 

detailing the priorities of each task you chose. 

• Sample Code 

Detail your unique application code by breaking it up into listings and explaining each 

line. Refer to the textbook for an example. Petri Nets should be included in this part 

with algebraic representation included in the description of each. 

• Cost Analysis 

Include a table with cost analysis of the prototype and a cost analysis of future design 

for “real-world” implementation of the prototype. 

The Last Page: 

• Discussion 

A. Demonstrate how the design criteria were met. DO NOT PROVIDE A 

PROCEDURE IN THIS SECTION. Refer to a Listing to explain how you met design 

criteria through the use of software. Refer to a drawing or schematic to explain how 

you met design criteria through the use of hardware. Be very careful using words 

like “most”, “high”, “low”, “greater”, “success”, “fail”, and “got”. These words are not 

acceptable. Instead write how “high” or “low” in the form of an actual number from a 

calculation you are referencing. In other words, define these relative terms through 

actual events or technical findings experienced throughout the project. 

B. Include future design ideas for “real-world” implementation of the design and detail 

the advantages and disadvantages of each idea. 

C. Be sure to discuss technical findings or problems in “real-time” terms such as 

“deadlock”, “deadlines”, “periods”, “worst case execution time”, “missed deadlines”, 

“priority inversion”, and “task synchronization”, “response-time”, and more. 

Other Notes 

1. Students should read the writing rubric supplied by the instructor because it will be used 

in the grading process of the lab report. 

2. It is highly recommended that students submit their reports to an English faculty member 

for review before the due date. The student is responsible for arranging this opportunity 

with an English faculty member. Please have the English faculty member sign the 

report that he or she has reviewed and submit that report with your final report. 

3. Each student must submit an individual report. Obviously two students who work 

together would have access to the same code developed during the lab activities. 

However, application of the code towards the project would be individualistic. 

4. The student is responsible for making the report clear and easy to understand. The 

reader should not have to take this course to understand what the lab is supposed to be 

about. The report must be taken seriously and written professionally as if you were 

submitting it to a manager in industry. 

5. Project reports must only contain technical information pertaining to the project being 

reported. This does not include subjective comments about irrelevant, inappropriate, 

and/or nonprofessional material. Project reports that include questionable material may 

not be considered for a grade. 

6. Project reports must be computer generated. Hand modified lab reports may not be 

considered for grading. Any portion of the formal report that isn’t computer generated 

will not be considered for grading. 

7. Project reports must be printed and stapled at least one hour before the due date. If the 

instructor has any indication that this rule has not been followed, the report will not be 

considered for grading. 

8. Project reports are only collected before lab begins. If you are late to class then your 

project report is late and will not be collected. 

9. Project reports that are in the laboratory print device while the labs are being collected 

then the project report will not be collected. 

10. Project reports that resemble another student’s unique work will not be considered for 

grading. 

Formal Project Report Format RAF 9/27/07

Formal Project Report Format/Specifications

Create successful ePaper yourself

Delete template?

Save as template?