240 likes | 262 Views
~ FYP ~ Final Presentation. Final Presentation. Supervisor, second reader and coordinator, and anyone else Students present PPT for 10 mins and demo software for 5-10 mins, a Q+A session follows in which the audience asks the students questions and clarifications
E N D
Final Presentation • Supervisor, second reader and coordinator, and anyone else • Students present PPT for 10 mins and demo software for 5-10 mins, a Q+A session follows in which the audience asks the students questions and clarifications • To check students wrote software • To check students understand topic clearly • To check a good approach was taken • To assess the students presentation skills • To confirm marks assigned to project
DTXXX/4 Programme Name Full Project Title Your Name Supervisor: Name
Practice this until you can do it in 20 seconds Project Overview • <one sentence explaining the project>
Presentation Contents • Introduction • Background • Design • Development • Test and Evaluation • Conclusions
Introduction Start off with a newspaper headline, a quote, a statistic, something sexy !!!
Practice this until you can do it in 10 seconds Background • Show pictures of the systems/apps that inspired you.
Practice this until you can do it in 10 seconds Background • Show references for some of the key papers/books.
Practice this until you can do it in 10 seconds Methodology • Software Methodology used:
Practice this until you can do it in 10 seconds Design • System Architecture:
Between 2 and 6 slides. Highlight the evolution of the design. Design • Front-End Design
Between 2 and 6 slides. Highlight the evolution of the design. Design • Back-End Design
Development • Technologies • Operating System(s): Your choice(s) • Programming Language(s): Your choice(s) • Scripting Languages: Your choice(s) • Database(s): Your choice(s) • Tool(s): Your choice(s) • Other Technologies: Your choice(s)
Development • Show a diagram of the overall software development.
Between 2 and 10 slides. Highlight the challenges of development. Development • Talk about the challenges of the development • Include code snippets • Mention some places you went to, to locate solutions
Demo Tips • MUST DO: Make A Video Of Your System Running with some commentary, use Screencast-O-Matic, submit with slides. • Practice the demo at least 5 times • Let Damian know as soon as you can if you need any hardware for the demo, e.g. a monitor, a VGA convertor, etc.
Between 1 and 5 slides. Testing and Evaluation • Mention black, grey, and white box. • Mention a test plan. • Mention unit, module, subsystem, integration, and acceptance. • Consider usability testing • Include users if the system is going to be used by people • Evaluate per the discipline
1 slide. Conclusions 3 Conclusions
1 slide. Future Work 3 Future Work
Q+A • Take 3 seconds before you answer a question, say “Hmm, that’s a good question” • Don’t be afraid to ask the person to repeat the question • Don’t argue
Q+A • Typical questions • What was the hardest bit about the project? • If you have 3 more weeks what else would you do? • Why did you choose this project? • Why did you choose that programing language? • How did the project change from the interim demo? • Do you think this is mainly a development project or a design project? • Where is the main complexity?