1. 1 건국대학교 항공우주정보시스템공학과 기초설계 ( 공학설계 ) #6 보고서 작성 및 발표 (Report Writing and Oral Presentation)

2. 2 보고서 작성 설계보고서 일반사항  Design Report writing is an important skill for engineers.  The purpose of the Design Report is to prepare you for your future profession.  Design Reports are complex because they reflect the final results of detailed research, often undertaken over an extended period. Yet, little of this detail is included in the body of the report.  The report itself includes summary information, including the rationale behind critical decisions leading to the recommendations. However, there is a place for the detail: the Appendix, where it can be accessed as needed.  The Design Report, therefore, gives the reader access to 3 levels of information:  A Summary  The Introduction, the Analyses sections, the Conclusion  The Appendices

3. 3 보고서 작성 보고서의 기본 요구사항 No universal rules since not all projects are the same Easy to recognise Precise & informative title Well organized layout & formats Pleasurable to read Accurate, fluent & concise Appropriate headings Suitable diagrams, charts & graphs  Important prerequisites for writing a good laboratory report:  understanding the purpose of the report, providing your reader with a clear map of your report  writing up your outcomes and recommendations in appropriate descriptive and summary vocabulary  using well-designed explanatory charts and clear equations.

4. 4 보고서 작성 Before writing, consider: Why you are writing What you hope to achieve Who you are writing for  These considerations will determine your report’s content, organization, textual and visual design Reports generally include these sections in this order: Abstract Introduction Literature Review Methodology Results Discussion Conclusion

5. 5 보고서 작성  설계 보고서 작성 목적  To inform readers of engineering design results precisely, concisely, and specifically.  To convey information clearly and to persuade your reader of your arguments. Explain problem or issue studied Discuss research method Describe data collected Describe research findings Explain implications  Describe research Explain problem or issue studied Discuss research method Describe data collected Describe research findings Explain implications

6. 6 보고서 작성  설계 보고서 작성 시 유념할 사항  think who the readers are and what you want them to learn from the report  plan the structure and contents, before you write anything  Determining Your Purpose and Audiences Your report will go to your manager who must approve your design before it can be implemented. The report must allow your manager to decide if your design satisfies all requirements. Company management may also read the executive summary and conclusions of the report. Eventually, your report may go to the end customer.

7. 7 보고서 작성 How does a report differ from an essay?  “A report is a statement of an investigation or of any matter on which definitive information is required.” (Oxford English Dictionary, 2008)  “Essays are an intellectual exploration of a topic involving looking at different arguments and evidence and developing the writer’s perspective.” (Plymouth University, 2011, p1) ReportEssay Formal structure Structure can be left to the discretion of the writer but normally has an introduction, main text in paragraphs and conclusion Defined sections with headings, including, as required: Methodology, Results/findings, Discussion/evaluation Does not contain subheadings (unless specifically asked for by the tutor). Different points are written as paragraphs Commences with a Summary or Abstract before the Introduction Commences with an Introduction; there is no Abstract or Summary Systematically defines and analyses a subject or problem Discusses, explains, analyses, interprets or evaluates a topic Used to communicate the results or findings of a project/piece of research. Used to develop points or arguments in depth via a sequence of paragraphs (discursive writing) Different sections may require different styles of writing throughout, depending on their purpose. Same writing style is generally maintained throughout May include tables, figures and illustrationsNo illustrative material accompanies prose. Information may be recorded in bullet pointsNo illustrative material accompanies prose. May make recommendations for future actionsVery unusual to make recommendations although conclusions will be drawn

8. 8 보고서 작성 Layout: how to structure a report Reports are written for different audiences and consequently their exact layout may vary. Specific industries or institutions will have their own ‘house style’; however, as a general rule the following common elements should be presented: Title page Title of report, Writer(s), Module reference number and title, Module tutor or leader, date, word count Contents page List of chapters/section headings with corresponding page numbers; list of illustrations (tables and figures); list of Appendices Summary (Not numbered ) Also known as an Abstract. An overview, stand-alone section. 1.0 Introduction What the report will be about. See Section 5: Writing the Report 2.0 Main body Includes as appropriate, any methodology, results and discussions. Includes numbered sub-sections. See Section 5: Writing the Report 3.0 Conclusion May include also recommendations. See Section 5: Writing the Report References (Not numbered ) Precise details of the work of others Appendices Lengthy and detailed material that informed the report but does not necessarily need to be read. Can be used to check for accuracy. Includes statistics, questionnaires, interviews, etc. Each appendix is numbered but the section itself is not.

