|Course Code||COMP3900 / COMP9900|
|Course Title||Computer Science / Information Technology Project|
|Lecturer in Charge||Matthew Sladescu|
Monday 1:00pm - 3:00pm online
(in week 2, due to public holiday, lecture time will be replaced by: Tuesday 9:00am - 11:00am)
Lectures in 2020 T2 will be delivered online through echo360, which will be accessible through Moodle.
Timetable for all classes
|Consultations||Contact Lecturer in Charge to arrange for a consultation|
|Units of Credit||6|
This is a software project capstone course. Students work in teams of ideally five (5) members to define, implement and evaluate a real-world software system. Most of the work in this course is team-based project work, although there are some introductory lectures on software project management and teamwork strategies. Project teams meet weekly starting from Week 1 with project mentors to report on the progress of the project. Assessment is based on a project proposal, two progressive demonstrations and retrospectives, a final project demonstration and report, and on the quality of the software system itself. Students are also required to reflect on their work and to provide peer assessment of their team-mates' contributions to the project.
Before commencing this course, students should:
For COMP9900, students must be in their final semester of study, and have completed at least 72 UOC towards MIT program 8543.
For COMP3900, students must have completed COMP1531, and COMP2521 or COMP1927, and are enrolled in a BSc Computer Science major with completion of 102 UOC.
After successfully completing this course, students will be able to:
This course contributes to the development of the following graduate capabilities:
|Graduate Capability||Acquired in|
|Scholars capable of independent and collaborative enquiry, rigorous in their analysis, critique and reflection, and able to innovate by applying their knowledge and skills to the solution of novel as well as routine problems||Project|
|Entrepreneurial leaders capable of initiating and embracing innovation and change, as well as engaging and enabling others to contribute to change||Project|
|Professionals capable of ethical, self- directed practice and independent lifelong learning||Project|
|Global citizens who are culturally adept and capable of respecting diversity and acting in a socially just and responsible way||Project|
The learning focus in this course is primarily a team-based software project (for students to practice their skills and knowledge in a real-world, teamwork setup). The course will have an emphasis on the practical software development skills in a teamwork environment. Students will learn the basic concepts of software project management through introductory lectures.
The Student Code of Conduct ( Information , Policy ) sets out what the University expects from students as members of the UNSW community. As well as the learning, teaching and research environment, the University aims to provide an environment that enables students to achieve their full potential and to provide an experience consistent with the University's values and guiding principles. A condition of enrolment is that students inform themselves of the University's rules and policies affecting them, and conduct themselves accordingly.
In particular, students have the responsibility to observe standards of equity and respect in dealing with every member of the University community. This applies to all activities on UNSW premises and all external activities related to study and research. This includes behaviour in person as well as behaviour on social media, for example Facebook groups set up for the purpose of discussing UNSW courses or course work. Behaviour that is considered in breach of the Student Code Policy as discriminatory, sexually inappropriate, bullying, harassing, invading another's privacy or causing any person to fear for their personal safety is serious misconduct and can lead to severe penalties, including suspension or exclusion from UNSW.
Plagiarism is defined as using the words or ideas of others and presenting them as your own. UNSW and CSE treat plagiarism as academic misconduct, which means that it carries penalties as severe as being excluded from further study at UNSW. There are several on-line sources to help you understand what plagiarism is and how it is dealt with at UNSW:
Make sure that you read and understand these. Ignorance is not accepted as an excuse for plagiarism. In particular, you are also responsible that your assignment files are not accessible by anyone but you by setting the correct permissions in your CSE directory and code repository, if using. Note also that plagiarism includes paying or asking another person to do a piece of work for you and then submitting it as your own work.
UNSW has an ongoing commitment to fostering a culture of learning informed by academic integrity. All UNSW staff and students have a responsibility to adhere to this principle of academic integrity. Plagiarism undermines academic integrity and is not tolerated at UNSW. Plagiarism at UNSW is defined as using the words or ideas of others and passing them off as your own.
If you haven't done so yet, please take the time to read the full text of
The pages below describe the policies and procedures in more detail:
You should also read the following page which describes your rights and responsibilities in the CSE context:
Week 3 @ 11.59pm,
21 June (Sunday)
|Progressive Demo A||Project||Week 5 Lab Time||2.5%||CLOs 4,7,8|
|Retrospective A||Project||Week 7 Lab Time||2.5%||CLOs 2,3,4|
|Progressive Demo B||Project||Week 8 Lab Time||2.5%||CLOs 4,7,8|
|Retrospective B||Project||Week 9 Lab Time||2.5%||CLOs 2,3,4|
|Software Quality||Project||Beginning of your Week 10 Lab||20%||CLOs 1,2|
|Project Report||Project||Beginning of your Week 10 Lab||20%||CLOs 4,5,6|
|Final Project Demo||Project||Week 10 Lab Time||20%||CLOs 2,4,7|
|Participation & Peer Assessment||Project||Friday Week 10 @ 11:59pm||20%||CLOs 1-8|
The following table outlines a provisional schedule for this course. The contents of the lectures are described roughly and are subject to adjustments.
|1||Course introduction & Assessment Overview, User Stories||Group formation, project brainstorming||-|
Agile, Scrum Framework, Using Jira for Scrum, Git & GitHub
||Work on the project, progress report||-|
Project Management techniques
||Work on the project, progress report||
due @ 11:59pm, 21 June (Sunday)
|4||-||Work on the project, progress report||-|
|5||-||Work on the project, progressive Demo A||
Progressive Demo A
due in lab
Work on the project, progress
Present Retrospective A Outcomes
due in lab
Work on the project, progressive
Progressive Demo B
due in lab
Work on the project, progress report
Present Retrospective B Outcomes
due in lab
|10||Final wrap-up lecture||
due @ the beginning of your Week 10 lab
due @ the beginning of your Week 10 lab
Final Project Demo
due in lab
Participation & Peer Assessment
due @ 11:59pm on Friday
There are no specific texts and recommended readings for COMP3900/COMP9900. Programming language specific texts may be useful as references, depending on the programming language(s) used in the project. Other online resources and/or documentation related to this trimester's real-world projects will be provided in the course website during the trimester.
This course is evaluated each term using the myExperience system at the end of the term.
In the previous offerings of this course, students noted the small number and similarity of the projects teams needed to choose from as well as the unfairness in the way the contributions of team members are assessed.
Based on the feedback from previous terms, the number and diversity of projects on offer has increased and the formula to calculate the peer assessment marks is adjusted.
Your feedback is important and will be considered to improve future offerings of this course. Students are also encouraged to provide informal feedback during the term, and let the lecturer in charge and mentors know of any problems as soon as they arise. Suggestions will be listened to very openly, positively, constructively and thankfully, and every reasonable effort will be made to address them as soon as possible.
Resource created Thursday 23 April 2020, 11:08:57 AM, last modified Friday 31 July 2020, 01:18:37 PM.