How to run a meaningful industry projects for Software Engineering
By Tiang Cheng Email me
Motivation
For students
- Encourage young software engineers
- Provides real industry experience
- It's about process, the the product
For industry
- opportunity for R and D
- Find fresh talent
- It's about the product, nit the proces
Guidelines for choosing a project
Bad project: Implement an AI algorithm for crown behaviour
Good projects:
- Simplicity
- Cutting edge, but not bleeding edge
- Functionally flexible
- Technically simple
Recipes for success
- Make it challenging - involves research
- Solve a real problem
- Know the direction you want to go
- Know the problem domain
- 20 - 40 hours development time
Sontrolling the CSope and Risk
- Most common point of failure
- Dictated by industry, not the students
- Pick a direction, but by flexible
Industry commitments
- 2 - 10 hours per week
- Technical support, advice, and close supervision
- Sense of humour, team spirit and leadership
- Strong team commitment and communication
- Be a mentor
Good examples:
- Implement and test XYZ algorithm
- Convert ABC application from one language to another
- Delveop a Proof of Concept (Process)
- Set up a Web2.0 website to accept SOAP messages and forward on in JKL format
General Project Lifecycle
- Requirements SPecification
- Architecture Design
- Implementation
- Test
- Deliver
Contact detailas:
UWA:
Profession computing 307
Curtin University
Software Engineering Project 451/452/402
Conclusion
- Industry Project are a win-win proposal