Vous êtes sur la page 1sur 8

Personal Details:

NAME:

UiTM ID:
IC NO :

PROGRAM:

COURSE CODE:

SEMESTER:

EMAIL ADDRESS:

NO. HP:

ADDRESS:

LECTURER/SUPERVISOR

HP NO.

LOG BOOK OWNERS SIGNATURE

ROOM NO.

DATE

Mechanical Design Project Log Book


The log book plays an important role in documenting and maintains a concise track record of all phases of the design
project. This activity is considered as one of the methods used to communicate between the different parties when
working on a project. Good documentation is a key of successful mechanical design project because it can be used as
a reference about project learning and results, hence log book is required. Remember that you must record everything
even the matter should be discussed with the project supervisor. Project supervisors should review and sign the log
book at regular intervals until the end of the semester. So please make sure;
Keep a detailed record for all phases of the project that have bearing on developments such as handouts, ideas,
calculations, drawings, experiments, and etc.
Include problems and possible or actually solutions plus calculations and tests have been carried out.
Any information such as drawings, graphs, handouts be dated and signed by the project supervisor and attached
to the log book.
If a change is made, not need to delete or cancel just draw a line through the original entry and clearly indicate
what the change is and why it was made.
Students must make sure that their logbooks are up-to-date because the supervisor will request to look at the log
book without any notice.
Make used the logbook as a design tool to record details of your ideas and keep a record of your successes and
problems. Enter everything in there, no matter how irrelevant you might think it is.
Finally, when the project is completed, each team member should submit their own log book to the supervisor along
with the final group project report.

PROJECT SCHEDULE
ACTIVITY

PERSON
INCHARGE

10

11

12

13

14

WEEKLY ACTIVITY LOG


Topic:

Reported by

Page No:

Date

Verified by:

Date:

EXAMPLE OF ACTIVITY LOG


The following examples were taken from Team 74 Overdrive from Bridgewater, New Jersey. They were the Amaze
Award winners at the 2007 FTC World Championship, as well as members of the winning alliance.

THE POSSIBLE RECORD IN LOG BOOK

Sketches/doodling
Customer needs/requirements
Class notes
Project objectives
Meeting notes
Action Items
Half-baked Ideas
Math calculations
Work-in-progress
Design alternatives
Vendor notes
Research findings
Sources of ideas
Evaluation of data/results
Design reviews
Decision criteria
Design process
Rationale for decisions
Project reflections
Professional development

The possible question you can ask and answer after


several project activities such as
Meeting
What were the main outcomes of the meeting?
Was the meeting productive, and why?
What are your personal action items before the next
meeting?

Is the team heading in the right direction?


Brainstorming
Which ideas seem more feasible, and why?
Are there enough good ideas?
How could better ideas be developed based on this
session?
Engineering Analysis
What were the governing equations?
What were the most important findings?
What do the results mean and how should they be
applied?
Visualization
What are the major features/discoveries and why are
these significant?
What was learned about the problem or solution
possibilities?
What problems were resolved and what still needs to be
addressed?
How does this piece integrate with the whole?
Searching
What key information did I find? How does it help achieve
the project objectives?
Are there other sources that should be pursued?
What new questions were generated?
Refer to www.engr.mun.ca/~sbruneau/teaching/.../logbookinstructions.pdf

Appendix 2.0