Software Engineering Methods

This subject is not offered in 2013.

120 hours

None

None

Students cannot enrol in and gain credit for this subject and:

433-342 Software Engineering Methods

For the purposes of considering request for Reasonable Adjustments under the Disability Standards for Education (Cwth 2005), and Student Support and Engagement Policy, academic requirements for this subject are articulated in the Subject Overview, Learning Outcomes, Assessment and Generic Skills sections of this entry.

It is University policy to take all reasonable steps to minimise the impact of disability upon academic study, and reasonable adjustments will be made to enhance a student's participation in the University's programs. Students who feel their disability may impact on meeting the requirements of this subject are encouraged to discuss this matter with a Faculty Student Adviser and Student Equity and Disability Support: http://services.unimelb.edu.au/disability

Software is present in almost every part of our lives, and continues to change the world. Of importance to users is that software is correct, complete, reliable and efficient. The scale and complexity of most software ensures that achieving these qualities is non-trivial. This subject introduces students to the software engineering principles, processes, tools and techniques for analysing, measuring and developing correct, complete, and reliable software.

The subject is one of the foundational subjects for the Master of Engineering(Software). It is a prerequisite for many of the advanced software engineering electives.

On completion of this subject, students should be able to:

• Select appropriate methods to build in quality and dependability into software systems
• Select and apply effective testing techniques for verifying medium and large scale software systems
• Select and apply measures and models to evaluate the quality and dependability of a software system
• Work in a team to evaluate and apply different methods for quality and reliability of a software system.

• Project work during semester comprising:

Two assignments each consisting of approximately 500 words each and taking approximately 15 hours each (20%). These are due in weeks 5 and 8 respectively.
One small assignment consisting of approximately 250 words and taking approximately 5 hours (5%). This is due in week 9.
One research project executed in teams of 3-4, consisting of a report of no more than 3000 words (25%). The project is due at the start of week 12.
One two-hour end-of-semester written examination (50%).

• To pass the subject, students must obtain:

at least 50% overall;
at least 50% (25/50) in project work; and
at least 50% (25/50) in the written examination.

• ILO 1 to 3 are addressed in the examination, the two assignments, and the group research project.

ILO 4 is addressed in the group research project.
Generic skills are addressed by all assessment items.

None

This subject potentially can be taken as a breadth subject component for the following courses:

• Bachelor of Arts
• Bachelor of Commerce
• Bachelor of Environments
• Bachelor of Music

You should visit learn more about breadth subjects and read the breadth requirements for your degree, and should discuss your choice with your student adviser, before deciding on your subjects.

On completion of this subject, students should have:

• An in-depth technical competence in the selection and application of methods to develop, measure and test quality of software systems
• The ability to undertake problem identification, formulation and solution