Software Engineering (CSC-502) Dept.

of Computer Engineering

The Medi-Connect
A comprehensive report upon the Software Development Lifecycle for
the project - using the spiral methodology.

1.Extending The Medi-Connect

1. Planning Goals:
Primary Goals: Determine the core functionalities of your app, such as video
consultations, appointment scheduling, or medical records management . Success
Criteria: Define what success looks like for each feature, e.g., user satisfaction, system
reliability, and compliance with health regulations.

Scope:
In-Scope: Clearly outline features to be included in the initial release . Out-of-Scope:
Identify features or enhancements that will be considered in future updates.

Stakeholder Identification : Healthcare Providers: Include doctors, nurses, and

administrators . Patients: Potential users of the app who will interact with its features
.Regulatory Bodies: Ensure compliance with health regulations and standards .

Aside from these specifications, the ultimate goal is to both horizontally and
vertically scale the project to a growing user base with growing requirements
from the stakeholders.

2. Risk Analysis

• Risk Identification:
• Technical Risks: Challenges in implementing video streaming, integrating with
existing health systems, or ensuring app security .
• Regulatory Risks: Compliance with health data protection laws and regulations to
protect the patient details

• Operational Risks: User adoption, reliability of service, and integration with

healthcare workflows.

• Risk Mitigation : Technical Solutions: Select reliable technologies and plan for
rigorous testing.

SIGCE 1 A.Y. 2024 - 25

Software Engineering (CSC-502) Dept. of Computer Engineering

Regulatory Compliance: Consult with legal experts to ensure adherence to laws and
standards.
Operational Planning: Develop user training materials and support plans.

1.3Engineering
The following scaling ideas should be implemented:

Appwrite
fig. 1.3.1. Horizontal Scaling

fig. 1.3.2. VerticalScaling

SIGCE 2 A.Y. 2024 - 25

Software Engineering (CSC-502) Dept. of Computer Engineering

The project will be scaled in three phases, Horizontal Scaling, Vertical

Scaling and Deployment. Horizontal scaling would involve optimizing the
application’s source code without adding additional hardware cost. This would be
achieved by orchestrated Appwrite Containers using Twilio. Vertical scaling will
only be used once all efforts have been used up in horizontal scaling. This
would involve implementing auto scaling hardware allocation and creating a load
balancing system.

1.5Evaluate
The healthcare app, designed to facilitate video consultations for patients
unable to visit the hospital, can be effectively evaluated using the Spiral Model, which
emphasizes iterative development and risk management. In the initial phase,
requirements gathering and risk assessment reveal a strong need for reliable video
communication and data privacy features. Subsequent iterations involve prototyping
and user feedback, refining the interface and functionality to ensure ease of use and
adherence to healthcare regulations. Each spiral cycle focuses on addressing identified
risks and incorporating stakeholder input, leading to a robust, user-centric application
that evolves through continuous testing and improvement. This iterative approach helps
in delivering a high-quality product that meets user needs and adapts to emerging
challenges in telemedicine.
Applying the Spiral Model to the healthcare app involves iterative cycles of
planning, risk analysis, engineering, and evaluation, ensuring the app meets both
technical and user requirements effectively. In each spiral, the team revisits goals and
constraints, addressing potential risks such as data security and user experience
challenges. Early prototypes are tested with real users to gather feedback and identify
areas for improvement, allowing for continuous refinement of features like video
consultation quality and user interface design. This approach fosters flexibility, enabling
the development process to adapt to changing needs and emerging technologies in
telehealth. By integrating stakeholder feedback and addressing risks at every stage, the
Spiral Model supports the creation of a reliable and user-friendly healthcare solution.

SIGCE 3 A.Y. 2024 - 25

Software Engineering (CSC-502) Dept. of Computer Engineering
2.payment: . Requirement Analysis:
Define Needs: Identify the payment features required, such as handling one-time
payments, subscriptions, or both. Determine the types of payments (credit/debit cards,
digital wallets) and currencies supported.
Choose Payment Gateway: Select a payment gateway (e.g., Stripe, PayPal, Square) based
on transaction fees, ease of integration, and support for required payment methods.
2. Design:

User Interface: Design a user-friendly payment interface integrated into the MediConnect
application. Ensure it provides a seamless and intuitive experience for users making
payments or managing subscriptions.
Backend Architecture: Develop the backend architecture to handle payment processing,
including secure APIs for interacting with the payment gateway, transaction records, and
payment confirmation.
3. Implementation:

Payment Gateway Integration: Implement the chosen payment gateway using its SDK or
API. Ensure compliance with PCI-DSS standards for handling payment data securely.
Security Measures: Incorporate encryption (SSL/TLS) to protect data during
transmission and use tokenization to safeguard payment details. Regularly update and
patch systems to address security vulnerabilities.
4. Testing:

Sandbox Testing: Utilize the payment gateway's sandbox environment to test the
integration without real transactions. Verify that all payment functionalities (e.g.,
processing payments, handling refunds) work correctly.
End-to-End Testing: Conduct comprehensive testing to ensure the payment process is
smooth from start to finish, including error handling and user notifications.
5. Deployment:

Go Live: Deploy the payment feature to the production environment. Ensure all
components are correctly configured and functioning as expected.
Monitor and Support: Continuously monitor payment transactions for issues and provide
support to address any problems. Use tools for real-time monitoring and logging to
quickly identify and resolve issues.
6. Maintenance and Updates:

Ongoing Maintenance: Regularly review and update the payment system to adapt to new
payment methods, security standards, and user feedback.
User Feedback: Collect and analyze user feedback to improve the payment experience
and address any pain points or issues reported.

SIGCE 4 A.Y. 2024 - 25

3. Conclusion
Developing a healthcare app requires a strategic approach guided by the
Spiral Model to ensure its success. Start by establishing clear objectives and
defining the scope to focus on essential features while planning future
enhancements. Gather detailed
requirements through engagement with stakeholders, including healthcare
professionals and patients, and ensure compliance with regulations.
Conduct a
comprehensive risk analysis to identify potential challenges and develop
mitigation strategies. Create and refine prototypes iteratively to validate
requirements and improve functionality based on real-world feedback.
Develop a well-structured project
plan with timelines, milestones, resource allocation, and budget estimates to
guide development efficiently. Assess the feasibility of technical, economic,
and operational
aspects to ensure alignment with project goals. Plan for iterative development
with incremental feature releases and continuous user feedback integration.
Maintain robust documentation throughout the process to support future
maintenance and scalability.
This thorough approach helps create a healthcare app that effectively meets user
needs, adheres to industry standards, and provides valuable services like
video consultations
and patient data management.