9. 9 보고서 작성 준비와 작성 6 단계 The Six Stages of Planning and Writing Process Before any work can begin, the scope or ‘terms of reference’ of the report need to be clearly understood. Key questions to ask:  What is the report about?  What will it cover?  What is outside the brief?  How does this define the research? Stage 1: Clarifying the brief Make sure that the assignment brief is fully understood. What are the instructions? What was said at the assignment launch? If unsure, ask for clarification.

10. 10 보고서 작성 준비와 작성 6 단계 Stage 2: Doing the research Check the reading list for the assignment and any additional departmental reading lists. Be specific about what needs to be researched/analysed. Use Find it @ Harper and other recommended data bases. If unclear, ask the library staff for help in using the databases and research tools. Do not rely on the Internet – check the validity of the sites used. Use peer reviewed journals rather than the popular journals (although these can be a good starting point). Read summaries and assess usefulness. Don’t forget books and e-books! The library has an extensive range! Look for key words. Check the contents and indices of books for relevant ideas. Ensure when making notes, all the details of each reference are recorded for the reference list.

11. 11 보고서 작성 준비와 작성 6 단계 Stage 3: Organizing the content Re-examine the assignment brief. Review the notes made and group under the various headings. Be ruthless – discard anything that is not relevant or does not address the brief. Avoid padding. Make sure ideas are paraphrased into own words – avoid ‘copy and paste’. Make sure the order is logical. Stage 4: Analysis Don’t be narrative and simply describe the information/data. Critically examine the material gathered. What evidence has been found to make or substantiate the points? Are there any contrasting/conflicting theories, ideas or arguments? Does any of the research have limitations? Does the material relate to the assignment brief task? On balance, is there a compelling conclusion?

12. 12 보고서 작성 준비와 작성 6 단계 Stage 5: Drafting Follow the correct report structure for reports at Harper Adams University (see Section 5: Writing the report - essential characteristics). Be simple and concise; don’t include superfluous words and unnecessary detail. Avoid jargon but use correct technical terms. Include and make reference to tables, graphs and illustrations as appropriate. Include sub-headings for greater clarification. Read the draft and see if it is possible to remove 25% of the words without changing the meaning. Check assignment brief to ensure all aspects covered. Make changes – redraft. Stage 6: Proof reading Use the spelling and grammar checker; be careful to set it to the UK version. Read the report out loud – this helps check punctuation and that sentences and paragraphs make sense. Check all ideas and work by other authors have been cited in the text and correctly referenced in the reference list. Check all tables, figures and illustrations are numbered, have titles and the source is acknowledged. Ensure that text is paraphrased (own words) and there is no ‘copy and paste’. Ensure, where necessary, quotation marks are in place and correctly cited. Check layout, contents page, page numbers, labelling/captions.

13. 13 보고서의 구조 Clear structure The following are all key elements of a clearly structured Design Report. Title page title of project, client / lecturer / tutor, date, your name and student ID. Summary the summary page (level 1) sets the problem in context, summarizes what you have done, and provides the key outcomes and recommendations Table of contents this page clearly outlines each part of the report using section headings and page numbers (Use Word heading style for consistency in your document). Introduction the introduction (level 2) introduces and situates the problem being addressed and discusses any previous research in the area. Analysis section/s (often given a specific title) You need to provide a summary walkthrough of the analysis which led to your recommendations. Keep it simple, use only key charts and equations, and restrict it to 3 – 7 pages in length. Note that the detail (e.g. raw data) should be placed in the Appendix section. Considering Alternatives Being creative in seeking solutions Identifying possible solutions Documenting the alternatives Evaluating Alternatives Evaluating the alternatives against the selection criteria Choosing a justifiable option Justifying your choice Writing your Final Report Summarizing all steps of the process Identifying the preferred option/s Explaining your choice Submitting your report Placing your report in a ring binder with separators marking each section. The report should be ready to be audited at any time.

14. 14 보고서의 구조 The Design Report production process Your report will be based on the work you have undertaken beforehand. You will be working and thinking in many different ways. The following list outlines the processes you will probably go through. Beginning Meeting with the client/supervisor Understanding the Project Brief Planning the Project Understanding the scope of the project Deciding on the participants Starting the project file Creating the project plan Researching Possibilities and Process Investigating similar problems, research issues, possible solutions Identifying selection criteria for choosing the best solution Conclusion (and recommendations) this should give a brief summary of what you have done and include your recommendations. References this is a list in standard form of all the books, web sites and resources you have referred to in the report. Bibliography a wider reading list of other books and resources you used but did not refer to directly in the report. Appendices you may have more than one appendix which will describe in detail, if necessary, the analyses you have undertaken for the brief and the data you obtained. Place your work in a Design Folder many lecturers recommend you maintain a design folder in which you keep a record of the work undertaken for the brief. Uses section markers to help you with the summary process. Remember the cover sheet.

