Undergraduate - UnitFIT3037 - Software engineering

This unit entry is for students who completed this unit in 2014 only. For students planning to study the unit, please refer to the unit indexes in the the current edition of the Handbook. If you have any queries contact the managing faculty for your course or area of study.

print version

6 points, SCA Band 2, 0.125 EFTSL

Refer to the specific census and withdrawal dates for the semester(s) in which this unit is offered, or view unit timetables.

Level	Undergraduate
Faculty	Faculty of Information Technology
Offered	Gippsland Second semester 2014 (Day) Gippsland Second semester 2014 (Off-campus) South Africa Second semester 2014 (Day)

Synopsis

In this unit students will learn about many aspects of working with a large team on large projects to produce quality software products on time and within budget. The student will gain an appreciation of the tools and techniques used to develop software systems within a group context. Topics to be studied include: software development lifecycle models; sizing, estimation, planning and control of projects; functional specification and design of real-time systems; formal specification and design using Z; integration and testing strategies, configuration management; reuse and re-engineering.

Outcomes

At the completion of this unit students will have:

A knowledge and understanding of:

the continuing software crisis, problems encountered in the development of large software systems: poor quality, late delivery and budget overruns;
techniques used in software engineering to counter these problems;
the role of software lifecycle models in project control and planning;
different categories of software metrics;
software estimation methods;
methods for specifying real-time systems;
techniques and tools to support configuration management;
strategies for testing software;
the roles and responsibilities of project team members.

Developed the skills to:

apply techniques for scheduling and control of large projects;
construct and validate a software specification;
formal methods specification of software systems;
functionally design of software systems;
describe large software systems using appropriate language and technical specification techniques to suit the intended audience;
be aware that quality software is not a luxury but essential in solving the software crisis.

Assessment

Examination (3 hours): 55%; In-semester assessment: 45%

Workload requirements

Minimum total expected workload equals 12 hours per week comprising:

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

Two hours of lectures
One 2-hour tutorial

(b.) Study schedule for off-campus students:

Off-campus students generally do not attend lecture and tutorial sessions, however should plan to spend equivalent time working through the relevant resources and participating in discussion groups each week.

(c.) Additional requirements (all students):