1-Page proposal

Due Wednesday Oct 16th @ 9 am

Note: Please print out 3 copies of your proposal for Wednesday's class in addition to turning it in electronically

From this assignment, students may show...

Abstractions and Representations - Reasoning

Technical Writing - Reasoning

Documentation and Usability - Recognition

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

Motiviation and context

This writing assignment is the first of four opportunities for you to communicate what a DSL will look like for your domain. Two reasons for breaking up the writing portion into these iterative pieces are:

A note about grading/assessment

We hope you finish this course achieving the reasoning and radiant level learning objectives. At this stage, earning these objectives is aspirational; we have 2 months left in the course to grow. Not earning an achievement and receiving feedback should not feel like punishment; we hope this intention is evident by allowing future successes to earn the same objective(s).

An alternative assessment approach to achieve the same effect would have you only submit a final version for assessment, but submit rough drafts for feedback. We consider our approach to be equivalent, but with more explicit structure and expectations. Also, by allowing you to earn achievements along the way, we hope the process feels (and is) less all-or-nothing.

Please let us know if you need any additional support, and in exchange, we hope you are encouraged to take risks and explore the design space without worry.

Example proposal

This example shows the level of detail and scope expected of you for this assignment. This example does not act as paragons of reasoning or radiance mastery.

A proposal for the Timed hardware computation.

What should I turn in?

A 1-page (250 ~ 500 word) proposal describing what domain you are supporting with a DSL, what language features you are and are not providing, and why you made those decisions. Feel free to reference any material we have seen in the course. Please write mindfully by supporting claims and decisions with examples and justification wherever possible.

How will I be evaluated?

We will provide feedback with respect to the design questions your decisions address. We will be adhere to the guidelines for reasoning outlined in the grading rubric.

We will award the learning objectives if, after reading your proposal, we have follow-up questions intended to help you persue radiance for your domain. To enable this, we will need enough information, examples, and analysis to understand your claims, how they relate to ideas from the course, and where you are "drawing the line" (e.g. not overpromising). While we do not expect you to be an expert of the domain you pick, we do expect you to be able to propose an approach, in detail, for a subset of the domain you've researched.

We may not award the learning objectives if, after reading your proposal, we need to ask clarifying questions to disambiguate your claims. You are not expected to write perfect academic prose. All feedback is an opportunity for learning. This assignment's constraints (small word limit, no prescribed citation structure, hypothesis and promise rather than describing results) may be the sole reason your work does not achieve the learning objective now, but will in the later writing assignments.

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

Please print 3 copies of your proposal to bring to Wednesday's class!

Method of submission

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