15. 15 보고서의 구조 Presenting data and illustrations: tables, figures, diagrams and photographs Tables  Tables are used to present results or summarise written information, for example, to compare and contrast two processes. In certain circumstances, particularly if reporting interviews, Speech Bubbles or Word Clouds may be used; check assignment brief to see if this is acceptable for the report.  Tables usually support or illustrate points in the text.  The caption (title) is above the table. Figures These include everything that is not a table – graphs, charts, diagrams, photographs. The type of figure chosen will depend on the nature of the data and the purpose for which it is to be used.  Numerical data can often be more clearly understood as a graph or chart, for example line, scatter plot, histogram, bar chart, and pie chart.  Processes can often be made more explicit by a flow chart.  Complicated machines or interrelationships lend themselves to diagrams.  Photographs can illustrate many things such as diseases, landscape features or machinery; they can be of great use if annotated. Whatever type of figure used, the caption (title) goes below it and below the source.

16. 16 보고서의 구조 Required Sections of the Design Report 1 Front Matter 2. Executive Summary 3. Customer Needs and Requirements 4. Concept Generation and Concept Selection 5. Selected Design Solution 6. Build Summary 7. Testing and Validation 8. Conclusion and Recommendation 9. References 10. Appendices

17. 17 보고서의 구조 ( 예 1) TABLE OF CONTENTS Executive Summary……………………………………………………………………….2 Introduction………………………………………………………………………………20 Background/Information Sources………………………………………………………..21 Engineering Specifications………………………………………………………………30 Design Evolution (Generation and Selection)....………………………………………...36 First Concept Description, The “Alpha Design”……………………………………...…45 Engineering Analysis………………………………………………………………….…47 Concept Description……………………………………………………………………...48 Engineering Design Parameter Analysis………………………………………………...58 Final Design and Prototype Description…………………………………………………66 Fabrication Plan………………………………………………………………………….79 Validation Plan and Results…………………………………………………………...…89 Design Critique and Discussion………………………………………………………….94 Recommendations………………………………………………………………………..96 Conclusions………………………………………………………………………………97 Acknowledgements………………………………………………………………………98 References………………………………………………………………………………100 Appendix A: Bill of Material…………………………………………………………....102 Appendix B: Description of Engineering Changes since DR 3…………………………103

18. 18 보고서의 구조 ( 예 2) Attachment 2 – Suggested Report Outline Statement of Compliance Table of Contents List of Figures and Tables 1.0 Executive Summary 1.1 System Overview 1.2 Competition Projections/Conclusions 1.3 Innovations 2.0 Schedule Summary 3.0 Table of Referenced Documents, References, and Specifications 4.0 Loads and Environments, Assumptions 4.1 Design Loads Derivations (i.e. accelerations, landing shock, etc.) 4.2 Environmental Considerations (winds, rain, etc.) 5.0 Design Layout & Trades 5.1 Overall Design Layout and Size 5.2 Optimization (Sensitivities, System of systems: planform, layout, powerplant, etc.) 5.2.1 Competitive Scoring and Strategy Analysis 5.2.2 Optimization and Sensitivity Analysis 5.3 Design Features and Details (Subassembly sizes) 5.4 Interfaces and Attachments 6.0 Analysis 6.1 Analysis Techniques 6.1.1 Analytical Tools (CAD, FEM, CFD) 6.1.2 Developed Models (Take-Off, Turning Flight, etc) 6.2 Performance Analysis 6.2.1 Runway/Launch/Landing Performance 6.2.2 Flight and Maneuver Performance (Incl. Surface Sizing) 6.2.3 Shading/Downwash 6.2.4 Dynamic & Static Stability 6.2.5 Aeroelasticity 6.2.6 Lifting Performance, Payload Prediction, and Margin 6.3 Mechanical Analysis 6.3.1 Applied Loads and Critical Margins 6.3.2 Mass Properties & Balance 7.0 Assembly and Subassembly, Test and Integration 8.0 Manufacturing 9.0 Conclusion List of Symbols and Acronyms Appendix A – Supporting Documentation and Backup Calculations (2 Pages) Appendix B - Payload Prediction Graph (1 Page)

19. 19 보고서 항목별 주요내용 Report Format and Organization Abstract  Always comes first  Microcosm of entire paper – contains key info from each section Contains essential information only – it is brief! Covers research highlights Gives the research problem and/or main objective of the research Indicates the methodology used Presents the main findings and conclusions Background/Introduction  Explains the research problem and its context Explains importance of the problem (Why does it matter? Why is more information needed?) Explains reason and goals for study Explains the limitations of the research performed Literature Review  Summarizes and evaluates the literature that you have used in your study by considering: How that literature has contributed to your area of research The strengths and weaknesses of previous studies How that literature informs your own research and understanding of the research problem You want your reader to fully understand the significance of your research

