1 / 36

Chavez, Melesan Karen De Luna, Lin Detera , Patrick Kevin Martinez, Jellene Joy

Dental Clinic Database System Functional Requirements. Chavez, Melesan Karen De Luna, Lin Detera , Patrick Kevin Martinez, Jellene Joy. Software Functions. Main Module. Options: Open Patient Module Open Transaction Module Open Financial Report Module. Patient Module. Options:

ita
Télécharger la présentation

Chavez, Melesan Karen De Luna, Lin Detera , Patrick Kevin Martinez, Jellene Joy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Dental Clinic Database System Functional Requirements Chavez, Melesan Karen De Luna, Lin Detera, Patrick Kevin Martinez, Jellene Joy

  2. Software Functions

  3. Main Module • Options: • Open Patient Module • Open Transaction Module • Open Financial Report Module

  4. Patient Module • Options: • Add Patient • Update Patient • View Individual Patient • View Patient Log • View All Patients • Search Patient

  5. Transaction Module • Options: • New Transaction • Edit Transaction • View Individual Transaction • View Transaction Log

  6. Financial Report Module • Options: • Add Financial Report • View Financial Log

  7. User Type

  8. Data files and descriptions

  9. Patient File • Contains: • Patient No. • Patient Name • Age • Gender • Address • Contact Numbers • Occupation • Dental Status

  10. Transaction File • Contains: • Transaction No. • Patient Name • Patient Contact Numbers • Patient Gender • Date of Transaction • Procedures Done • Price • Dentist

  11. Report Types and Descriptions

  12. Profit Report • Generated daily • Contains: • Date of Report • Clinic Income • Total Procedures and Transactions Made

  13. Procedures Report • Contains: • Number of Procedures • Date Done • Patient

  14. Use case diagram

  15. Use Case Diagram

  16. Use Case Descriptions

  17. Main Module • Precondition: • 1. The user has ran the software successfully. • Flow: • 1. The user will have to choose from the options presented to him. These options are the patient module, transaction module and view the financial report. • 2. The main module window will close and the window for the selected module will open. • Alternative flow: Close • 1. The user chooses to close the system. • 2. The system will shut down.

  18. Patient Module • Use Case: Add Patient • Precondition: • 1. The user selected the ‘add patient’ option from the patient module. • Flow: • 1. The user will be asked for the patient details. • 2. The user fills in the patient’s details. • 3. The user submits the form. • Alternative Flow: • 1. The user chooses to cancel the form. • 2. The system goes back to the patient module main window.

  19. Patient Module • Use Case: Add Patient • Exceptional Flow • 1. If the user fails to update one or more required fields the user will be prompted to input these information. • 2. If the user entered information that already exists in the database the system will prompt the user to edit the details. • Post condition: • 1. The patient’s information will be stored into the database.

  20. Patient Module • Use Case: Update Patient • Precondition: • 1. The user selected the patient’s profile to edit either using ‘view all patients’ function or viewing the patient’s individual profile. • 2. The user selected the ‘update patient’ option from the patient module main window. • Flow: • 1. A window will open displaying the current information of the patient. The fields containing the information are editable. • 2. The user makes necessary changes to the patient’s profile. • 3. The user saves the changes.

  21. Patient Module • Use Case: Update Patient • Alternative Flow: Cancel • 1. The user chooses to cancel the form. • 2. The system goes back to the patient module main window. • Exceptional Flow • 1. If the user fails to update one or more required fields the user will be prompted to input these information. • 2. If the user entered information that already exists in the database the system will prompt the user to edit the details. • Post condition: • 1. The changes made will be saved in the database.

  22. Patient Module • Use Case: View All patients • Precondition: • 1. The user selected the ‘view all patients’ option from the patient module main window. • Flow: • 1. The system will display the list of patients of Dental Circle Clinic. • 2. Extends (select action)  • Alternative Flow 1: View Individual Patient • 1. The user selects a patient from the list of all patients. • 2. The system goes to the ‘view individual patient’ function. • Alternative Flow 2: Back • 1. The user chooses the back option. • 2. The system goes back to the patient module main window.

  23. Patient Module • Use Case: View Individual Patient • Precondition: • 1. The user selected a patient from the ‘view all patients’ function, or used the ‘search patient’ function. • Flow: • 1. Information about the selected patient is displayed. • 2. The user will have options to choose from. These being to edit the patient’s profile, view the patient log, or to go back. • 3. Extends (select action) • Alternative Flow 1: Update patient • 1. The user will be taken to the ‘update patient’ function. • 2. The user will be able to update the patient’s profile. • Alternative Flow 2: Back • 1. The user will go back to the patient module main screen.

  24. Patient Module • Use Case: View Individual Patient • Alternative Flow 3: View patient log • 1. The system will go to the patient log function. • 2. The user will be able to view the patient’s log. • Postcondition: • 1. The patient’s profile will be displayed.

  25. Patient Module • Use Case: View Patient Log • Precondition: • 1. The user is viewing an individual patient’s profile. • 2. The user selected the ‘view patient log’ option.  • Flow: • 1. The user chooses the ‘view patient log’ option from the patient’s profile window. • 2. The user will be able to see the previous procedures • Alternative flow: Back • 1. The user chooses the back option. • 2. The system will go back to the patient’s profile window. • Postcondition: • 1. The user will be able to view previous procedures done on the patient, the date it was done, and the total amount of the procedure.

  26. Patient Module • Use Case: Search Patient • Precondition: • 1. The user selected the ‘search patient’ option from the main patient module window. • Flow: • 1. The user will be asked for the patient’s name to be searched. • 2. The system will filter the list of patients in the database and display those that match the keyword entered. • Alternative flow: Back • 1. The user will select the back option. • 2. The system will go back to the main patient window.

  27. Patient Module • Use Case: Search Patient • Exceptional flow: • 1. The user failed to enter a name on the search bar, the system will prompt the user to enter a valid keyword. • 2. No match found by the system. The system will alert the user that there is no match found on the database. • Postcondition: • 1. The system will display the list of patients that match with the keyword (patient’s name) entered by the user.

  28. Transaction Module • Use Case: New Transaction • Precondition: • 1. The user selected the ‘new transaction’ option from the transaction module window. • Flow: • 1. The system will ask the user to select the patient that is concerned with the transaction. • 2. The user will have to enter needed information (procedure done on the patient) asked by the system. • 3. The user selects the submit option. • 4. The system will automatically add other details such as the date and the price of the procedure done to the database. • 5. The system will send this information to the financial report module.

  29. Transaction Module • Use Case: New Transaction • Alternative flow: Cancel • 1. The user selects the cancel option. • 2. The system will go back to the main transaction module window. • Exceptional flow: • 1. If the user fails to enter the required field (the procedure done) being asked by the system, it will warn the user of this error and once again ask for an input.

  30. Transaction Module • Use Case: Edit Transaction • Precondition: • 1. The user is viewing an individual transaction. • 2. The user selected the ‘edit transaction’ option from the individual transaction’s window. • Flow: • 1. The previous details of the transaction will be shown in a window. The details will become editable. • 2. The user will make the necessary changes. • 3. Once done, the user will select the save option. • Alternative flow 1: Cancel • 1. The user selects the cancel option. • 2. The system will return to the main transaction window.

  31. Transaction Module • Use Case: Edit Transaction • Alternative flow 2: Delete • 1. The user chooses the ‘delete’ option. • 2. The system will delete the recorded transaction from the database. • 3. The system will update the financial report module. • Postcondition: • 1. Changes made to the transaction will be recorded in the database.

  32. Transaction Module • Use Case: View Transaction Log • Precondition: • 1. The user selected the ‘view transaction log’ option from the main transaction window. • Flow: • 1. The user will be able to view the list of all transactions made in Dental Circle Clinic. • 2. Extends (select action) • Alternative flow: Back • 1. The user selects the back option. • 2. The system will go back to the main transaction window. • Postcondition: • 1. The user is shown the list of all transactions made.

  33. Transaction Module • Use Case: View Individual Transaction • Precondition: • 1. The user selected to view an individual transaction from the list of transactions in the “view all transactions” function.  • Flow: • 1. The user selects an individual patient from the list shown. • 2. The user will be able to view the transaction details. • 3. Extends (select action) • Alternative flow 1: Edit transaction • 1. The user will select the edit transaction option. • 2. The user will go to the edit transaction function and will be able to edit the details of the transaction.

  34. Transaction Module • Use Case: View Individual Transaction • Alternative flow 2: Back • 1. The user will select the back option. • 2. The system will go back to the list of transactions. • Precondition: • 1. The user will be able to see the details of the selected transaction.

  35. Financial Report Module • Use Case: Add Financial Report • Precondition: • 1.The user has entered a new transaction. • Flow: • 1. The user has saved a new transaction from the transaction module. • 2. The system will automatically add the details of the income in the financial report. • Alternative flow: Delete • 1. The user deleted a certain transaction from the transaction module. • 2. The system will update the changes made in the financial report and save it to the database. • Postcondition: • 1. The system will have an additional log to the finance database.

  36. Financial Report Module • Use Case: View Financial Report • Precondition: • 1. The user has selected to view the financial report from the main module window. • Flow: • 1. The user will choose a certain time interval (daily, weekly, monthly, yearly). • 2. The system will display the financial report of the clinic for the certain time interval chosen. • Alternative flow: Back • 1. The user chose the “back” option. • 2. The system will return to the main module window. • Postcondition: • 1. The user will be shown the financial report of Dental Circle clinic.

More Related