SoftwareEngineering En21cs301643 RiteshMalviya
SoftwareEngineering En21cs301643 RiteshMalviya
PRACTICAL FILE
SESSION
1 .
10
11
12
Practical 1: Identify the problem and solution statement for the suggested
system for relevance.
Problem Statement:
Many patients face challenges accessing timely medical care, and healthcare providers
need efficient tools to deliver remote consultations. Existing systems may lack user
friendliness, security, and seamless integration with electronic health records (EHRs),
hindering the quality of online medical consultations.
Solution Statement:
Develop an online medical consultation system that addresses these challenges and
provides a comprehensive platform for both patients and healthcare providers. The
system should offer the following key features:
1. User Registration and Authentication: Allow patients to create accounts securely and
verify healthcare providers' credentials to ensure trustworthiness.
5. Payment Processing: Enable secure online payment for consultation fees, insurance
claims, or prescription orders.
7. Medical History Management: Patients should be able to view and update their medical
history, including allergies and chronic conditions.
8. Notifications and Reminders: Send appointment reminders, medication reminders, and
followup notifications to both patients and providers.
9. Feedback and Rating System: Implement a feedback and rating system for patients to
provide reviews and ratings for healthcare providers.
10. Security and Privacy: Ensure data security, privacy, and compliance with healthcare
regulations (e.g., HIPAA) to protect patient information.
11. UserFriendly Interface: Develop a user friendly web or mobile application for easy
navigation and use by patients and healthcare providers.
12. Analytics and Reporting: Provide healthcare providers with tools to analyze
consultation data, track patient outcomes, and improve the quality of care.
Practical 2: Prepare a SRS along with functional and non functional
requirements and Use Case diagram.
1. Introduction
Purpose: The purpose of this document is to outline the requirements for the
development of an Online Medical Consultation System, providing remote healthcare
services.
Scope: This system will serve patients and healthcare providers, enabling them to
conduct secure and efficient medical consultations online.
Document Conventions: The document follows industry standard conventions for
defining requirements.
2. Functional Requirements
Appointment Scheduling
Patients can view the availability of healthcare providers and schedule appointments.
Healthcare providers can manage their appointment schedules.
Secure Communication
Secure video and text based communication tools will be available for consultations.
All communication must comply with HIPAA regulations for patient data protection.
Payment Processing
Patients can make secure online payments for consultation fees.
The system will support multiple payment gateways.
Performance Requirements
The system should support a minimum of 1,000 concurrent users.
Response times for critical functions should be within 2 seconds.
Security Requirements
The system must comply with HIPAA regulations for data security.
Data encryption must be used for all data in transit and at rest.
Scalability Requirements
The system should be scalable to accommodate an increasing number of users and
healthcare providers.
Usability Requirements
The user interface must be intuitive and user friendly.
Accessibility features must be included for users with disabilities.
Reliability Requirements
The system should have a minimum uptime of 99.9%.
Data backup and recovery procedures must be in place.
Regulatory Compliance
The system must comply with all relevant healthcare regulations and laws in the
respective regions.
4. System Architecture
The system will follow a multitier architecture, separating presentation, logic, and data
layers to ensure scalability and maintainability.
5. User interface
Detailed user interface design specifications will be created when necessary.
6. Data Requirements
Database schema and data flow diagrams will be developed.
7.External Interfaces
Integration with payment gateways will be improved.
8. Use Cases or Scenarios
Detailed use cases and scenarios can be written to describe user interactions.
12. Signature
Participants will review and sign the final SRS form to indicate their agreement to the
terms.
Practical 3: Function Oriented Data Flow Diagram.
Patient :
Doctor :
Actors (Users):
1. Book Appointment:
- Actor: Patient
- Description: Patients can request, schedule, and manage appointments with doctors.
6. Prescribe Medication:
- Actor: Doctor
- Description: Doctors can prescribe medications and treatment plans during
consultations.
7. View Prescription:
- Actors: Patient, Doctor
- Description: Both patients and doctors can view and access prescribed medications
and treatment instructions.