Note: This is an archived Handbook entry from 2009. Search for this in the current handbook
|Dates & Locations:|| |
This subject has the following teaching availabilities in 2009:Year Long, - Taught on campus.
Timetable can be viewed here. For information about these dates, click here.
|Time Commitment:||Contact Hours: Twenty-four hours of lectures and twenty-four 1-hour workshops |
Total Time Commitment: Not available
433-252 Software Engineering Principles and Tools, 433-253 Algorithms and Data Structures and 433-254 Software Design.
|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
CoordinatorMr Saeed Araban
Students will work on a substantial practical team project drawn from areas such as system software, applications software, graphics or networks. They will be involved in all phases of the project, including requirements analysis, functional specification, system design, implementation, documentation and testing. Lectures will cover applied software engineering issues in areas such as configuration management, release engineering, technical reviews, and software testing.
|Objectives:||The objectives of this subject are for students to experience team-oriented software engineering; to appreciate the importance of planning and managing the software process; to be involved in requirements elicitation and the subsequent phases of software development including documentation, requirements analysis, specification, design, implementation and testing; and to be familiar with some of the problems that can arise during execution of the software development process.|
Software processes developed by the team for their specific project as evidenced by project management documents, a software requirements specification, design specification, and test plan of approximately 200 pages in total (70%); and a release component consisting of a working system, user documentation and installation (30%). Students are expected to spend 12 hours per week on the project. To pass the subject students must obtain at least 50% overall, 35/70 for their process component, and 15/30 for their release component.
|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 an: |
Bachelor of Engineering (EngineeringManagement) Software |
Bachelor of Engineering (Software Engineering)
Download PDF version.