The computer network and application, Papers of Computer Networks

We have different topics covered including the introduction, summary important rules

Typology: Papers

2020/2021

Uploaded on 10/16/2023

sharmeen-amir-1
sharmeen-amir-1 🇵🇰

1 document

1 / 9

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Introduction
We are making Online Clinic Management system in which patient visits the Online Clinic Management
system. A patient needs to login into the portal first. If the patient is new, then the patient must register
with the portal. After login patient views the department and doctors for an appointment, he sees the
schedule of the doctor and selects the appropriate date and time then proceeds to confirmation of
booking and payment. Patients can view and edit appointments, also upload, and view reports, can
download and view prescriptions on the portal.
A patient can update profile as well. The doctor can login and manage the appointment schedule, doctor
view patient appointments, and send the confirmation notification to the patient. The doctor can
manage prescriptions and reports. Admin can manage doctor's and patient's profiles, will manage clinic
departments, and assign departments to doctors.
We have selected this to make it an automated Online Clinic Management system, make it easy to
access the patient, doctor at its place, and to keep the record and history at each level. Proper
systemization of work will be done.
Roles & Responsibilities
Our Product owner is responsible for continuous inspection of the product backlog and can re-prioritize
the items based on the production requirements. During every sprint, the Scrum squad remarks to him
so that he can then determine whether to dispatch the outcome or product to the customer or to make
similar modifications earlier than the outcome go out. He will be engaged in client acceptance testing as
the outcome or product is being developed to get an early perception of the outcome or product so that
any alterations are achieved early in the improvement alternatively than later.
Our Scrum Master is accountable to get the required have faith the Scrum Master ought to have no line-
management accountability for one of the crew members.
He has countless necessary responsibilities:
He will be appearing as a Guard in the Scrum Team from exterior requests and disruptions. He will be
performing as an exchange agent and adapt strategies to maximize the productiveness of the team. He
will additionally train the Scrum Team and do away with impediments for the Scrum Team. He is
additionally accountable to make certain environment-friendly conversations between the Scrum Team
and the Scrum Product Owner. Moreover, he will be facilitating several Scrum Events.
Our Tech Lead will be performing as a technical chief of the improvement group with an enormous
technical background. He is accountable for the normal dash or generation consequence, and he will
make use of the project’s satisfactory practices and coding standards. He will put together and assist the
crew to prepare the design; must have a very correct grasp of the task architecture. He will be checking
the coding and unit trying out and additionally habits a peer overview and supply feedback. He is
accountable to take away the technical impediments. He is accountable for replacing the dash tracker
with accurate records to perceive the chance and problems proactively at the dash level. He is
accountable for continuously searching for approaches to make bigger the team’s velocity/productivity
through eliminates waste.
pf3
pf4
pf5
pf8
pf9

Partial preview of the text

Download The computer network and application and more Papers Computer Networks in PDF only on Docsity!

Introduction We are making Online Clinic Management system in which patient visits the Online Clinic Management system. A patient needs to login into the portal first. If the patient is new, then the patient must register with the portal. After login patient views the department and doctors for an appointment, he sees the schedule of the doctor and selects the appropriate date and time then proceeds to confirmation of booking and payment. Patients can view and edit appointments, also upload, and view reports, can download and view prescriptions on the portal. A patient can update profile as well. The doctor can login and manage the appointment schedule, doctor view patient appointments, and send the confirmation notification to the patient. The doctor can manage prescriptions and reports. Admin can manage doctor's and patient's profiles, will manage clinic departments, and assign departments to doctors. We have selected this to make it an automated Online Clinic Management system, make it easy to access the patient, doctor at its place, and to keep the record and history at each level. Proper systemization of work will be done. Roles & Responsibilities Our Product owner is responsible for continuous inspection of the product backlog and can re-prioritize the items based on the production requirements. During every sprint, the Scrum squad remarks to him so that he can then determine whether to dispatch the outcome or product to the customer or to make similar modifications earlier than the outcome go out. He will be engaged in client acceptance testing as the outcome or product is being developed to get an early perception of the outcome or product so that any alterations are achieved early in the improvement alternatively than later. Our Scrum Master is accountable to get the required have faith the Scrum Master ought to have no line- management accountability for one of the crew members. He has countless necessary responsibilities: He will be appearing as a Guard in the Scrum Team from exterior requests and disruptions. He will be performing as an exchange agent and adapt strategies to maximize the productiveness of the team. He will additionally train the Scrum Team and do away with impediments for the Scrum Team. He is additionally accountable to make certain environment-friendly conversations between the Scrum Team and the Scrum Product Owner. Moreover, he will be facilitating several Scrum Events. Our Tech Lead will be performing as a technical chief of the improvement group with an enormous technical background. He is accountable for the normal dash or generation consequence, and he will make use of the project’s satisfactory practices and coding standards. He will put together and assist the crew to prepare the design; must have a very correct grasp of the task architecture. He will be checking the coding and unit trying out and additionally habits a peer overview and supply feedback. He is accountable to take away the technical impediments. He is accountable for replacing the dash tracker with accurate records to perceive the chance and problems proactively at the dash level. He is accountable for continuously searching for approaches to make bigger the team’s velocity/productivity through eliminates waste.

