i.) The use case description for the check-in patient is given below. Determine the interface
and entity classes that are required to implement the check-in patient use case. Define the
attributes (variables) of entity classes that store data or information.
Name: Check-in patient
Summary: The staff checks in a patient to the system
Actors: Staff, Health Insurance
Pre-conditions: None
Main sequence:
1. The staff checks if a patient has an appointment.
2. If the patient has an appointment, the staff enters or updates patient information to the
system, which include patient name, address, phone number, social security number and
health insurance.
3. System sends the patient’s health insurance information to the health insurance. If the
health insurance approves the patient’s doctor visit, the health insurance confirmation
number is created and sent back to the system.
4. System adds the patient name to a list of patients being served by a doctor.
Alternatives:
•If the system cannot find the patient’s appointment, the staff cancels check-in.
• If the health insurance denies the patient’s doctor visit request and patient does not want
to pay all cost, the staff cancels check-in.
• If the health insurance denies and the patient wants to pay all cost, staff adds the patient
name to a list of patients being served by a doctor.
Post-conditions: The staff has checked in a patient.
ii.) Write a program that asks the user the names of two files. The first file should be opened for
eading and the second file should be opened for writing. The program should read the
contents of the first file, change all characters to uppercase, and store the results in the
second file. The second file will be a copy of the first file, except that all the characters will
e uppercase. Use Notepad or another text editor to create the first file that stores two lines
of strings, which are used to test your program.