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

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


The Parts of a Proposal

• Title PageTitle Page• 0. Abstract0. Abstract• 1. Introduction and Motivation1. Introduction and Motivation• 2. Objectives2. Objectives• 3. Benefits3. Benefits• 4. Theory and Concept4. Theory and Concept• 5. Scope5. Scope• 6. Methodology6. Methodology• 7. Plan of Action7. Plan of Action• 8. References8. References• 9. Appendicies9. Appendicies


Title Page

• Project titleProject title– in Thai and Englishin Thai and English

• Your name, student number, e-mail addressYour name, student number, e-mail address

• Department (CoE), your degreeDepartment (CoE), your degreeFaculty of Engineering, PSUFaculty of Engineering, PSU

• Advisor (and co-advisor)Advisor (and co-advisor)– also called supervisor and co-supervisoralso called supervisor and co-supervisor

• DateDate


0. Abstract

• A summary/overviewA summary/overview• Never less than three sentencesNever less than three sentences

– about 200 wordsabout 200 words– sentence 1: sentence 1: backgroundbackground– sentence 2: the sentence 2: the problemproblem you are tackling you are tackling– sentence 3: planned sentence 3: planned goalsgoals/results/results


1. Introduction and Motivation

• Background to your problemBackground to your problem

• Explain what is already knownExplain what is already known– shows that your know the workshows that your know the work– do not just copy sentence 1 of the abstractdo not just copy sentence 1 of the abstract– 1-3 paragraphs1-3 paragraphs

Rationalealso called


• Thesis StatementThesis Statement– what is the problem you are working on?what is the problem you are working on?

– why are you solving this problem?why are you solving this problem?

– connect the problem back to what you just said in connect the problem back to what you just said in the background paragraphsthe background paragraphs

– do not just copy sentence 2 of the abstractdo not just copy sentence 2 of the abstract

Problem Statementalso called


2. Objectives

• Specify the goal(s) of your projectSpecify the goal(s) of your project– the end product(s), the result(s)the end product(s), the result(s)– one paragraph for each goalone paragraph for each goal

• Say how each goal fits into your thesis statement Say how each goal fits into your thesis statement from (1)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.


3. Benefits

• What is the potential impact of your work What is the potential impact of your work on:on:– future researchfuture research– future applications/software/productsfuture applications/software/products– the communitythe community

• e.g. other students, dept., faculty, uni., region, e.g. other students, dept., faculty, uni., region, country, worldcountry, world


4. Theory and Concept

• Overview work relevant to your problemOverview work relevant to your problem– describe articles, books, softwaredescribe articles, books, software– explain maths, equationsexplain maths, equations– one sub-section for each topicone sub-section for each topic

• Say how the work fits into your thesis Say how the work fits into your thesis statement (1) and objectives (2)statement (1) and objectives (2)

• Explain what's good/bad about the workExplain what's good/bad about the work

Literature Reviewalso called


5. Scope

• Summary of the extent, boundaries, and Summary of the extent, boundaries, and limitations of your worklimitations of your work– what can your work do / not do?what can your work do / not do?

• Hardware & software used/needed.Hardware & software used/needed.

• LimitationsLimitations– anything which limits the quality/quantity of your anything which limits the quality/quantity of your

workwork• e.g. lack of hardware/softwaree.g. lack of hardware/software


6. Methodology

• Explain the tasks that make up your workExplain the tasks that make up your work– write one sub-section for each taskwrite one sub-section for each task– explain tasks in the order that you plan to do explain tasks in the order that you plan to do

themthem

• 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 Planor Material and Methods

also called


• For each task, say what techniques/methods For each task, say what techniques/methods you will use.you will use.

• Provide implementation details:Provide implementation details:– e.g. software used, hardware used, apparatus, e.g. software used, hardware used, apparatus,

other materials (e.g. books), data sources, data other materials (e.g. books), data sources, data collection, testing done, analysis donecollection, testing done, analysis done


• Explain a task so next year (or afterwards), Explain a task so next year (or afterwards), another student can duplicate your work.another student can duplicate your work.

• Do not write a user manualDo not write a user manual– write for a future write for a future implementorimplementor


7. Plan of Action

• Use a Use a Gantt ChartGantt Chart to explain the plan. to explain the plan.• A picture showing task order/connectionA picture showing task order/connection

– gives dates gives dates

– shows how you plan to organize your tasksshows how you plan to organize your tasks– refer back to tasks in (6)refer back to tasks in (6)– may show sub-goals (2)may show sub-goals (2)

• I'll explain Gantt Charts later.I'll explain Gantt Charts later.


Example

• What does it look like?What does it look like?


8. References

• The references must list all your The references must list all your information sources information sources – articles, books, web sites, etc.articles, books, web sites, etc.– every reference must be every reference must be citedcited in your report in your report

Bibliographyalso called


• Must be up-to-dateMust be up-to-date• Must be relevant to your workMust be relevant to your work• Best types of references:Best types of references:

– First: books and journal articlesFirst: books and journal articles– Second: conference articlesSecond: conference articles– Third: technical reportsThird: technical reports– Four: web sitesFour: web sites

• Do Do notnot include: include:– newsgroup postings, forum postingsnewsgroup postings, forum postings– popular magazinespopular magazines

• e.g. no "PC Magazine"e.g. no "PC Magazine"


Citations and Reference Style • The The Harvard styleHarvard 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.


• For every reference, include the author’s For every reference, include the author’s surname, first name, its date, and its title. surname, first name, its date, and its title.

• Also:Also:• for an for an articlearticle: the title of the journal or conference : the title of the journal or conference

record in which the article was published, and the record in which the article was published, and the article’s page rangearticle’s page range

• for a for a bookbook: the name of the book’s publisher: the name of the book’s publisher• for a for a web siteweb site: the URL, and when last accessed: the URL, and when last accessed


Using a Citation

• A citation is not part of the sentence:A citation is not part of the sentence:– BAD: "I read (Downey BAD: "I read (Downey et al.et al. 2002)." 2002)."

– GOOD: "Downey's work on Python is very GOOD: "Downey's work on Python is very relevant to my project (Downey relevant to my project (Downey et al.et al. 2002)." 2002)."

• It's usually best to put a citation at the end It's usually best to put a citation at the end of a sentence.of a sentence.


• The citation goes The citation goes beforebefore the fullstop: the fullstop:

– "I used the QuickSort algorithm (Hoare 1962)"I used the QuickSort algorithm (Hoare 1962)..

• A paper with no citations is uselessA paper with no citations is useless– even if it has referenceseven if it has references

• When you write about a paper use the author's last When you write about a paper use the author's last name, not the paper title.name, not the paper title.


• Put "Put "et al.et al." in italics, and don't forget the "."" in italics, and don't forget the "."

• When writing about a paper, use the past When writing about a paper, use the past tense.tense.


Avoid Plagiarism

• PlagiarismPlagiarism means copying another person’s means copying another person’s work work andand not saying it is that person's work not saying it is that person's work– e.g. copy and paste from a book/Webe.g. copy and paste from a book/Web

• You must You must cite the sourcecite the source of anything that is of anything that is another person’s work:another person’s work:– text, ideas, code, data, diagrams, images, etc.text, ideas, code, data, diagrams, images, etc.


Appendicies

• Appendicies are often used for:Appendicies are often used for:– code listings, copies of papers, extracts from code listings, copies of papers, extracts from

Web pages, hardware data sheetsWeb pages, hardware data sheets

• OptionalOptional

• Each appendix should have a title, and Each appendix should have a title, and explanation of why it is included.explanation of why it is included.

Documents

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