object-oriented analysis and design.

software engineering

scenario : In an outpatient clinic automation system, the examination process begins when a patient who has previously registered in the system comes to the outpatient clinic with their identification number. A protocol is created for each patient and documents showing the protocol number are given to the patient's hand.

The patient can perform all kinds of procedures in the polyclinic with this protocol number. In this system, the scenario of creating a prescription for the patient examined by the doctor proceeds as follows; The doctor starts a new prescription creation process by entering the patient's protocol number. It enters the system by choosing one of the drug types (antibiotics, painkillers, etc.) listed by the system. Then, he chooses one and the number of drugs of that type.

The process of adding medication to the prescription should continue until the doctor sends a save prescription request. When a save recipe request is received, the system communicates with the E-Recipe system and saves the prescription in this system and displays the recipe number given to the prescription by this system on the screen. Doctors should only be able to prescribe drugs for diseases in their area of expertise.

This situation should be checked while adding a drug to the prescription, and the addition of a drug that the doctor cannot prescribe should be prevented. At the same time, not every drug can be prescribed to every patient. Some drugs can be prescribed if the patient has a report for a particular disease. This control should be done for drugs that require a report while adding a drug to the prescription. If the patient does not have a report about the drug, the drug should not be added to the prescription.

Assuming that patient, drug, protocol and doctor information were created in previous processes and kept in the database, for the use case of automation named "Prescription Creation" described above;

Operational Contracts Established for Use Case:

OC1: Operation name: Create Recipe(protocolNo)

Scope: Recipe Creation Precondition:

- Last condition:

1. An object of the Recipe Creation class named ro must be created,

2. ro object must be associated with Register object,

3. A Recipe object named r must be created,

4. object ro and object r must be associated,

5. Protocol object specified by the protocolNo that comes as a parameter with the r object must be associated.

6. The properties of the r object must be initialized.

OC2: Operation name: Add drug(drugID, number)

Scope: Recipe Creation Prerequisite: A RecipeCreation object in progress must exist.

Last condition:

1. An object of the laLineItem class named province must be created,

2. ili object must be associated with Recipe object

3. The ili object is combined with the laDescription object specified by the drugID as a parameter. must be associated

4. The Quantity property of the province object must be set with the incoming quantity as a parameter.

OC3: Operation name: recipeComplete()

Scope: Recipe Creation Prerequisite: A RecipeCreation object in progress must exist.

Last condition:

1. The RecipeCreation object must be associated with the Registry object.

2. Ongoing Recipe object must be associated with the E-Prescription system

3. RecipeNo property of the ongoing Recipe object must be set

so we need to :

1- Draw the (use-case) collaboration diagram(s) by specifying the 'GRASP' patterns you use.

NOTE: GRASP patterns otherwise not excepted please

System E-perscripton System Doctor makePrescriptionCreation(protocolNo) patient information loop add medicine (MedID,count) more medicine prescription status completeTheRecipe() savePersciption(prescipiton prescriptionID prescriptionID +