Our Developer is responsible for creating the project deliverables, together with the rest of the Scrum team. He is responsible to attend daily scrum meetings reporting the planned tasks for each day. He is responsible to assure to Product Owner and Scrum Master that the allocated work is being performed as planned. He is responsible to Provide inputs on the creation of User Stories to the Product Owner. He is responsible to understand the User Stories. He is responsible to estimate User Stories approved by the Product Owner. He is responsible to commit User Stories to be done in a sprint and develop the list of tasks based on the User Story. He is responsible to report to the Scrum Master impediments to the progress of the project. He is responsible to agree on the length of a sprint with the other Scrum Team members. He is responsible to develop the Sprint Backlog, create the deliverables, and, Scrum Board, and Impediment Log. He is responsible to participate in Prioritized Product Backlog Review Meetings. He is responsible to participate in the Retrospect Project Meetings as well. Our Software Tester is accountable for accepting, implementing, and updating the Agile Test approach. He will be functioning with Product Owners to sketch acceptance criteria and the DoD Definition of Done. He is accountable for measuring and reporting look at insurance throughout all relevant insurance dimensions, ensuring suited use of trying out tools. He is accountable for configuring, using, and managing check environments and looks at data. He is accountable for writing and executing computerized tests and reporting returned to the team. He is accountable for reporting defects and working with the group to unravel them. He is accountable for teaching different crew individuals in applicable components of testing. He is accountable for making sure the gorgeous trying-out duties are scheduled at some point of launch and new release planning. He is accountable for taking part proactively in each day's standup meetings, story grooming sessions, crew retrospectives, suggesting and imposing improvements. Our dash purpose is to strengthen the software program rapidly. How did you secure the commitment that you made at the start of your project? As we know that commitment is of vital significance to the execution of a project team. The successful project leader develops commitment through supporting and innovating behaviors. We centered on what was once important, confirmed through examples, profitable contribution and outcomes, and managed disrespect. We searched for improvements, resolved difficult expectations in an open environment, and encouraged risk-taking. Our entire group mission contributors exercised the dedication which constructed behaviors which is very necessary in a team we equipped values, and made greater management, project goals and tasks, the task squad which are our members. We also overcome obstacles and worked through all conflicts jointly as a team. Product backlog Admin Doctor Patient i. Admin Login ii. Admin Set Payment method iii. Admin Manage website setting iv. Admin Manage department v. Admin Forget password i. Doctor Forget password ii. Doctor Change password iii. Doctor Manage Prescription iv. Doctor View Consultations i. Patient Give Feedback ii. Patient View prescription iii. Patient Registration iv. Patient Submit payment v. Patient Book appointment vi. Patient View doctor

it had been hundreds a trade-off, and thus the complete cluster desired to weight the professionals and cons primarily based whole on the merchandise timetable and complexity. So, our product owner, commencement master, and commencement team worked to entire a particular product addition. throughout a sprint, work was achieved to make new points primarily based whole on the person testimonies and backlog. By making each Sprint the identical length, our scrum team discovered its very own potential for work. Estimations & deviations We have decided to work in to three sprints and then we have split the tasks on each sprint and made them the priority. Sprint 1 No# User Story Estimate days Priority 1 As an Admin I shall be able to login so that I can view dashboard section. 1 1 - Very High 2 As an Admin I shall be able to view a dashboard where I can manage all the website. 1 2 - High 3 As an Admin I shall be able to logout so that no one can access my account. 1 3- Medium 4 As a Doctor I shall be able to register so that the account is created. 1 1 - Very High 5 As a Doctor I shall be able to view a dashboard where I can manage all the Patient. 1 2 - High 6 As a doctor I shall be able to login so that I can provide consultation to patients. 1 1 - Very High 7 As a doctor I shall be able to manage my information so that it patient view it. 1 4- Low 8 As a doctor I shall be able to logout so that no one can access my account 1 3- Medium 9 As a Patient I shall be able to register myself at the online Registration so that I can get appointment and view doctors details 1 1 - Very High 10 As a Patient I shall be able to login so that I can view the dashboard and doctor. 1 2 - High 11 As a Patient I shall be able to logout so that no one can access my account. 1 3- Medium 11

