Outline or Annotated Bibliography

Due Friday Nov 1st @ 9 am

From this assignment, students may show...

Software Ecosystem and Development - Reasoning

Abstractions and Representations - Reasoning

Technical Writing - Reasoning

Documentation and Usability - Reasoning

Metacognition, Reflection, and Personal Growth - Reasoning

... in addition to other learning objectives students feel their work accomplishes.

Motiviation and context

Before you start writing prose, it can be helpful to have an opportunity to sketch from end to end how you think the project will go. For others, it is helpful to explore the space and evaluate other works' design decisions before deciding on your own. Matthew has seen both approaches employed in the proposals submitted for hw12-1.

So, please consider this a way to start answering questions and incorporating the feedback from hw12-1 with a little more detail, but without worry about the things we typically worry about with a formal paper (formatting, proper citations, etc.) which will be asked for in the penultimate draft.

What to turn in

Either:

An extended outline

Incorporate the feedback you received on your proposal by expanding the proposal into an outline. An outline gives the section and subsection flow of the paper, and has a short piece of text (from your proposal no doubt) to describe the section. In addition, you should annotate the sections with: Hopefully through this format, you will be able to address questions and ideas from 12-1 and be able to get specific about the parts of your language design in a flexible way.

An annotated bibliography

An annotated bibliography will consist of a collection of sources (papers, tools and existing documentation, anything) and annotations which should describe: Hopefully through this format, you will be able to address questions and ideas from the feedback you received to 12-1 and be able to narrow the scope of your project by exploring the domain.

Something else

If neither of these formats work for you, please feel free to submit some other writing artifact (e.g. an editorial response to the feedback you received to 12-1) for any learning objectives you wish to engage with.

Optional META.md

META.md should include
  1. your name
  2. your utln
  3. how much time you spent on this assignment
  4. the witness "proof" for how you earned each learning objective.

Please Submit

Contents to be submitted

Method of submission

Please commit your changes in the hw16-1 directory of your private repo and push them to the remote server before 9 am.