60 likes | 84 Views
This guide by Timothy Lethbridge from University of Ottawa offers valuable advice on ensuring top marks for your software engineering capstone project. Learn how to impress your customer, focus on quality, prepare a standout final demo, and handle mid-semester presentations efficiently. The tips cover meeting customer expectations, optimizing code quality, delivering a captivating demo, and completing final deliverables successfully.
E N D
SEG4911 – Projet génie logiciel en fin d’études / Software Engineering Capstone Project The Final Drive to Your A+ Timothy Lethbridge University of Ottawa
The home stretch: Key things to do to maximize your mark 1. Ensure your customer gives you a good rating • Meet with them • Demo to them regularly • Surprise them with ‘something extra’ • Be responsive to their change requests • Invite them to the final course demo • Promise them a small amount of support after the course (only if you can deliver on this)
Things to do … 2. Focus on quality at the end • Drop or hide things that are not going to be working well • Clean up the code (but be careful not to break it) • Ensure there are good comments, etc. • Drive down your list of bugs by fixing them • And show a graph of this
Things to do … 3. Prepare your final demo with flair and showmanship • Customers, and other people may be invited • Do a full-fledged demo • With a decent sized, interesting example • On the real system, not simulated • Practice many times so you don’t stumble on remaining bugs
Things to do … 3. the demo, continued • Pretend you are demonstrating to a venture capitalist who may be interested in funding your ‘company’ 4. For the mid-semester presentation • Explain interesting design issues, algorithms • Give an overview of how your management and quality assurance plans worked out • Describe what changed from the original plans • Discuss lessons learned and war stories
Things to do … 5. Final deliverables • Commented code • Updates to your wiki pages describing requirements. design, etc. • Final group meeting minutes • A summary wiki page explaining • How each team member contributed • Lessons learned