Computer Systems Organization (CSCI-UA-0201.001/002)
Spring 2014 -- Section 1 (Honors) and Section 2
Professor: Andrew Case

Avoid multiple exits from loops.
- The Elements of Programming Style (Kernighan & Plaugher)

General .:. Schedule .:. Assignments .:. Resources .:. Help

Cooperation and Acknowledgements

Cooperation comes in many ways. We encourage the use of proper collaboration. The following is an example to help you understand the difference between the two. If you have questions about whether something is proper or not, please ask your professor.

Collaboration

As an example, let's say a student is writing a Java swing interface for an assignment, and the student isn't able to get their component to show up in the appropriate container (window/etc.)

An improper response might be:

You need to add this line of code 'frame.add(myButton);'.
This kind of answer doesn't help the student to understand the concepts involved and will generally result in the student adding this to their code not fulling grasping why or how this code works.

A proper response might be:

In order for swing components to show up, they have to be added to the container you want them to show up in. Have you added it to a container? Take a look at this Java documentation for how to do that.
This answer doesn't directly relate to the homework assignment, rather it is just a conceptional fact about how Java works.

Acknowledgements

Diffirent assignments allow different amounts of collaboration and code re-use. If you are allowed to use source code that is not your own, or base your code on someone elses work, you are still required to provide acknowledgements for any code that has been used or any code that you may have based your code on. Here is an example of a proper acknowledgement:

/**
 * The algorithm used for drawing this Koch Snowflake is based on the work by
 * aisha91 (http://aisha91.hubpages.com/) in his/her work on 
 * http://aisha91.hubpages.com/hub/Java-Source-Code-Recursive-Snow-Flakes
 */
[... source code cut ...]


© 2010-2014 Andrew I. Case