<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>NIT1103 by Sunam Pradhan</title>
      <link>https://padlet.com/sunamp/ijinfiztgrpi</link>
      <description>Session 10</description>
      <language>en-us</language>
      <pubDate>2019-04-15 03:40:05 UTC</pubDate>
      <lastBuildDate>2019-04-15 05:31:12 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url></url>
      </image>
      <item>
         <title></title>
         <author></author>
         <link>https://padlet.com/sunamp/ijinfiztgrpi/wish/351562083</link>
         <description><![CDATA[<div>1. To help readers get an understanding of a technical topic.<br>2. To provide information regarding the technical aspects of the subject of the report.<br>3. Recommendations on correct usage, information about side-effects, safety information, or research conclusions.<br>4. Product manuals, feasibility reports, research papers or articles, and technical specifications reports.<br>5. <br>- Simple words instead of complex words.<br>- Effective layout of document<br>- Examples, illustrations,  graphs, licenses, and references<br>- Accurate, and objective<br>- Complete<br>Callan, Rob, Mevan, Norhan</div>]]></description>
         <enclosure url="" />
         <pubDate>2019-04-15 04:59:47 UTC</pubDate>
         <guid>https://padlet.com/sunamp/ijinfiztgrpi/wish/351562083</guid>
      </item>
      <item>
         <title></title>
         <author>nisargpatel2242000</author>
         <link>https://padlet.com/sunamp/ijinfiztgrpi/wish/351562115</link>
         <description><![CDATA[<div>1. Draw theory and real world situation together, Presenting Information in structured and accessible format.<br>2.Gives insight into the technical research topic.<br>3. Progress, process and result.<br>4.<br>5.  <br>-Understand the type of technical report you are writing<br>-Write down your specific aim<br>-Plan the sections and subsections you need.<br>-Write in plain English<br>-Avoid jargon</div><div><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2019-04-15 05:00:09 UTC</pubDate>
         <guid>https://padlet.com/sunamp/ijinfiztgrpi/wish/351562115</guid>
      </item>
      <item>
         <title>Hariesh, Kieran, Nancy</title>
         <author></author>
         <link>https://padlet.com/sunamp/ijinfiztgrpi/wish/351564877</link>
         <description><![CDATA[<div>1.  Provide information that is complex but to write it in a simple and informative way to assist the audience in understanding more about the subject. Basically, explaining how something works or how to complete something.<br><br>2.  Technical reports is a style of communication that conveys the importance of information which has been compiled and may have been heavily researched. It can be a professional way to present your topic to the target audience. <br><br>3.   It can contain an introduction to the subject, the planning, has to be drafted and well structured. There should be no plagiarism, has to be paraphrased. Should provide a clear and concise conclusion. <br><br>4. <a href="https://www.cibse.org/getmedia/c0758775-08ef-4cb9-9b8a-169074be5ee5/Technical-Report-1-CEng.pdf.aspx">https://www.cibse.org/getmedia/c0758775-08ef-4cb9-9b8a-169074be5ee5/Technical-Report-1-CEng.pdf.aspx</a><br><br>5.  Technical report should be drafted first to identify any possible corrections, make sure to always paraphrase from any document that may be used. Never plagiarise. Make sure the technical report is well structured and flows. Have an introduction, body paragraphs and conclusions. </div>]]></description>
         <enclosure url="" />
         <pubDate>2019-04-15 05:24:46 UTC</pubDate>
         <guid>https://padlet.com/sunamp/ijinfiztgrpi/wish/351564877</guid>
      </item>
      <item>
         <title>Stephen, Phoebe, Ahlaam &amp; Ahmad</title>
         <author></author>
         <link>https://padlet.com/sunamp/ijinfiztgrpi/wish/351564900</link>
         <description><![CDATA[<div>1. Main purpose of a technical report</div><div>A technical report describes the process, progress, or results of technical or scientific research or the state of a technical or scientific research problem.</div><div>To elaborate complex information to a specific targeted audience in a professional state that will assist them to understand the purpose of the technical report</div><div><br></div><div>2. Why are technical reports important? </div><div><br></div><div>A technical report is important as it is used to communicate technical information which assists in decision making.  </div><div><br></div><div>3. What are the components of a technical report?</div><ul><li>Title Page</li><li>Summary</li><li>Content page</li><li>Introduction</li><li>Body of the report</li><li>Conclusion</li><li>References</li><li>Bibliography</li><li>Acknowledgements</li><li>Appendices if necessary</li></ul><div><br></div><div>4. Examples</div><ul><li><a href="https://www.cibse.org/getmedia/c0758775-08ef-4cb9-9b8a-169074be5ee5/Technical-Report-1-CEng.pdf.aspx">https://www.cibse.org/getmedia/c0758775-08ef-4cb9-9b8a-169074be5ee5/Technical-Report-1-CEng.pdf.aspx</a></li><li><a href="https://www.cibse.org/getmedia/89e51a03-c7ee-487a-82e0-2617460c4c08/Technical-Report-2-CEng_Redacted.pdf.aspx">https://www.cibse.org/getmedia/89e51a03-c7ee-487a-82e0-2617460c4c08/Technical-Report-2-CEng_Redacted.pdf.aspx</a></li><li><a href="https://www.cibse.org/getmedia/d4b4225e-d216-47ba-a69f-6011a5efa765/Technical-Report-3-CEng_Redacted.pdf.aspx">https://www.cibse.org/getmedia/d4b4225e-d216-47ba-a69f-6011a5efa765/Technical-Report-3-CEng_Redacted.pdf.aspx</a></li></ul><div><br></div><div>5. 5 guidelines</div><div>What makes a good technical report is the <strong>clarity</strong> of the report, how clear the author has explained the topic and how comprehensible is it on the readers point of view.</div><div><strong>Objectivity </strong>is very important as the report must not come from a biased point of view but from a professional point.</div><div><strong>Accuracy </strong>is the probably the most important aspect of a technical report as the the information provided has to as  to be as accurate as possible to allow the audience to understand the given data is all correct and referenced.</div><div><strong>Structure </strong>majority of readers have a desired format, meaning the structure would be important for the readers needs.<br><strong>Discussion </strong> results of any data experiments should be given to the audience and not allow the audience to ‘predict’ what the outcome of specific data is</div><div><strong>Language </strong>should be understandable and legible, with no abbreviations or jargon that could obscure the message of the report. It should also be professional, with no slang terms or contractions.</div><div><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2019-04-15 05:25:05 UTC</pubDate>
         <guid>https://padlet.com/sunamp/ijinfiztgrpi/wish/351564900</guid>
      </item>
   </channel>
</rss>
