Recording Patient Visit
Mary will be responsible for recording the visit of every patient. The record will be costing of doctor identify, patient identity, date and time. This will allow her to get all the visit related data in future.
The primary actor of this use case is Mary.
Stakeholders and Interests
Doctor, Patient and Mary are the primary stakeholders of this use case. The interest of the patient is to check-up their health issue. The doctor’s interest is to do their job as expected. Mary’s interest is more profit.
The patient must be registered. If the patient is new, then the patient must get registered. Another condition is that at least a doctor must be present at the hospital.
Post conditions
The patient visit will be recorded into the system.
- Mary opens the system’s visit record section, the system output a form in the interface with fields to fill with doctor, patient details, date and time.
- Mary enters the details in the form and submits it, the system checks whether the patient is registered or not. If the patient is registered then system accept the form, otherwise an error message is displayed.
New patient wants to visit on urgent basis.
Mary will register the patient with only necessary details.
After the visit is over, Mary collects the additional details and submit in the system.
Student ID <Please Fill> Name <Please Fill>
Tutorial (Day/time) Group No <Please Fill>
Record Equipment Used
Short description
The doctors will record the utensils used in a treatment. The system will provide them an interface which consist of all the equipment available in the hospital. The doctor will only select the used tools.
Primary Actor
The primary actor of this use case is doctor.
Stakeholders and Interests
Doctor and Mary are the primary stakeholders of this use case. Doctor’s is that required equipment can be obtained whenever required. Mary’s interest is that she wants to have full record of all the tools used in a treatment so that she can arrange required tools in time. Literally, having the knowledge of the stock of equipment is her interest.
Preconditions
The tolls must be stored in the system database. The doctor cannot select a tool that is not recorded.
The form must recognize that the selected tool can be used in the described treatment. The system will use some codes to define which tool can be used in which treatment. In case the conditions are violated, Mary can record that herself.
Main Success Scenario
- The doctor will open the utensil used form. The system will show various fields like number of tools used. For each of the tools used, this quantity value will need to be entered.
- After the doctor submits the form, the system will check whether the input data are valid or not.
Alternative Flows of Events
In case Mary needs to store the details herself, the system will generate a form that lokks slightly different from doctors.
Mary will enter doctor details.
Reason of choosing a different tool.
Student ID <Please Fill> Name <Please Fill>
Tutorial (Day/time) Group No <Please Fill>
Equipment Used
Make Payment
Short description
The patients will make payment for their visits and treatments. The system accepts the payments in total. Such as a patient is paying for two surgeries, the system will sum the cost and accept the payment.
Primary Actor
The patient is the primary actor.
Patient and Mary are the stakeholders. Patient’s interest is in delivering the charge for the service they have received. As the business is registered and every treatment is taxable, the patients are bound to pay. Mary’s interest is making profit and growing business.
Preconditions
The patient must be registered. If the patient is new, then the patient must get registered. The patient can pay through card or cash, not by checks. If the payment is through cash then Mary must manually input the numbers of notes of each type.
Post conditions
Patient will receive an invoice in their mail regarding payment, if not then they must contact Mary.
Main Success Scenario
- Patient will scratch their card and make payment through, the system will collect the payment details from the card reader and store the details in the system.
- Mary will input the amount of cash the patient is paying such 5 notes of hundred dollars and many more. In this case, the system relies on Mary. If the total amount is less than treatment cost, the system will alter Mary and she will recorrect the digits.
In emergency, Mary can accept check. The will hold the check number and account holder name. After the check is deposited and charge is received, Mary will enter the details of the notes bank have given them and enter that detail in the system.
Student ID <Please Fill> Name <Please Fill>
Tutorial (Day/time) Group No <Please Fill>
Calculate Staff Payment
Short description
The account will check the attendance of the doctors, their basic salary, their charge for surgery and all these details will be used to calculate the salary of the doctors.
Primary Actor
The primary actor of this use case is Accountants.
Stakeholders and Interests
Doctor, Accountants and Mary are the primary stakeholders of this use case. The interest of the accountant is to do their job and progressing the business process. The doctor’s interest is to receive their money for the service they offer. Mary’s interest is giving salaries to the doctors so that they will be loyal to the hospital.
Preconditions
The doctor must have a bank account and the account number is registered in the system.
Post conditions
The account number registered in the system is valid.
Main Success Scenario
- The accountant will try to access the attendance of the doctors and a spreadsheet will be downloaded.
- The accountant will only enter the number of days the doctors were present. It is done manually because, doctors often leave early or come late. Mary decides whether to mark that present as whole day or half day.
Alternative Flows of Events
In case a doctor is present all the days in a month then system automatically collect the attendance data.
The system has predefined values of charge for surgery and other cost related details.
Based on these details, the system calculates the salary.
Payment Processing
Interviewer: Project Manager
Interviewee: Mary (Owner of the project)
Interview Setting: The location of the interview is Mary’s office. The interview started at 12 p.m. on Tuesday.
Affiliation with interviewee: The project manager is collecting the system requirements related information. Project manager talked with Mary in Group Meetings but PM wants to get all small details and attend meeting in private with Mary.
Interviewer: Do you have any experience in using Information Systems?
Interviewee: No, I have not used any IS in this organization.
Interviewer: Are comfortable with desktop applications or mobile?
Interviewee: I am comfortable with desktop application as they provide more font size, space and options.
Interviewer: Is monitoring all the information a part of your job? I mean, do you need to see patient, doctor, payment, cancel appointment and information like that?
Interviewee: I alone handle all the administrative processes. I want to take full control of my business.
Interviewer: Do you think promoting your business using the Information System is a good idea?
Interviewee: Depends on how the promotion will be done? Sending random greetings message or remind of their birthdays can be a good idea.
Interviewer: Do you want the system to cover all the organization business processes?
Interviewee: I want the system to track every processes in the organization for me.
Project management as of now winds up one of the key instruments for accomplishing operating and vital goals in the vast majority of the organizations abroad as well as in Russia too. In any case, project usage using the organization’s own assets does not generally prompt the outcomes arranged by the authority group (Niazi et al. 2016). Real reasons underlying conceivable disappointments include a sharp increase in the quantity of projects and the absence of in-house pros who can oversee projects extremely well.
Outsourcing the project will provide various advantages like following.
- The tenders can be carried out properly.
- The risk handling processes will be further enhanced as the project will be handled by experts and they adequate knowledge on these projects
- At the time managing the project, the best standards can be utilized
- Less chance of failure is the main advantage of outsourcing a project (howver, some of the projects still fail)
Instead of outsourcing the whole project, Mary can outsource only the planning, development or closing part of the project (Binder 2016). Some of the organizations often outsource for post implementation processes.
Binder, J., 2016. Global project management: communication, collaboration and management across borders. Routledge.
Hajri, I., Göknil, A. and Briand, L., 2017. A change management approach in product lines for use case-driven development and testing. In 23rd International Working Conference on Requirements Engineering: Foundation for software Quality (REFSQ 2017).
Hajri, I., Goknil, A., Briand, L.C. and Stephany, T., 2015. Applying product line use case modeling in an industrial automotive embedded system: Lessons learned and a refined approach. In Model Driven Engineering Languages and Systems (MODELS), 2015 ACM/IEEE 18th International Conference on (pp. 338-347). IEEE.
Nassif, A.B., Capretz, L.F. and Ho, D., 2016. Enhancing use case points estimation method using soft computing techniques. arXiv preprint arXiv:1612.01078.
Niazi, M., Mahmood, S., Alshayeb, M., Riaz, M.R., Faisal, K., Cerpa, N., Khan, S.U. and Richardson, I., 2016. Challenges of project management in global software development: A client-vendor analysis. Information and Software Technology, 80, pp.1-19.
Wautelet, Y. and Poelmans, S., 2017. Aligning the elements of the RUP/UML business use-case model and the BPMN business process diagram. In International Working Conference on Requirements Engineering: Foundation for Software Quality (pp. 22-30). Springer, Cham.
Wolters, D., Gerth, C. and Engels, G., 2016. Modeling Cross-Device Systems with Use Case Diagrams. In CAiSE Forum (pp. 89-96).
Yue, T., Briand, L.C. and Labiche, Y., 2015. aToucan: an automated framework to derive UML analysis models from use case models. ACM Transactions on Software Engineering and Methodology (TOSEM), 24(3), p.13.
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
