This preview shows page 1. Sign up to view the full content.
Unformatted text preview: APS111 and APS113 – Fall 2011 Engineering Notebook Instructions In Introduction to Professional Engineering in Canada, the authors state that “Engineering design logbooks should be kept for even the most basic design project.” But design logbooks are not restricted to projects, as course notebooks are for courses. “Get in the habit of keeping a logbook with you,” they write, “because you never know when you will get an inspiration for a design project, or when a design idea may prove to be the seed of an innovation.” Your engineering notebook is where you will keep track of your work as you progress through the design process. This should include plans considered but not pursued, analytical calculations, records of experimental data, information found, and any other “significant thinking” you did while working on the project. It is the chronological documentation of your work. Notebooks of this type are used in many companies and the rules will be different in each industry. The rules we have set out here are typical of the best practices found in industry. When you work for a company, your notebook belongs to the company and they keep it when you leave your job. However, in this course the notebook belongs to you and you can keep it after the completion of the course. What to Purchase The notebook must be a standard bound lab notebook such as a black or blue physics or chemistry lab book (http://bit.ly/p6HD4a). The size, color, and/or page format (ruled or quad) does not matter. A loose‐leaf binder or spiral bound notebook is not acceptable. Rules • You must put the date next to each new entry. It should be clear when each item was entered into your notebook. Never change or alter the date of an entry. • Never erase or white‐out entries; cross out with a single line if you want to “delete” something. • Include descriptive titles before each entry. This helps organization and allows you to retrieve ideas quicker when writing reports. • Never remove pages from your notebook. This is a legal document; missing pages could imply an attempt to hide facts or could be a result of stolen information. • The entries in your notebook should be written in ink. • Do not leave blank pages between entries. • Your notebook must be brought to all tutorials, team meetings, and client meetings. Layout • Make sure your entries are legible, clear and understandable. Anyone should be able to it read and understand the entries. 35 APS111 and APS113 – Fall 2011 • When attaching documents, such as agendas, into your notebook make sure you avoid covering any writing below. Tape or staple documents over blank pages, or keep a separate binder of print‐outs, date the pages in the binder and refer to them in the notebook, e.g. “see project binder for agenda of the February 23 team meeting.” If you tape or staple the material into your notebook then sign across the boundary between the affixed page and the notebook page. Content • Contact information for each team member as well as the team rules must be well documented and easily found within the notebook. • Minutes, task delegations, and comments must be noted after each meeting. Notes during group discussions must also be included with appropriate headings. • All ideas generated during brainstorming. • Important information you find and all sources researched must be recorded. This includes bibliographical details such web links, book names, page numbers, and dates of publication. • Diagrams, schematics, sketches, flow charts, product prices, and other details must be entered or attached. • Notes in preparation for writing documents such as draft outlines. • Tasks you perform and the results of team activities and decisions. • Your own working notes on your project. • Insights you have and ideas you develop. • Reflections on what you have learned (figured out). • Organization of your thoughts and tracking of your project status. • Documentation of the searches you have run and keywords used. • If you include printouts from the internet or other sources they should be annotated to indicate; date printed, how it was found (search words used, or link), what on the page is of interest and why (briefly). Printouts can be kept in a binder separate from your notebook, but have a system (by date, or number pages) of filing them so you can reference the information in your notebook. A well‐documented project will help to keep you on schedule, moving forward, and working effectively. It will keep you from re‐treading over ideas already discarded, decisions already made, and searches already done. When preparing your notebook ask yourself: •
• Could someone else quickly pick up the project where you left off by reading your notebook if you were suddenly called away to work on another project? If you had to put this project aside for a year and then pick it up again, could you quickly get back up to speed by reading your notebook? 36 APS111 and APS113 – Fall 2011 Marking In ESP I 3% of your final course grade is determined by notebook checks conducted in tutorial by your TA on the days indicated in the course schedule. Your notebook will be evaluated using the rubric below. In ESP II your engineering notebook will be one source of information for your Portfolio. The portfolio is worth a significant portion of your ESP II final mark. Engineering Notebook Evaluation Rubric Criteria Yes No Dated Correctly? Mistakes crossed out rather than whited‐out Descriptive titles? All pages intact? (i.e. no torn out pages) Written in ink? Handwriting legible? Pages attached without covering other content? Content exclusive to project? (i.e. no non‐esp material) Start at 1.5. Subtract 0.5 for each “No”. / 1.5 Team members names and contact information? Team rules? CI name and contact information? Meeting notes? (i.e. minutes, task delegation, meeting times, etc.) Research notes? (i.e. source, keywords, findings, etc.) Other notes? (i.e. ideas, reflections, insights, etc.) Ideas worked out graphically in sketches, diagrams Start at 1.5. Subtract 0.5 for each “No”. /1.5 Total /3.0 37 ...
View Full Document
- Fall '09