🎉🎉 Welcome to COMP1531 🎉🎉

COMP1531 is the first station on a very long voyage to becoming the best software engineer you can be. We're going to have a great term - even if we're all not physically together. COMP1531 has a passionate teaching team - nearly all of whom have been in your shoes within the last few years. Everyone here will primarily interact with two tutors throughout this term. We're all excited to meet you.

Through the term you'll all working not only with your tutor(s), but also with our course admins and lecturers.

Emily Luxa 🍍 Course Admin	Hayden Smith 🫐 Guest Lecturer	Jake Renzella 🥭 Lecturer in Charge	Nick Patrikeos 🍓 Course Admin

This page offers an outline of this course. Take the time to read it, as it covers everything that we expect you from this term, and everything you should expect from us!

- COMP1531 teaching team

---

Contents

• 1. Course Details
• 2. Course Summary
• 3. Teaching Strategies
• 4. Assessment
• 5. Schedule / Timetable
• 6. Student Conduct
• 7. Resources for Students
• 8. Course Evaluation and Development

---

1. Course Details

Find information relating COVID-19 and this offering here and here .

Course Code	COMP1531
Course Title	Software Engineering Fundamentals
Convenor	Jake Renzella
Lecturer(s)	Jake Renzella
Admin(s)	Nick , Emily
Units of Credit	6
Course Website	WebCMS (this website!)
Handbook Entry	http://www.handbook.unsw.edu.au/undergraduate/courses/current/COMP1531.html

---

2. Course Summary

This course is teaches students about software engineering principles via exposure to the important practice of building correct products in effectively functioning teams.

You will be exposed to agile software practices, team collaboration and effective communication through implementing a group project based on agile software methodologies that requires you to analyse, design, build and deploy a web-based application. This course is typically taken in soon after completing COMP1511, but could be delayed and taken later. It provides essential background for the teamwork and project management required in many later courses.

2.1. Assumed Knowledge

We assume all students have completed COMP1511 (or equivalent).

Students should be familiar with the basic concepts of programming, including loops, functions, libraries of code, compiling, and writing code to follow specifications.

2.2. Student Learning Outcomes

After completing this course, students will be able to:

1. Demonstrate effective use of applying the software development to build full-stack end-user applications
2. Demonstrate effective use of static testing, dynamic testing, and user testing to validate and verify software systems
3. Understand key characteristics of a functioning team in terms of understanding professional expectations, maintaining healthy relationships, and managing conflict.
4. Demonstrate an ability to analyse complex software systems in terms of their data model, state model, and more.
5. Understand the software engineering life cycle in the context of modern and iterative software development practices in order to elicit requirements, design systems thoughtfully, and implement software correctly.
6. Demonstrate an understanding of how to use version control, continuous integration, and deployment tooling to sustainably integrate code from multiple parties.

---

3. Teaching Strategies

This course uses the standard set of practice-focused teaching strategies employed by most CSE foundational courses:

• Lectures
• Tutorials
• Laboratories
• Help Sessions
• Major Group Project
• Final Exam

This course aims to provide the students with a strong foundation in the fundamental principles and practices of software engineering that will prepare them for the advanced software engineering workshops. As such, a broad range of key software engineering topics will be taught and reinforced through a group project, that will enable students to apply the theoretical concepts acquired to solve a practical software engineering problem. An agile software delivery style has been chosen for the implementation of the group project, to make students familiar with modern agile development methodologies.

3.1. Lectures

Lectures will be used to present the theory and practice of the techniques in this course. Although the lectures will primarily focus on the key concepts of software engineering, some lectures will also include practical demonstrations of various key technologies required for the implementation of the group project. Lecture slides will be available on the course web page.

3.2 Tutorials

Tutorials help clarify ideas from lectures and work through exercises based on the lecture material. You should make sure that you use them effectively by examining in advance the material to be covered in each week's tutorial, by asking questions, by offering suggestions and by generally participating.

Tutorials will often involve collaborative and break-out work where you will work with a group of other students to solve or answer problems. This will often be done in your major project group.

Tutorial information, once released, can be found by going to the tutorial page. Tutorial solutions will be released at the end of the tutorial's week.

Tutorials contribute to your class mark.

Tutorials will be run via Microsoft Teams .

3.3. Laboratories

In terms of the weekly workload, each week with a tute/lab you will be given a "lab" (i.e. take-home activities to complete in your own time) that is due at the end of that week.

In terms of the 2 hour period each week allocated for labs, these sessions run immediately after your tutorial.

