Skip to main content

Senior Design Resources

Important Dates:

  • Undergraduate Programs Project Funding Request Deadline - October 22, 2023
  • Conference Registration Form Deadline - February 4, 2024
  • Senior Design Conference - May 9, 2024
  • Senior Design Thesis Library Submission Deadline - June 13, 2024
  • 2023-2024 Key Dates for Seniors

Project Funding:

Senior Design Safety Requirements:

Research Assistance:

Conference Registration:

  • Online conference registration will open in early January. Registration will close on February 4, 2024
  • Changes to a team's registration information must be sent to swibeto@scu.edu by March 8, 2024.

Presentation Format:

Thesis Writing Information:

Department Specific Guidelines:

Thesis Submission Information:

  • Step 1: Submit your completed thesis to your department for review and approval. Please speak with your department (and/or advisor) for specific submission instructions and deadlines if not already listed in the Department Specific Guidelines section above.
  • Step 2: Submit the approved thesis and accompanying documents to your department for final Library submission as outlined in the Senior Design Thesis Library Submission Process.

Please contact Jean Tsai at ctsai2@scu.edu or (408) 554-4468 for more information.

IMPORTANT FINAL STEP:

All equipment, instruments, and materials borrowed from an advisor or school lab must be returned before a final grade can be assigned for senior design!

BIOE 194, 195 and 196 - Senior Design Project

Final Design Thesis (FDT) Guideline for Biomolecular Track Research

This recommended structure for your report is based on the recommended structure for the final thesis document that you will submit at the end of the academic year. This guideline is recommended for the theses in the field of biomolecular engineering. Please note, this guideline does not intend to replace School of Engineering general formatting guidelines. Instead, it is ONLY a guideline that is IN ADDITION to School of Engineering general formatting guidelines. For general formatting guidelines, use format at: http://scu.edu/engineering/srdesign/student.cfm

General Comments -Reports must be neatly word processed, carefully proofread for correct spelling and grammar, and edited for continuity and style consistency between different authors.

Formatting Comments - Follow the following guidelines:

1. There should not be large sections of white space in the body of the thesis. Move text or resize figures accordingly. You may have blank space at the end of a chapter given that the next chapter will begin at the top of the next page.

2. Figures must be numbered with captions below the figure, with font size of 10.

3. Table must be numbered with captions above the table, with font size of 10.

4. All references must be properly cited and listed in a bibliography. This is critical - you MUST have fully documented citations, and all cited work MUST be properly credited. A free online software "Mendeley" is recommended for your bibliography organization from the beginning. Please go to www.mendeley.com for software download and setup instruction.

5. Respect the copyrights. In short, if you didn't create it, it is not yours. Students need to obtain owner's written permission to use it. That includes images, cartoons, figures, tables, data and sentences that you can usually download from internet and copy from textbooks. Please plan ahead for those signatures.

Common report organization - This shows a typical final thesis outline, although actual contents and organization may vary by project. Consult with your advisor and/or the instructor if you would like to get feedback on an alternate report structure.

Although the format may vary, underlined topics are required for all theses. For the FDT, students are required to include, at a minimum, the sections that are highlighted.

  1. Signature page - use format at: http://scu.edu/engineering/srdesign/student.cfm
  2. Title page - use format at: http://scu.edu/engineering/srdesign/student.cfm
  3. Abstract - this is a well-crafted and highly concise summary of the report. It should be no more than 1 page. A good abstract motivates the issue, states the goals of the project and the work accomplished, summarizes the results, and notes the impacts and/or conclusions. Ironically, it's better to write the abstract AFTER you have finish the rest of the thesis, in other words, this is the last piece of your thesis writing. Refer to the following example, and specifically note the structure of the abstract in terms of content: http://scu.edu/engineering/srdesign/student.cfm
  4. Acknowledgments - You MUST properly acknowledge financial support and in- kind contributions of sponsors, donors, mentors, etc. Sponsors may have very specific wording that must be included in such reports, so check on this with your advisor. You may also use this section to thank friends and family for their assistance and support.
  5. Table of contents – use format at: http://scu.edu/engineering/srdesign/student.cfm
  6. List of Figures – use format at: http://scu.edu/engineering/srdesign/student.cfm
  7. List of Tables – use format at: http://scu.edu/engineering/srdesign/student.cfm
  8. List of abbreviations - including those for the chemicals, biologicals, instruments and technical terminology.
  9. Introduction and Significance (What and Why)

This section is the most time-consuming part to write. You can skip to work on next section if you feel stuck but always remember to come back to finish it off.

In this section, you need to tell the readers what you want to do and why you do it. These two topics need to be explained in details. Then you want to outline how you are going to do it. The general order for this part could be:

