COMP SCI 7098 - Master of Computing & Innovation Project
North Terrace Campus - Semester 1 - 2016
The course information on this page is being finalised for 2016. Please check again before classes commence.
General Course Information
Course Code COMP SCI 7098 Course Master of Computing & Innovation Project Coordinating Unit Computer Science Term Semester 1 Level Postgraduate Coursework Location/s North Terrace Campus Units 9 Contact Up to 3 hours per week Available for Study Abroad and Exchange N Course Description This course offers an introduction to the development and management of large software projects. Topics covered in this course include the application of: software specification, risk analysis, project management, quality assurance and the study of ethical considerations.
Course Coordinator: Dr Amali WeerasingheLecturer
Mr Ali Shemshadi
The full timetable of all activities for this course can be accessed from Course Planner.
Course Learning OutcomesThis course offers an introduction to the development and management of large software projects.
The aims of this course are listed below
- The development of skills in proposing and presenting new project ideas.
- The development of skills in project management, risk assessment, and planning.
- The development of skills in software development and deployment.
- The development of skills in software demonstrating and presenting software.
University Graduate Attributes
No information currently available.
Required ResourcesLecture slides, assignment specifications and additional materials will be provided online at the MCI Project course forum:
There is no required textbook for this course.
Online LearningThere is an online forum, managed by Moodle. A link to Moodle appears on the subject web-page. We will use the Moodle forum to announce all changes to the course, exercises, and tutorials. You are therefore strongly advised to read all mail that comes from this source — do not ignore it!
Learning & Teaching Activities
Learning & Teaching ModesThe course will be taught using a variation of team-based learning, with lecture/demonstration sessions interspersed with online videos and forum discussions. There will also be tutorial classes to support rehearshals of oral presentations/demos and provide opportunity for peer feeback.
The information below is provided as a guide to assist students in engaging appropriately with the course requirements.This course will involve significant practical work based around a software project. Work for this course will include, in lecture exercises, practical presentations, meetings with project supervisors, written reports, online planning artefacts, production of a software product and live software demonstrations.
The contact time for courses varies. For a full time student, you should expect to spend around 40-48 hours per week on your studies. For this course, you have 3 contact hours per week. You should spend another 17-19 hours on study, preparation and project work.
Learning Activities SummaryThere will be 12 hours of weekly lectures during the course, covering the
following topics:• Course Outline• Preparing a Pitch• Constructing a Business Case• Describing your approach• Software Project Management• Testing and Software Quality• Introduction to Ethics• Presenting Project Outcomes
You will be allocated an advisor for your project. You will be expected to have a short meeting with your advisor in the first week and at least once before each week an item of assessment is due to update him or her on your progress. You can also use these meetings to receive feedback on artifacts, draft presentations or reports that you have produced. To make such feedback useful you are expected to send a copy of the item to your supervisor at least a day prior to the meeting. Of course, the more carefully refined your draft item is the more useful the feedback will be to you.
You will also be expected to maintain a project management activity as an aid for both you and your supervisor to monitor the project’s progress.
The University's policy on Assessment for Coursework Programs is based on the following four principles:
- Assessment must encourage and reinforce learning.
- Assessment must enable robust and fair judgements about student performance.
- Assessment practices must be fair and equitable to students and give them the opportunity to demonstrate what they have learned.
- Assessment must maintain academic standards.
Assessment SummaryAssessment for this course is based on your project. There is no examination for this course. The project work for this course is in four components:- Oral Presentations 30%- Written Documents, worth 35%- Software Demonstration 25%- Online Project management activity, worth 10%
Assessment Related RequirementsTo pass, you must obtain a passing mark overall and achieve at least 40% for the final report. If your mark for this component is less than 40%, your overall mark will be capped at 44F.
Assessment DetailThe following table lists all the individual components to be completed and their due dates.
Assessment Description Due Date Weight Pitch Oral presentation to sell your project concept Week 4 10% Business Case Document supporting business case for project Week 4 5% Approach Oral presentation describing approach for your project Week 6 5% Project Plan Document outlining your project plan Week 6 10% Project Management Activity Staying on track. Tracking project progress and issues Continuous from Week 5 to Week 13 10% Final Presentation Oral summary of project outcomes Weeks 12 and 13 15% Software Demonstration Live software demonstration Weeks 12 and 13 25% Final Report Document summarizing project outcomes Week 13 20%
Penalty for Late Submission of Assessment Tasks
You should hand your coursework in on time. If you hand in your work late, your mark will be capped, based on how many days late it is.- 1 day late – mark capped at 75%- 2 days late – mark capped at 50%- 3 days late – mark capped at 25%- more than 3 days late – no marks available
Students may apply for extensions to their written and online assignment work by emailing the course coordinator, prior to the due date.
They must provide evidence of impairment to support their request for an extension.
SubmissionAll written documents shall be submitted through the course forum.
Students will receive feedback on all the presentations, demonstrations and written work.
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.
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.
- Academic Integrity for Students
- Academic Support with Maths
- Academic Support with writing and study skills
- Careers Services
- International Student Support
- Library Services for Students
- LinkedIn Learning
- Student Life Counselling Support - Personal counselling for issues affecting study
- Students with a Disability - Alternative academic arrangements
- YouX Student Care - Advocacy, confidential counselling, welfare support and advice
Policies & Guidelines
This section contains links to relevant assessment-related policies and guidelines - all university policies.
- Academic Credit Arrangements Policy
- Academic Integrity Policy
- Academic Progress by Coursework Students Policy
- Assessment for Coursework Programs Policy
- Copyright Compliance Policy
- Coursework Academic Programs Policy
- Elder Conservatorium of Music Noise Management Plan
- Intellectual Property Policy
- IT Acceptable Use and Security Policy
- Modified Arrangements for Coursework Assessment Policy
- Reasonable Adjustments to Learning, Teaching & Assessment for Students with a Disability Policy
- Student Experience of Learning and Teaching Policy
- Student Grievance Resolution Process
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.