in c# please

thank you

Grading Rubric: 75% for the UML class diagram and design, 25% for the code. Create a class diagram for Banner, the system you use for activities such as registering for courses. You can use NClass or any other diagramming tool of your choice. The UML diagram should include: class names, class fields/attributes, class methods, constructors, and any subclass / superclass relationships you see. (Hint: look for nouns (classes) and verbs (methods)) Deliverables: .ncp file or similar of the class diagram, image of the class diagram, and C# code files. The following list of requirements should be used as a basis for what is included in your class diagram: Banner enables students to register for sections of courses. Banner enables students to browse for sections of courses. Banner allows students to waitlist course sections. Banner allows students to drop course sections. Banner lets students plan future semester course schedules. Banner allows faculty to view their own schedule. Banner allows faculty to browse courses. Banner allows faculty to enter grades, such as midterm or final.. Banner allows faculty to view their own schedule. Banner allows faculty to view their courses' waitlists. Banner allows faculty to manage prerequisite overrides. Banner allows students to evaluate progress in their degree through DegreeWorks program evaluation Banner allows advisers to view their advisee list. Banner allows advisers to remove registration holds. Banner allows advisers to view student profiles. Banner allows advisers to evaluate advisees' degree progress. Banner allows advisers to view advisees' current course section registrations. Design guidelines: Include at least 2 fields per class (mostly private, though some could be public, like static or const) Include at least 1 method per class(constructors do not count for your method count). For constructors, create at least one constructor per class with at least one class that has more than one constructor. Create properties to encapsulate your private fields. The property getters and setters will manage fields that should have the appropriate access modifier Consider "auto-implemented properties in C#, as many of your properties will have code beyond the basic return and assignment of the fields. You must implement at least one property that does not utilize auto-implemented properties. Create at least one example each in your classes that use the following C# concepts: const. static Create or generate C# class files to represent what you created in UML for this WebAdvisor model. I do not expect you to write your own Banner program, I am expecting you to create a fairly in-depth class diagram and create the code skeleton for the implementation of that design. The "Generate Code" feature in NClass can help you reduce the effort needed in this part. The parts of the code I expect to be most incomplete would be the methods within the classes (you can use "throw new NotlmplementedException()" to ensure code compiles). Your resulting code MUST compile. Assignment grading will strongly consider the comprehensiveness, relevance, and accuracy of your UML class diagram(s). The numerical guidelines above are very low to ensure I do not place unreasonable constraints on your design (for example, 2 fields per class). Consider the Shapes UML example from the textbook for help on what I am looking for, as well as other UML examples posted in Content in D2L (such as NClass diagrams): Shape +Calculatora Calculatorimeter Square +Legth2/$1 32 Calculateral Calculate Perimeter) Rectangle Height -Calculatora Calculatorimeter Circle +Radius Calculate Area +Calculului Ellipse SemiMejorAxis +Semi Minoris +Calculators Calculate Perimeter Calculate Perimeter Withamani Calculate Perimeter Cartel