The unit is a level-3 core unit in the new Bachelor of Software Engineering (Honours) degree to be introduced in 2016.

Introduced for course architecture programs. Effective semester 1, 2016

Updated 2018 to accurately reflect unit after further development in preparation for its first delivery.

23/09/2020 Admin: Update to include new assessment and teaching approach fields as per Handbook requirements.

This unit gives students the opportunity to develop the individual skills and techniques learned in prerequisite and co-requisite units in the context of a full-year team project. Each will contribute to the delivery of a complete software system that is larger than anything they have built in previous units.

They will also have their first exposure to client proxies that are not IT specialists, giving them their first chance to practice realistic requirements elicitation and validation.

Students will apply one of the standard "heavyweight" process models such as the Spiral Model or the Rational Unified Process, complementing their application of a lightweight model in FIT2101 and ensuring that they have a rounded view of software engineering process.

This unit will give students a solid preparation for FIT4002, in which they will complete a year long project for an external client, or IBL.

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

1. develop a software application using a prescribed team-based methodology, conducting all activities associated with the development methodology;
2. plan and manage the full range of activities in a software engineering project in accordance with the development methodology;
3. determine and articulate the functional and non-functional requirements of a software system based on interaction with stakeholders;
4. identify aspects of quality that are important in the context of the project, and devise and implement strategies for ensuring quality goals are met;
5. use appropriate technologies to support the development and ongoing maintenance of a software system, such as issue tracking, project management, continuous integration, and revision control;
6. apply industry-standard technologies to allow different computer systems to interact with each other;
7. analyse professional issues occurring within the development and deployment of software applications, and identify appropriate actions based on relevant law and industry codes of ethical behaviour.

020103

In this unit, students will undertake a full-year software development project in a self-managing team. Students will apply the skills they learned in prerequisite and co-requisite units to a larger project than any they have encountered to date. Through attempting larger-scale software development they will learn how the techniques they have encountered in isolation work together as an integrated methodology to make such complex projects feasible.

The project will be managed through a heavyweight process model such as the Spiral Model, to ensure students are exposed to a representative example of both heavyweight and lightweight processes (which are covered in FIT2101) through the BSE core.

For the first time in their degrees, students will solicit and document requirements from client proxies who are not IT professionals. This builds their communication skills with other stakeholders in preparation for the industry-based project or IBL.

Technological requirements

On-campus

Students will meet regularly with unit staff and stakeholders. Students may need space for conducting group work on campus outside scheduled hours.

This unit will be contact in workshops facilitated by unit staff. These will involve peer-assisted learning, studio teaching, active learning, seminars (led by students, staff, or guest speakers). This is a flipped and project-based unit.

In-semester assessment: 100%

1. Quizzes: - 10% - ULO: 1, 2, 3, 4, 5, 6, 7
2. Domain analysis report - 10% - ULO: 1, 2, 3, 4
3. Technical Report 1: Topics in design - 10% - 1, 2, 4, 5, 7
4. Technical Report 2: Topics in Quality Assurance - 10% - 1, 2, 4, 5, 7
5. Technical Report 3: Topics in post-deployment software management: 10% - ULO: 1, 2, 4, 5, 7
6. Project milestone 1: 15% - ULO: 1, 2, 3, 4, 5, 6, 7
7. Project Milestone 2: 10% - ULO: 1, 2, 3, 4, 5, 6, 7
8. Project Milestone 3: 10% - ULO: 1, 2, 3, 4, 5, 6, 7
9. Project Milestone 4: 15% - ULO: 1, 2, 3, 4, 5, 6, 7

12

Minimum total expected workload equals 12 hours per week comprising:

(a) Contact hours for on-campus students:

(b) Additional requirements (all students):

Access to groupwork space outside scheduled contact hours may be required

FIT, with configuration management systems, CI, and support services managed by eSolutions.

FIT2101 and FIT2107