Summary

In this assignment, you are required to model the dotnet Hospital Management System by developing a console application using C#.

The application should have appropriate data structures to distinguish between a Doctor, Administrator and Patient as well as store the necessary links between them (such as an appointment, between a Doctor and a Patient). You are given complete control in how you create these data structures, but guidance has been given overpage.

Objects should be stored in the system and also written to .txt files such that the system can read them in and regenerate existing objects on load. This is mandatory.

Students will need to submit the complete project folder in zip format, which will have the complete C# code, solution file, data file, etc. required to run/test the program. Any special instructions required to run the code has to be provided in a text file. Submitting a lone “ .exe” is not acceptable.

Assignment Objectives:

The purpose of this assignment is to demonstrate competence in the following skills:

•    Ensure firm understanding of the .NET framework, C# basics and C# syntax

•    Understand how the .NET framework implements OO concepts and the implications this has for new language design

•    Array and string manipulation

•    Creating custom classes and methods in C#

•    File reading, writing and manipulation in C#

•    Creating interactive console applications

•    Creating good OO design.

Program and data structures:

•    How you structure the classes in your program is your choice. One thing you are not allowed to do is make your program fully contained inside Program.cs, or any single class.

•    In the dotnet Hospital Management System, a user can log in as either a Patient, a Doctor, or an administrator. These are different roles, which would store different information, and would have a different menu. Your code structure should reflect this.

•    Additionally, your code will need to generate Appointments. An appointment would need a reference to a single Doctor and a single Patient; your code structure should reflect this. You do not need to manage Dates/times for appointments (or anywhere, for that matter) in your code. This may result in appointments being difficult to distinguish and sort; you will not be marked down for this.

•    Every patient, doctor and admin, has a unique ID. This ID should be an integer of reasonable length (5-8 digits). This can be randomly generated, or incremental, but it should be generated by the system on object creation, not chosen/inputted by the user.

Further recommendations:

•    Objects will need to be printed out one by one, it’s recommended that each data structure has a toString() function which compresses the notable data of the class into a succinct line.

•    Each role should be its own class and it should have its own MainMenu method, don’t try and create separate versions of the menu in Program.cs.

•    Don’t get confused by Administrators. Doctors and Patients can’t at any stage have “admin privileges”; the administrator is a completely separate entity.

•    You may find it useful to abstract common functionality into its own class, such as a FileManager class with static read and write methods or a Utils class which contains the methods to generate ID’s and filter lists.

Marking Guide

Below is the marking guide for this assessment. It is designed to allow you to get a Pass grade with minimal effort while still demonstrating that you understand the core principles of .NET development, to get a Distinction with reasonable effort, and to get a High Distinction with solid effort, and 100% with considerable effort. It is recommended that you pay attention to the grade distribution and work towards your own skill level.

In the demos in the lab, your code needs to be compiled in Visual Studio Community edition 2022 and then the tutor will test for normal functionality as described in the descriptions above. If your code does not compile you will receive zero marks (no exceptions).