SE Presentation

Students are required to create a presentation that covers a particular software engineering topic in depth. All topics related to software engineering or to the design and implementation of concurrent applications are valid.

  • Presentations will be 30 minutes long.
  • Presentations will consist of either a set of slides or a screen cast or a combination of the two.
  • Suggested Topics are listed below but students are free to propose their own topic ideas to Prof. Anderson for consideration.
  • Teams of up to two students each can work on developing a presentation. A 30 minute presentation developed by two students should be of much higher quality and/or go into greater depth than a 30 minute presentation developed by a single student. In other words, the fact that two people were working on the presentation should be evident in the final product.
  • Slides can be created in a number of formats including Powerpoint, Keynote, Google Docs or PDF.

Presentations are due to Professor Anderson by Friday, March 19th at 11:59 PM. Students are free to submit presentations early.

Students should contact Professor Anderson when they have selected a topic... he will update this page to indicate that the topic is "taken" so that we do not have students working on the same thing.

Presentations will be reviewed by Prof. Anderson and the grader and the roughly the top 10 presentations will be selected to be presented in class. All presentations will be made available on the class website. If you are selected to present in class, and you need to demo a particular piece of software during your presentation, you will need to verify that the software in question can run on the professor's laptop or be presented via a screencast. This requirement is in place due to the need to capture the presentation on the video of the lecture being created for CAETE students.

Potential Topics

  • History of SE Research Topics (TAKEN)
  • Specific agile life cycles (except for Extreme Programming)
    • Scrum (TAKEN)
  • Software Engineering in the Aerospace Industry (TAKEN)
  • The Wide Finder Project by Tim Bray (TAKEN)
  • Rich Internet Applications (TAKEN)
  • Distributed configuration management systems: git, mercurial, etc.
    • git (TAKEN)
    • mercurial (TAKEN)
  • Continuous build systems (TAKEN)
  • Testing frameworks (TAKEN)
  • Concurrency Frameworks
    • java.util.concurrent (TAKEN)
    • C++ concurrency framework (TAKEN)
    • Grand Central Dispatch (TAKEN)
    • Python's multiprocessing module (TAKEN)
  • Model-Based Software Engineering: Pick a model and present....
    • One student is looking for a specific model now.
  • Software Disasters: Lessons Learned (TAKEN)
  • Web Application Frameworks
    • Spring MVC (TAKEN)
    • Drupal (TAKEN)
  • Software Security (TAKEN)
  • Software Architecture (TAKEN)
  • Enterprise System Development
  • Software as a Service (SaaS) (TAKEN)
  • Service-Oriented Architecture (SOA) (TAKEN)
  • Compare/Contrast of modern integrated development environments (TAKEN)
  • Software Design Techniques (TAKEN)
  • Virtual Development Teams (TAKEN)
  • Team Structures for Software Development Teams (TAKEN)
  • Software Metrics (TAKEN)

or propose your own...

Kenneth M. Anderson, 2010.