1 / 5

General Assignment Guidelines and Marking Scheme

General Assignment Guidelines and Marking Scheme. COMP444 – System Software Design Revision 1.0. General. There will be letter grades assigned to your assignments. If basic assignment requirements say: Do task 1 Do task 2 Do task 3

alden
Download Presentation

General Assignment Guidelines and Marking Scheme

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. General Assignment Guidelines and Marking Scheme COMP444 – System Software Design Revision 1.0 Serguei A. Mokhov, mokhov@cs.concordia.ca

  2. General • There will be letter grades assigned to your assignments. • If basic assignment requirements say: • Do task 1 • Do task 2 • Do task 3 • And you just do what it says, which is good, and what any student is expected to be able do anyway, you get a good grade of B… • In order to get A+, you must do excellently and produce high-quality work with extras; details follow. Serguei A. Mokhov, mokhov@cs.concordia.ca

  3. General (2) • Good and useful SOEN practices are in place. • READE is a must. • Makefile is a must. Serguei A. Mokhov, mokhov@cs.concordia.ca

  4. Extras • If your app gives some extra features or extensions that are logical and useful to the problem being solved, or refines gray spots in the requirements and/or design, that’s a big asset towards your app and your grade. Serguei A. Mokhov, mokhov@cs.concordia.ca

  5. Code • Naming (variables, functions, structures and types). • Modularity • Structure • NO hardcoding • Error handling (e.g. return values from all system calls). Serguei A. Mokhov, mokhov@cs.concordia.ca

More Related