Skip to content

Latest commit

 

History

History
52 lines (37 loc) · 2.78 KB

grad_assn.md

File metadata and controls

52 lines (37 loc) · 2.78 KB
Title Author
Grad Student Assignment handout
Neil Ernst

Report Due: Friday, one week after class ends, 11:59pm as a Github commit. We mark the last commit unless told otherwise.

DM me your suggested topic/format by Oct 1. I reserve the right to veto your topic.

Note:

  • Assignments are to be completed individually.
  • Format your submission as a Markdown document.

Presentation Guidelines

  • marks will be deducted if not followed
  • First page should be a cover page that indicates your name and student number, title of your project, and a table of contents for the document.
  • Include page numbers, i.e. 1 of 10 and your name
  • Include clear section headings that match the assignment description
  • Support your assertions with reference to specific lines of code or document sections. Cite this using hyperlinks. For example, "ActionView's prepare_context method has a potential buffer underflow problem"

Overview

One of:

  1. [Research] Report on a new trend in software design and archictecture. To do this, find a practitioner report/whitepaper/presentation that discusses one of the topics below. Summarize and present to the class.
  2. [Challenge] Prepare a submission to the DysDoc Declutter challenge or Summarization Challenge. Report results in class.

Possible topics:

  • software design in the software 2.0 era
  • automatically generated documentation
  • pick an existing software design paper (e.g., from MSR, ICSA, ICSE) and replicate the findings.
  • microservice migration
  • automated design problem detection
  • formal analysis of software designs with verification tools like Coq, TLA+, Alloy
  • port existing OO code to functional/prototype paradigms
  • something discussed with me in advance

Deliverables

Research Focus

  • an in-class presentation approxmiately 20 mins. Summarize the architecture concept(s) being discussed and explain the concept to the class. With my assistance, you will organize a class discussion or exercise on the topic. Your presentation should explain the concept using code examples and diagrams. Create 5 discussion questions.

Challenge Focus

  • For DysDoc focus, a design doc + a tool Omar and I can use. We will schedule a demo time in the week following end of term.

Marking Rubric

The presentation will be judged on the basis of quality (novel topic, validated conclusions, interesting insights, source material). You will also be judged based on your additional contribution to the existing blog or report.

The tool will be judged on novelty, software quality (both internal (architecture/design) and external (usability, usefulness)) and documentation support.

Hints