Embed Size (px)
Citation preview
Running successful industry projects with Software Engineering Students.By Tiang Cheng
Barcamp Perth - 30 June 2007
2 of 19
Introduction Motivation Guidelines for choosing a project Recipes for Success General Project Lifecycle Conclusion
Contents
Barcamp Perth - 30 June 2007
3 of 19
Introduction Motivation
Students Industry
Guidelines for choosing a project Recipes for Success General Project Lifecycle Conclusion
Contents
Barcamp Perth - 30 June 2007
4 of 19
Motivation - Students Why do an industry project?
Encourage young software engineers
Provide invaluable ‘real’ industry experience
The goal is the process (How to build a software product) not the product itself
Barcamp Perth - 30 June 2007
5 of 19
Motivation - Industry
Opportunity for R&D
Finding fresh talent
Building leadership skills
The goal is the product. We don’t need to know the process of building software.
Barcamp Perth - 30 June 2007
6 of 19
Introduction Motivation Guidelines for choosing a project Recipes for Success General Project Lifecycle Conclusion
Contents
Barcamp Perth - 30 June 2007
7 of 19
Choosing a Project - Guidelines An example of a bad project
Develop and implement an Artificial Intelligence algorithms for crowd behaviour
Good projects are: Simple Cutting edge, but not bleeding edge Technically Simple (Have one
objective) Functionally Flexible (Add functionality)
Barcamp Perth - 30 June 2007
8 of 19
Introduction Motivation Choosing a project Recipes for Success
Project scope - Guidelines Controlling Scope and risks Industry commitments Good examples of projects
General Project Lifecycle Conclusion
Contents
Barcamp Perth - 30 June 2007
9 of 19
Project Scope - Guidelines Challenging. Involves research as well
as development.
Solve a real problem
Know what direction you want to go
Know your problem domain
Only 20 to 40 hours development time (Very short)
Barcamp Perth - 30 June 2007
10 of 19
Controlling Scope and Risks Scope is most common cause of
failed projects.
“Unable to deliver to client’s expectations”
Scope is dictated by industry, not students.
Pick a direction, and be flexible in your requirements and goals.
Barcamp Perth - 30 June 2007
11 of 19
Industry Commitments Provide 2 to 10 hours a week
Technical support, advice, and close supervision
Sense of humour, team spirit, and leadership.
Strong team commitment and communication
Be a Mentor
Barcamp Perth - 30 June 2007
12 of 19
Good Examples Implement and test XYZ algorithm
Convert ABC application from Perl to .Net
Develop a Proof of Concept (Process)
Build a java/c#/Ruby application to autocreate podcasts.
Barcamp Perth - 30 June 2007
13 of 19
Introduction Motivation Guidelines for choosing a project Recipes for Success General Project Lifecycle
Software Development Lifecycle What actually happens in SDLC Project Lifecycle
Conclusion
Contents
Barcamp Perth - 30 June 2007
14 of 19
Software Development Lifecycle Requirements Specification
Architecture Design
Implementation
Test
Deliver
Barcamp Perth - 30 June 2007
15 of 19
SDLC - Detailed1. Initial Requirements meeting
2. Team write document Version 0.1
3. Industry review meeting
4. Second meeting
5. Rewrite document
6. Industry review meeting
7. Approval, or repeat steps 5 and 6 until Industry is happy.
Repeat for each stage in the Software Development lifecycle
Barcamp Perth - 30 June 2007
16 of 19
Project lifecycle Introduction and project presentation
to all students
Pick and choose a team
Regular project team meetings to assist in SDLC
Final presentation
Poster sessions, Seminars
Barcamp Perth - 30 June 2007
17 of 19
Conclusion Industry projects are a win-win
proposal
Successful projects require pre-planning, and ongoing project management by the industry partner. Treat it as you would an internal project
Rewarding investment.
Barcamp Perth - 30 June 2007
18 of 19
Where to go from here?
UWA Senior LecturerDr Mark [email protected]
CurtinSenior LecturerBrian von [email protected]
Barcamp Perth - 30 June 2007
19 of 19
Thank You!
Any questions?
