C # - Creating an administrative system for the hospital

Closed job
agnesik
agnesik
Employer
Job category:
Desktop/web applications
Expected budget:

Negotiable

Preferable skills:
Published:
Valid until:

Job description

ASSESSMENT, IT IS NOT A COMMERCIAL PROJECT

The aim of the project is to create an administrative system for the hospital. The system is supposed to enable

users simple records of hospital employees. Each employee has a name, surname and PESEL number

as well as username and password. The system includes the following types of users: doctor,

nurse, administrator.

The doctor, apart from the standard data of each user, also has a specialty (cardiologist,

urologist, neurologist or laryngologist) and PWZ number. Doctors and nurses also have a list of theirs

24-hour on-call duty, assuming that one person may have a maximum of 10 on-call duty per month

and her on-call duty cannot take place day by day. Moreover, only one on-call duty on a given day can be held

a doctor for a given specialization (e.g. a cardiologist, urologist and ENT specialist may be on duty on a given day, but not

two cardiologists).

After starting the system, it asks for the username and password. After logging in, in the case of

doctors and nurses, it is only possible to display a list of all doctors and nurses (Name,

Name, job + possible specialization) and the roster schedule of the indicated person in a given month.

After logging in, the administrator can see all users on the list. It can also edit the data

each of them (along with the roster schedule) and add new users (including administrators)

to the system.

At the end of the program, the entire list of employees is serialized and saved to a file,

and at startup - read and deserialized.

The whole world of employees is to be modeled in a separate project (class library), and the panel

control - as a separate application (Console, Win Forms or WPF).

Required functions:

The project must follow the object-oriented programming paradigm and must use inheritance, encapsulation, abstraction and polymorphism. Moreover, it must be resistant to errors (both user and system errors, e.g. missing file).

Submitted offers 2

Add your offer or ask the client for more details