Note: This is an archived Handbook entry from 2014.
|Dates & Locations:|| |
This subject is not offered in 2014.
|Time Commitment:||Contact Hours: 36 hours, consisting of one 1-hour lecture and two 1-hour workshops per week |
Total Time Commitment:
Study Period Commencement:
Semester 1, Semester 2
|Recommended Background Knowledge:|| |
|Non Allowed Subjects:|| |
Students cannot enrol in and gain credit for this subject and:
433-340 Software Engineering Project
|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
The aim of the subject is to give students an understanding of how and when to apply their knowledge of computer science and software engineering in the development of a non-trivial software system. The subject also aims to give students an understanding of the importance of analysis, design and management activities within a development process and to provide a realistic environment in which students understand how the practical aspects of computer science and software engineering are applied to real world projects.
Students will work in teams to analyse, design, implement and test a non-trivial software system for a realistic client. A key part of the project is for students to develop and manage a repeatable process in order to deliver a quality software product Workshops will explore the application of theory to the project and include selected topics drawn from: requirements analysis, design, implementation, testing and software project management relevant to the phase of the project that students are currently working on.
INTENDED LEARNING OUTCOMES (ILO)
On completion of this subject the student is expected to:
The subject is assessed on the project management, problem analysis, software design, implementation and testing, artefacts generated during the project and submitted at the end of the project, and on a final report submitted by the team at the end of the project.
1. The analysis and process-related documentation totalling approximately 8000-10000 words (55%) and includes:
2. A final release, of Software, submitted in week 12, requiring approximately 45 hours of work (30%) that assesses the team’s ability to develop a non-trivial software system using software engineering principles and techniques
3. A component of the marks will be based on the individual’s contribution to the project over the course of the semester (15%)
A component of each submission addresses each of the Intended Learning Outcomes (ILOs)
ILOs 1, 2, and 4 are specifically addressed by the final release (item 2)
ILO 3 is specifically addressed via the project management component of item 1
|Prescribed Texts:|| |
|Breadth Options:|| |
This subject is not available as a breadth subject.
|Fees Information:||Subject EFTSL, Level, Discipline & Census Date|
On completion of this subject students should have developed the following skills:
LEARNING AND TEACHING METHODS
The software systems project provides a realistic learning environment with a realistic product specification.
Tutors in the subject act as mentors and guide teams throughout the project. The interaction between the student team and the tutors often raise issues that provide the topics for workshops.
The subject comprises one lecture and one two-hour workshop per week. Lectures are used to coordinate the teams, deliver software engineering theory and practice relevant to the stage of the project reached, and to share experiences between the teams. Workshops are used to discuss issues raised within the project, translate theory to practice relevant to the stage of the project reached, to provide hands-on practice with tools, and to share experiences.
INDICATIVE KEY LEARNING RESOURCES
The subject is administered through the Universities Learning Management System. Templates for the various artefacts, guidelines on engineering processes and links to software engineering tools are available through the LMS. A standard development environment is provided that includes programming languages, libraries and development tools is provided to the students and is available on most engineering computers.
CAREERS / INDUSTRY LINKS
The software industry is expanding and along with it the demand for software engineers that are capable of the analytical and management skills beyond programming. The industry is also changing in the nature of the projects being undertaken with many software engineers now working in multidisciplinary project teams. The skills and experience gained in this subject are valued by employers and are often seen as a necessary grounding for a career in software and technology related industries.
The subject aims to source product ideas from clients outside of the Department where possible and thus seeks to expose students to the types of environments in which software engineering projects take place. Guest lectures by are also given to highlight aspects of industrial practice and to expose students to the practical aspects of software engineering.
Science-credited subjects - new generation B-SCI and B-ENG. |
Selective subjects for B-BMED
Download PDF version.