You are on page 1of 1

Lab report

1. Assignment Number: State as in Moodle, e.g. LA1.1.1, LA1.1.2 etc.

2. Problem statement: Elaborate descriptions should be skipped, and usually the first
2-3 lines in the LA problem statement should be okay.

3. Class Diagram:
Refer a sample with explanation.

4. Logic: Use class / instance variable / method names from the class diagram for stating the
computation logic. Write an algorithm/flowchart/pseudocode and / or their combination as
per your convenience. No credit for rewriting the code.

5. Inputs, Outputs and Error handling: 


Inputs for the e.g. n (int)
program
Expected Outputs e.g, factorial (int)
from the program
Error handling (for e.g. Display error when n < 0
preventing wrong
data processing)

6. Test cases and results:


SL Test Case Expected Observed Status
Result Result
1 Must start with a verb with Expected result Observed result Status should be
test data as applicable, e.g. when the after running Ok / Failed, e.g.
enter n value as 4) program will be the program, Ok for this test
run, e.g. e.g. factorial case as expected
factorial output output is 24 result and
should be 24 observed result
have matched
2 .. .. .. ..

7. Conclusion 
- State the theoretical concepts you have learnt and applied under this assignment.
- State the ways your program could have improved; think of the best practices you have seen
in the class.

Page 1 UD/OOP/LR/v1.0

You might also like