Sie sind auf Seite 1von 11

ENS1154 Introduction to Engineering Unit Plan Semester 1 2013

Welcome to Introduction to Engineering, ENS1154. This unit covers a wide range of introductory topics to engineering which will introduce you to the discipline and practice of professional engineering. Engineering is a very broad and continuously evolving profession that is satisfying and enjoyable to learn and to practice. DESCRIPTION This unit introduces students to the discipline and practice of professional engineering. The role of engineers and some of the important concepts that characterise the engineering approach to solving technical problems are described. In addition, the importance of appropriate communication, teamwork and the management aspects of engineering are introduced. The unit includes a group design project that takes the student through the engineering design process from client specification, around an iterative design loop, to a fully documented final solution.

LEARNING OUTCOMES On completion of this unit, students will be able to: 1. identify the roles and responsibilities of a practicing engineer; 2. identify the stages in a design cycle and prepare a design strategy that incorporates the components of this cycle; 3. describe the importance of ethics, safety and sustainability in engineering design, and embed these issues into their design processes; 4. demonstrate the oral and written communication skills that are critical in relationships between engineers and clients, where clients may include the general public. 5. work in a team to plan and carry out a project. UNIT CONTENT 1. Generic attributes of an engineering graduate. 2. Systems engineering a systematic approach to the description, analysis and design of complex systems; design cycle specifications, functional description, synthesis and evaluation; simulation and prototypes; problem solving skills and tools. 3. Responsibilities of an engineer - ethics, safety in design, sustainable design. 4. Communications preparing engineering documents: technical reports, manuals, procedures and proposals; project presentation. 5. Engineering management - fundamentals of project management, engineering economics, risk management. 6. Design Projects - teamwork and the engineering design process. TEACHING AND LEARNING PROCESSES Students attend one two hour lecture and one three hour tutorial session each week. Lectures are used to introduce main concepts and to guide students through important points. Tutorials are used to assist students in the application of concepts presented in lectures through exercises, using software tools and class discussions. Assignments provide students with the opportunity to develop selected theories of the unit through research, critique and application of concepts.

GRADUATE ATTRIBUTES The following graduate attributes will be developed in this unit Ability to communicate Ability to work in teams Critical appraisal skills Ability to generate ideas Cross-cultural and international outlook ASSESSMENT Item Project Project Exercise Assignment Assessment Major group design project Group practical project Tutorial exercises and online activities Portfolio of work done and skills demonstrated Value 50% 10% 20% 20%

TEXTS Dowling, D., Carew, A., and Hadgraft, R. (2012). Engineering your future: an Australasian guide. (2nd ed). Milton, Qld.: John Wiley. Beer, D. F. & McMurrey, D. A. (2010). A guide to writing as an engineer (3rd ed.). New York: John Wiley. SIGNIFICANT REFERENCES Horenstein, M. N. (2010). Design concepts for engineers. (4th ed.). New Jersey: Prentice-Hall. Dym, C. L., & Little, P. (2008). Engineering design: a project-based introduction. (3rd ed.). New York: John Wiley. Holtzapple, M. T. , & Reece, W. D. (2008). Concepts in engineering. (2nd ed.) New York: McGraw-Hill. JOURNALS AND OTHER PUBLICATIONS IEEE Spectrum

REFERENCING ECU adopts the APA (American Psychological Association) Referencing system ECU Referencing Guide available at the ECU Bookshop or downloaded free at: http://www.ecu.edu.au/CLT/pdf/refguide.pdf American Psychological Association (APA) provides free tutorials at: http://www.apastyle.org/learn/tutorials/basics-tutorial.aspx

ACADEMIC MISCONDUCT Edith Cowan University has firm rules governing academic misconduct and there are substantial penalties that can be applied to students who are found in breach of these rules. Academic misconduct includes, but is not limited to: plagiarism unauthorised collaboration; cheating in examinations; theft of other students work

Additionally, any material submitted for assessment purposes must be work that has not been submitted previously, by any person, for any other unit at ECU or elsewhere. The ECU rules and policies governing all academic activities, including misconduct, can be accessed through the ECU website. Staff are expected to be critical of student work, looking for any evidence of plagiarism/cheating. Staff may use search software to scan/record your work against the electronic works of others on the Internet. "Plagiarism means to knowingly or unknowingly present as one's own work the ideas or writings of another without appropriate acknowledgment or referencing, including Paraphrasing text without acknowledging source (includes any copying) Paraphrasing text inadequately Copying another student's assignment (from any source) Copying of visual representations (cartoons, line drawings, photos, paintings, computer programs, images, tables, graphs)

