Grade % Excellent 100% Program Specifications / Correctness 50% No errors, program always works correctly and meets the specification. Mark 50 Readability 20% No errors, code is clean, understandable, and well-organized. Mark 20 Documentation 20% No errors, code is well-commented. Mark 20 Code Efficiency 5% No errors, code uses the best approach in every case.

Presentation features 1.1 Suitable signage and design 1.2 Use of a variety of Input controls. – eg: Dropdown, Radiobuttons, Text, Number. Class Operations 2.1 Use Classes to hold the methods and the variables 2.2 Use MVC Database Features 3.1 The program will have a database back end 3.2 The database must be operated on using Entity Framework, with Linq and at least one lambda. 3.3 Create a full CRUD (Create, Read, Update, and Delete) front end Observation and Explanation 4.1 The student has been observed creating the program in the class 4.2 The student has verbally explained and visually shown the program logic to the tutor, verifying a thorough understanding of the code and architecture. 4.3 The student has commented the code in important non repeating sections providing a concise explanation of what each section does using Summary and comments.

Mark 20 16 12 0 Code Efficiency 5% No errors, code uses the best approach in every case. N/A Code uses poorly-chosen approaches in at least one place. Many things in the code could have been accomplished in an easier, faster, or otherwise better fashion. Mark 5 4 3 0 Assignment Specifications 5% No errors N/A Minor details of the assignment specification are violated, such as files named incorrectly or extra instructions slightly misunderstood. Significant details of the specification are violated, such as extra instructions ignored or entirely misunderstood.

Mark 50 40 30 0 Readability 20% No errors, code is clean, understandable, and well-organized. Minor issues with layout, variable naming, or general organization. At least one major issue with layout, variable names, or organization. Major problems with at three or four of the readability subcategories. Mark 20 16 12 0 Documentation 20% No errors, code is well-commented. One or two places that could benefit from comments are missing them or the code is overly commented. Complicated lines or sections of code uncommented or lacking meaningful comments. No comments present.

Grade % Excellent 100% Adequate 80% Poor 60% Not Met 0% Program Specifications / Correctness 50% No errors, program always works correctly and meets the specification. Minor details of the program specification are violated, program functions incorrectly for some inputs. Significant details of the specification are violated, program often exhibits incorrect behaviour. Program only functions correctly in very limited cases or not at all.

Database Features 3.1 The program will have a database back end created in SQL Management Server and connected remotely to your program. 3.2 The database will contain at least 3 tables connected with relationships of sufficient complexity. 3.3 The database must be operated on using Entity Framework, with Linq and at least one lambda. Observation and Explanation 4.1 The student has been observed creating the program in the class 4.2 The student has verbally explained and visually shown the program logic to the tutor, verifying a thorough understanding of the code and architecture. 4.3 The student has commented the code in important non repeating sections providing a concise explanation of what each section does using Summary and comments.

Marking Schedule Tick Achieved Form features 1.1 Use a CRUD frontend to operate on your data with the relevant form feature Class Operations 2.1 Use Classes to hold the methods and the variables 2.2 To the best of your ability separate out the 3 layers of Presentation (stuff you see on the forms), Business (all the coding in classes) and Database (all the database calls) in their own classes. 2.3 For multiple Business classes create a folder to keep them in

Documentation 20% No errors, code is well-commented. One or two places that could benefit from comments are missing them or the code is overly commented. Complicated lines or sections of code uncommented or lacking meaningful comments. No comments present. Mark 20 16 12 0 Code Efficiency 5% No errors, code uses the best approach in every case. N/A Code uses poorly-chosen approaches in at least one place. Many things in the code could have been accomplished in an easier, faster, or otherwise better fashion.

% of Grade Excellent 100% Adequate 80% Poor 60% Not Met 0% Program Specifications / Correctness 50% No errors, program always works correctly and meets the specification. Minor details of the program specification are violated, program functions incorrectly for some inputs. Significant details of the specification are violated, program often exhibits incorrect behavior. Program only functions correctly in very limited cases or not at all. Mark 50 40 30 0 Readability 20% No errors, code is clean, understandable, and well-organized. Minor issues with layout, variable naming, or general organization. At least one major issue with layout, variable names, or organization. Major problems with at three or four of the readability subcategories.

Marking Schedule Form features 1.1 The maximum amount that can be bet for each bettor in a label 1.2 The Up/down box can only go to that maximum number for each bettor 1.3 When the Bet is laid the Name, Amount, and Dog appear on the right 1.4 When a person is out of money, they cannot bet again 1.5 When all the bettors lose (which they eventually will) the game is over Class Operations 2.1 Two classes Greyhound and Bet (Bet is optional) 2.2 An Abstract Punter class 2.3 Three inherited bettor classes Unit test 3.1 A unit test using Instantiation

Assessment conditions: This is a resource-based assessment. This means that you may have access to any relevant resources to assist you. This could include, for example, your learning materials, information on the Internet, and so on. However, all work must be your own with no assistance from any other person. Submission requirements: You’re required to upload the following on Cloud Campus: • This document, completed where appropriate • Visual Studio project files • Upload your project on Github and paste the link below