0 ratings0% found this document useful (0 votes) 48 views1 pageProj 16
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content,
claim it here.
Available Formats
Download as PDF or read online on Scribd
Se FEE EEO eEE CEL EEE CEP E EC EEE ECO EPEEEEEEEE Eee EEE Tree er err ere)
it? What resources were available for the project? Were they sufficient? Could you have
achieved more with more money? What was the original time-plan for the project, and was it
followed? If not, why not, and how would you do things differently next time? Is it cost-
effective? Has the project been worthwhile to you personally? What have you learned from
it? Has it changed your impression of what it means to be an electronic engineer / researcher?
One other golden rule while I remember it: it must be obvious what you did, and what ideas
you had yourself and didn't find on a web-page or from another reference. (This is another
difference between a project report and a technical report: in a technical report no-one would
care whose idea it was, or who did what.)
Another golden rule while I’m at it, true for both project reports and technical reports: you
should always include enough detail about any experiments performed that another researcher
could come along and repeat your results.
2.5 Resources on the Web
There are a lot of good introductions to technical report writing on the web; but bear in mind
that most of them are concemed with technical reports, not project reports (and the two are
slightly different). It's well worth reading a few of these to get an idea of the subject and issues
of technical writing.
For example, http://owl.english.purdue.edu/ has a lot of resources available. Any list I put here
will be out of date by the time you read this, so I suggest doing a web-search for technical
writing information, and having a browse.
2.6 Speeling and Grammatically Errors
‘These really irritate me. Perhaps I am a bit too pedantic in this area, but I regard them as a sign
of carelessness, and insufficient attention to detail. An engineer who is careless with details
isn't much use to anyone: just overlooking a single point in a new design can render the whole
product useless.
Fortunately, automatic spelling and grammar checkers have been getting much better over the
last year years, and can now spot most of the common problems. There is no excuse now for
confusing ‘its’ and ‘it’s? ir’, ‘there’ and ‘they're’. (Although you shouldn't be using
's’ or ‘th
“they're” in any case ~ see the section on style.)
Word’s spelling checker does a reasonable job, but I would recommend that Word users
download and add in the free version of Grammarly (https://www.grammarly.com/) to check
their grammar. This can pick up most of the common errors. Run this check frequently,
especially when you start writing, and you may find that it trains you to be a better writer,
which saves time later on. (As with all grammar checkers, you may not always agree with its
recommendations, but the important thing is to know why you disagree'”.)
" After having this report for nearly twenty years, when I first ran it through Grammarly’s checker it highlighted
214 basie issues. Some of these were deliberate errors, some were Grammarly pointing out that some quotes I
used were in American English, and some were pointing out that the grammar I was using was slightly old-
fashioned (usual practice ean change surprisingly fast, especially with things like the move from ‘proof read”
‘© 2002-22 University of York 16 Version 6