LATE SUBMISSION If a student is unable to submit a within-semester assessment task (i.e. assignment) on or by the due date, the penalty will be 5% (of the possible mark) per working day, and after five working days the mark will be zero.

LECTURER Dr Ganesh Arulampalam Email: g.arulampalam@ecu.edu.au UNIT COORDINATOR: Dr Alexander Rassau Email: a.rassau@ecu.edu.au WEEKLY SCHEDULE: WEEK TOPIC MAJOR ASSESSMENTS 1 Engineering Basics 2 Engineering Process & Requirements 3 Problem Solving & Innovation 4 Communication and Documentation 5 Engineering Design Design Project Report 1 due 6 Engineering Project Management 7 Sustainable Engineering 8 Risk Management & Project Management 2 Design Project Report 2 due 9 Engineering Economics Practical Project Demonstration 10 Ethics and Safety in Engineering 11 Presentation Skills & Revision Design Project Final report due 12 FINAL PRESENTATIONS Design Project Final Presentations Note: Lecture topics subject to change at lecturers discretion

CALCULATORS Calculator policy The following calculators are the only calculators that are permitted to be used in tests and examinations for all engineering units: Casio FX-100 Sharp EL520 All engineering students should purchase one of the above calculators, ensure that they are familiar with its operation, and bring it to all tests or examinations for engineering units. Any students found using non-compliant calculators after the commencement of a test or examination, for any engineering unit, will be considered cheating and will be dealt with as stipulated in the Academic Misconduct policy with full consequences.

ASSESSMENTS DESIGN PROJECT: EWB Challenge Project Component Preliminary Report 1 Progress Report 2 Project Final Report Project Presentation TOTAL % of Unit Marks 5% 5% 30% 10% 50%

Due Dates: See unit Blackboard site for up to date information. PROJECT DESCRIPTION The design project for this unit is based on the Engineers Without Borders Australia Challenge (EWB Challenge). The EWB Challenge is a national design competition for first-year university students. The competition aims to develop students' learning experiences and key attributes through a teambased design approach utilising inspirational sustainable development projects. The details of the overall objectives, specific design projects and final report submission requirements are given in the challenge document, available from the Challenge website www.ewb.org.au/ewbchallege. The Project for this Unit also has additional deliverables (components) in the form one progress report and a final presentation by the team during the final week of lectures and tutorials. These additional components have been incorporated to aid the students preparation as well as provide experience of real-world project management processes and issues. Students should refer to the unit site on Blackboard for details. TEAMS Students are to work in teams of 4 to 6 students. Teams cannot be changed without prior approval by lecturer. Only one presentation and one of each report are required per team.

DESIGN PROJECT COMPONENT SUBMISSION REQUIREMENTS First Report The first report would represent the preliminary project document and should cover the following: The project task selected by the team Reasons for selecting the task Requirements analysis Research / option study relevant to task Preliminary Assignment Project Plan tasks and timeline for the Challenge project (this assignment). The report should demonstrate the teams understanding of the task, the ability to analyse and break-down the design task into smaller components, information gathering skill and the ability to plan and prioritise. The report is designed to reflect real-world engineering practices where a preliminary project plan and report would need to be submitted prior to commencement of a project. It is meant to be part of a structured engineering approach to the project, not merely as an academic exercise, and the tone of the report should reflect this. The Project Plan should contain some reasoning with regards to tasks and time allocated. It is expected that there will be variations to the timeline when actually carrying out the project, and this will have to be justified and discussed in Report 2. Marks will also be allocated to presentation and formatting as per documentation standards discussed in lectures and tutorials (structure, referencing etc.). Marking Scheme for Report 1 Content The project task selected and reasons Preliminary requirements analysis Research /option study relevant to task Preliminary Assignment Project Plan o Tasks and timeline for the team Documentation Structure and required components Referencing Presentation o Language, style, layout, enhancements TOTAL 60% 10% 15% 20% 15% 40% 10% 10% 20%

TOTAL

TEAM RATING SCHEME Each team will be required to come up with a contribution rating for each member for each of the team submissions. The rating will be based on a marking rubric given in the tutorials. This scheme is designed to allow the team members to make known their view of each members contribution and provide a method of equitably distributing marks. It is designed to reward those who contribute more to the project (assignment) and penalise those who dont carry their fair share. The team rating will be posted on the team wiki and has to be agreed to by all members. Rating should be done AFTER the report is submitted, so that full contribution of each team member can be considered. Points on Team Rating It is a proportional weighting scheme that weights the individuals marks based on the teams mark. It uses the ratio of the individuals total rating to the teams total rating Marks above full mark will be limited to full mark

