Spring2015.CITA180Homework2 History

Show minor edits - Show changes to output

Added lines 7-10:
!!Assignment

Find a complete, interesting melody. Transcribe it using Python in JEM.
Deleted lines 23-26:

!!Assignment

Find a complete, interesting melody. Transcribe it using Python in JEM.
Changed lines 7-11 from:
!!Purpose

This
assignment focuses on:

* creating an interesting melody with JythonMusic
to:
!!Learning Objectives

This
assignment has the following objectives:

* Understand the fundamentals of music theory.
* Analyze music and create musical studies modeled on pre-existing works.
* Apply numeric and string data types to represent information.
* Use variables in program development.
* Use predefined classes in program development (object-based programming).

Also how to:

* Create
an interesting melody with JythonMusic
Changed line 3 from:
'''Due Time''': 9:20 am
to:
'''Due Time''': 9:20 AM
Changed line 3 from:
'''Due Time''': 9:20
to:
'''Due Time''': 9:20 am
Added lines 1-49:
'''Assigned Date''': Wednesday, Feb. 4, 2015\\
'''Due Date''': Monday, Feb. 9, 2015\\
'''Due Time''': 9:20

Last modified on {$LastModified} (see [[http://www.cs.cofc.edu/~manaris/index.php/Spring2015.CITA180Homework2?action=diff&source=n&minor=n | updates]])

!!Purpose

This assignment focuses on:

* creating an interesting melody with JythonMusic

!!Assignment

Find a complete, interesting melody. Transcribe it using Python in JEM.

!!Documentation

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." [1]

In general, you should comment any variable, obscure statement, block of code, etc. you create.

Follow the documentation instructions from [[http://www.cs.cofc.edu/~manaris/?n=Spring2015.CITA180Homework1?action=print | Homework 1]]. In particular, your header documentation should mention the name of the piece where the melody comes from, and, if you used a score available on-line, include the URL where the score can be found.

!!Bonus

Once you complete the above, feel free to do additional work, for bonus points:

# Any other idea you can think of (just document your idea in the program's comments, so that I'll know what you are trying to do, when I am grading).

!!Submissions

You will submit your assignment via [[https://lms.cofc.edu/ | OAKS]]. Be prepared to demo your music to the rest of the class. Your submission consists of:

# Your Python program. Give it a meaningful name, e.g., '''furElise.py'''.

# A printout of your program - to be submitted in class on the due date.

# Be ready to perform it in class.

# If you do the bonus, submit a separate, additional program. Give the program a different meaningful name.

!!Grading

Your grade will be based on how well you followed the above instructions, and the depth/quality of your work.

!!Reference

# Cooper, D. and Clancy, M. (1985) "Oh! Pascal", 2nd ed., W.W. Norton & Company, New York, p. 42.