PetAid Online Is An Web Based Service Project Report
PetAid Online Is An Web Based Service Project Report
Students Details
Name ID
Mahamudul Hasan Ashik- - 221002265
Mahabubur Rahaman Shovo- - 221002281
Mijanur Rahman - - 221002527
Submission Date:23-12-24
Teacher Name : Md. Shoab Alam
[For teachers use only: Don’t write anything inside this box]
Marks: Signature:
Comments: Date:
Contents
1 Introduction 3
1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Problem Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Literature Review 6
3 Methodology 7
3.1 SRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1.1 Functional Requirements . . . . . . . . . . . . . . . . . . . . . 8
3.1.2 Non-Functional Requirements . . . . . . . . . . . . . . . . . . 10
3.2 SDLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.1 Model Evaluation for PetAid Online Project . . . . . . . . . . 11
3.2.2 Final Selection: Iterative Model, Spiral Model, and Agile Model 13
3.3 DFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.3.1 Level 0 DFD for PetAid Online . . . . . . . . . . . . . . . . . 14
3.3.2 Level 1 DFD for PetAid Online . . . . . . . . . . . . . . . . . 16
3.4 UML Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.4.1 Core Features and Systems . . . . . . . . . . . . . . . . . . . . 21
3.4.2 Who’s Involved and How They Work Together? . . . . . . . . . 22
3.4.3 Adoption Services . . . . . . . . . . . . . . . . . . . . . . . . 23
3.4.4 Medication Guidelines . . . . . . . . . . . . . . . . . . . . . . 23
3.4.5 Education and Awareness . . . . . . . . . . . . . . . . . . . . 23
3.4.6 Relationships in PetAid Online . . . . . . . . . . . . . . . . . . 24
3.5 UML Sequence and Communication Diagram . . . . . . . . . . . . . . 25
3.6 UML Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4 Conclusion 31
1
4.1 Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.2 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.2.1 Limited Real-Time Data Collection . . . . . . . . . . . . . . . 32
4.2.2 Dependence on Internet Connectivity . . . . . . . . . . . . . . 32
4.2.3 Scalability Challenges . . . . . . . . . . . . . . . . . . . . . . 32
4.2.4 Limited Integration with External Systems . . . . . . . . . . . 32
4.2.5 Security Concerns . . . . . . . . . . . . . . . . . . . . . . . . 32
4.2.6 User Education and Engagement . . . . . . . . . . . . . . . . . 32
4.2.7 Veterinary Availability . . . . . . . . . . . . . . . . . . . . . . 33
4.3 Future Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.3.1 System Development . . . . . . . . . . . . . . . . . . . . . . . 33
4.3.2 Health Monitoring . . . . . . . . . . . . . . . . . . . . . . . . 33
4.3.3 Online Consultation Feature . . . . . . . . . . . . . . . . . . . 33
4.3.4 Data Management . . . . . . . . . . . . . . . . . . . . . . . . 33
4.3.5 Testing and Optimization . . . . . . . . . . . . . . . . . . . . . 34
4.3.6 User Feedback and Iteration . . . . . . . . . . . . . . . . . . . 34
5 References 35
2
Chapter 1
Introduction
1.1 Overview
A comprehensive web-based Web application called PetAid Online was created to as-
sist pet owners in better managing the health of their pets. The project tackles typical
pet care issues like monitoring symptoms, spotting possible illnesses, and giving appro-
priate prescription instructions. It also has features including a section for pet adoption
and rescue, online veterinary consultations, and educational materials to raise awareness
about pet care and health.
PetAid Online’s documentation process has been methodical and has complied with
the Software Development Life Cycle (SDLC). To guarantee that all project goals are
precisely stated, this entails doing a thorough requirement analysis and producing a
Software Requirements Specification (SRS) document. We created Data Flow Dia-
grams (DFDs) at levels 0, 1, and 2 to help comprehend the system’s operation and flow.
3
1.3 Motivation
The idea for PetAid Online arose from the need to address challenges faced by pet
owners and animal rescuers. The motivations are:
• To guide medication usage: Offers clear guidelines to ensure safe and proper
use of pet medicines.
Approach:
• PetAid Online was designed as a reliable platform that integrates various features
into a single system.
• The Software Development Life Cycle (SDLC) was followed, including re-
quirement analysis and preparation of a detailed SRS document.
• Diagrams such as Data Flow (DFDs) and UML models were created, including
Use Case, Sequence, and Class Diagrams, to map the system’s workflow and
functionality.
• This structured approach ensures the platform effectively tackles the problems
faced in pet care and adoption.
4
Objective
The main objectives of the PetAid Online project are as follows:
• To offer medication guidelines: Provide clear information about the proper use
of pet medicines and dosage instructions.
• To support pet adoption and rescue: Facilitate the connection between potential
adopters and available pets, as well as promote animal rescue efforts.
• To raise awareness about pet health: Educate pet owners on proper care, treat-
ment, and adoption through informative content on the platform.
To address these issues, PetAid Online was designed as a reliable platform that inte-
grates various features into a single system. By following the Software Development
Life Cycle (SDLC), the project team conducted requirement analysis, prepared a de-
tailed SRS document, and created diagrams such as Data Flow (DFDs) and UML
models including Use Case, Sequence, and Class Diagrams, which outline the sys-
tem’s workflow and functionality. This structured development approach ensures that
PetAid Online effectively tackles the problems faced in pet care and adoption.
5
Chapter 2
Literature Review
PetAid Online aims to tackle important challenges in obtaining veterinary support. Al-
though there are many online veterinarians and consultation services, the level of sup-
port available online is not always well understood. In our country, various types of
veterinary support can be found, including websites and social media platforms like
Facebook and WhatsApp. These channels mainly focus on offering assistance to pet
owners. On a global scale, many online veterinary support systems share similar goals
with our project. These systems highlight how online platforms can improve access to
veterinary care, making it simpler for pet owners to find the help they need. By utiliz-
ing these findings, PetAid Online seeks to develop a well-rounded solution that fills the
existing gaps in veterinary support.
6
Chapter 3
Methodology
3.1 SRS
7
Figure 3.2: Non Functional Requirement Di gram
• Disease Identification:
– Enable users to input symptoms and receive suggestions for possible dis-
eases their pets might have.
8
– Allow users to access the platform in "guest" mode for those needing infor-
mation or medication guidelines.
– Allow users to book virtual appointments with veterinarians for advice and
treatment.
– Enable appointment scheduling, video calls, and secure messaging between
users and veterinarians.
• Community Forum:
– Implement a community space for users to share experiences, tips, and ad-
vice on animal care and rescue.
– Create discussion threads and Q&A sections for user interaction.
– Allow users to provide feedback and rate their experiences with veterinari-
ans and platform services.
– Implement a rating system to enhance community trust and transparency.
9
3.1.2 Non-Functional Requirements
• Speed:
– The system should process user requests and return results within 2 seconds
for 95% of interactions to ensure responsiveness.
• Security:
– The system must implement SSL encryption for all data exchanges to pro-
tect sensitive information.
– Multi-factor authentication should be required for user accounts to enhance
security.
• Portability:
• Compatibility:
– The system should integrate with at least three popular pet management apps
(e.g., PetDesk, Pawtrack) through APIs for smooth data exchange.
– Ensure the platform is compatible with the latest versions of Android and
iOS for mobile applications.
• Reliability:
• Usability:
– The user interface should be intuitive, enabling users to complete tasks (e.g.,
scheduling appointments, tracking pet health) in no more than three clicks.
– Provide in-app help documentation and tutorials.
• Maintainability:
10
3.2 SDLC
Figure 3.3: Table 4.1: Comparison matrix for PetAid Online project with different
models
2. V-Model – Score: 17
• Suitability: The V-Model, like the Waterfall model, is designed for projects with
stable requirements. It excels in validation and quality assurance, making it ap-
propriate for features such as medication guidelines. However, it struggles with
flexibility, which is critical for evolving features like health tracking and symptom
identification.
• Score Rationale: While it benefits from strong documentation and validation, it
is less effective for adapting to change or addressing emerging user needs.
• Suitability: The Iterative model is well-suited for projects that require regular
updates and the integration of user feedback. PetAid Online, with its evolving
features like health tracking and medication guideline updates, would benefit
from this flexibility. The model supports a balance between iterative progress
and thorough testing, which makes it both adaptable and reliable.
11
• Score Rationale: Its strengths in flexibility, user feedback integration, and cost-
effective changes make it the best fit for the project.
• Suitability: The Spiral model emphasizes risk management and allows for it-
erative refinements. This is especially useful for high-risk components like dis-
ease tracking and medication management. However, the model can be resource-
intensive and time-consuming to implement.
• Score Rationale: Strong in risk management and flexibility but slightly more
complex and costly than the Iterative model.
• Suitability: The Agile model offers flexibility and adaptability, making it suitable
for projects requiring continuous updates and user involvement. For PetAid On-
line, it can keep features like adoption tracking and awareness campaigns aligned
with changing user demands. However, it may lack the structured documentation
necessary for accurate medical information.
• Score Rationale: Agile excels in user feedback integration and flexibility but is
less suited for maintaining detailed documentation for medical guidelines.
• Suitability: The Prototyping model allows for quick iterations and immediate
feedback, which is useful for testing features such as disease tracking. However,
it is not ideal for a fully-developed platform like PetAid Online due to its insuffi-
cient focus on detailed documentation and quality control.
12
3.2.2 Final Selection: Iterative Model, Spiral Model, and Agile
Model
Based on the evaluation, the Iterative Model (Score: 26), Spiral Model (Score: 23),
and Agile Model (Score: 19) emerge as the top choices for the PetAid Online project.
Together, these models provide a comprehensive framework that balances flexibility,
risk management, and the integration of user feedback.
Iterative Model (Score: 26) The Iterative model is ideal for projects like PetAid
Online, which require frequent updates. Its approach allows for continuous develop-
ment, enabling the team to refine features like symptom trackers and disease identifica-
tion tools based on feedback from veterinarians and pet owners. Its blend of flexibility
and structure ensures effective testing and alignment with project goals, reducing the
cost and complexity of updates.
Spiral Model (Score: 23) The Spiral model’s emphasis on risk management makes
it an excellent choice for high-risk components such as medication guidelines and health
consultation features. By incorporating risk analysis into every development cycle, this
model helps address issues like data inaccuracies early in the process. While it is more
complex and time-consuming, its ability to mitigate risks is invaluable, especially for
projects involving sensitive data.
Agile Model (Score: 19) The Agile model is known for its adaptability and rapid
user feedback incorporation, making it ideal for features like adoption and rescue data
modules, as well as awareness campaigns. Its iterative approach ensures that the plat-
form remains dynamic and responsive. While Agile’s lack of focus on detailed docu-
mentation can be a drawback for medical accuracy, combining it with more structured
models like Iterative or Spiral creates a hybrid approach that balances speed and flexi-
bility with rigorous documentation and quality control.
13
3.3 DFD
External Entities
• Pet Owners/Rescuers
• Veterinarians
• Welfare Organizations
Data Flows
• Pet Owners/Rescuers → PetAid Online System:
– Symptoms
14
– Consultation Requests
– Adoption/Rescue Details
– Disease Suggestions
– First-Aid Guidelines
– Veterinarian Responses
– Educational Content
– Consultation Requests
– Symptom Data
– Adoption Statistics
– Rescue Requests
15
3.3.2 Level 1 DFD for PetAid Online
• Pet Owners/Rescuers:
• Veterinarians:
• Welfare Organizations:
16
– Provide details about rescue/adoption support and receive updates on adop-
tion statistics and rescue requests.
Processes
Data Stores
17
– Hosts awareness materials like blogs, videos, and FAQs.
Data Flows
– Submit symptoms.
– Request consultations.
18
• Pet Owners/Rescuers → User Management:
19
3.4 UML Use Case Diagram
The sequence diagram illustrates how objects in the PetAid Online system interact
over time. It highlights the communication flow between different modules to ensure
efficient processing of user requests.
Pet Owner
Rescuer
20
Guest User
• Can access limited features without registration, such as browsing general pet
care and welfare information.
Veterinarian
Welfare Organization
Adoption System
21
Medication Guidelines
• Promotes welfare and educates users about pet care best practices.
Platform Interactions
PetAid Online Platform connects all the actors and features, ensuring smooth interac-
tions. Veterinarians and welfare organizations are integral to the system for professional
advice and collaborative welfare efforts.
Rescuers
Vets (Veterinarians)
Welfare Organizations
22
Guest Users
Health Tracking
• A pet owner or rescuer enters a pet’s symptoms (e.g., coughing, loss of appetite).
• The system processes the info and shows possible issues or diseases.
• They meet online via video calls, making it easier than visiting in person.
• If plans change, users can cancel or reschedule appointments without any fuss.
• Users can register pets for adoption, and welfare organizations help spread the
word.
23
3.4.6 Relationships in PetAid Online
• Pet Owners ↔ Vets: Pet owners rely on vets for advice, and vets depend on
accurate information from owners to help pets.
24
3.5 UML Sequence and Communication Diagram
v
25
• Adoption System: Handles adoption-related processes.
• Information Repository: Stores and retrieves data for the system.
• Back-end: Manages overall data flow and communication between modules.
The user (part-owner/rescuer) starts the process by sending health information via the
PetAidOnline User Interface.
• If the health information is insufficient (shown as else in the ALT block), the
system initiates an Online Consultation.
• The user receives recommendations based on the consultation.
• In parallel (denoted by the PAR block), the Adoption System and Medication
Guidelines modules might be accessed.
• The Adoption System stores and retrieves adoption information based on user
requests.
4.3.6 Self-Calls
Some interactions involve self-calls, where a module processes data internally before
returning a response (e.g., Online Consultation).
26
Features Highlighted
• Health Monitoring: Uses sensors to provide detailed tracking of a pet’s symp-
toms.
• Medication and Adoption Systems: Adds functionality for pet treatment and
adoption-related queries.
• Data Flow: Ensures that all user interactions result in secure data storage and
retrieval.
27
3.6 UML Class Diagram
• User (Pet Owner): Represents individuals who own pets and interact with the
system to manage health information and adoption processes.
• Pet: Represents the pet(s) owned by the user. Each pet has its own health record
and may have consultations linked to it.
• Consultation: Represents the medical or behavioral consultations that the pet
receives, such as veterinary visits or behavioral consultations.
• Adoption: Represents the process where a user adopts a pet, typically from a
shelter or rescue organization.
28
• Health Record: Represents the medical and health history of the pet, including
consultations, diagnoses, and treatments.
The User (Pet Owner) begins the process by sending health information for their pet via
the PetAidOnline User Interface. The system helps in managing the pet’s health and
other records.
• The User browses available pets, selects one for adoption, and submits an adop-
tion application.
• Upon approval, the User (Pet Owner) officially adopts the pet and becomes its
registered owner. The pet is now linked to the user.
• The Pet requires regular medical checkups, so the User schedules consultations.
• Each consultation results in an updated Health Record, which includes details of
diagnoses, treatments, and follow-up care.
• The User regularly checks the pet’s health and schedules any necessary consulta-
tions or treatments.
• Health Records are continuously updated to track the pet’s health, including di-
agnosis, treatment plans, and vaccination status.
• Every consultation leads to an updated Health Record that documents the pet’s
current health, diagnosis, and treatment.
• The system efficiently manages the health and adoption records of the pet, ensur-
ing that all interactions are well-documented.
4.3.6 Self-Calls
In some cases, internal modules within the system perform self-calls. For instance, the
Online Consultation module may handle requests internally before returning the results
to the User.
29
4.4 Features Highlighted
• Health Monitoring: Tracks the pet’s symptoms and health using sensors to pro-
vide real-time updates.
• Data Flow: Ensures that all interactions result in secure data storage and retrieval,
keeping the system organized.
30
Chapter 4
Conclusion
4.1 Discussion
The PetAid Online project follows a clear and organized approach using the Software
Development Life Cycle (SDLC) to ensure the system meets its intended goals. We
began with Requirement Analysis, where we carefully gathered information about the
system’s functionalities and documented it in the Software Requirements Specification
(SRS). This helped us understand what the system should achieve and the necessary
features.
Following the requirement gathering, we selected the appropriate SDLC Model that
would guide the entire development process, ensuring an efficient and structured work-
flow. To better understand how data flows within the system, we created Data Flow
Diagrams (DFD) at three levels (0, 1, and 2), which illustrated how information is pro-
cessed and how different components interact.
We also created a UML Use Case Diagram to represent the different actions users
can take within the system, providing a clear overview of user interactions. To further
clarify the system’s behavior, we developed a UML Sequence Diagram that shows how
different components of the system interact over time. Finally, we created a UML Class
Diagram, which helped us define the structure of the system by organizing the classes
and their relationships.
By following this structured approach, we ensured that the PetAid Online system
is designed in a clear, logical, and user-friendly way, making it easier to develop and
maintain.
4.2 Limitations
While the PetAid Online system offers a comprehensive solution for managing pet
health, adoption, and consultations, there are certain limitations that need to be ac-
knowledged. These limitations should be considered for future improvements and de-
velopment phases.
31
4.2.1 Limited Real-Time Data Collection
The system currently relies on manual input from users and external sensors for health
monitoring. Although sensors can capture valuable data, they may not always provide
real-time updates on a pet’s health status, potentially leading to delays in diagnosis or
treatment recommendations.
32
4.2.7 Veterinary Availability
The online consultation feature depends on the availability of qualified veterinarians. In
regions with a shortage of vets or those that lack online consultation infrastructure, the
system’s utility may be limited.
In conclusion, while the PetAid Online system is designed to provide comprehen-
sive solutions for pet owners, there are areas that require further development. Address-
ing these limitations will be key to enhancing the overall user experience and function-
ality of the system in the future.
33
personal information is kept safe and confidential, adhering to data protection standards.
34
Chapter 5
References
35