Second Report The second report would incorporate the preliminary design as well as intermediate project review. It should cover the following: Design option trade-off analysis Relationship between preliminary design and requirements Preliminary detail design Preliminary project plan for design solution initial estimates for solution implementation timeline, resources, budget etc. Outline of environmental concerns that will have to be addressed in final report Review of tasks completed and timelines (including reasons / analysis for variations) Updated Assignment Project Plan tasks, task allocations, timeline, and budget for the Challenge project (this assignment). Marks will also be allocated to presentation and formatting as per documentation standards discussed in lectures and tutorials (structure, referencing etc.). This report is a follow-on of the process started in the First Report. In terms of Design Process, this report is meant to cover the middle section of the design process flow, from Trade-off analysis to early stage of detailed design. The teams would also need to demonstrate that thought has been put into the practical implementation issues such as time and cost (the other legs of a project). The first two reports are designed to help structure the students thought processes and lead the teams to the final project design and report. Some of the components have been labelled as preliminary or initial as it is expected that these components will be developed further and refined in the final project submission. The second report is also designed to reflect real-world engineering practices, where progress reports will need to be submitted to management and/or client to monitor progress and review outcomes. In any real-life project, it is expected that there will be changes to the solution proposed and variations to the timeline when actually carrying out the project and this will have to be justified and discussed. Marks will also be allocated to presentation, formatting and referencing as in previous report, though given a smaller weighting. Details are given in marking scheme following. Marking Scheme for Report 2 Content Design option trade-off analysis Relating concept design to requirements Preliminary detail design Preliminary implementation design o Time, human resources, other resources, budget (if actually implemented) Initial outline of environmental concerns Review of tasks completed and timelines o Including reasons/analysis for variations Updated Assignment Project Plan o Tasks and timeline for the team Documentation Referencing Presentation o Language, style, layout, enhancements NB: The Team Rating Scheme applies once again as outlined above.

TOTAL

80% 10% 10% 20% 15%

10% 10%

5% TOTAL 20% 10% 10%

FINAL PROJECT REPORT


The Final Project Report will encapsulate the whole project and should be a stand-alone document (relevant parts of the first two reports should be incorporated where appropriate). The Final Report should conform to the Submission Requirements of the EWB Challenge. The Report should address all of the marking criteria for the Final Report.

This report should contain all relevant parts of previous reports within it. Readers (assessors, judges etc) should not be expected to know about or have access to previous reports. In fact, the report should assume that the reader knows NOTHING about the project or even the EWB Challenge. The object of the report is to convince the reader that you have come up with the best solution for one or more problems as outlined in the Challenge document. In order to achieve this, information must be presented in a clear, logical and convincing manner. All claims or statements should be substantiated, either via references or supporting documentation (e.g. supplier specifications, brochures etc.). The judges and assessors should not be expected to accept any statements or claims made just because the team says so! It is recommended that risk management and a benefit-cost analysis be included as part of the project report. The marking scheme for this assessment is based on EWBs assessment criteria, and may be subject to change. Details of the marking scheme as it stands are given in the following table.

Marking Scheme for Final Report (subject to change) Demonstrate application of technical knowledge to the specified problem Total 45% 5% 2%

Explanation of how design criteria were developed to suit the specific needs of the community (includes Requirements Analysis) Design criteria should include consideration of the communitys perspective of the design proposal. Demonstration of how scientific and engineering knowledge have been utilised in the design process Identification of a range of appropriate technologies and/or design solutions Compare design options against design criteria and determine a preferred option Clear presentation of final design and how it meets the requirements Implementation plan / project plan - including role of local community, skills and equipment required, training for local community, etc Operation and disposal factors taken into account - includes raw materials, maintenance costs and skills required, expected lifetime Innovation - new processes / products - re-use of existing processes and products in innovative way Total

8% 5% 10% 8% 5% 2%

Integration of Sustainable Development and Design Context into the decision making process Outline impacts and benefits of the project, in a form the community can readily understand Environmental impacts and benefits Economic impacts and benefits Social impacts and benefits

25%

6% 6% 6% 4% 3% 30% 2% 2% 3% 3%

Appreciation for the ethical responsibilities of engineers, includes safety considerations Demonstration of attempts to use locally available materials for the proposed design Effective communication and team management for project Total Reflection of the effectiveness of consultation with the community throughout the design process Outline of the difficulties expected when trying to communicate with the community Outline of the role of each team member Project Management considerations - team structure, work allocation, effectiveness of team, communication methods, etc. Report Writing skills Referencing Presentation and Supporting Material - , structure, language, layout, plans, diagrams, tables. Clear presentation and logical flow of information Executive summary covers all aspects of the report concisely and coherently and contains reflection on learning / experience gained through the EWB Challenge Overall effectiveness of Report

