Outline

Overview

This unit is a sequel of Software Construction and Design I (SOFT2201). It introduces advanced concepts which build on the topics of SOFT2201. SOFT3202 covers topics including software validation and verification, the theory of testing, and advanced design patterns. The unit has a strong focus on the theoretical underpinning of software design. In the labs the theory is applied with contemporary tools with concrete examples.

Unit details and rules

Unit code	SOFT3202
Academic unit	Computer Science
Credit points	6
Prohibitions ?	INFO3220
Prerequisites ?	SOFT2201
Corequisites ?	None
Assumed knowledge ?	None
Available to study abroad and exchange students	Yes

Teaching staff

Coordinator	Josh Burridge, joshua.burridge@sydney.edu.au
Lecturer(s)	Josh Burridge, joshua.burridge@sydney.edu.au

Type	Description	Weight	Due	Length
Final exam (Take-home extended release)	Final exam Extended release project-based exam leveraging prior work	50%	Formal exam period	48 hours
Outcomes assessed:
Assignment	Project Milestone 1 Initial submission for exam baseline software	0%	Mid-semester break	Variable - code
Outcomes assessed:
Assignment	Task 1: Testing Small software testing task - autograded	5%	Week 03	Variable - code
Outcomes assessed:
Assignment	Testing assignment Autograded code assignment testing unknown software	15%	Week 04	Variable - code
Outcomes assessed:
Assignment	Task 2: GUI Small GUI implementation task	5%	Week 06	Variable - code
Outcomes assessed:
Assignment	Task 3: Caching Small database caching task	5%	Week 08	Variable - code
Outcomes assessed:
Assignment	Project Milestone 2 Main feedback submission for exam baseline software	15%	Week 10	Variable - code
Outcomes assessed:
Assignment	Task 4: Analysis Short code and design analysis task	5%	Week 12	Approx 2 pages
Outcomes assessed:
Assignment	Project Milestone 2 Resubmission Repeat submission for exam baseline software if required.	0%	Week 13	Variable - code
Outcomes assessed:
= hurdle task ? = Type E final exam ?

Assessment summary

Tasks 1-4: Short software implementation or analysis tasks to give feedback on mastery of successive unit topics.
Project Milestone 1: Initial implementation of the Project – milestone has been met if the Project executes successfully with the required features. This milestone may be met on a future (Milestone 2) submission if the first attempt is not successful.
Project Milestone 2: ‘Camera-ready’ implementation of the Project – milestone has been met if the Project continues to execute successfully as per Milestone 1, as well as meeting minimum design quality standards. Grade will be based on meeting design quality standards above this minimum.
Project Milestone 2 Resubmission: Optional resubmission in the event original Milestone 2 submission was unsuccessful. The original Milestone 2 grade will stand, but the resubmitted work may be used for the Final Examination.
Final Examination: The Project is required to be modified in a previously undisclosed way during the formal exam period. A report is required analysing the software before and after this modification. Grading is based on software features, software quality, analysis, and communication.

This unit runs a project-based assessment in place of a written exam. This assessment takes place through multiple weeks and multiple submissions as indicated under Project Milestones. Success in the modification work during the formal exam period is only possible if these Project Milestones have been met, and work completed for these Milestones will influence the resulting exam mark. As such they form a combined hurdle as part of the School of Computer Science's normal 40% exam requirement.

Detailed information for each assessment can be found on Canvas.

Assessment criteria

The University awards common result grades, set out in the Coursework Policy 2014 (Schedule 1).

As a general guide, a high distinction indicates work of an exceptional standard, a distinction a very high standard, a credit a good standard, and a pass an acceptable standard.

Result name	Mark range	Description
High distinction	85 - 100
Distinction	75 - 84
Credit	65 - 74
Pass	50 - 64
Fail	0 - 49	When you don’t meet the learning outcomes of the unit to a satisfactory standard.

For more information see sydney.edu.au/students/guide-to-grades.

For more information see guide to grades.

Late submission

In accordance with University policy, these penalties apply when written work is submitted after 11:59pm on the due date:

Deduction of 5% of the maximum mark for each calendar day after the due date.
After ten calendar days late, a mark of zero will be awarded.

