The official course outline may be found here, however here is some more specific information for this iteration:
DPST1093 is the first stop on a very long voyage to becoming the best software engineer you can be. We will have a great term - even if we're all not physically together.
Throughout the term, you'll all be working not only with your tutor(s), but also with our course admins and lecturers.
This page offers an outline of this course. Take the time to read it, as it covers everything that we expect from you from this term and everything you should expect from us!
- DPST1093 teaching team
This course 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 require you to analyse, design, build and deploy a web-based application. This course is typically taken soon after completing DPST1091 but could be delayed and taken later. It provides essential background for the teamwork and project management required in many later courses.
We assume all students have completed DPST1091 (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.
This course uses the standard set of practice-focused teaching strategies employed by most CSE foundational courses:
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.
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.
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 on its release can be found by going to the tutorial page . Tutorial solutions will be released at the end of the week the tutorial is in.
Tutorial participation and engagement contributes to your project mark.
Tutorials will be run in person and you will need to bring your own device.
Each week will have one 1-hour lab that follows the tutorial and one 2-hour lab which will be later in the week.
The 1-hour lab will be software project management focused. You will carry out common tasks in the agile project management style such as stand-ups, code reviews, sprint meetings, end of sprint reviews (iteration review) and project check-in.
The 2-hour lab will be code focused. You can use this time to get help with lab questions (past or present), and you can seek feedback for your work.
Consultations are unprepared drop-in "clinics" where students and groups can go to seek help about course-related matters, whether that be the lectures, project, tutorials, or labs.
Consultations will be run online and typically be for 1 hour each week. More consultations will be provided prior to important milestone due dates.
From Week 6 onwards, each team will have a 30 minute remote consultation at the beginning of the week (Monday)
There will be one main project which will run through the teaching period from weeks 1-13 and contributes to 60 % 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 2 tutorial & lab. A short survey will be sent no later than week 1 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 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. 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 certain milestones, your group will present your work in the next lab project check-in 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. If working online, this also includes participating 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 members' contributions to the group project.
In Week 12, students will have an individual project instead of an exam during the examination period. This project involves utilizing all the skills learnt during the course to complete an individual project. This project involves modifying and extending an existing code base - students will have 4 days (Mon - Thu) to experiment with the codebase and then one 8 hour period to complete the tasks on the 5th day.
This course is evaluated each session using the MyExperience system.
Resource created Monday 29 April 2024, 11:52:01 AM, last modified Monday 22 July 2024, 07:34:28 PM.