• (1) Project check-ins . Your tutor will run a meet with each group for a 20 minutes for a project check in.
• (2) Marking labs off . Your lab assist will meet with each group to mark your labs off and answer questions about labs. Your tutor will mark your lab off with your other group members in the "room", so be prepared in advance that your group members will be there for part of the marking.

A schedule of what times your group should attend which sections can be found on the tutorial and labs schedule page.

Lab solutions will be released 1 week after the end of the week they are due (with exception of first few weeks where lab solution releases will be delayed due to late enrollments).

Appropriating responding to, and actioning any feedback given by tutors in previous labs is expected by all students.

Labs contribute to your class mark.

3.3.1. (1) Project check-ins

In weeks 1, 2, 3, 5, 8, and 9, your project check ins are a chance your group and your tutor to sync up about your progress and work through problems together.

In weeks 4, 7, and 10, your project check in periods will consist of a presentation and Q&A as specified in the project specification.

3.3.2. (2) Marking labs off

Labs will typically be due at the end of the week they are provided. You are required to show & discuss your lab with your lab in the lab of the week immediately following the week the lab is due. Submitting the lab is not enough to be awarded a mark. You cannot obtain marks by emailing your tutor your labs. If you are unable to submit your lab on time due to extenuating circumstances, please apply for special consideration.

3.4. Lab Feedback (Formatif)

In an effort to provide more formative feedback on your lab work, each week you can chose to submit one of the week's labs which you already completed. We recommend you pick a particularly challenging or interesting, completed lab to your tutor via the formatif system. You will also provide a short reflection on what made the lab challenging/interesting. During the week, your tutor will take some time to provide some more in-depth feedback, more than you would typically receive on your other labs. This provides a private, one-to-one opportunity to improve your understanding. These reflections are not graded, and they will not require you to complete any extra work other than engaging with your tutor in the reflection process.

3.5. Help Sessions

Help sessions are unprepared drop-in "clinics" where students and groups can go to seek help about course related matters, whether that be the project, tutorials, or labs. Current tutors or lab assistants will supervise each help session.

Help sessions will be run via Microsoft Teams.

The timetable for help sessions will be available soon.

3.6. Major Group Project

There will one main group project which will run through the teaching period from weeks 1-10 and contributes to 45 % of the overall course mark.

The course staff will form groups of 4-5 students in your allocated tutorials at the beginning of the course. You will be notified of what group you're in during your week 1 tutorial & lab. A short survey will be sent no later than the 8th of February 2022 that will allow you to make preferences of who is in your group. These groups will and must be within your own tutorial group.

The group project will be implemented using an agile software delivery mode. As such, your team will be required to build and deliver the project in milestones. Each milestone will deliver a part of the requirements of the project and will encompass all the SDLC activities, namely analysis, design, coding and testing. At the end of the milestone, you (as a team) will demonstrate to your lab class the functionality implemented during that milestone. Changes to project requirements are a natural and unavoidable part of any software project life-cycle. Hence, students will need to bear in mind that project requirements may be subject to change and enhancements to functionalities may be made at the end of each milestone. You will need to carefully design the solution for your current milestone, such that the solution is extensible to accommodate these changes.

After each milestone due date, your group will present your work in the next lab that occurs. This is outlined in the major project specification. To receive a mark for that milestone, each team member must be present for the demonstration during the relevant lab time, with working audio and with their camera on. Having no audio or video will result in a loss of marks. If you are unable to attend, you must apply for special consideration and have your application accepted.

Tutors will continually monitor the GitLab repositories to see the team's progress and individual member's contribution to the group project.

3.7. Final Exam

There will be a centrally timetabled final exam which will in your UNSW exam timetable. The exam may contain a mixture of short answer questions and programming exercises. More specific details of the exam will be provided through the course.

If you cannot attend the final exam because of illness or misadventure, then you must submit a Special Consideration request, with documentation, through MyUNSW within 72 hours of the start of the exam exam. If your request is reasonable, then you will be awarded a Supplementary Exam. No supplementary exams will be provided for students who score marks 49 or below on grounds of being "close" to a pass.

---

4. Assessment

Item	Due	Weighting
Labs	Weeks 2, 3, 4, 5, 7, 8, 9, 10	20%
Major Project	Milestones due beginning of weeks 4, 7, 10	45%
Final Exam	Exam period	35%

4.1. Class Mark (20%)

Your class mark is made up of marks associated with tutorials, labs. There is a total of 24 marks that can be gained between tutorials and labs throughout the course (i.e. 4 bonus marks), although it will be capped at 20 overall.

