Bill Manaris : Spring 2017 / CITA 180 Final Project

Assigned Date: Friday, Apr. 21, 2017
Due Time: 8:00 AM
Due Date:

Last modified on April 29, 2017, at 11:37 PM (see updates)

This is an assignment that could be pursued eitheralone or in pairs.


This assignment aims to develop and apply skills in planning, designing and executing a music and/or artistic composition / performance using JythonMusic. Possible techniques and approaches in completing this project may include:


Compose a2-3 minute piece or interactive artistic experiencefor 1 or more performers. This must involve 1 or more OSC devices (see above). It may also include additional MIDI devices and or GUI interfaces.

It has to make artistic sense.

Since this is used in lieu of a final exam, you have to also submit a written report that describes it (see below).


You will submit your assignment by both handing in a printed report in class, and online via OAKS.

Be prepared to demonstrate your program in class.

Do all of the following:

  1. Hand in a printout of a report (created via Word or Google Docs). This should include:
    1. Your name, class, assignment, and title of piece.
    2. A description of your aesthetic objectives and work process.
    3. List of sounds (for those obtained from a website, include URLs), if using samples.
    4. Your final GUI (as a digital image) with caption/description, if applicable.
    5. Photographs (one or more) of your performance equipment (e.g., phone) in action (ask a friend to help you, or use a mirror). Include appropriate captions explaining what each picture shows.
    6. Your Python source code (in an Appendix).
  2. Upload the same on OAKS. There should be several files in your submission (your program, your report with the images (in PDF), and the audio material used).
  3. Be ready to demo your program in class on the day of the exam.


All your materials (see above) need to be ready on the time of the final - no late days can be used for this. This is the final exam.

Your grade will be based on how well you followed the above instructions. Also on:

Code Documentation

Follow the Golden Rule of Style: "A program should be as easy for a human being to read and understand as it is for a computer to execute." [3]

In general, you should comment any variable, obscure statement, block of code, method, and class you create.

Your comments should express why something is being done, as opposed to how the how is shown by the code.

Top Documentation

Additionally, your code should always include opening comments as follows:

#   Author:    Your names
#   Email:      Your email addresses
#   Class:      CITA 180
#   Assignment: Final Project
#   Due Date:  The assignment's due date
#   Purpose:  A full description of your program (use your own words).

#   Input:  What kinds of inputs are being used.
#  Output:  What kinds of outputs are being generated.
(Printable View of