This unit has an exception to the standard University policy or supplementary information has been provided by the unit coordinator. This information is displayed below:

Task 1 and the Testing Assignment are both auto-graded with results and solutions being released upon the due date. As such no late submissions may be accepted for these assessments. Late submissions are possible for the Project Milestone 1 and Project Milestone 2 submissions, however timely feedback may not be possible, particularly for the Project Milestone 2 Resubmission. No Project work may be submitted after the due date for Project Milestone 2 Resubmission - the current state of the Project at this time will be used for the formal exam period modification.

Academic integrity

The Current Student website provides information on academic integrity and the resources available to all students. The University expects students and staff to act ethically and honestly and will treat all allegations of academic integrity breaches seriously.

We use similarity detection software to detect potential instances of plagiarism or other forms of academic integrity breach. If such matches indicate evidence of plagiarism or other forms of academic integrity breaches, your teacher is required to report your work for further investigation.

You may only use artificial intelligence and writing assistance tools in assessment tasks if you are permitted to by your unit coordinator, and if you do use them, you must also acknowledge this in your work, either in a footnote or an acknowledgement section.

Studiosity is permitted for postgraduate units unless otherwise indicated by the unit coordinator. The use of this service must be acknowledged in your submission.

Learning support

Simple extensions

If you encounter a problem submitting your work on time, you may be able to apply for an extension of five calendar days through a simple extension.  The application process will be different depending on the type of assessment and extensions cannot be granted for some assessment types like exams.

Special consideration

If exceptional circumstances mean you can’t complete an assessment, you need consideration for a longer period of time, or if you have essential commitments which impact your performance in an assessment, you may be eligible for special consideration or special arrangements.

Special consideration applications will not be affected by a simple extension application.

Using AI responsibly

Co-created with students, AI in Education includes lots of helpful examples of how students use generative AI tools to support their learning. It explains how generative AI works, the different tools available and how to use them responsibly and productively.

Weekly schedule

WK	Topic	Learning activity
Week 01	Administrivia, Unit-in-brief	Lecture (2 hr)
Week 02	Java & Library environment overview. Review of unit testing.	Computer laboratory (2 hr)
Week 02	Theory of unit testing: when, what, how, why. Mocking.	Lecture (2 hr)
Week 03	Unit test independence using the Mockito mocking library.	Computer laboratory (2 hr)
Week 03	Beyond unit testing: integration testing, performance testing.	Lecture (2 hr)
Week 04	More sophisticated testing combining JUnit, Mockito, & Hamcrest. Performance testing.	Computer laboratory (2 hr)
Week 04	Review of Software Design Principles	Lecture (2 hr)
Week 05	Beginning again: reinforcing the fundamentals of Software Design	Computer laboratory (2 hr)
Week 05	Introduction to GUI code patterns	Lecture (2 hr)
Week 06	GUI patterns in Java using JavaFX/Swing	Computer laboratory (2 hr)
Week 06	Networked software design patterns	Lecture (2 hr)
Week 07	Combining GUI software with HTTP calls in Java	Computer laboratory (2 hr)
Week 07	Database software design patterns	Lecture (2 hr)
Week 08	Database access and caching patterns in Java	Computer laboratory (2 hr)
Week 08	Concurrency patterns	Lecture (2 hr)
Week 09	Worker patterns in JavaFX and Swing/AWT	Computer laboratory (2 hr)
Week 09	Software Architectural Patterns	Lecture (2 hr)
Week 10	Implementing more complex architectures in GUI software using Java	Computer laboratory (2 hr)
Week 10	Introduction to Enterprise Software Patterns	Lecture (2 hr)
Week 11	Implementing enterprise patterns in Java	Computer laboratory (2 hr)
Week 11	Analysing Software Design	Lecture (2 hr)
Week 12	Software Design Case Study	Computer laboratory (2 hr)
Week 12	Re-Review of Software Design Principles	Lecture (2 hr)
Week 13	Exam Project Review	Computer laboratory (2 hr)
Week 13	Unit Review	Lecture (2 hr)

Study commitment

Typically, there is a minimum expectation of 1.5-2 hours of student effort per week per credit point for units of study offered over a full semester. For a 6 credit point unit, this equates to roughly 120-150 hours of student effort in total.