* Background/motivation of subject matter. This is big picture rationale. It can be your vision of a "big thing", for example, cancer therapy, organ replacement, etc. No details needed here, it will be one paragraph, but your vision should be scientifically reasonable.

* Review of field/literature. This part needs the details and the review of previous literatures must be comprehensive. The literatures should be related to your "big thing". If there are many literatures (usually the case), you need to group them and categorize into paragraphs. Respect the copyrights and comprehensively cite references in bibliography.

* Critics of the current literatures and technologies. Nothing is perfect, you need to think

hard to analyze the literatures and identify the shortcomings of the reported theories and technologies. But all the critics should be based on scientific principles, not something you "thought", "guessed". After that, you can point out the key constraints to overcome these drawbacks. No "leap of faith" is allowed here.

* Statement of project goal, objectives and expected results. Here you can tell the readers exactly how to overcome these shortcomings and make things better in one or two sentences. That's your project goal. You can start with "Herein,". Next, you want to outline the milestone steps in order to reach your project goal. The relationship among those steps can be serial or parallel. For each step or milestone, you can spend maximum 3 sentences to describe. No details are needed here. Leave them to the following chapters. Last, you can describe briefly the expected results. These are the hypothetical results, you really don't want to get into details.

* A back-up plan. A back-up plan is needed. What about your design does not work out as you expected, what is your rescue plan? Ideally this backup plan should be conservative, the protocols and experiments should be well-established.

* Significance. You want to tell the readers what are the benefits and potential impacts if this project works and obtained the results above. Think big! Imagination is allowed here. for example, the field, well-beings, health, life of human kind, etc.

Team and management.

* Budget for the entire project. discuss main issues, refer to appendix for spreadsheet. * Timeline for the entire project. discuss main issues, refer to appendix for Gantt chart.

10. Chapters of project. Each step or milestone described above makes its own chapter. From now on, everything needs to be explained or described in details. Every piece of data you show must be true, original and repeatable. These chapters make up the main body of the thesis.

The organization of each chapter could be:

Introduction - This is very similar to the “introduction” part of the whole thesis, except being more focused on one milestone step you are going to describe in this chapter. "What" is this milestone or step you are going to do in this chapter, and its relationship and position in terms of the whole project ("why"). Next, you want to review the existing research and technologies regarding the milestone step in current chapter. This time, the review is more focused and detailed.

Details of key constraints - you could start with the critics of the existing technologies and continue with analysis and identification of the key constraints for this sub-project.

Detailed design description, novel approaches/solutions to problems - description has to be in depth and logic. Do not make a hypothesis on top of another hypothesis. Use photos, sketches, CAD drawings, layouts, flowcharts, etc. if necessary. High level descriptions and summaries blended with narrative, detailed documentation in appendices. Do not use technical jargons, for example, PCR should be written in “polymerase chain reaction”.

Detailed supporting analyses - brief description of approach to, and results of, major analyses and/or prototyping results.

Expected results - Detailed subsystem test/verification procedures/data specifically showing whether requirements are met or not.

A back-up plan

Materials and Methods - List all the chemicals, biologicals, instruments you used for your experiments, including their brand, company, model number. If mammalian cells, also includes the batch number of production. Describe every protocol you used in detail, the bottom line is that the readers can reproduce your experiment without asking you. Since this part is black and white, you can start to write this part as soon as you finish a particular experiment.

Results - This part you present the experimental results obtained from your own research. All the data, figures and tables should DIRECTLY result from your own experiments. Do not show any figures and tables from other publications. If it is cartoon illustration, you need to make your own. This part is also black and white, you just need to explain how you obtain those results (protocols, methods, data collection and organization etc), what each figure, curves and table means. No hypothesis in this part, just plain statement of the facts.

Discussion - In this part, you can discuss your results.

 

11. Summary and Conclusion. This is the final chapter of the main body of the thesis. It typically starts with a summary of the project. In this Summary section, you should restate your project objective and the milestone steps you did, discuss results (overall evaluation of the design, experimental results etc.). A table may help here.

Next, you move to integrate all the milestone steps and verify if your whole project design works or not. At the end of all the discussion, you need to write a clear statement if your project design works or not.

This chapter also typically has a Future Work section in which you provide a well-thought-out list of suggested improvements and areas for future exploration. The chapter often concludes with a Lessons Learned section in which you reflect on the project as an educational experience, discuss what your challenges were, consider what you did well and what you realize you should improve, and identify nuggets of wisdom to pass on to future students.

12. Engineering Standards and Realistic Constraints - discuss how the following considerations impact your design: economic, environmental, sustainability, manufacturability, ethical, health & safety, social, and political. At least five of these factors must be discussed in sufficient detail to show understanding of the issues and relevance to the project. Refer to the SCU Engineering Handbook for guidance and background on these issues. For FDT, include 5 topics of your choosing with one paragraph describing the importance and relevance of each topic. Note that this is not just a creative writing assignment. Most projects have very real standards and constraints that are relevant. Either you face them directly as you do your project, or perhaps they would be an issue if your product were to ever really be put into production/use.

