Skip to main content

Systems Engineering M.Eng. Project Report Requirements

in this section

Section Navigation

In This Section:

Project Report Requirements -- Spring 2018

This document outlines the contents, format, deadlines, and submission procedures for the M. Eng. in Systems Engineering project report as a requirement for graduation. Keep in mind that this report may have to be completed and submitted to the Systems Engineering program office in addition to whatever submission your project advisor requires to satisfy your grade for the project class. Your project advisor may require a different deadline than the submission to the Systems Engineering program office. If allowed by the project advisor, project reports may be submitted as group reports.

Systems Engineering Content Requirements

The M. Eng. Systems Engineering project must follow the Systems Engineering Project Guidelines and the report must meet Final Report Requirements, as specified in the accompanying document, Systems Engineering Project Guidelines and Final Report Requirements.

For most M. Eng. projects’ reports, there will naturally be sections on customer analysis, context analysis, requirements analysis, consideration and analysis of functions and structures of alternative solutions, a management plan, risk analysis, and so on. In the rare case that your project does not follow this pattern, you can demonstrate you have followed the System Engineering Project Guidelines by including in your report a supplement summary of your systems engineering work. This summary must be a minimum of 5 pages (1.5 spaced, 12-point font, excluding figures and tables), and be of interest to an audience of systems engineers. For example, you could describe how you tailored the systems engineering process (as covered in SYSEN 5100) to meet the needs of your project or provide a review of specific systems engineering techniques (as covered in SYSEN 5200) which you applied.

Draft Outline

If your project is one of the pre-approved projects directly run under the Systems Engineering program (i.e., your project course number is SYSEN 5900), then the draft outline requirement is waived.

If your project is not one of the pre-approved projects directly run under the Systems Engineering program you must submit a draft outline on or before the last day of class for approval. The draft outline should be approximately 2 pages (1.5 spaced, 12-point font, excluding tables and figures) and address in moderate detail each of the numbered items as outlined under the Final Report Requirements section in the accompanying document, Systems Engineering Project Guidelines and Final Report Requirements. The purpose of this draft outline is to help ensure that the Systems Engineering content of your report is likely to meet the graduation requirements of the Systems Engineering program.

Submit the draft outline to the Systems Engineering program office via the GFA, Marcella Purcell, at mk594@cornell.edu, no later than May 1, 2018.

Final Report

The Systems Engineering program reserves the right to consider the quality of any report and supplements in their determination of a student’s eligibility to graduate.

If your project is not one of the pre-approved projects directly run under the Systems Engineering program, in your final report you must highlight or clearly indicate which pages or sections of the report you believe satisfy the Systems Engineering content requirements as this will enable the reviewer to make a rapid decision in your favor. Failure on your part to clearly indicate the Systems Engineering content may result in the rejection of your report.

Submit a PDF version of your final report to the Systems Engineering program office via the GFA, Marcella Purcell, at mk594@cornell.edu no later than May 14, 2018. If you have concerns about satisfying this requirement, you may contact the GFA but it cannot be guaranteed that other arrangements can be made.

"Robocup, The Formula SAE Car... These may sound like mere student projects. But we pit our best designs, our best thinking, against other universities around the world. It's competition on a global level - an invaluable way to learn. And we perform."

Albert R. George, J.F. Carr Professor of Mechanical & Aerospace Engineering