General Engineering Introduction/Documentation/quiz

{Engineers do not have to document anything. |type="()"} + False - True {Engineering documentation that requires verbal explaining should be minimized. |type="()"} - False + True {Engineering failure documentation includes tutorials. |type="()"} + False - True {Engineering success documentation creates tutorials. |type="()"} - False + True {Engineering documentation starts with writing in a notebook. |type="()"} - False + True {Presentations are based made by displaying source documents from a physical electronic location that everyone in the audience is familiar with |type="()"} - False + True {The crafts and trades started the documentation process that evolved into engineering. |type="()"} + False - True {The primary objective of engineering documentation is secrecy. |type="()"} + False - True {Engineering documentation's goal is to make management happy. |type="()"} + False - True {Replication involves documenting steps to failure. |type="()"} - False + True {Replication involves repeating expected symptoms, error messages, and failure modes. |type="()"} - False + True {Materials are not always the most expensive part of a project. |type="()"} - False + True {Documentation can seem expensive, but can save money when the entire project (physical testing, marketing, support, etc.) lifecycle is considered. |type="()"} - False + True {Hands-on experiences are becoming less expensive. |type="()"} + False - True {Best practice is a concept that captures mediocrity by describing what everyone is doing. |type="()"} - False + True {Best practice is what every engineer aspires to create |type="()"} + False - True {Engineers check other engineers work and then do what: |type="[]"} + physically stamp pieces of paper - consult with other engineers + add a digital signature - report the results to the board of engineers {Engineers work with other engineers on a project because: |type="[]"} - two engineers working together are more productive than working separately - two engineers can harmonize their thoughts, agree and check each other's work + multiple engineers can work through their differences to produce a better product - because they have different specialties + because there is so much work, engineers chop the team problem in to smaller, individual problem {The collective mind is a concept that |type="[]"} - assumes multiple engineers have the same thoughts - assumes that a group of people have more creative thoughts than a single engineer + is used as resource to improve a product + has issues, thoughts, opinions that need to be addressed whether they push the project forward or not {Engineering projects |type="[]"} - only have to be documented at the end of the project + are always documented because they are documented continuously {Engineering projects are mostly at what stage when documented? |type="[]"} - failure - working - some parts working - everything working - before testing + all stages {The target audience of engineering documentation includes |type="[]"} + engineers that might work on the project + engineers that want to check what has been done - engineers that want to build their expertise in a new area {Project management needs documentation to |type="[]"} + keep clients happy + to know what is going on + account for time and materials for future planning purposes + can see task evolution {Other engineers read engineering documentation when first hired |type="[]"} - keep clients happy + to see if they can push a project forward - make themselves look good to management - make themselves look good to other engineers - engineers like to solve problems {A portfolio is |type="[]"} - a list of your Facebook, linked-in and twitter id's - a list of all your work on engineering projects + links to all your engineering projects {Employers are beginning to ask for portfolio rather than a resume. Why? |type="()"} + engineers are beginning to expect electronic documentation - a resume has no links - a resume has to be scanned before a human resource algorithm search for key words {Most students are putting their engineering project documentation where? |type="[]"} - on a hard drive they own - on a thumb drive they can pass out rather than a resume - on a school created web site + on the internet cloud (google docs, drop box, amazon s3) and making public {Photos are to be uploaded to |type="[]"} + Wikimedia commons - wikiversity - wikibooks - Wikipedia {Video is to be uploaded to |type="[]"} + YouTube - canvas - vimeo - flicker - bittorrent {What is graded weekly? |type="[]"} + notebook + electronic documents + presentations + demonstrations {The notebook grade will be number based upon what? |type="[]"} - handwriting - English + format + transparency + goingtodo, doing, rant triplet number + drawings - saying positive things about your team mates documenting task assigned and task done