Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
General sketch of the project format for the 25% Writing Grade:
Index
1. INTRODUCTION (One page obligatory with a short history description of your product/process of
interest, ending with the reason and form of improvement to it)
2.1 SPECIFIC OBJECTIVES (Three or more for a period of four months hypothetically)
3. RESEARCH AND DEVELOPMENT (What to write about and length will be uploaded on Moodle)
4. DESIGN AND TESTING (What to write about and length will be uploaded on Moodle)
5. MANUFACTURING AND INDUSTRY (What to write about and length will be uploaded on
Moodle)
6. SAFETY, MAINTENANCE AND QUALITY CONTROL (What to write about and length will be
uploaded on Moodle)
7. CAREERS AND EMPLOYMENT (What to write about and length will be uploaded on Moodle)
8. INNOVATION AND BUSINESS EVENTS (What to write about and length will be uploaded on
Moodle)
9. CONCLUSIONS and GLOSSARY (All the technical terms plus other several important words used
in your context; more than fifteen)
1
PROYECT ELABORATION FORMAT
English for Engineers level IV, University of Antioquia
2. General Objective.
Body of the Research. Several chapters describing what you have done, focusing on the novel aspects of your Comentado [A5]: REVIEW THE GUIDES IN THE MOODLE
PLATFORM TO HAVE AN IDEA ABOUT HOW WE WOULD WORK ON
own work. EACH CHAPTER.
9. Conclusions and Glossary Comentado [A6]: LIST HERE THE TECHNICAL WORDS AND
MEANINGS OF OTHER WORDS ACCORDING TO YOUR CONTEXT IN
THE PROJECT
10. Biblio/Webgraphy.1 Comentado [A8]: LIST HERE THE REVISED ARTICLES, BOOKS OR
WEB PAGES THAT SUPPORT YOUR PROJECT.
1
Note: these are models for citing different biblio/webgraphy sources:
a) Scientific Articles: Last name, Name’s initials (Year), Title, Journal name, Volumen, Edition number, pages.
Example: cited in a text: “Thimbleby's guidelines (1) suggest that…” then written in the Bibliography: 1.
Thimbleby, H.W. (1983), ``Guidelines for `manipulative' text editing'', Behaviour and Information Technology, 2
ed., pg.127 – 161.
b) Books: Last name, Name’s initials (Year), Title, City, Editorial.
2
PROYECT ELABORATION FORMAT
English for Engineers level IV, University of Antioquia
1. Transfer your own experiences of doing the project, and the knowledge you will gain, from your brain
onto paper in a coherent, logical and correct form.
2. Remember that your project is an academic dissertation, not a popular article or commercial proposal.
For example, rather than describing only a series of events and a final product, try to establish criteria, present
arguments, derive principles, pose and answer questions, measure success, analyse alternatives and so on.
3. Strive to be absolutely precise. What you write must not be misinterpreted. Take exceptional care to
choose the right word for the occasion. Do not, for example, write ``optimum'' if you mean ``good'', and so on.
4. Do not make claims that you cannot support. Your project should clearly separate specification, design,
implementation and testing. For instance: ``the program is wanted to do X; it is designed to do nearly-X; it is
implemented to do most-of-X; the testing showed that it did some-of-X (and here is the evidence of that)''
instead of “The product does ...”
5. Consider illustrations to be next to the text, so they can aid the reader to understand it better. Preferably,
make the text clearer than to add a figure or diagram.
6. Avoid circumlocutions. Prefer short sentences to long sentences, and short words to long words. Avoid
Latin phrases - these are only acceptable if they abbreviate a circumlocutionary English phrase, for example:
“Mutatis mutandis” is permissible in place of ``making the appropriate changes.''
7. Avoid slovenly structure. Take your time; rearrange words or phrases within sentences, sentences within
paragraphs, paragraphs within sections and sections within the whole project until you have got it right. Aim for
a logical progression from beginning to end, with each sentence building on the previous ones.
8. Avoid writing ``... as we shall see in chapter X ...’’ Always write the most important things in the first
sections before its further development.
9. Footnotes are not acceptable - unless they are used for putting a note or an editing observation for a word
or phrase in the text.
12. ".": the point is before the ending quotation marks if ending a sentence.
c) Web pages: Last name, Name’s initials, Title of the article, Institution name, [Online]: http://xxx.xx.x , Date of
consultation.
d) Online e-books: Last name, Name’s initials, recovered from http://xxx.xx.x
e) Document in electronic format: Last name, Name’s initials, Title, doi: xx.xxxx
f) Thesis: Last name, Name’s initials (year), Title. [Unedited Magister or Doctorate thesis]. Name of the institution,
localization.
3
PROYECT ELABORATION FORMAT
English for Engineers level IV, University of Antioquia
13. e.g.: usually put this before a series of examples or for clarifying a previous idea. Use “For Instance” or
“For example” in replacement.
14. i.e.: it is used more often to widen an idea and also for clarifying a previous one. It means ``in other
words'' or ``that is''.
15. et al.: this means “and others”. This is the animated form of “etc.” and it is used for citations of more
than five authors.
16. do not: the apostrophe or abbreviation (’) (don’t) should not be used in formal writing for personal
pronouns.
Why – How – When – Where? For your R&D project or product idea.
c. Implement the Necessity Vision for the improvement of your engineering area of interest:
- Changing an old product.
- Innovating.
- Optimizing.
- Reducing Costs.
2
Note: The goal is to find a further limitation feasible enough to get a real and specific demonstration of the modification,
improvement or change of the product and/or process that you want to impact on at the end of the project but that could
require a little bit more time to reach. Try to think as if it were a thesis focused to the industry, achievable in a short period
of time. If that is not the case for you, be sure that what you want to do or invent is realistic. Again, take into account the
needs of your area of interest.
4
PROYECT ELABORATION FORMAT
English for Engineers level IV, University of Antioquia
1 2 3 4 5 6 7 8 9 10
Presentation
Without merit All merit
-Lots of errors -No errors
-Rough draft -Elegant draft
-Hard to read -Easy to read
Title, Objectives, Table of Contents,
Introduction
-Vague -Succinct
-Uninformative -Informative
Problem analysis (e.g. investigation,
requirements, theory)
-Careless -Thorough
-Superficial -Insightful
Design and Implementation (e.g. artefact,
experiment, study)
-Unspecified -Well specified
-Bad-executed -Well-executed
-No Solution -Solution