• Your Labs mark is out of 16. Each set of weekly lab exercises you submit is worth up to 2 marks in the course. Each lab contains two types of exercies:
  • Core exercises which must be completed for full marks that week and are most relevant to the week's content.
  • Choice exercises, each choice exercise has a number of points associated with it. You can pick from a list of choice exercises each week however you like to reach that week's target number of choice points (e.g. 8). If if you score 8 choice points in that lab you receive the full 2 marks. This amount of choice points varies per week - lab instructions have the full info. If you score more choice points than the maximum for that lab, you will not receive bonus marks beyond that.
• Your Tutorial is out of 8 marks. Attendance and participation in tutorials 2, 3, 4, 5, 7, 8, 9, 10 will add up to 8 marks in the course. A number of factors contribute toward you receiving a high grade in this area, including but not limited to:
  • Attending the full tutorial
  • Asking good and logical questions throughout the tutorial
  • Taking initiative to answer questions and be engaged
  • Attending with your webcam on for online tutorials (or your phone if you don't have one).
• A note for in-person attendance: If you are unwell, or required to isolate, do not attend your in-person tutorial or lab. Get in touch with your tutor and alternative arrangements can be made including special consideration, or alternative forms of attendance such as dialling in via a team member's computer if you are well enough. In these instances, your attendance mark will not be impacted. Your health and safety, and that of your class mates is priority.

You will be notified by the course authority in week 5 as to how your tutorial attendance and participation mark is progressing.

This marking structure is designed so that students can make choices in how they want to learn. Some students may want to spend time attacking challenge exercises, while others want to spend time engaging more in tutorials. With a few extra bonus marks there is plenty of wiggle room to gain full marks.

Labs have no late penalty , because late submissions are not accepted . While this may seem harsh, some courses have their labs due on the previous Friday - so we are giving you the full weekend to complete your lab. The reason we have no late penalties is because we have to run automarking and provide feedback to you between your lab submission and lab the following week, and therefore once the labs are submitted and marked, solutions will be known to all students.

There are no bonus marks available for labs - you can get 100% in your class mark without ever doing any challenge exercises, so there are bonus marks implicitly built in.

4.2. Major Project (45%)

The marking criteria for your major project will be specified in the major project specification which can be (once released) found here .

4.3. Final Exam (35%)

The marking criteria for your final exam will be specified in the exam specification which can be (once released) found here .

---

5. Course Schedule / Timetable

The schedule for this course will be available soon, and will be outlined clearly in the timetable for lectures , tutorials/labs , and help sessions .

---

6. Student Conduct

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.

If you have any concerns, you may raise them with your lecturer, or approach the School Ethics Officer , Grievance Officer , or one of the student representatives.

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:

• Plagiarism and Academic Integrity
• UNSW Plagiarism Procedure

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

• UNSW's policy regarding academic honesty and plagiarism

The pages below describe the policies and procedures in more detail:

• Student Code Policy
• Student Misconduct Procedure
• Plagiarism Policy Statement
• Plagiarism Procedure

You should also read the following page which describes your rights and responsibilities in the CSE context:

• Essential Advice for CSE Students

At any time in this course, when you push code to gitlab from your own machine (locally or on CSE account), you are acknowledging that this code you push is your own work, except here permitted by the originality rules for this course and this assessment. You acknowledge that this pushed code has not been submitted for academic credit elsewhere, and you acknowledge that you have read an understood the University Rules in respect of Student Academic Misconduct.

---

7. Resources for Students

There is no single text book that covers all of the material in this course at the right level of detail and using the same technology base as we are. The lectures should provide sufficient detail to introduce topics, and you will then study them in further depth in the tutorials, labs and group project. For some lectures, further reading material may be given for students who wish to gain a deeper understanding.

---

8. Course Evaluation and Development

This course is evaluated each session using the MyExperience system.

However, during the term students are encouraged to provide feedback both during lectures, during tutorials, and generally to course staff via email. Anonymous feedback forms will be provided to students throughout the course.

There have been a number of changes made since 21T3, including increasing the amount of formative feedback provided on the labs, lowering the weighting of the group project (from 50% -> 45%), and a re-evaluation of the tutorial content to better align the material to support you in the labs and projects. We are also streamlining the tutorial and lectures process, by moving all online engagement to Teams by introducing a course-level Team which will contain the lecture schedule and Help Session calls.

Further, we have gone through the weekly labs and made quality-of-life changes and clarifications, as well as implementing a new core/choice model, where certain lab activities each week will be marked as core tasks which you must submit. This will ensure you cover the material we feel will best support you in the course, while still providing some choice in how you complete weekly activities.