Presentation is loading. Please wait.

Presentation is loading. Please wait.

242-702. Seminar II: Parts/1 1 Seminar II Objectives – –briefly explain the parts of a proposal as required by the Faculty of Engineering 242-702, Semester.

Similar presentations


Presentation on theme: "242-702. Seminar II: Parts/1 1 Seminar II Objectives – –briefly explain the parts of a proposal as required by the Faculty of Engineering 242-702, Semester."— Presentation transcript:

1 242-702. Seminar II: Parts/1 1 Seminar II Objectives – –briefly explain the parts of a proposal as required by the Faculty of Engineering 242-702, Semester 2, 2014-2015 1. The Parts of a Proposal

2 242-702. Seminar II: Parts/1 2 The Parts of a Proposal Title Page Title Page 0. Abstract 0. Abstract 1. Introduction and Motivation 1. Introduction and Motivation 2. Objectives 2. Objectives 3. Benefits 3. Benefits 4. Theory and Concept 4. Theory and Concept 5. Scope 5. Scope 6. Methodology 6. Methodology 7. Plan of Action 7. Plan of Action 8. References 8. References 9. Appendicies 9. Appendicies

3 242-702. Seminar II: Parts/1 3 Title Page Project title Project title –in Thai and English Your name, student number, e-mail address Your name, student number, e-mail address Department (CoE), your degree Faculty of Engineering, PSU Department (CoE), your degree Faculty of Engineering, PSU Advisor (and co-advisor) Advisor (and co-advisor) –also called supervisor and co-supervisor Date Date

4 242-702. Seminar II: Parts/1 4 0. Abstract A summary/overview A summary/overview Never less than three sentences Never less than three sentences –about 200 words –sentence 1: background –sentence 2: the problem you are tackling –sentence 3: planned goals/results

5 242-702. Seminar II: Parts/1 5 1. Introduction and Motivation Background to your problem Background to your problem Explain what is already known Explain what is already known –shows that your know the work –do not just copy sentence 1 of the abstract –1-3 paragraphs Rationale also called

6 242-702. Seminar II: Parts/1 6 Thesis Statement Thesis Statement –what is the problem you are working on? –why are you solving this problem? –connect the problem back to what you just said in the background paragraphs –do not just copy sentence 2 of the abstract Problem Statement also called

7 242-702. Seminar II: Parts/1 7 2. Objectives Specify the goal(s) of your project Specify the goal(s) of your project –the end product(s), the result(s) –one paragraph for each goal Say how each goal fits into your thesis statement from (1) Say how each goal fits into your thesis statement from (1) Say how you will measure the success of each goal. Say how you will measure the success of each goal. Do not just copy sentence 3 of the abstract. Do not just copy sentence 3 of the abstract.

8 242-702. Seminar II: Parts/1 8 3. Benefits What is the potential impact of your work on: What is the potential impact of your work on: –future research –future applications/software/products –the community e.g. other students, dept., faculty, uni., region, country, world e.g. other students, dept., faculty, uni., region, country, world

9 242-702. Seminar II: Parts/1 9 4. Theory and Concept Overview work relevant to your problem Overview work relevant to your problem –describe articles, books, software –explain maths, equations –one sub-section for each topic Say how the work fits into your thesis statement (1) and objectives (2) Say how the work fits into your thesis statement (1) and objectives (2) Explain what's good/bad about the work Explain what's good/bad about the work Literature Review also called

10 242-702. Seminar II: Parts/1 10 5. Scope Summary of the extent, boundaries, and limitations of your work Summary of the extent, boundaries, and limitations of your work –what can your work do / not do? Hardware & software used/needed. Hardware & software used/needed. Limitations Limitations –anything which limits the quality/quantity of your work e.g. lack of hardware/software e.g. lack of hardware/software

11 242-702. Seminar II: Parts/1 11 6. Methodology Explain the tasks that make up your work Explain the tasks that make up your work –write one sub-section for each task –explain tasks in the order that you plan to do them Link each task to your problem (1) Link each task to your problem (1) Link each task to your objectives (2) Link each task to your objectives (2) Research Plan or Material and Methods also called

12 242-702. Seminar II: Parts/1 12 For each task, say what techniques/methods you will use. For each task, say what techniques/methods you will use. Provide implementation details: Provide implementation details: –e.g. software used, hardware used, apparatus, other materials (e.g. books), data sources, data collection, testing done, analysis done

