Reason	Deductions	Mark	Comment
Documentation	0	5.0	Good
Block Comments	0	5.0	Good commenting
Poor Names	0	5.0	Good Naming
Poor Layout	0	5.0	Excellent Layout
Poor Structure	0	5.0	Good
Code Not Working	0	5.0	Code works fully

Your first program (4.1) is excellent.

Reason	Deductions	Mark	Comment
Documentation	0	5.0	Good
Block Comments	0	5.0	Good commenting
Poor Names	0	5.0	Good Naming
Poor Layout	0	5.0	Excellent Layout
Poor Structure	0	5.0	Good
Code Not Working	0	5.0	Code works fully

Reason	Deductions	Mark	Comment
Documentation	-1.0	5.0	4.0
Block Comments	0	4.0	Good commenting
Poor Names	0	4.0	Good Naming
Poor Layout	0	4.0	Excellent Layout
Poor Structure	0	4.0	Good
Code Not Working	0	4.0	Code works fully

Use Case names are like methods their name needs to start with a verb Also the structure of the use case diagram is not correct. Write Chapter 1 needs to be attached directly to the user for example Your class diagram is not correct as you did not use SimpleIO, you had your own GetString in your Book Class. The classes need to be a different colour to the folder

Reason	Deductions	Mark	Comment
Documentation	-1.0	4.0	Poor use case, not test plan
Block Comments	-1.0	3.0	No Class comments, poor method comment
Poor Names	0	3.0	Good Naming
Poor Layout	0	3.0	Excellent Layout
Poor Structure	-0.5	2.5	Good
Code Not Working	0	2.5	Code works fully

You have not understood how to represent your program as a use case diagram, please look at the recommended videos. Also you needed a test plan which tested that all possible outcomes work. You have created a class with a single methods. Inside that class you have two block comments which should hav suggested to you that this one method is too big, and needs splitting into three methods. Input data, calculate BMI and output results. Those could have been the use cases as well.