20. 20 보고서 항목별 주요내용 Report Format and Organization Methodology  Explains how data was gathered/generated  Explains how data was analyzed  Assumes reader understands material Does not include explanatory material  Is in past tense and passive voice The research has been carried out It is the research, and not your activities, that are of interest Results  Visually and textually represents research findings Visual representation of results: Graphs, tables, diagrams, charts Explanatory text: – Text points out the most significant portions of research findings – Indicates key trends or relationships – Highlights expected and/or unexpected findings

21. 21 보고서 항목별 주요내용 Report Format and Organization Discussion  Assesses and comments on research results  Includes: Explanation for Results : Comments on unexpected results, offering hypothesis for them Comparison to literature: Does your research confirm previous studies? Deviate from them? Explanation for how info can be applied in broader context Summary  Discusses: What was learned through research What remains to be learned Weaknesses and shortcomings of study Strengths of study Possible applications of study (how it can be used) Recommendations

22. 22 주요 tips Technical Writing : Useful tips  Keep report as short as possible  Organize for the convenience of the users  Write accurately, concisely & unobtrusively  Use appropriate diagram with right label at the right place  Provide summaries which will give the whole picture, in miniature  Include correct references  Check technical errors, typing errors & inconsistency

23. 23 Oral Presentation In many units in Engineering, you have to report work in oral presentations. You may have to present a proposal for a design, a progress report of an on-going investigation or the final outcomes of a project. When you are working in a group, the presentation will then be a group presentation where a number of the group members, if not all, present different aspects of the work. There are significant differences between a report of your work in an oral presentation and in a written report.  An oral presentation involves face-to-face, more informal spoken communication where you only have time to inform the audience of the key aspects of your work.  Do not take an oral presentation word for word from a written report! Purpose of an oral presentation  report key information about a technical project  use spoken delivery techniques and visual aids to enhance communication

24. 24 구두발표 (Oral Presentation) Elements of Preplanning (5Ws and 1H)  Who is my audience? Background, Expectation  What is my purpose? Message to Deliver  Where is all the equipment I need? Means to Communicate  When am I on the program agenda? Context  Why am I giving this talk? Importance  How long should I speak? Level of Details Verbal Elements (4S)  Short  Simple  Strength  Sincerity

25. 25 Oral Presentation Three Structural Parts  Introduction: purpose, what, etc.  Body: main content  Conclusion Visual Aids Rehearse your presentation Communicating Design/End Results to Client

26. 26 ECE 404 Scott Umbaugh, Textbook: Design for ECE Engineers, Ford & Coulsto n 26 Tips  Prepare – practice, practice, practice  Eye contact with entire audience  Avoid too much information  Meet time constraints  Look and act professionally  Use visuals effectively

27. 27 ECE 404 Scott Umbaugh, Textbook: Design for ECE Engineers, Ford & Coulsto n 27 Slides  Use a large font, 24 pt or more  Avoid more than 4 or 5 bullets per page  Avoid fancy graphics that add no value  Group slides for major points (top-down)  Avoid reading slides

28. 28 Your presentation should be 10 to 15 minutes for a project engineering team (5-10 min for a team of 2). Due to the limited class time you will be cutoff if you exceed the upper limit. Make sure you read Chapter 12 in the text, Evaluation:  Professionalism ‑ appearance, manner, visual aids  Clarity ‑ Can we understand what your design is about?  Organization ‑ Is your talk well ‑ organized? Does it follow a logical progression? Is it presented in a top-down manner?  Completeness ‑ Are all the parts there? Did you provide a good introduction? Clear, positive conclusions and/or summary? etc...  Communication ‑ Did you maintain eye contact with the entire audience? Did they understand you ? etc...  Time Limits ‑ Did you stay within the specified time limits?  Questions ‑ Were you successful at fielding questions after you presentation? Are you knowledgeable on the subject matter ?

29. 29 Good....................OK…....................Poor 4 3 2 1 0 Introduction ___ ___ ___ ___ ___ Clarity ___ ___ ___ ___ ___ Organization ___ ___ ___ ___ ___ Professionalism ___ ___ ___ ___ ___ Communication ___ ___ ___ ___ ___ Conclusion ___ ___ ___ ___ ___ Time limits ___ ___ ___ ___ ___ Completeness ___ ___ ___ ___ ___ Understanding ___ ___ ___ ___ ___ Questions ___ ___ ___ ___ ___ Oral_Pres_Papers.doc  Evaluation and Grade Sheet