Marking Scheme
Marking Scheme
Marking Scheme
Page 1 of 4
Objective: This assignment has been designed for students to apply appropriate concurrent program design methods in designing and implementing a concurrent program from a program specification.
Marking Criteria The criteria used to evaluate the assignment are as follows:
Overall program structure structure diagram Appropriateness of coding techniques used to implement design Appropriateness of the Java concurrent programming facilities used Execution of program without errors and in accordance with specification. Appropriateness of concurrent program design (basic requirements) - Finite State Processes (FSP) Appropriateness of concurrent program design (additional requirements) - Finite State Processes (FSP) Appropriateness of Class Diagram Usefulness of instructions for compiling and running the program including comment lines in source codes. Presentation of the Labelled Transition System (LTS) diagrams and LTS traces. Presentation of the source code listings except UI-related codes Reporting of appropriate tests of program execution Depth of discussion listing of section(s) that did not meet requirements and/or code extracts of sections that met requirements. Critical Appraisal
Level 3
Marking Scheme
Page 2 of 4
Performance Criteria
1.
A demonstration of your work to the lecturer. Marks will be allocated on the basis of your ability to deliver a coherent, clear and well-prepared verbal presentation of your system. To achieve a mark of: Fail: Not able to articulate and explain basic functionality of system Pass: Your delivery must be clear, but may suffer from a lack of organisation or preparation. Credit (2nd Lower): As above, plus your presentation is clear, well organised and prepared. Credit (2nd Upper): as above, plus be able to clearly answer questions from your lecturer about your system. Your examples cover the majority of the functionality of the system, and are well chosen to do so. First Class: as above, plus the presentation must have an extra spark that makes it stand out from the other presentations. This mark is reserved for presentations that are of an excellent standard. Assessment of functionality. This will be assessed by your tutor experimenting with your electronic submission. To achieve a mark of: Fail: Your system cannot compile with the command javac *.java. Pass: The system works properly having met basic requirements. . Credit (2nd Lower): As above, plus the system provides meets all expected functionality. Credit (2nd Upper): As above, plus the system is free from deadlock First Class: As above, plus the system must have an extra spark that makes it stand out from other systems. This mark is reserved for systems that have outstanding functionality, and is free from data corruption and interference. Report on Correctness. This report must provide an argument of how you know that your system behaves correctly. To receive a mark of: Fail: Your report cannot be easily read by your lecturer and has many missing parts. Pass: Your report must be easily read, informally outline the particular concurrency issues that your system faces and satisfactorily meet documentation requirements (see marking criteria). Credit (2nd Lower): As above, plus you must provide a test report or a theoretical argument (e.g. verified Finite State Processes (FSP) descriptions of your system) which shows that your system is free from data corruption and deadlock. Credit (2nd Upper): As above, plus you must provide Labelled Transition System (LTS) traces in additional to LTS diagrams that shows that your system is free from data corruption and deadlock. First Class: As above, plus the report must be among the best in the class, and must stand out from the other reports in your class.
o o o o
2.
o o o o o
3.
o o
Level 3
Marking Scheme
Page 3 of 4
Marking Scheme
Level 3
Marking Scheme
Page 4 of 4
Marks (10 marks for each criteria below) Criteria 1. Overall program structure structure diagram 2. Appropriateness of coding techniques used to implement design 3. Appropriateness of the Java concurrent programming facilities used 4. Program runs appropriately 5. Appropriateness of concurrent program design (basic requirements)- Finite State Processes (FSP) 6. Appropriateness of concurrent program design (additional requirements)- Finite State Processes (FSP) 7. Appropriateness of Class Diagram SUB-TOTAL (T1) Marks (5 marks for each criteria below) Criteria 8. Usefulness of instructions for compiling and running the program including comment lines in source codes. 9. Presentation of the Labelled Transition System (LTS) diagrams and LTS traces. 10. Presentation of the source code listings except user interface related codes 11. Reporting of appropriate tests of program execution 12. Depth of discussion listing of section(s) that did not meet requirements and/or code extracts of sections that met requirements. 13. Critical Appraisal SUB-TOTAL (T2) Total Marks = T1 + T2
Level 3
Excellent (10/9)
Good (8/7)
Average (6/5)
Poor (4/3)
Excellent (5)
Good (4)
Average (3)
Poor (2)
5*
4*
3*
2*