#Requirements (5%)
#Marks Total Criterion
#3 3 Client requirements are comprehensively covered
#0 2 Client requirements are accurately prioritised (e.g. must have, should have, nice to have)
#Marker feedback: Missing priorities for each requirement.
#Total: 3 / 5
#Detailed Design (10%)
#Marks Total Criterion
#2 3 Public classes are comprehensively documented, and they appear sufficient to meet majority of client requirements
#Marker feedback: Some classes have javadoc descriptions, but methods are missing documentation.
#0.5 1.5 Interactions (method calls, parameter passing) between classes are documented
#Marker feedback: No high level class diagram.
#0.5 1.5 Design and dataflow of GUI forms are comprehensively described
#Marker feedback: No GUI workflow diagrams.
#0.5 2 An appropriate network protocol for the project is comprehensively described (sufficient information to create an alternate client/server)
#Marker feedback: Network protocol documentation is incomplete, it should show each of the requests, parameters, and expected responses.
#1.5 2 An appropriate database schema for the project is comprehensively documented (sufficient information to recreate)
#Marker feedback: A graphical ER diagram would make the relationship between tables clearer.
#Total: 5 / 10
#Unit Testing (10%)
#Marks Total Criterion
#0.5 4 Black box unit tests are present and cover normal cases and boundary cases
#Marker feedback: Unit tests do not actually 'test' anything - they are devoid of JUnit assertions and catch any exceptions, meaning they will never fail
#0.5 1 Black box unit tests are present and cover exceptional cases
#Marker feedback: As above
#0.5 3 Glass box unit tests are present and achieve total code coverage over the code that can be reasonably unit tested
#Marker feedback: As above
#0 2 Mock objects are used to replace real resources (e.g. database, network connection) for the purposes of unit testing
#Marker feedback: Could not see any evidence of mocks being used.
#Total: 1.5 / 10
#Implementation (10%)
#Marks Total Criterion
#2 4 Demonstrated software is working and covers all the client's must-have requirements
#Marker feedback: Can see some requirements implemented in code, but video does not show the software functioning.
#1 2 Demonstrated software is working and covers all the client's should-have requirements
#Marker feedback: See above.
#0 1 Demonstrated software is working and covers all the client's nice-to-have requirements
#Marker feedback: See above.
#2 2 Code quality is good, without need for refactoring
#1 1 Code is appropriately commented (referring to inline comments, not JavaDoc-style as these are marked within the detailed design)
#Marker feedback: Very few high level comments.
#Total: 5 / 10
#Integration (5%)
#Marks Total Criterion
#1.5 2 Build scripts that build the software and run unit tests are demonstrated
#Marker feedback: Build script does not do packaging, run unit tests or anything else.
#1.5 3 A continuous integration pipeline that builds the software and runs unit tests is demonstrated.
#Marker feedback: CI not demonstrated in video.
#Total: 0.5 / 5
#Individual contributions (5%)
#Marks Total Criterion
#1 1 Individual demonstrates that they contributed a fair portion of the work that went into the detailed design.
#1 1 Individual demonstrates that they contributed a fair portion of the work on developing unit tests.
#Marker feedback: No unit tests present.
#1 1 Individual demonstrates that they contributed a fair portion of the work on implementing the code.
#2 2 Individual demonstrates that they have a comprehensive understanding of the entire project.
#Total: 5 / 5
#Individual source control (5%)
#Marks Total Criterion
#2 2 Individual demonstrates that they have plenty of commits in the project Git log.
#Marker feedback: Git commits not shown in video.
#2 2 Individual demonstrates that they have written useful commit messages.
#Marker feedback: Git commits not shown in video.
#1 1 Individual demonstrates that they have been contributing to the repository throughout the duration of the project.
#Total: 5 / 5
#Grand total: 20 / 50
#10 / 7
#connect github and commit and push my code.
#12 / 7
#testing - multi thread
#JavaFx - Pie chart
#But did not working, Check Tomorrow
#14 / 7
#Intermediate Modification
#Individual source control is done
#Integration session is done (CI part)
#Processing #Unit-Testing #JavaFx(Pie char)
#15 / 7
#half of Unit-Testing is done (DTO is done)
#15 / 7 - Afternoon
#Unit-Test is done.
#Trying an ANT building.
#Individual source control is done.
#Individual demonstrates is clear.
#Integration part (half part).
#Integration (5%)
#Marks Total Criterion
#Build scripts that build the software and run unit tests are demonstrated
#Marker feedback: Build script does not do packaging, run unit tests or anything else.
#A continuous integration pipeline that builds the software and runs unit tests is demonstrated.
#Marker feedback: CI not demonstrated in video.
#Individual demonstrates that they have plenty of commits in the project Git log.
#Marker feedback: Git commits not shown in video.
#Individual demonstrates that they have written useful commit messages.
#Marker feedback: Git commits not shown in video.
#Individual demonstrates that they contributed a fair portion of the work on developing unit tests.
#Unit Testing (10%)
#Marks Total Criterion
#Black box unit tests are present and cover normal cases and boundary cases
#Marker feedback: Unit tests do not actually 'test' anything - they are devoid of JUnit assertions and catch any exceptions, meaning they will never fail
#Black box unit tests are present and cover exceptional cases
#Marker feedback: As above
#Glass box unit tests are present and achieve total code coverage over the code that can be reasonably unit tested
#Marker feedback: As above
#Mock objects are used to replace real resources (e.g. database, network connection) for the purposes of unit testing
#Marker feedback: Could not see any evidence of mocks being used.