2500 word literature review in 8 hours

School of Engineering: T2-2015 (SEN719-Engineering Project 1)

Engineering Project 1 (SEN719)

Assignment 1 – Project Proposal

(40% of Total Marks)

Due:

Friday 21 August 2015,

5.00pm (Melbourne Time)

Via CloudDeakin

Pre-submission Checklist

□ Completion of task □ ONE file submission ONLY (word or pdf) □ Via CloudDeakin (Dropbox) ONLY □ Individual submission □ Scanned copy of project registration must be attached □ WBS and Gantt chart is attached □ Meeting schedule with project supervisor/s is attached

Note: Students are strongly advised to read all information in all sections and also to refer Marking Criteria (Assessment Rubric) included in this document in Appendix 3.

Page 1 of 7

School of Engineering: T2-2015 (SEN719-Engineering Project 1)

1.0 Introduction The aim of this assignment is to provide you an opportunity to learn how to conduct a literature re- view (critically) in an area of your chosen project. This project proposal is a report that defines the initial aims, scope and resource requirements for the project and students will need to demonstrate a clear understanding of key literature that supports the need for the project, as well as detailing the specific aims and scope to be addressed. You should consult with your supervisors or/and industry advisers in order to design realistic project tasks and experiments. You are strongly suggested to dis- cuss your literature review with your project supervisor/s.

2.0 Learning Outcomes This assignment has been devised to allow students to demonstrate progress towards achieving the following unit learning outcomes:

ULO1 – Critically conduct a literature review in an area related to the project topic

ULO3 – Formulate a detailed project proposal that contains background information based on the literature review, methodology to be used to carry out the project, and the proposed timeline.

Students are encouraged to review all other learning outcomes to discover additional learn- ing opportunities which will increase the quality of their submission and final results.

3.0 Task You have by now finalised and registered your engineering project, either with academic supervisor or industry supervisor (in some cases joint supervision by academic staff and industry person). Your pro- ject problem is from a range of topics and disciplines and you will be working on this problem in order to identify potential solutions and determine the ‘optimum’ solution by applying principles of project management to the client. After you have finalised and registered your engineering project, you are to develop a “Project Pro- posal or Scope Document” that clearly defines the project problem and requirements. The scope doc- ument must be prepared in consultation with your project supervisor. This will include project objec- tives and expected outcomes. This submission is about your Project Proposal but more emphasis is on a critical literature review in the area related to your project. You are required to independently write a project proposal in consul- tation with your supervisor for specific requirements. You are advised to refer the "Project Plan" tem- plate available in unit CloudDeakin Website and your proposal document should complete most sec- tions of the "Project Plan" template. You can make adjustments to this template needed for your pro- ject. You submission should include evidence of substantial relevant literature search to gain an under- standing of problem and methods associated with your project which will also be included in the Scope document. The detail project methodology identifying potential ‘optimum’ solution/s by ap- plying principles of Project Management must also be included. In addition, the Project Plan/Scope Document must demonstrates effective project management techniques e.g. MS Project, meeting documentation, Gantt chart, project documentation workbook, etc.

Page 2 of 7

School of Engineering: T2-2015 (SEN719-Engineering Project 1)

4.0 Submission Requirements

The following are submission requirements for all student teams. • There is no specific length required for this report, as each project is different. However, 2000-

3000 words are highly recommended (excluding appendices). But there is not a strict rule on the length of your submission as long as your proposal has all essential inclusions. Consult your su- pervisor for additional and specific requirements.

• You must include all necessary components of Project Proposal (Plan) as outline in the project plan template (available in CloudDeakin Unit Website). You should also include required appen- dices (see details below).

• You should focus on "Quality Plan" and include Occupational Health and Safety (OH&S). • Appendices: All attachments should be included in appendices. These are:

o The project registration form signed by you and you supervisor (compulsory). o The work breakdown structure (WBS) and Gantt chart. Convert your Gantt chart in ei-

ther word or pdf format, if needed (compulsory). o Detail meeting schedule with your project supervisor/s for the remaining of trimester

(compulsory). o If you have any special requirements (say project expenditure, technical support, etc.)

then you can also include in the Appendix (Optional). • A written report is to be prepared using an appropriate academic writing style and to include a

list of references. Refer to Deakin’s Guide to Assignment Writing and Referencing, available online from Student Life, for appropriate report styles and referencing.

• Read the Assessment Criteria for guidance on how this assignment will be marked. Make sure that any analysis you present is your own – not simply a summary of what is presented in source or reference materials. Your submission is a Proposed Project Plan (and not a full Project Report).

• The submitted report file format must be MS Word or pdf (.doc/.docx/.pdf). • Don’t waste time with fancy layouts, colours, cover pages, and so on. A simple text-based format

is all that is needed with the report layout consisting of a few sections of text (with section head- ings). Use photos or diagrams sparingly and only if necessary and/or relevant to include in your report. Just use a basic and common text font such as Arial or Times New Roman with at least 10 point font size for body text. Single-space paragraphs are acceptable.

• There must be a Reference Section (Bibliography) in your submission. Marks will be deducted if it is omitted, not suitably formatted, or lacking more than at least six relevant citations. Use a suitable referencing style such as the IEEE or Harvard Style or similar. (IEEE is preferred)

• Don’t be tempted to plagiarise. If you unsure what constitutes plagiarism, cheating, or collusion then refer to the Academic Honesty information provided for all units on DSO in the Unit Guide and Information folder.