Required readings

All readings for this unit can be accessed on the Library eReserve link available on Canvas.

Design Patterns: Elements of Reusable Object-Oriented Software, Gamma, Helm, Johnson & Vlissides, Addison Wesley, 2004, http://www.pearson.com.au/products/?sq=1486024440

Learning outcomes

Learning outcomes are what students know, understand and are able to do on completion of a unit of study. They are aligned with the University's graduate qualities and are assessed as part of the curriculum.

Outcomes
Graduate qualities

At the completion of this unit, you should be able to:

LO1. explain processes and elements in object-oriented design
LO2. apply advanced object-oriented design approaches to software design
LO3. apply advanced object-oriented design principles to implementation using an OO programming language
LO4. discuss and apply testing techniques to software systems
LO5. discuss and apply software validation/verification techniques to Software systems.

Graduate qualities

The graduate qualities are the qualities and skills that all University of Sydney graduates must demonstrate on successful completion of an award course. As a future Sydney graduate, the set of qualities have been designed to equip you for the contemporary world.

GQ1	Depth of disciplinary expertise Deep disciplinary expertise is the ability to integrate and rigorously apply knowledge, understanding and skills of a recognised discipline defined by scholarly activity, as well as familiarity with evolving practice of the discipline.
GQ2	Critical thinking and problem solving Critical thinking and problem solving are the questioning of ideas, evidence and assumptions in order to propose and evaluate hypotheses or alternative arguments before formulating a conclusion or a solution to an identified problem.
GQ3	Oral and written communication Effective communication, in both oral and written form, is the clear exchange of meaning in a manner that is appropriate to audience and context.
GQ4	Information and digital literacy Information and digital literacy is the ability to locate, interpret, evaluate, manage, adapt, integrate, create and convey information using appropriate resources, tools and strategies.
GQ5	Inventiveness Generating novel ideas and solutions.
GQ6	Cultural competence Cultural Competence is the ability to actively, ethically, respectfully, and successfully engage across and between cultures. In the Australian context, this includes and celebrates Aboriginal and Torres Strait Islander cultures, knowledge systems, and a mature understanding of contemporary issues.
GQ7	Interdisciplinary effectiveness Interdisciplinary effectiveness is the integration and synthesis of multiple viewpoints and practices, working effectively across disciplinary boundaries.
GQ8	Integrated professional, ethical, and personal identity An integrated professional, ethical and personal identity is understanding the interaction between one’s personal and professional selves in an ethical context.
GQ9	Influence Engaging others in a process, idea or vision.

Outcome map

Learning outcomes	Graduate qualities
Learning outcomes

Responding to student feedback

This section outlines changes made to this unit following staff and student reviews.

In response to student feedback, more opportunity for feedback on the project work during the semester has been added. More focus on the technical implementation requirements (databases, GUI, concurrency) has also been added.

Disclaimer

The University reserves the right to amend units of study or no longer offer certain units, including where there are low enrolment numbers.

To help you understand common terms that we use at the University, we offer an online glossary.

Current students

Overview

Overview

Unit details and rules

Teaching staff

Assessment

Assessment

Assessment summary

Assessment criteria

Late submission

Academic integrity

Learning support

Learning support

Simple extensions

Special consideration

Using AI responsibly

Weekly schedule

Weekly schedule

Study commitment

Required readings

Learning outcomes

Learning outcomes

Graduate qualities

Outcome map

Responding to student feedback

Responding to student feedback

Disclaimer

On this page

Useful links

Media

Student links

About us

Connect

Current students

SOFT3202: Software Construction and Design 2

Semester 1, 2022 [Normal day] - Camperdown/Darlington, Sydney

Overview

Overview

Unit details and rules

Teaching staff

Assessment

Assessment

Assessment summary

Assessment criteria

Late submission

Academic integrity

Learning support

Learning support

Simple extensions

Special consideration

Using AI responsibly

Weekly schedule

Weekly schedule

Study commitment

Required readings

Learning outcomes

Learning outcomes

Graduate qualities

Outcome map

Responding to student feedback

Responding to student feedback

Disclaimer

On this page

Useful links

Media

Student links

About us

Connect