1 / 10

ENGI 2420 Structured Programming (Lab Tutorial 0)

ENGI 2420 Structured Programming (Lab Tutorial 0). Memorial University of Newfoundland. 0.1 Assignment Policy 0.2 Grading Scheme 0.3 How to use Eclipse C/C++ 0.4 How to use Teaching Machine 0.5 Web-submit. Lab Tutorial 0. 0.1 Assignment Policy. Weekly Assignments.

rhett
Download Presentation

ENGI 2420 Structured Programming (Lab Tutorial 0)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ENGI 2420Structured Programming (Lab Tutorial 0) Memorial University of Newfoundland

  2. 0.1 Assignment Policy0.2 Grading Scheme0.3 How to use Eclipse C/C++0.4 How to use Teaching Machine0.5 Web-submit Lab Tutorial 0

  3. 0.1 Assignment Policy Weekly Assignments • There will be weekly assignments • All assignments are due at 11:59 pm the day after the lab for your section • Late assignments will not be accepted except by special permission of the lecturer • Submitted electronically through the “web-submit” system • Must be submitted in ONE file called "assignn.cpp", where n is the assignment number (such as “assign0.cpp”) • Be careful to submit the correct file!

  4. 0.1 Assignment Policy Program Testing • Behavior of your submitted assignment will be checked by an automated testing program • You are responsible for testing your own program to ensure that it works correctly • the Eclipse environment with the MinGW toolchain, as available in EN-3000/3029, will be the final arbitrators of compiler

  5. 0.1 Assignment Policy Group Work • Writing and debugging your own code • Sharing of assignments or working in groups is NOT permitted • Any instances of copying will be treated as plagiarism • Note that allowing someone else to copy your assignment is treated the same as copying an assignment from someone else • However, discussing problems with others is strongly encouraged

  6. 0.2 Grading Scheme Grading Scheme • Total 10 marks graded in two parts: behavior and style • Program behavior (7 Marks) - checked by an automated testing program that will not be made available to you - tested using a standard set of test cases (also unknown to you) - your responsibility to ensure that your program works correctly in all cases • Programming style (3 Marks) - TAs will evaluate your code for style - TAs will state the reason why some marks are deducted

  7. 0.2 Grading Scheme Programming Style • Mnemonic variable and function names e.g., “avgStrideNum” for a variable meaning average-stride-number • Appropriate comment blocks for files and functions - An initial file comment block

  8. 0.2 Grading Scheme Programming Style (II) • Appropriate comment blocks for files and functions - the definitions for the function main - declarations and definitions for any other functions needed • Meaningful and balanced comments, which mean neither too little nor too much - worthless comment (e.g., x = a + 5; // assign a plus 5 to x)

  9. 0.2 Grading Scheme Programming Style (III) • Consistent and appropriate indentation (if… else, for, while, etc.) • Clean and simple structure (convoluted code is difficult to get right)

  10. 0.1 Assignment Policy0.2 Grading Scheme0.3 How to use Eclipse C/C++0.4 How to use Teaching Machine0.5 Web-submit Lab Tutorial 0

More Related