• Online and in-person resources and materials are available from Student Life for all students to assist with assignment writing and referencing skills. Student Life also provides online and in-per- son resources to assist with understanding plagiarism and how to avoid producing it in your aca- demic work.

5.0 Submission Deadline

Students are to upload their Assignment Submission on CloudDeakin under the Assign- ment 1 Dropbox link by Friday 21 August 2015, 5pm (Melbourne Time).

Page 3 of 7

School of Engineering: T2-2015 (SEN719-Engineering Project 1)

Appendix 1 (compulsory)

Project Registration Form and Specification Guideline

Student Name

ID Number

Proposed Supervisor(s)

Project Title

Project Aims & Objectives

Outside organisation involved (if any) and main contact

Special University resources required (equipment, technician support etc. Please attach tech- nician support/requisition form if applicable )

Deliverables (artefact, research, strategy, output etc)

What is distinctive/honours worthy about the proposed project?

Student Signature with Date Supervisor Signature with Date

Page 4 of 7

School of Engineering: T2-2015 (SEN719-Engineering Project 1)

Appendix 2 (Optional) Technician Support/Requisition Form

Student Name: ID: Paper Code:

Requisition Date Student Project Requisition Form Requisition

Number ddmmyy/xx

Item Number Item Description (include brand, part number etc)

Qty Est. Cost (each)

Date req’d Account Number Supplier Information (include name, address, contact name etc)

1

2

3

4

Total Technician Support Requirements

Job Number

Job Description

Qty

Est. Hours

Date req’d

Account Number

W/shop or Lab requirements

1

2

3

4

Academic Supervisor signoff Name: Signature:

Senior Technician signoff Name: Signature:

Account Codes:

Page 5 of 7

School of Engineering: T2-2015 (SEN719-Engineering Project 1)

Appendix 3

Marking Rubric Criteria HD

80 or more D

70 or more C

60 or more P

50 or more N

49 or less

Find and collect data us- ing available literature and internal enquiry for information

10 points

Shows evidences of wide lit- erature survey, relevant, in- sightful and critical reading. Use highly relevant and h i g h l y reliable information sources to collect data and for addressing project is- sues.

8 points

Shows evidences of critical reading, and major sources are included. Use relevant and reliable infor- mation sources to collect data for addressing the questions specified in the project.

6 points

Show evidences of litera- ture survey and reading but does not always main- tain a critical and evalua- tive attitude towards it. Use relevant information sources to collect data for addressing project issues.

5 points

Shows some evidences of critical reading, but in general uncritically ac- cepts what sources say. Use less reliable infor- mation sources to collect data required for ad- dressing project issues.

4 points

The author(s) has done a minimal amount of background reading, usually of an uncritical nature. Unreliable data sources used.

Evaluate, analyse and credible use of data and information to achieve a clear understanding of the project topics and to address project issues.

30 points

Provides a VERY clear and accurate description and ex- planation of the issues spec- ified in the project. Show evidences of critical analysis of information and appropri- ate use of various sources of data, including previous re- search in the field by others, to address project issues.

24 points Provides a mostly accurate description and explana- tion of the issues specified in the project. Evidence of rational of the study, criti- cal analysis of infor- mation. Reasonable use of data and information to address project issues.

18 points

Provides an acceptable level of description and explanation of the issues specified in the project. Evidence of rational of the study with some refer- ences, analysis of infor- mation.

15 points Provides a low level of description and under- standing of the issues specified in the pro- ject. Some evidence of rational of the study with some references, analysis of information.

14 points Provides an inaccu- rate description and understanding of the issues specified in the project. Insufficient analysis of refer- ences, analysis of in- formation.

Page 6 of 7

School of Engineering: T2-2015 (SEN719-Engineering Project 1)

Demonstrate knowledge of engineer- ing project manage- ment issues such as: the constraints of project management; the pro- ject management knowledge areas and process groups; the pro- ject life cycle, all as re- lated to engineering

20 points

Outstanding demonstration of covering all relevant pro- ject management knowledge areas. A critical approach to project man- agement and other evi- dence used. Excellent un- derpinning of the argument, well linked to the PM and required tasks.

14 points Very well demonstration of covering of most rele- vant project management knowledge areas. Argu- ments well put together and well linked to the PM and other tasks.

8 points

Well demonstration of covering of some relevant project management knowledge areas. Few un- substantiated arguments put together and some- what linked to the PM and other tasks.

5 points

Generally appropriate evidence of covering of relevant project manage- ment knowledge areas.

4 points

Very minimal or no evi- dence of covering of rel- evant project manage- ment knowledge areas.

Information Literacy and Referencing

20 points Highly reliable information sources have been used and cited in all instances using a proper referencing style.

18 points Reliable information sources have been used in most cases and all have been cited using a proper referencing style.

16 points Reliable information sources generally used and have been cited or referenced.

10 points Not all information used from reliable sources and an attempt was made at referencing.

14 points References are not done.

Report Presentation, Format and Appendices ( Overall format/presen- tation/structure, gram- mar, etc.)

20 points

Exceptionally high standard report. All essential attach- ments are included in Ap- pendices.

16 points Very good standard of re- port. Most attachments are included in Appen- dices.

12 points

Good standard. Few at- tachments are included in Appendices.

10 points

Acceptable standard of report. Only minimal at- tachments are included in Appendices.

9 points

Not-acceptable or non- satisfactory report with no attachments in- cluded in Appendices.

Overall Score HD 80 or more

D 70 or more

C 60 or more

P 50 or more

N 49 or less

Page 7 of 7