University of Melbourne · Master of Software Engineering
Call for industry partners.
We invite organisations to partner with graduate software engineering teams—from early requirements analysis to the design and delivery of a substantial software solution.
There is no charge for organisations to partner with our student teams.
Partners contribute their time, organisational context and feedback throughout the semester.
Choose the right pathway
Where is your project today?
You do not need to select a subject before contacting us. We will help identify the best fit and scope.
Semester 1SWEN90009
Discover & define
Software Requirements Analysis
Best for an important problem that is not yet well understood, where stakeholders, priorities or possible solutions need to be investigated.
Student teams may deliver
Stakeholder and problem analysis
Business process and domain models
Prioritised functional and quality requirements
Prototypes and validation evidence
A requirements package for future delivery
Focus: deciding what should be built and why.
Semester 2SWEN90014
Design & deliver
Masters Software Engineering Project
Best for a well-framed project with a committed partner, a feasible semester scope and clear access to the knowledge or data needed by the team.
Student teams may deliver
Refined project scope and requirements
Software architecture and technical design
A substantial working prototype or solution
Testing and quality evaluation
Technical documentation and handover
Focus: delivering and evaluating a software solution.
A project may be suitable for one or both subjects. Participation in both can create continuity from discovery to delivery, subject to scope, student allocation and teaching-team approval.
Why participate
A fresh perspective on work that matters.
01
Structured attention
A team devotes a semester to understanding or progressing a challenge that day-to-day work may leave unresolved.
02
Independent thinking
Students bring current software engineering methods and question assumptions constructively.
03
Useful artefacts
Receive documented analysis, models, prototypes or software outcomes suited to the selected subject.
Suitable projects
Grounded in a genuine organisational need.
Strong projects have an engaged contact person, access to domain knowledge and enough uncertainty for students to make meaningful engineering decisions.
01
Business processes and internal tools
02
Data, reporting and decision support
03
Customer and community services
04
Research software and digital platforms
05
System integration and modernisation
06
Responsible AI-enabled software
A good project provides
A real user, operational or research need
A partner who can meet the team regularly
Access to relevant stakeholders and domain knowledge
A scope that can produce a meaningful semester outcome
Projects are less suitable when
The solution and every feature are already fixed
No one is available to answer questions or review work
Success depends on restricted data students cannot access
A production-ready commercial system is required on a fixed deadline
The partnership
A clear process, supported by the teaching team.
01
Enquiry
Tell us about the project
Share the organisational context, the need and what a useful outcome might look like.
02
Scoping
Agree on subject and scope
We assess suitability, expectations, access constraints and the appropriate student pathway.
03
Semester
Work with the student team
Join a kickoff and regular focused meetings to provide context, answer questions and review progress.
04
Completion
Review and handover
Attend the final presentation and receive the agreed project artefacts and recommendations.
What we ask of partners
Context, access and timely feedback.
One
named contact who can represent the organisation
Regular
meetings at agreed points through the semester
Appropriate
access to stakeholders, systems or de-identified examples
Constructive
feedback on student understanding and project outcomes
Common questions
Is there a fee to participate?+
No. There is no project fee for participating organisations. Partners contribute time, access to relevant people or information, and regular feedback to the student team.
Which subject should I propose my project to?+
You can submit one enquiry without choosing. SWEN90009 suits open problems requiring investigation; SWEN90014 suits well-framed projects ready for design and implementation.
Does the project need to involve AI?+
No. We welcome a broad range of software and socio-technical problems. AI may be considered where it serves a genuine need, but it is not a requirement.
Will we receive production-ready software?+
SWEN90009 focuses on analysis rather than implementation. SWEN90014 may produce a substantial working solution, but it remains an educational project and should not be treated as guaranteed production delivery.
Can projects involve confidential information?+
Non-confidential or de-identified information is strongly preferred. Any confidentiality, privacy, intellectual-property or system-access needs must be discussed during scoping.
Who can become a partner?+
Companies, government teams, research groups, not-for-profits and community organisations are welcome to enquire.
Industry project expressions of interest · 2027
Start with a short conversation.
Send a brief description of your organisation, the project or problem and the people it affects. We will help you assess its suitability.