Sprint 2 Sprint 3 No# User Story Estimate days Priority 1 As an Admin I shall be able can change password 1 1 - Very High (^2) As an Admin I shall be able to Manage doctor 1 2 - High (^3) As an Admin I shall be able to View Patient 1 3- Medium 4 As an Admin I shall be able to Set consultation fee manually 1 1 - Very High (^5) As an Admin I shall be able to view Consultation 1 2 - High (^6) As a Patient I can manage forget password 1 1 - Very High (^7) As a Patient I can retrieve forget password 1 4- Low (^8) As a Patient I shall be able to get registration 1 3- Medium (^9) As a Patient I shall be able to view prescription 1 1 - Very High 10 As a Patient I shall be able to give feedback 1 2 - High (^11) As a Doctor I shall be able to set forget password 1 2 - High 12 As a Doctor I shall be able to Logout^1 1 - Very High 13 As a Doctor I shall be able to Update consultation setting 1 4- Low (^14) As a Doctor I shall be able to Manage consultations 1 3- Medium (^15) As a Doctor I shall be able to Manage Prescription 1 1 - Very High (^16) As a Doctor I shall be able to view feedback 1 2 - High 16 No# User Story Estimate days Priority (^1) Doctor can set appointments schedule 1 1 - Very High 2 Doctor can manage patient appointments^1 2 - High 3 Doctor can manage patient profile^1 3- Medium 4 Doctor can edit profile info^1 1 - Very High 5 Patient will view doctor^1 2 - High 6 Patient will book appointment^1 1 - Very High 7 Patient will submit payment^1 4- Low 8 Admin will manage website setting^1 3- Medium 9 Admin will set payment method^1 1 - Very High 10 Admin will manage department 1 2 - High 10

  1. Doctor Set Appointments Schedule
  2. Doctor Manage Patient Appointments
  3. Doctor Manage Patient profile
  4. Doctor Edit Profile info
  5. Patient View doctor
  6. Patient Book appointment
  7. Patient Submit payment Sprint 3 goals
  8. Admin Forget password
  9. Admin Logout
  10. Doctor Update consultation setting
  11. Doctor Manage Consultations
  12. Doctor Change password
  13. Admin Manage doctor
  14. Admin Set consultation fee manually
  15. Doctor View Consultations
  16. Doctor Manage Prescription
  17. Doctor Change password
  18. Doctor Forget password
  19. Patient Registration
  20. Patient View prescription
  21. Patient Give Feedback How did you secure that you reached that Sprint goal? Daily Meetings Yes, we have a tendency to have a daily project meeting, and that we continually decide the daily goals and check the sprint goals. We have a tendency to mentioned the event team issues and mentioned their solutions and check the sprint targets. What Agile testing did you use as an approach, why? As we've got a bent to worked in many sprints therefore initial to envision each module, we've got a bent to use the unit testing thus every single module are going to be tested with none error we have a tendency to square measure able to proceeded. aside from the unit testing we've got a bent to performed the acceptance testing by showing it to shopper as we've got a bent to previously mentioned in Defense (approved by customer). Load testing is in addition utilized in our project to envision what share users it'll bear. What information you got from your testing? was it useful or not? The information that we tend to got when the take a look is beneficial as we tend to need to grasp that our all the test cases we've written area unit tested properly and performed well and there's no uncertainty whereas performing arts the load testing. What activities was performed and why these were done and if they were done when it was needed? There are many activities done this project which is necessarily needed that are as following.

 Firstly, the very first activity to make up a group of people to working in the team which also leads to the scrum lead as well. In this team we defined different roles to every single person in the team so that everyone can work accordingly. We have different roles in our team such as the product owner, scrum master, developer, and software tester.  After that we divided out work in the sprints so that our work is done iteratively, and risks can be measured side by side after the testing is done on each sprint. In our project work has been done in the following sprints.  Sprint 1: While using the agile technique a project owner will be discussing to accomplish the project with the scrum master. Project owner will be informing him of the requirements of the project. And Scrum master will be describing the backlog and will discuss the sprint 1 tasks with the team lead. After that team lead will communicate all tasks with his team and discuss the progress of the work with the scrum master. Our developer and the software tester will follow the team lead to-do list of tasks. In sprint following are the activities done by the doctor, patient and admin: Admin : login, view dashboard, manage doctor (create, edit, delete), logout. Patient : Registration, login, view dashboard, manage password (forget, reset), logout. Doctor : Registration, login, view dashboard, logout.  Sprint 2: Like sprint 1 there are also different activities perform by the doctor, patient, and admin. Admin : manage website setting, set payment method, and manage departments. Patient : view doctor, book appointment and submit payment Doctor: set appointment schedule, manage patient appointments, manage patient profile, and edit patient profile.  Sprint 3: In the current sprint we will be completing the remain part of the project which is including some parts from the admin like admin can change password, Manage doctor, View Patient. We have remained section from Patient Dashboard like change password, forget password, View prescription, The Doctor: s Dashboard parts like forget password, Update consultation setting, manage consultations, Manage Prescription will be completed in the current sprint Admin : change password, manage doctor, view patient, set consultation fee, view consultation. Patient : manage and retrieve forget password, get registration, view prescription, and give password. Doctor: set forget password, logout, update consultation settings, manage consultations, manage prescription, and view feedback. What risks you saw and how you treated them?  The first risk we saw in this online clinic management system is that online health organizations move to electronic attention records has created new patient privacy exposures as records are additional simply accessed by consultants, vendors and alternative third parties for economical operation, and targeted by cyber criminals. So this risk has treated in this project as the only admin registers the doctors and patients and manage their records no one other allowed to view the details and to access the patient or doctor.  The other risk we saw that the negotiation of person on the payment to the doctor which can lead disruption to this management so for this we limit the payment setting to admin without any negotiation and having the fix the fee of consultation. How you secured the quality of your product or service?