Demo Day

Poster

You choose the format

Goal: explain the technical components of your project.

Points:

1. Overview of the project
2. Significant diagrams
3. Project and team tools
4. Architecture and/or component diagram
5. Pictures of the project
6. Lessons learned

Presentation Guidelines

General points:

• For a non-technical audience
• Business professional (as you define it)
• Make sure that diagrams are legible
• 25 minutes

Content

1. What problem are you solving?

   • Describe the project as a story
   • Draw the audience into your world

2. Overview of Requirements

   • High level Use Case Diagram
   • Component Diagram
   • Use diagrams to explain the project (not to explain the diagram)

3. Project Management

   • Show original schedule (Gantt/PERT). How did it change?
   • Show final Requirements Traceability Matrix. How did it change?
   • Summarize team dynamics.

4. Architecture

   • Diagram of production environment (all servers, devices, connections, etc.)
   • What are the development / staging / production environments

5. Risk Management

   • Prototype and results from CSC 354
   • Summarize
   • How did this help in CSC 355?

6. Test Results

   • Show example test – similar to what you are going to demo
   • What automated testing did you perform?

7. Tool Teaser (just one)

   • How you used the tool
   • How it benefited (or not) your project
   • NOTE: poster shows all tools and technology used

8. Demo

   • Clearly outline the steps of the demo
   • Have different tabs/screen open ahead of time
   • Practice

9. Lessons Learned

   • Biggest challenge(s)
   • Biggest lesson learned
   • Your one sentence take-away

Binders

• Sections:

  • Software Development Plan
  • Requirements Traceability Matrix
  • Software Requirements Specification
  • Test Plans and Results
  • Detailed Design Document
  • Installation / User’s guide

• Dividers between documents

• Keep on table during poster session