The below is a summary that you will use as a basis to make Future State models:

Pet owners can make appointments online, and change or cancel appointments online

The Receptionist can input schedule details, such as what days they are available and not available

The Veterinarian (Vet) can see the status of the appointment schedule, and can print out hard copies of the schedule

Receptionist can make changes to the schedule and to the appointments

The online system is for existing patients only

Manual processes are still needed to register new patients only

Reminders can be sent to Pet Owners by text or email

3. Class Diagram (Future State) showing all the entities/stakeholders systems/actors etc....with the relationships and multiplicities (cardinalities) between them.

1. Diagram: with a list of attributes for each class (on the diagram). An attribute is something that is tracked by the system. E.g. Address, Phone #, Credit Card, delivery preferences....this will depend on the class itself.
2. Flow chart (Future State Process) using swim lanes
3. The flow chart must be traceable to the Use Case.
4. Use at minimum start, end, process, decision symbols. Suggest using sub process.
5. How you will avoid scope and requirement creep?
6. Tasks: 1.I want changes in following class diagram as per the instruction given above which are bold and underlined. Also want flow chart diagram.
7. 

PetClinic ClinicID ClinicName PhoneNumber Pet Owner M Address Veterinarians ClientID M Appointment M Clients Name PhoneNumber Make appointment AppointmentID Schedule Address AppointmentTime at AppointmentDay M Vetavailability Works at AppointmentAvailability Make M PaymentStatus Payment Status Veterinarian M VetID Payment M VetName PhoneNumber PaymentID Schedule Address PaymentDate Works at Email appointment PaymentRef Clients Amount PaymentMode Pet M Issue Receptionist Treat PetID M Paymentdetails ReceptionistID Species Name Date OfBirth PhoneNumber Diagnosis M Owns