13. Bibliography. Students MUST cite references properly and completely. Recommend using free online software “Mendeley”.

14. Appendices. Appendices hold detailed information that isn’t appropriate for the body of your narrative design report. That said, you should realize that the body of your report should still include some detail, but it is a selected set of detail. So, the body should include key figures, summary tables of specifications and results, high-level drawings (like configuration sketches, functional and component diagrams, data flow diagrams, etc.), specific test and simulation plots showing behavior and results, and perhaps particularly interesting detail (mechanical drawing, electronic schematic, pseudo-code, etc.) of critical components. In general, all the negative and non-critically positive results that you mentioned but didn’t fully described in the body go to appendix.

BIOE 196 – Senior Design
Final Design Thesis (FDT) Guidelines
Medical Device Track

Suggested FDT Organization

While the particulars of each project might lead to alternate organizational structures, the outline below is typical of many senior thesis documents in the past. For general formatting guidelins, use format at: http://scu.edu/engineering/srdesign/student.cfm.

General Comments - Reports must be neatly word processed, carefully proofread for correct spelling and grammar, and edited for continuity and style consistency between different authors.

Formatting Comments – Follow the following guidelines:

  • There should not be large sections of white space in the body of the thesis. Move text or resize figures accordingly.
  • All references must be properly cited and listed in a bibliography. This is critical – you MUST have fully documented citations, and all cited work MUST be properly credited.

Common report organization – This shows a typical final thesis outline, although actual contents and organization may vary by project. Consult with your advisor and/or the instructor if you would like to get feedback on an alternate report structure.

