Software Engineering Methods

Subject 433-342 (2009)

Note: This is an archived Handbook entry from 2009. Search for this in the current handbook

Credit Points: 12.50
Level: 3 (Undergraduate)
Dates & Locations:

This subject has the following teaching availabilities in 2009:

Semester 2, - Taught on campus.
Pre-teaching Period Start not applicable
Teaching Period not applicable
Assessment Period End not applicable
Last date to Self-Enrol not applicable
Census Date not applicable
Last date to Withdraw without fail not applicable


Timetable can be viewed here. For information about these dates, click here.
Time Commitment: Contact Hours: Twenty-four hours of lectures and approximately 11 hours of tutorials
Total Time Commitment: Not available
Prerequisites:

433-341 Software Engineering Process and Practice

Corequisites: None
Recommended Background Knowledge: None
Non Allowed Subjects: None
Core Participation Requirements:

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

Coordinator

Dr Timothy Miller
Subject Overview:

Software Engineering Methods aims to examine some of the more specific processes required for the production of high quality software, for example, methods for testing software, ensuring reliability or performance in software.

Objectives:

On completion of this subject students should:

  • understand the principles of software testing;
  • know how to apply software testing techniques to the development of quality software;
  • understand the principles of software reliability and methods for assessing software reliability; and
  • understand and apply a range of engineering methods.
Assessment:

Two written assignments of approximately 5 pages per assignment including figures and tables (10% each); a project and project report, of approximately 20 pages (30%); and a 2-hour end-of-semester written examination (50%). To pass the subject, students must obtain at least 50% overall, 10/20 in assignments, 15/30 in project work, and 25/50 in the written ­examination.

Prescribed Texts: None
Recommended Texts:

Information Not Available

Breadth Options:

This subject is not available as a breadth subject.

Fees Information: Subject EFTSL, Level, Discipline & Census Date
Generic Skills: On completion of this subject students should have:
  • the ability to apply knowledge of basic science and engineering fundamentals;
  • in-depth technical competence in at least one engineering discipline;
  • the ability to undertake problem identification, formulation and solution; and
  • the ability to utilise a systems approach to design and operational performance.
Related Course(s): Bachelor of Engineering (Computer Engineering)
Bachelor of Engineering (Electrical Engineering)
Bachelor of Engineering (EngineeringManagement) Software
Bachelor of Engineering (Mechatronics) and Bachelor of Computer Science
Bachelor of Engineering (Software Engineering)
Related Majors/Minors/Specialisations: Computer Science Major

Download PDF version.