FIT2107 is a core unit for the new Bachelor of Software Engineering (Honours) degree being introduced in 2016.

Introduced for course architecture programs. Effective semester 1, 2016

31 March 2016: - Added Reason for change on behalf of CE :

Because I am planning to partially flip the classroom and place more emphasis on provided readings. Lectures will focus more on demonstrating techniques and less on explaining theory.

We already have comprehensive readings in the area, and we will augment these with quizzes to test student understanding.

The unit will run for the first time in S2 2017, and this change will be implemented for the first running.

07/12/2017 - Updating prerequisites to include the new programming unit.

20/9/2019: Admin - updating exam duration to include additional 10 minutes as per University requirement.

14/7/2019: Adding reason for change on behalf of CE. Update to learning outcomes and synopsis to reflect updated unit content. For implementation semester 2, 2020. 02/10/2020 Admin: Update to include new assessment and teaching approach fields as per Handbook requirements.

07/09/2021 Revamping of Engineering First Common Year, from ENG1003 to ENG1103, and ENG1060 to ENG1104. Effective semester 1, 2022.

09/09/2021: Admin - fixing prereqs to add back the existing prereq of ENG1003 and ENG1060.

The unit is a level 2 core unit in the Bachelor of Software Engineering (Honours). It is one of the units in the suite of software engineering core units.

The unit focuses on quality assurance issues and techniques in software development projects.Students will learn about the definition of software quality properties, and the variety of strategies and tools that can be used to ensure that a software system meets appropriate quality goals.

The knowledge attained is essential for students undertaking software engineering projects in later years. The unit serves as a prerequisite unit for FIT3170 Software engineering practice.

At the completion of this unit students should be able to:

1. identify appropriate quality goals for a moderately-sized software development project, select an appropriate quality assurance strategy to give confidence that these quality goals can be achieved, and document this strategy appropriately in the context of a software process model;
2. apply quality assurance techniques such as modern code reviews to code development artifacts;
3. perform systematic, automated unit testing on source code modules, using both specification-based and code-based approaches, utilising automated testing frameworks, including faking and mocking tools.
4. perform integration and system testing on a moderately-sized software system, using continuous integration frameworks and tracing tests back to requirements;
5. select appropriate tools to collect metrics, including test coverage, reliability, and design quality metrics, to analyse the quality of a software development project, and make recommendations based on the results;
6. describe the major classes of formal methods used in software engineering, including model checking and theorem proving, and identify situations where their use is justified.

029999

This unit focuses on quality assurance issues and techniques in software development projects. It defines software quality and introduces a number of quality assurance measures, including human review and inspection of code artefacts, as well as execution-based testing.

Students will apply systematic testing techniques in the context of individual modules and entire systems, using appropriate tools to automate the testing process where possible. Students will systematically document their testing plans and outcomes.

Technological requirements

Students wishing to work outside labs will need a computer with an internet connection and the ability to install software.

On-campus

Partially flipped classroom

In this unit students will provided with extensive written notes, supplemented by one hour of lectures for information transfer and context-setting. To encourage the understanding of underlying theory, students will complete fortnightly quizzes including some long-answer written questions.

This, as well as practical skills in the area, will be developed in the laboratory classes where students will work in small groups on both laboratory exercises and in-semester assessment.

Examination (2 hours and 10 minutes): 40%; In-semester assessment: 60%

1. Quizzes: 10% - ULO ?
2. Artefact Review: 15% - ULO ?
3. System Testing: 15% - ULO ?
4. Unit Testing: 20% - ULO ?
5. Exam: 40% - ULO ?

Minimum total expected workload equals 12 hours per week comprising:

(a.) Contact hours for on-campus students:

(b.) Additional requirements (all students):

The workshops should be in a large room with 40+ students and more then one staff member to facilitate group activities on a variety of scales, team teaching and peer learning.

Computers will be required, but one computer per group is sufficient.

(ENG1003 and ENG1060) or (ENG1103 and ENG1104) or one of FIT1045, FIT1053, FIT1048 or FIT1051