Although the format may vary, underlined topics are required for all theses. For the FDT, you are required to include, at a minimum, the sections that are underlined.

  • Signature page – use format at: http://scu.edu/engineering/srdesign/student.cfm.
  • Title page – use format at: http://scu.edu/engineering/srdesign/student.cfm.
  • Abstract – this is a well-crafted and highly concise summary of the report. A good abstract motivates the issue, states the goal of the project and the work accomplished, summarizes the results, and notes the impacts and/or conclusions. use format at: http://scu.edu/engineering/srdesign/student.cfm.
  • Acknowledgments – You MUST properly acknowledge financial support and in-kind contributions of sponsors, donors, mentors, etc. Sponsors may have very specific wording that must be included in such reports, so check on this with your advisor. You may also use this section to thank friends and family for their assistance and support.
  • Table of contents use format at: http://scu.edu/engineering/srdesign/student.cfm. List of Figures - use format at: http://scu.edu/engineering/srdesign/student.cfm. List of Tables - use format at: http://scu.edu/engineering/srdesign/student.cfm.
  • Introduction (What and Why)

    background/motivation of subject matter (big picture rationale) o review of field/literature (with references cited in bibliography) o statement of project goal, objectives and results

    Systems-Level Chapter (the big picture) – Projects with several subsystems are often complicated enough that you need to use a systems-level chapter to provide the reader with an overview of the system so that they have a good ‘big picture’ idea of what’s going on prior to your discussion of detailed component-level analyses and designs. If this applies to you, here are common topics in the appropriate order for such a chapter:

    o System-level overview – Summary of the overall system with a mission/product architecture sketch with words that point out the main parts of the system and how they interact, a physical configuration sketch with words that describe the physical layout and location of key elements, a functional component-level sketch showing main parts and how they are functionally connected to perform tasks, etc.

    o Customer needs and system level requirements - refer to PDS (preliminary design specification), market survey report, QFD (quality function deployment), as needed

    o Benchmarking results - what’s out there that is similar
    o Functional Analysis – note that this section shows how the system is broken into the main

    subsystems with the idea that your next few chapters will go into these subsystems in more detail
    Functional decomposition (main functions and subfunctions)
    Specific lists of subsystem-level inputs/outputs, behaviors, constraints,

    performance requirements, resource budgets, etc. (summarize here, details in

    appendix)
    o Key system level issues, system options, tradeoffs, rationale for choice (refer to selection

    matrices in appendix)
    o Team and project management

    •  Project challenges and constraints and how they are dealt with

    •  Budget (discuss main issues, refer to appendix for spreadsheet)

    •  Timeline (discuss main issues, refer to appendix for Gantt chart)

    •  Design process (your approach to design for this project)

    •  Risks and mitigations

    •  Team management (approach, issues, responses)

      Subsystem Chapters - one for each major subsystem

    o Intro to role/requirements of subsystem (match systems chapter)
    o Summarize options and trades (refer to selection matrices in appendices)
    o Detailed design description, novel approaches/solutions to problems
    o Detailed supporting analyses (brief description of approach to, and results of, major

    analyses) and/or prototyping results
    o Detailed mech/elec/code descriptions as needed with photos, sketches, CAD drwgs,

    layouts, flowcharts, etc. High level descriptions and summaries blended with

    narrative, detailed documentation in appendices
    o Detailed subsystem test/verification procedures/data specifically showing whether

    requirements are met or not

  • System Integration, Test and results (experimental protocol and results, comparison to predictions) – Given that many of the previous chapters are often specific to the details of the subsystems and components of your system, the purpose of this chapter is to discuss how these systems were integrated and tested. It details how tests and verification was performed and what the results were. In presenting results, there should be an emphasis on demonstrating that critical requirements and customer needs were sufficiently met. For FDR, include a simple description of your integration and test/verification approach (is integration challenging, how much planning will it take, will you have any formal procedures for assembly, what verifications/tests will you perform and how will they be accomplished, do any of them require special equipment or procedures, how much time will assembly take, how much time will verification take, and so on).

    Costing analysis (analysis of overall prototype costs vs. budget, and, if appropriate, production costing estimates and evaluation) – depending on your project, this may be an appendix

    Patent search or Business Plan – depending on your project, this may be an appendix

    Professional Issues and Constraints (discuss how the following considerations impact your design: ethical, science, technology, & society, civic engagement, economic, health & safety, manufacturability, usability, sustainability, and environmental impact). At least five of these factors must be discussed in sufficient detail to show understanding of the issues and relevance to the project. Refer to http://scu.edu/engineering/srdesign/upload/Professional-Issues-and-Constraints.pdf for guidance and background on these issues. For FDR, include 5 topics of your choosing with one paragraph describing the importance and relevance of each topic. Note that this is not just a creative writing assignment. Most projects have very real standards and constraints that are relevant – either you face them directly as you do your project, or perhaps they would be an issue if your product were to ever really be put into production/use.

    Summary and Conclusions – This is the final chapter of the main body of the thesis. It typically starts with a summary of the project. In this Summary section, you should restate your project objective and the work you did, discuss results (overall evaluation of the design, experimental results, the extent to which the product satisfied the customer, etc.), and review the impact of the work you did. This chapter also typically has a Future Work section in which you provide a well- thought out list of suggested improvements and areas for future exploration. The chapter often concludes with a Lessons Learned section in which you reflect on the project as an educational experience, discuss what your challenges were, consider what you did well and what you realize you must improve, and identify nuggets of wisdom to pass on to future students. For FDR, I expect at least two-page summary of your project goals, the work you did, discussion on the results (overall evaluation of the design, experimental results, the extent to which the product satisfied the customer, etc.), and your plan for the rest of the year. The details of this plan should be included as an Appendix, and should include the build/buy plan, a list of possible problem areas/risks, and a development timeline.

    Bibliography – you MUST cite references properly and completely. Use format at: http://scu.edu/engineering/srdesign/student.cfm

    Appendices – Appendices hold the detailed information that isn’t appropriate for the body of your narrative design report. That said, you should realize that the body of your report should still include some detail – but it is a selected set of detail. So, the body should include key figures,

  • summary tables of specifications and results, high-level drawings (like configuration sketches, functional and component diagrams, data flow diagrams, etc.), specific test and simulation plots showing behavior and results, and perhaps particularly interesting detail (mechanical drawing, electronic schematic, pseudo-code, etc.) of critical components. That said, ALL detail is included in the appendix – to include complete sets of mechanical drawings, source code, circuit designs, analytic results, experimental plans/procedures/results, etc. In general, all important “work product” generated as you develop your system should be presented via an appendix.

    o Detailed design definition information and reports, such as customer needs surveys, the PDS, requirements lists/flowdowns, resource budgets, etc.

    o Detailed design analysis results such as functional decomposition, sketches and lists of alternate designs, decision matrices or rationale, QFD analysis, etc.

    o Detailed engineering analyses - readable and well organized detailed calculations (hand and FEA), dynamic and controls analyses and simulations, etc.

    o System-level descriptions – configuration sketches, mission/product architectures, functional and component diagrams, etc.

    o Mechanical detail and assembly drawings (only drawings that are specifically referenced should be in the body of the report). NOTE: a full set of detail and assembly drawings with complete bills of materials must be included.

    o Electronic circuit designs
    o For biotechnology related projects, schematics of your experimental system –

    drawings/charts that show the overall experimental processes, and any schematics of each

    step that explains the working principles of your system
    o Software source code
    o Project management data - time lines and budget spreadsheets, build/buy plans/decisions,

    etc.
    o Test and verification information – test plans/procedures, experimental data
    o Information from manufacturers – spec sheets, manuals and application notes for key

    components, etc.
    o copies of important patents