| 1 | |
| 2 | |
| 3 | '''1. Guidance for Use Case Template''' |
| 4 | |
| 5 | |
| 6 | |
| 7 | Document each use case using the template shown in the Appendix. This section provides a description of each section in the use case template. |
| 8 | |
| 9 | '''2.Use Case Identification''' |
| 10 | |
| 11 | '''2.1. Use Case ID''' |
| 12 | A use case diagram represents a set of use cases and actors and their relationships. |
| 13 | The main actors that are involved in the first use case diagram are: administrator, doctor and nurse. Every actor is related to a certain number of use cases. Every use case represents the tasks that should be performed within the application by a certain actor. Administrator is in relation with the same use cases that is the actor Doctor, this is done because the administrator at the same time can work as a doctor in a given health center. |
| 14 | 2.2. Use Case Name |
| 15 | |
| 16 | F.1 logging in into the system F.2 patient is saving with all information and if the user won’t to search the patient information it can searchfrom |
| 17 | F.3 adds new patient m the user has to write the patientID, name, surname, age and all there information about the new patient to have them in electronic |
| 18 | F.4 user can search for appointment, diagnosis, blood test analysis or to add all of them. |
| 19 | |
| 20 | |
| 21 | |
| 22 | |
| 23 | '''3. Use Case Definition''' |
| 24 | |
| 25 | ''' 3.1. Actors''' |
| 26 | |
| 27 | Actors: |
| 28 | Primary Actor: Doctor |
| 29 | -Doctor: needs no errors, fest and no easy work, having all patient information in the electronic way. |
| 30 | -Patient: wants fast exam service, not waiting, having appointment, having labs analysis in the same center. |
| 31 | -nurse: need no complicated software. |
| 32 | |
| 33 | Preconditions: Doctor is identified and authenticated. |
| 34 | Post conditions: patient is saved, patient examination is saved, appointment is allotted to save, lab analysis record can be saved. |
| 35 | |
| 36 | '''3.2. Trigger''' |
| 37 | |
| 38 | Basic Flow: |
| 39 | 1. Doctor or nurse logs in into the system. |
| 40 | 2. Doctor save the new patient |
| 41 | 3. Patient take appointment |
| 42 | 4. Doctor or nurse fined the patient by identification nr. |
| 43 | 5. Doctor gives to patient appointment |
| 44 | 6. Doctor save the examination of patient with diagnose and therapy. |
| 45 | 7. System automatically records all the saved thinks. |
| 46 | 8. Doctor gives appointment for doing the blood test. |
| 47 | 9. Patient does the blood test analysis. |
| 48 | 3.3. Description |
| 49 | |
| 50 | Login, patient save ore search, patient examination save or search, appointment allow to save or search, lab analysis record save or search. |
| 51 | |
| 52 | '''3.4. Preconditions''' |
| 53 | |
| 54 | List any activities that must take place, or any conditions that must be true, before the use case can be started. Number each precondition. Examples: |
| 55 | 1.Login |
| 56 | 2.Name surname or identification nr of patient |