Page 9 - SE_Approach_for MSEE_MSCE_Capstone_15_Page_review2
P. 9
2016 ASEE Rocky Mountain Section Conference
Input from the "customer" will then be use to provide corrections in the final report
detailing 1) the product, 2) specifications 3) system diagram including blocks, and
interfaces 4) interface specifications, 5) detailed subsystems and 6) design tradeoffs.
For design tradeoffs, the instructor is looking for what choices did the student make and why.
The student must include the rationale of hardware/software selection as well as the design
choices that the student eliminated.
Week 11: Final Report and Oral Presentation, Technical Merit. The final technical report is a
polished version and compilation of previous work and deliverables that was revised and fine-
tuned to produce a professional document. In addition to items for Week 10, the student must
include:
A presentation due on Week 6 defining the product and outline their progress to date
(Preliminary Design Review)
A demonstration of the product or providing sufficient modeling to demonstrate
performance and quality of the proposed product (Critical Design Review)
Other items identified in weekly progress and activity reports
A final report detailing: (1) the product, (2) specifications, (3) system diagram including
blocks, and interfaces, (4) interface specifications, (5) detailed subsystems and (6) design
tradeoffs, that is: what choices did the student make and why including the components,
or elimination of design choices and why?
In addition to the above a systems engineering deliverables, the completed project must consider
sufficient scope and technical merit to demonstrate proficiency and expertise in this capstone
project. The next section lists several factors and considerations to help stress the importance of
technical merit during the execution of the capstone project.
Technical Merit
The engineering department anticipated that a student can satisfactory meet the weekly
deliverables from the system engineering process but the project may lack technical depth at the
Masters level. To take this into account, a percentage weight of 30% for technical merit is
considered. Several factors are considered to evaluate and assess the technical depth and merit
of a project including:
Degree of technical difficulty in solving a problem and finding a solution
Evidence and technical depth of analysis on the solution
Considerations and technical depth of alternative solutions
Substantiate proposed solutions with data and facts including technical and economic
feasibility
Evidence and technical depth of synthesis and evaluation tasks from engineering courses
in the Master’s program
Evidence and technical depth of newly acquired technical skills not emphasized or taught
in the program (also measures degree of independent learning by the student)
Evidence of integrating information from many sources to gain insight to the problem
© American Society for Engineering Education, 2016
Input from the "customer" will then be use to provide corrections in the final report
detailing 1) the product, 2) specifications 3) system diagram including blocks, and
interfaces 4) interface specifications, 5) detailed subsystems and 6) design tradeoffs.
For design tradeoffs, the instructor is looking for what choices did the student make and why.
The student must include the rationale of hardware/software selection as well as the design
choices that the student eliminated.
Week 11: Final Report and Oral Presentation, Technical Merit. The final technical report is a
polished version and compilation of previous work and deliverables that was revised and fine-
tuned to produce a professional document. In addition to items for Week 10, the student must
include:
A presentation due on Week 6 defining the product and outline their progress to date
(Preliminary Design Review)
A demonstration of the product or providing sufficient modeling to demonstrate
performance and quality of the proposed product (Critical Design Review)
Other items identified in weekly progress and activity reports
A final report detailing: (1) the product, (2) specifications, (3) system diagram including
blocks, and interfaces, (4) interface specifications, (5) detailed subsystems and (6) design
tradeoffs, that is: what choices did the student make and why including the components,
or elimination of design choices and why?
In addition to the above a systems engineering deliverables, the completed project must consider
sufficient scope and technical merit to demonstrate proficiency and expertise in this capstone
project. The next section lists several factors and considerations to help stress the importance of
technical merit during the execution of the capstone project.
Technical Merit
The engineering department anticipated that a student can satisfactory meet the weekly
deliverables from the system engineering process but the project may lack technical depth at the
Masters level. To take this into account, a percentage weight of 30% for technical merit is
considered. Several factors are considered to evaluate and assess the technical depth and merit
of a project including:
Degree of technical difficulty in solving a problem and finding a solution
Evidence and technical depth of analysis on the solution
Considerations and technical depth of alternative solutions
Substantiate proposed solutions with data and facts including technical and economic
feasibility
Evidence and technical depth of synthesis and evaluation tasks from engineering courses
in the Master’s program
Evidence and technical depth of newly acquired technical skills not emphasized or taught
in the program (also measures degree of independent learning by the student)
Evidence of integrating information from many sources to gain insight to the problem
© American Society for Engineering Education, 2016
