Docsity
Docsity
Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity

Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips
Guidelines and tips
Sell on Docsity
Sell on Docsity
Docsity AI
Docsity AI
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

Submitting Work - Section Handout - Programming Methodology- 8, Exercises of Programming Methodologies

Stanford UniversityProgramming Methodologies

Introduction to computer science - Section Handout Assignment of Programming Methodology. Submitting Work. Prof. Sahami - Stanford University

Typology: Exercises

2010/2011

Uploaded on 10/06/2011

hollyb
hollyb 🇺🇸

4.8

(44)

431 documents

1 / 2

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Mehran Sahami Handout #8
CS 106A September 26, 2007
Submitting Work
Based on a handout by Eric Roberts
This handout provides a little more background on submitting work. Remember first of
all that each assignment requires two submissions: an electronic component submitted
through Eclipse and a hardcopy component submitted in class. Whether an assignment is
submitted on time is determined by the electronic submission, which is timestamped in
the submission process. That time is based on the time on the server that receives the
assignment, so it pays to submit things with a few minutes to spare, particularly if you
discover that your computer’s clock is running slow. The hardcopy piece should be
submitted in class on the due date for the assignment, and must match the electronic
submission. It is not appropriate, for example, to submit an uncommented rough draft
early and then hand in a beautifully commented listing for your hardcopy.
Submitting the electronic component
The Stanford version of Eclipse makes submission a relatively painless process. All you
need to do is select the Submit Project entry under the Stanford menu, as you did for the
Karel assignment:
Once you click on this button, Eclipse will bring up a dialog box asking you to select a
project from your workspace, enter your SUNet ID and password, and then click on the
Finish button.
In many cases—and particularly here in the case of Assignment #1—the project file will
contain the source files for all the problems, so that a single submission is sufficient to
deliver all the files. You may, however, make new submissions by invoking the
Submit Project mechanism additional times. Your section leader will receive only the most
recent submission.
The project you submit must contain all the files necessary to run your program. These
files will typically be .java files containing programs. However, particularly if you are
extending the program (say, because you’ve added some extra features in search of a + or
++ score), you may also have some image files or audio clips that are part of the
submission as well.
pf2

Partial preview of the text

Download Submitting Work - Section Handout - Programming Methodology- 8 and more Exercises Programming Methodologies in PDF only on Docsity!

Mehran Sahami Handout # CS 106A September 26, 2007

Submitting Work

Based on a handout by Eric Roberts

This handout provides a little more background on submitting work. Remember first of all that each assignment requires two submissions: an electronic component submitted through Eclipse and a hardcopy component submitted in class. Whether an assignment is submitted on time is determined by the electronic submission, which is timestamped in the submission process. That time is based on the time on the server that receives the assignment, so it pays to submit things with a few minutes to spare, particularly if you discover that your computer’s clock is running slow. The hardcopy piece should be submitted in class on the due date for the assignment, and must match the electronic submission. It is not appropriate, for example, to submit an uncommented rough draft early and then hand in a beautifully commented listing for your hardcopy.

Submitting the electronic component

The Stanford version of Eclipse makes submission a relatively painless process. All you need to do is select the Submit Project entry under the Stanford menu, as you did for the Karel assignment:

Once you click on this button, Eclipse will bring up a dialog box asking you to select a project from your workspace, enter your SUNet ID and password, and then click on the Finish button.

In many cases—and particularly here in the case of Assignment #1—the project file will contain the source files for all the problems, so that a single submission is sufficient to deliver all the files. You may, however, make new submissions by invoking the Submit Project mechanism additional times. Your section leader will receive only the most recent submission.

The project you submit must contain all the files necessary to run your program. These files will typically be .java files containing programs. However, particularly if you are extending the program (say, because you’ve added some extra features in search of a + or ++ score), you may also have some image files or audio clips that are part of the submission as well.

Submitting the hardcopy component

The hardcopy submissions must include the following:

  1. A listing of your program. Even though you will also submit an electronic version of your code, we require you to submit a listing of that program on paper. That listing must include all the code that you have written for the assignment, but need not include files that we supply if you haven’t changed them. Your section leader will note errors and stylistic issues on the hardcopy submission and return that to you at the interactive grading session.
  2. When you submit the hardcopy part of your assignment, please be sure to include your name and your section leader’s name on the listing_._ It’s amazing how many people forget to do this. Not having these names makes it very hard for us to sort the assignments.

Program listings and sample runs are both easy to generate in Eclipse. All you need to do is select the Print command under the File menu.

Make a backup copy of your assignment

Although we work hard to keep track of all the assignments that come in, the fact that CS 106A has so many students and such a large staff means that assignments have sometimes gotten lost. If your assignment goes missing, you will need to resubmit. To make resubmission possible, you are responsible for keeping a backup copy.