13 242-702. Seminar II: Parts/1 13 Explain a task so next year (or afterwards), another student can duplicate your work. Explain a task so next year (or afterwards), another student can duplicate your work. Do not write a user manual Do not write a user manual –write for a future implementor

14 242-702. Seminar II: Parts/1 14 7. Plan of Action Use a Gantt Chart to explain the plan. Use a Gantt Chart to explain the plan. A picture showing task order/connection A picture showing task order/connection –gives dates –shows how you plan to organize your tasks –refer back to tasks in (6) –may show sub-goals (2) I'll explain Gantt Charts later. I'll explain Gantt Charts later.

15 242-702. Seminar II: Parts/1 15 Example What does it look like? What does it look like?

16 242-702. Seminar II: Parts/1 16 8. References The references must list all your information sources The references must list all your information sources –articles, books, web sites, etc. –every reference must be cited in your report Bibliography also called

17 242-702. Seminar II: Parts/1 17 Must be up-to-date Must be up-to-date Must be relevant to your work Must be relevant to your work Best types of references: Best types of references: –First: books and journal articles –Second: conference articles –Third: technical reports –Four: web sites Do not include: Do not include: –newsgroup postings, forum postings –popular magazines e.g. no "PC Magazine" e.g. no "PC Magazine"

18 242-702. Seminar II: Parts/1 18 Citations and Reference Style The Harvard style: The Harvard style: Downey, A., Elkner, J., Meyers, C. (2002) How to Think Like a Computer Scientist – Learning with Python, Green Tea Press. Hoare, C.A.R. (1962) Quicksort, Computer Journal 5, pp. 10–15. Martelli, A. (2006) Python in a Nutshell, O’Reilly. Wikipedia (2007) Quicksort, en.wikipedia.org/wiki/Quicksort.. last accessed May 26, 2009 references citations in the proposal The quick-sort algorithm was invented by Hoare (1962); see also Wikipedia (2007). Python (Downey et al. 2002, Martelli 2006) is a highly dynamic language, suitable for object-oriented and functional programming.

19 242-702. Seminar II: Parts/1 19 For every reference, include the author’s surname, first name, its date, and its title. For every reference, include the author’s surname, first name, its date, and its title. Also: Also: for an article: the title of the journal or conference record in which the article was published, and the article’s page range for an article: the title of the journal or conference record in which the article was published, and the article’s page range for a book: the name of the book’s publisher for a book: the name of the book’s publisher for a web site: the URL, and when last accessed for a web site: the URL, and when last accessed

20 242-702. Seminar II: Parts/1 20 Using a Citation A citation is not part of the sentence: A citation is not part of the sentence: –BAD: "I read (Downey et al. 2002)." –GOOD: "Downey's work on Python is very relevant to my project (Downey et al. 2002)." It's usually best to put a citation at the end of a sentence. It's usually best to put a citation at the end of a sentence.

21 242-702. Seminar II: Parts/1 21 The citation goes before the fullstop: The citation goes before the fullstop: –"I used the QuickSort algorithm (Hoare 1962). A paper with no citations is useless A paper with no citations is useless –even if it has references When you write about a paper use the author's last name, not the paper title. When you write about a paper use the author's last name, not the paper title.

22 242-702. Seminar II: Parts/1 22 Put "et al." in italics, and don't forget the "." Put "et al." in italics, and don't forget the "." When writing about a paper, use the past tense. When writing about a paper, use the past tense.

23 242-702. Seminar II: Parts/1 23 Avoid Plagiarism Plagiarism means copying another person’s work and not saying it is that person's work Plagiarism means copying another person’s work and not saying it is that person's work –e.g. copy and paste from a book/Web You must cite the source of anything that is another person’s work: You must cite the source of anything that is another person’s work: –text, ideas, code, data, diagrams, images, etc.

24 242-702. Seminar II: Parts/1 24 Appendicies Appendicies are often used for: Appendicies are often used for: –code listings, copies of papers, extracts from Web pages, hardware data sheets Optional Optional Each appendix should have a title, and explanation of why it is included. Each appendix should have a title, and explanation of why it is included.


Download ppt "242-702. Seminar II: Parts/1 1 Seminar II Objectives – –briefly explain the parts of a proposal as required by the Faculty of Engineering 242-702, Semester."

Similar presentations


Ads by Google