6% 6% 3% 5%

NB: The Team Rating scheme applies once again as outlined previously.

Project Presentation The Project presentation should communicate the teams solution in a concise but convincing manner. The audience should be considered to be management committee / panel of investors that need to be convinced of the worth of the solution being presented. The Presentation should address all of the marking criteria for the Final Presentation (details will be provided at a later date). Each teams presentation should take no more than 15 minutes. Presentations that run over time will be penalised. EVERY team member should have a section to present orally (individual assessments will be made for this part). 2 minutes will be allocated to Question and Answer session (open to the floor)

Teams will also be assessed on organisation and efficiency of presentation (includes set-up and clearing time) Note: More detailed information on marking schemes and judging criteria will be provided for each component closer to the due dates. Marking Scheme for Project Presentation CRITERIA TOTAL 100% 20 %

Structure and Flow PURPOSEFUL STRUCTURE: gives audience sense of focus and purpose, uses introduction/ development/ conclusion, main points clear LOGICAL FLOW: Content presented in logical sequence, leading audience through the content and building up understanding of project solution. Content Appropriate content covered at relevant depth and clarity Effective use of audio-visual aids Pictures / diagrams / text used in appropriate fashion to enhance points being made. Overall Effectiveness How well information put across to audience How convincing that solution should be implemented Ability to engage audience. Individual presentation EFFECTIVE DELIVERY: adequate volume and voice projection, clear articulation, vocal variety, use of gestures/body language, appropriate verbal expression, eye contact and expression of interest in audience and topic

20 % 20 % 20 %

20 %

Practical Project
Project Component Demonstration / Competition Documentation Competition - heat winners Competition - overall winners TOTAL Project Description The practical project will require the student teams to build some form of device to achieve a stated objective given a set of requirements and constraints. The details of the project will change annually. The requirements statement will be left fairly open-ended to give teams the opportunity to be creative and innovative in their solutions. The project is fashioned as a competition, where teams will compete against others in the same tutorial session, and the tutorial-level category winners will compete in the Grand Final. The categories for the competition are: 1. Best Performance 2. Most Cost Effective (Performance / price) 3. Most Innovative The objectives of this project are to give students experience in designing a real working model based on given requirements and constraints, as well as to have some fun getting something (hopefully) working and competing with their peers. Teams will need to orally present the key elements of their solution prior to demonstration. Students will also need to create individual portfolio description of project and outcomes (see Portfolio section). Practical Project Marking Scheme DESIGN DOCUMENTATION Description of solution (oral) - Principles of operation - Key components (e.g. power source and drive/propulsion type) - Description of innovative components of design Costing of vehicle (written) - itemised costing (if purchased new) - total cost (mandatory) DOCUMENTATION TOTAL DEMONSTRATION Demonstrate working model - functional design Design meets weight and size criteria Performance Cost effectiveness Safety audience / environment Innovation DEMONSTRATION TOTAL 20 5 30 15 10 20 100 10 % of Unit Marks 8% 2% Bonus 1% Bonus 1% 10%

10

20

TUTORIALS AND QUIZZES There will be selected tutorial activities in the tutorial sessions that will be assessed. Tutors will inform students as to which particular activities will be assessed. There will also be a number of online quizzes based on the textbook recommended reading. The quizzes can be accessed via the unit site on Blackboard and will normally close two weeks after the lecture on that topic. Each quiz will be worth 1%. The tutorial exercises and online quizzes will make up 20% of the unit assessment.

PORTFOLIO Engineers are assessed on the skills they possess, not just their qualifications. In order to demonstrate these skills or competencies, engineers need to build up a portfolio of work they have done and the roles they have filled. This portfolio is used by Engineers Australia to determine if a graduate engineer is eligible for Chartered Engineer status. It may also used by potential employers to determine if a candidate has the necessary experience and skills that they require. Engineers Australia recommends that this portfolio be started right from the very first year of the engineering degree. This year, students in this unit will be asked to create their portfolio using an electronic portfolio tool called PebblePad. Students need to document work carried out in the projects and skills acquired or improved in this unit in their portfolio. The portfolio assessment will be worth 20% of the unit mark.

Note: Further details on Portfolio submission and marking scheme will be presented during the semester

Das könnte Ihnen auch gefallen