ELEC ENG 3024 - Project Management for Electrical Engineering

North Terrace Campus - Semester 2 - 2015

Teamwork; Project lifecycle; Project planning; Project monitoring and evaluation; Completion of a team project in electrical engineering involving teamwork, problem solving and use of project management and engineering skills.

  • General Course Information
    Course Details
    Course Code ELEC ENG 3024
    Course Project Management for Electrical Engineering
    Coordinating Unit School of Electrical & Electronic Engineering
    Term Semester 2
    Level Undergraduate
    Location/s North Terrace Campus
    Units 3
    Contact Up to 5 hours per week
    Available for Study Abroad and Exchange Y
    Incompatible ELEC ENG 3029
    Assumed Knowledge ELEC ENG 2007, ELEC ENG 2008, ELEC ENG 2009
    Course Description Teamwork; Project lifecycle; Project planning; Project monitoring and evaluation; Completion of a team project in electrical engineering involving teamwork, problem solving and use of project management and engineering skills.
    Course Staff

    Course Coordinator: Mr Alf Grasso

    Course Timetable

    The full timetable of all activities for this course can be accessed from Course Planner.

  • Learning Outcomes
    Course Learning Outcomes

    At the completion of this course students will be able to:

    1.    Understand the components of a project

    2.    Understand teamwork, develop team skills and the characteristics of a good team

    3.    Practice effective communication techniques

    4.    Develop Group/team rules

    5.    Plan and hold effective meetings

    6.    Use effective decision making procedures

    7.    Resolve team conflicts

    8.    Understand the Project Lifecycle, of definition, planning, implementing and completing

    9.    Undertake a feasibility study

    10.  Apply different models to the Project Lifecycle

    11.  Develop a Work Breakdown Structure (WBS)

    12.  Implement various Network Models for Analysis from the WBS (PERT, PDM, CP)

    13.  Develop a Gantt Chart from the WBS

    14.  Perform Earned Value Analysis

    15.  Undertake a Risk Analysis and Risk Mitigation Plan

    16.  Estimate Project Costs

    17.  Use report templates for status reports

    18.  Manage Change within the project

    19.  Undertake a Project Closeout

    20.  Understand the Systems (technical) Lifecycle of Definition, Analysis & Requirements, Design,         Implementation, Integration & Test, System Installation and Maintenance Support

    University Graduate Attributes

    This course will provide students with an opportunity to develop the Graduate Attribute(s) specified below:

    University Graduate Attribute Course Learning Outcome(s)
    Knowledge and understanding of the content and techniques of a chosen discipline at advanced levels that are internationally recognised. 1 to 20
    The ability to locate, analyse, evaluate and synthesise information from a wide variety of sources in a planned and timely manner. 2,3,5,7,9,10,11,12,13,14,15,16,17
    An ability to apply effective, creative and innovative solutions, both independently and cooperatively, to current and future problems. 2,3,5,6,7,9,10,11,12,13,14,15,16
    Skills of a high order in interpersonal understanding, teamwork and communication. 1,2,3,4,5,6,7
    A proficiency in the appropriate use of contemporary technologies. 4,11,12,13,14,15,16
    A commitment to continuous learning and the capacity to maintain intellectual curiosity throughout life. 2,3,4,5,6,7
    A commitment to the highest standards of professional endeavour and the ability to take a leadership role in the community. 2,3
    An awareness of ethical, social and cultural issues within a global context and their importance in the exercise of professional skills and responsibilities. 3,4,7
  • Learning Resources
    Required Resources
    There are no required resources; lecture notes will be available on the MyUni website.
    Recommended Resources
    Smith, Karl A.: Teamwork and Project Management, 2nd Ed, McGraw Hill, 2004.
    Hughes, B. and Cotterell, M.: Software Project Management, 3rd Ed, McGraw Hill, 2002.
    Online Learning

    Extensive use will be made of the MyUni web site for this course, https://myuni.adelaide.edu.au/webapps/login 

    Course notes, tutorial problems, project requirements, course schedule, group list and a practice exam will all be available for downloading from the web site.

    Tutorial solutions will NOT be available online

    Where the lecture theatre facilities permit, audio or video recordings of lectures will also be available for downloading.

  • Learning & Teaching Activities
    Learning & Teaching Modes

    This course relies on lectures as the primary delivery mechanism for the material.

    Tutorials supplement the lectures by providing exercises and example problems to enhance the understanding obtained through lectures.

    Practicals are used to provide hands-on experience for students to reinforce the theoretical concepts encountered in lectures.

    Continuous assessment activities provide the formative assessment opportunities for students to gauge their progress and understanding.

    Workload

    The information below is provided as a guide to assist students in engaging appropriately with the course requirements.

    Activity Quantity Contact Hours Workload hours
    Lecture 10 10 20
    Tutorial 5 5 10
    Practicals 12 36 108
    Group Reports 3 0 15
    Total 153
    Learning Activities Summary
    Lecture Topic
    1 General Project Management
    2 Teamwork
    3 Project Life Cycle
    4 Project Planning WBS
    5 Network Analysis
    6 Gantt Chart
    7 Earned Value Analysis
    8 Closeout
    9 System Development Lifecycle
    10 Implementation, Integration and Test
    Practicals
    Note that practical classes begin in week 1 of the semester. Students shall attend the first practical class when further instructions on the operation of the laboratory session will be provided. if any student cannot attend this session please contact Mr A Grasso alfio.grasso@adelaide.edu.au for alternative arrangements.

    The practical in this course involves the design and development of software to program a robot to traverse a set path. This will involve the detailed understanding of robot circuit schematics and component data sheets to determine how to control the robot.
    Specific Course Requirements
    Not applicable
    Small Group Discovery Experience
    Students will form into groups of 4 members and work on document generation (Project Plan, Software Design and Test Document, Final Report) and develop the software code to control the robot, and present their solution for assessment in week 12.

    The group will have to undertake various research tasks such as learning the C Programming Language, how to read circuit schematics, how various Integrated Circuits used in the robot are applied and controlled and research the use and application of various project management tools, such as Microsoft Project (or equivalent) and the developement of a Software Design Document and Test Plan. This work forms 45% of the assessment.

    The remaining 55% consists of 15% performance (meeting deadlines and participation in class sessions) and 40% for the final examination
  • Assessment

    The University's policy on Assessment for Coursework Programs is based on the following four principles:

    1. Assessment must encourage and reinforce learning.
    2. Assessment must enable robust and fair judgements about student performance.
    3. Assessment practices must be fair and equitable to students and give them the opportunity to demonstrate what they have learned.
    4. Assessment must maintain academic standards.

    Assessment Summary
    Assessment Activity Type Group or Individual Assessment Weighting Due Date Learning Objective addressed
    Reports (3) Formative Group 30% Weeks 4, 10 & 12 All
    Project Execution Formative Individual 15% All Weeks All
    Project Delivery Summative Group 15% Week 12 All
    Exam Summative Individual 40% End of Semester All
    Assessment Related Requirements
    The examination is a hurdle requirement. It is necessary to achieve at least 40% in the exam. If this is not achieved, the total course mark will be limited to a maximum of 49.

    A hurdle requirement is defined by the University's Assessment for Coursework Programs policy as "...an assessment task mandating a minimum level of performance as a condition of passing the course.

    If a student fails to meet a hurdle requirement (normally no less than 40%),and is assigned a total mark for the course in the range of 45-49, then the student is entitled to an offer of additional assessment of some type. The type of assessment is to be decided by the School Assessment Review Committee when determining final results. The student’s final total mark will be entered at no more than 49% and the offer of an additional assessment will be specified eg. US01. Once the additional assessment has been completed, this mark will be included in the calculation of the total mark for the course and the better of the two results will apply. Note however that the maximum final result for a course in which a student has sat an additional assessment will be a “50 Pass”.

    If a student is unable to meet a hurdle requirement related to an assessment piece (may be throughout semester or at semester’s end) due to medical or compassionate circumstances beyond their control, then the student is entitled to an offer of replacement assessment of some type. An interim result of RP will be entered for the student, and the student will be notified of the offer of a replacement assessment. Once the replacement assessment has been completed, the result of that assessment will be included in the calculation of the total mark for the course.
    Assessment Detail
    Assessment details of the three (3) reports will be provided during the semester.
    The Project Execution will be determined by the timely submission of management documents (timesheets, agendas and minutes) and the individual performance in client meetings (Weeks 2,4,6, 8 and 10).
    Project deliveries will be determined by the performance of the end products according to specified requirements which will be provided at the start of the semester, and the collective knowledge of students about their group’s solution.
    The examination will be on material presented in lectures and/or derived from tutorials.
    Submission
    All written submissions (3 reports) to be submitted as follows::

    (1) One student from each group is to upload an electronic copy of EACH submissions (i.e. the 3 reports) to the MyUni website.
    (2) One student from each group is to email the electronic copy of EACH submisisons (i.e. 3 reports) to: alfio.grasso@adelaide.edu.au.

    Late submissions (hardcopy and/or electronic) will be accepted but with a penalty applied.

    The final project code will need to be uploaded during the practical in week 12.

    Weekly timesheets, fortnightly agendas and minutes will need to be uploaded, prior to the specified deadline, to the MyUni website. Late submissions will NOT be accepted.

    Full details can be found at the School policies website:
    https://eleceng.adelaide.edu.au/current-students/undergraduate/
    Course Grading

    Grades for your performance in this course will be awarded in accordance with the following scheme:

    M10 (Coursework Mark Scheme)
    Grade Mark Description
    FNS   Fail No Submission
    F 1-49 Fail
    P 50-64 Pass
    C 65-74 Credit
    D 75-84 Distinction
    HD 85-100 High Distinction
    CN   Continuing
    NFE   No Formal Examination
    RP   Result Pending

    Further details of the grades/results can be obtained from Examinations.

    Grade Descriptors are available which provide a general guide to the standard of work that is expected at each grade level. More information at Assessment for Coursework Programs.

    Final results for this course will be made available through Access Adelaide.

  • Student Feedback

    The University places a high priority on approaches to learning and teaching that enhance the student experience. Feedback is sought from students in a variety of ways including on-going engagement with staff, the use of online discussion boards and the use of Student Experience of Learning and Teaching (SELT) surveys as well as GOS surveys and Program reviews.

    SELTs are an important source of information to inform individual teaching practice, decisions about teaching duties, and course and program curriculum design. They enable the University to assess how effectively its learning environments and teaching practices facilitate student engagement and learning outcomes. Under the current SELT Policy (http://www.adelaide.edu.au/policies/101/) course SELTs are mandated and must be conducted at the conclusion of each term/semester/trimester for every course offering. Feedback on issues raised through course SELT surveys is made available to enrolled students through various resources (e.g. MyUni). In addition aggregated course SELT data is available.

    The course was first offered in 2004 and a course or teacher SELT has been conducted each year from 2005 to 2013.

     

    SELT feedback has suggested

    ·         More Student Participation

    ·         More Stimulation of Interest

    ·         More examples of projects

    ·         More involvement with students

    ·         More Tutorials

    ·         Speak Slowly

    ·         More Explanations

    ·         Tutorial Solutions

    ·         Better Summary of Terms

    ·         More consultations about the project (?)

    ·         More accessibility

    ·         Participation during client meetings

    ·         Add Table of Contents for lecture material

    ·         Provide sample reports

    ·         More feedback

    ·         More independent learning

    ·         Different Projects, maybe some hardware based, other software based

    ·         Remove Project B

    ·         Relax rules

     

     

    After SELT feedback each year the course has been modified as follows

    ·         More examples of projects

    ·         Lecturer to attend more practicals & tutorials

    ·         5 tutorial now assigned rather than 3/4 previously

    ·         Lecturer tries to speak slowly

    ·         More Explanations and detail of worked examples in tutorials

    ·         A Request for tutorial solutions denied but if ANYONE cannot attend ANY tutorial (one or more) the lecturer is available to provide private guidance

    ·         Summary of Terms provided in L10 (must knows!)

    ·         Lecturer  ALWAYS respond to emails

    ·         Lecturer monitor relevant MyUni discussion boards

    ·         Lecturer is available for private consultations at any time during the semester, e.g. after lectures

    ·         Table of Contents added to lecture material

    ·         Reports templates are provided

    ·         Project has more independent learning

    ·         Project B no longer included in the course

    ·         Better to learn rules in industry now, rather than wait until after graduation

  • Student Support
  • Policies & Guidelines
  • Fraud Awareness

    Students are reminded that in order to maintain the academic integrity of all programs and courses, the university has a zero-tolerance approach to students offering money or significant value goods or services to any staff member who is involved in their teaching or assessment. Students offering lecturers or tutors or professional staff anything more than a small token of appreciation is totally unacceptable, in any circumstances. Staff members are obliged to report all such incidents to their supervisor/manager, who will refer them for action under the university's student’s disciplinary procedures.

The University of Adelaide is committed to regular reviews of the courses and programs it offers to students. The University of Adelaide therefore reserves the right to discontinue or vary programs and courses without notice. Please read the important information contained in the disclaimer.