Unit convenor and teaching staff |
Unit convenor and teaching staff
Convenor, Lecturer
Carl Svensson
Contact via iLearn forum, otherwise email
By appointment
Lecturer
James Zheng
Contact via iLearn forum, otherwise email
By appointment
|
---|---|
Credit points |
Credit points
10
|
Prerequisites |
Prerequisites
60cp at 1000 level or above including COMP1010 or COMP125
|
Corequisites |
Corequisites
|
Co-badged status |
Co-badged status
|
Unit description |
Unit description
This unit introduces engineering principles and practices to all stages of the software development lifecycle to ensure a systematic, quality-focused and quantifiable approach to the management, design, development, maintenance, verification and validation of [large and complex] software products, projects and processes. Problem formulation and solving are emphasised. Topics covered include: requirements gathering and specification; object-oriented modelling using the Unified Modeling Language (UML); process management; and software design, testing and evolution. |
Information about important academic dates including deadlines for withdrawing from units are available at https://www.mq.edu.au/study/calendar-of-dates
On successful completion of this unit, you will be able to:
Unless a Special Consideration request has been submitted and approved, a 5% penalty (of the total possible mark) will be applied each day one of the two written assessment is not submitted, up until the 7th day (including weekends). After the 7th day, a grade of '0' will be awarded even if the assessment is submitted. Submission time for all written assessments is set at 11:55 pm. A 1-hour grace period is provided to students who experience a technical concern.
The weekly tasks should be completed before the following workshop. If they are submitted after the workshop, they will receive at most a passing grade.
For any late submission of time-sensitive tasks, such as scheduled tests/exams, performance assessments/presentations, and/or scheduled practical assessments/labs, students need to submit an application for Special Consideration.
Students who fail the hurdle requirement - by missing deadlines, or absence from workshops - are required to complete at least 8 of 12 weekly problems at a satisfactory level, followed by a viva on the content of the weekly problems at the end of the session.
To pass this unit you must:
The Special Consideration Policy aims to support students who have been impacted by short-term circumstances or events that are serious, unavoidable and significantly disruptive, and which may affect their performance in assessment.
Written Assessments: If you experience circumstances or events that affect your ability to complete the written assessments in this unit on time, please inform the convenor and submit a Special Consideration request through ask.mq.edu.au.
Weekly Tasks: To pass the unit you need to complete at least 8 of 12 weekly problems before the weekly deadline and participate in the workshop of that week. If you miss a weekly practical class due to a serious, unavoidable and significant disruption, contact th eteaching staff of your registered class ASAP and catch up with your team.
The Special Consideration Policy aims to support students who have been impacted by short-term circumstances or events that are serious, unavoidable and significantly disruptive, and which may affect their performance in assessment. Note that a Special Consideration should only be applied for if you miss more than three of the weekly practical classes.
Name | Weighting | Hurdle | Due |
---|---|---|---|
Weekly Problem | 20% | Yes | Weekly |
Assignment 1 | 15% | Yes | Multiple in week 7 & 8 (see iLearn page for details) |
Assignment 2 | 15% | No | W12 Sunday 11:55pm Submission, W13 class presentation |
Final Exam | 50% | No | Exam Period |
Assessment Type 1: Practice-based task
Indicative Time on Task 2: 36 hours
Due: Weekly
Weighting: 20%
This is a hurdle assessment task (see assessment policy for more information on hurdle assessment tasks)
Each week from week 1 to week 12, problems or small tasks will be posted, Students must complete at least 8 of 12 of these tasks to be completed before the next workshop and attend the workshop where the tasks is discussed.
Students who fail the hurdle requirement - by missing deadlines, or absence from workshops - are required to complete at least 8 of 12 weekly problems at a satisfactory level, followed by a viva on the content of the weekly problems at the end of the session.
Assessment Type 1: Case study/analysis
Indicative Time on Task 2: 20 hours
Due: Multiple in week 7 & 8 (see iLearn page for details)
Weighting: 15%
This is a hurdle assessment task (see assessment policy for more information on hurdle assessment tasks)
Assignment 1 will allow you to demonstrate the development of your understanding and your ability to apply the things that you have learned in the first part (weeks 1 to 6) of the unit.
Assessment Type 1: Design Implementation
Indicative Time on Task 2: 20 hours
Due: W12 Sunday 11:55pm Submission, W13 class presentation
Weighting: 15%
Assignment 2 will be a assignment that will allow you to demonstrate the development of your understanding and your ability to apply the things that you have learned in the second part (weeks 7 to 12) of the unit.
Assessment Type 1: Examination
Indicative Time on Task 2: 24 hours
Due: Exam Period
Weighting: 50%
The final examination will be held during the usual University examination period and can cover all topics.
1 If you need help with your assignment, please contact:
2 Indicative time-on-task is an estimate of the time required for completion of the assessment task and is subject to individual variation
In week 1 here wil be a lecture. Workshops start in week 2.
This unit will be aligned with content from Software Engineering (Tenth Edition) by Ian Sommerville, Pearson, 2015, and Software Engineering: A practitioner's approach (Nineth Edition) by Roger S. Pressman and Bruce Maxim, McGraw Hill, 2020.
Lectures are used to motivate engagement with and reinforcement of the unit's subject matter. Lectures will of course include a significant amount of learning material, but even more importantly they include contextual material and learning activities that "make meaning" of the subject matter.
Workshops are smaller group classes which give you the opportunity to interact with your peers and with a teacher who has sound knowledge of the subject. Workshops will require working in small groups and sometimes involve reporting back to the class. The classes will focus on reinforcing understanding of the concepts and their practical applications to problems. It is important that you participate in the activities and make some notes from them to assist you with revision of the material. Contribution to the weekly workshop and completion of the weekly task is a hurdle requirement, to ensure continued engagement throughout the unit.
Assignments will play a key role in providing evaluation so that students and the teachers can gauge levels of understanding. Assignments will be related to the lecture material, workshop activities and weekly practical material and require students to bring together what they have been learning, and to think creatively and rigorously. The assignments are group assignment combined with individual reflection and individual vivas. The viva for assignment 1 is a hurdle tasks, to ensure engagement of all student in the group project.
A written exam (held within the university examination period) is designed to test your understanding of the course content and your application of the concepts to a number of scenarios or problem statements.
We will communicate with you via your university email and through announcements on iLearn. Queries to convenors can either be placed on the iLearn discussion board or sent to the unit convenor via the contact email on iLearn.
Week |
Lecturer |
Topic |
Notes |
---|---|---|---|
1 |
Carl |
Introduction to Software Engineering |
No workshops in week 1 |
2 |
Carl |
Complex Systems, Requirements Definition and Requirements Specification |
Requirements Team selection |
3 |
Carl |
Modelling Domains and Modelling Systems |
Design Team Selection |
4 |
Carl |
Communicating requirements for system structure, behaviour, data, and usage (including UML) |
|
5 |
James |
Software Development Methods, especially Agile |
|
6 |
James |
Software Project management, especially Version Control |
|
7 |
James |
DevOps and Software Configuration Management |
Assessment 1 (presentation and report due) |
8 |
James |
Software Testing and Quality |
Assessment 1 (viva) |
Teaching Break (2 weeks): work on Assignment 2 and Study for Final Exam |
|||
9 |
James |
Software V&V |
|
10 |
Carl |
Software Maintenance and Software Evolution |
|
11 |
Carl |
Project Management |
|
12 |
Carl |
Quality Management |
Assessment 2 (report due) |
13 |
Carl & James |
Review |
Assessment 2 (presentation) |
Macquarie University policies and procedures are accessible from Policy Central (https://policies.mq.edu.au). Students should be aware of the following policies in particular with regard to Learning and Teaching:
Students seeking more policy resources can visit Student Policies (https://students.mq.edu.au/support/study/policies). It is your one-stop-shop for the key policies you need to know about throughout your undergraduate student journey.
To find other policies relating to Teaching and Learning, visit Policy Central (https://policies.mq.edu.au) and use the search tool.
Macquarie University students have a responsibility to be familiar with the Student Code of Conduct: https://students.mq.edu.au/admin/other-resources/student-conduct
Results published on platform other than eStudent, (eg. iLearn, Coursera etc.) or released directly by your Unit Convenor, are not confirmed as they are subject to final approval by the University. Once approved, final results will be sent to your student email address and will be made available in eStudent. For more information visit connect.mq.edu.au or if you are a Global MBA student contact globalmba.support@mq.edu.au
At Macquarie, we believe academic integrity – honesty, respect, trust, responsibility, fairness and courage – is at the core of learning, teaching and research. We recognise that meeting the expectations required to complete your assessments can be challenging. So, we offer you a range of resources and services to help you reach your potential, including free online writing and maths support, academic skills development and wellbeing consultations.
Macquarie University provides a range of support services for students. For details, visit http://students.mq.edu.au/support/
The Writing Centre provides resources to develop your English language proficiency, academic writing, and communication skills.
The Library provides online and face to face support to help you find and use relevant information resources.
Macquarie University offers a range of Student Support Services including:
Got a question? Ask us via the Service Connect Portal, or contact Service Connect.
For help with University computer systems and technology, visit http://www.mq.edu.au/about_us/offices_and_units/information_technology/help/.
When using the University's IT, you must adhere to the Acceptable Use of IT Resources Policy. The policy applies to all who connect to the MQ network including students.
We value student feedback to be able to continually improve the way we offer our units. As such we encourage students to provide constructive feedback via student surveys, to the teaching staff directly, or via the FSE Student Experience & Feedback link in the iLearn page.
In response to feedback by students, and the advent of generative AI the assignments and weekly taks have be changed. The assignments are group assignment with an individual component, instead of fully individual assignments. Written reports will be accompanied by presentations and vivas.
Workshops will also link more closely with the assignment tasks to allow for more face to face time with group activities relating to the assignments.
Unit information based on version 2024.03 of the Handbook