Report must include: 30%

• Your report must include all items specified in the report template.

Program Design

 20%

• Divide your programs into modules or classes. A specification of a module or class should include only a description of input/output parameters of functions/methods.

• Use methods/functions. Specify preconditions and postconditions for each method/function.

• Use private data fields/variables.

• Error handing. Check for errors in the input data and logical errors.

• Readability. Your program should be well structured (split properly into classes/modules, methods/functions) and commented so that others can read, use and modify it easily.

• Conventions:

­ Choose identifiers that describe their purpose ( not literal values).

­ Use constants. For instance, do not use the number 10 inside a program but name it by

static final int important_constant = 10

#define important_constant 10

­ Use nouns for class names and verbs for method names.

 

 

Test and correctness 20%

• Provide all tests done to verify correctness of your program in the report .

• Give an explanation why you chose such tests.

Code Design 10

No Indent -5

For Loop -2

No constants -3

Exceptions not caught -5

Bad module division -5

No comments -5

No names -5

Weird stuff -3

Report 30

Item missing: -3

Assignment # missing -2

 

 

Test  20

Test: missing explanation 5

Test: missing tests (valid -5, invalid -5, random -5)

Implementation 30

Program doesn't compile -20 (10 java, 10 C)

Program crashes on valid input -10

Wrong results on valid input: -5

Missing feature -5

 

Implementation 30%

• This section would look at the effective implementation of your code. Does the code compile, does it run, does it crashes, does it give the right results, does it implements every feature?

Note: if your program doesn't run, you cannot do the tests, and that would remove an additional 20 points

 

Interface Design 10

No error recovery  -5

Bed menu interaction -5