Teamwork # 1 “Hubble repairs”. FALL 2020

MENG2110 – Teamwork # 1 “Hubble repairs”. FALL 2020. DUE before start of next lecture. Based on the presented case and videos (“Hubble repairs”), as a team, must produce a (about) fourto-five page (DO NOT USE TWO COLUMN TEXT) technical report on: Of the many design/engineering problems presented in the videos, choose one (it is NOT your design, but to report what NASA did) to do the following: 1. Understand the problem (may title it “problem description” in report) 2. Describe the plan/method to solve the problem (may title it “problem analysis/solution plan/method” in report) 3. Technically describe and discuss how the solution worked in the field (may title it “solution plan/method results” in report) 4. Look back: describe pros and cons (if any) of the used solution; propose, if possible, an alternative solution. Include any conclusion. HELP: Please, find following (as of today) links to "Hubble repair" lecture videos to start your research (note that there are MANY more videos and info available in the web, just Google it out ...) ; please, ALSO read instructions). General about http://www.youtube.com/watch?v=82ElIi5c0tY&feature=related or go to http://www.pbs.org and search "Hubble" https://www.youtube.com/watch?v=HuIJIVRgwdY NOTE: A technical report requires NEAT sketches and/or drawings to describe geometry, etc; copy and paste FIGURES is acceptable IF: Sketches/drawings must be reasonably according to the engineering standards. May use cut & paste photographs , but MUST ADD leader lines pointing to important features in them Drawings are numbered, have a title (“Figure 1. AND WHAT IS IN THE FIGURE …”), and should contain legends (leader-lines) indicating/pointing /describing the details/components. Then drawings are referred in text (as in “as shown in Figure …” ), and must be in the order of that reference. Text must be “elaborated” by the team; copy&paste text (or “verbatim” from videos) is NOT acceptable and will be consider plagiarism !! NOTE: a technical report is a clear, to-the-point, based on facts technical description of the problem and solution, and it is NOT a narrative concerning your experience (less about your “feelings”) ; style is referring to the problem/design, as in “It was found…”, “A solution was developed…”, etc. and it is ***NOT*** about the reporter (there is NO “… we … “ in technical reporting !!! ). NOTE: one report PER TEAM must be submitted. Email or Folio. Submitting multiple or repeated reports by a team WILL BE PENALIZED. Teams must coordinate actions ! REPORT MUST INCLUDE AS PART OF FILENAME : Team #_report#_and date, And clearly in first page TEAM “….” as given on first day of class, and each team member FULL name : as in ( , …, )