Project Proposal

Project Title

Project Proposal

Supervisor

Pr. Waheed Javaid

Submitted by

Faizan Naeem
{AF22LTSO257 }

Abdul Wahab
{AF22LTSO260 }

Sadia Mushtaq
{AF22LTSO259 }

Areesha Ishtiaq
{AF22LTSO248 }

Campus Name,
Riphah International College, Town Ship
[Date of Submission]
Project Proposal
 Project Proposal

Project Registration
Project ID
(for office use)
Title of Project
Type of project [ ] Traditional [ ] Industrial [ ] Continuing
Nature of project [ ] Development [ ] Research [ ] Survey
Area of specialization/
Field
Project Group Members
Sr.# Reg. # Student Name CGPA Email ID Phone # Signature
(i) Group Leader

(ii)

(iii)

(iv)

(v)

Declaration: FYP group members have cleared all prerequisites courses For FYP-I as per their
degree requirements.

Supervisor Name and Signatures: Principal:

___________________________ _________________

Plagiarism Free Certificate

This is to certify that, I am ________________________ S/D/o _______________________, group
leader of FYP under registration no RIC/_______________ at Computer Science Department, Riphah
International College Lahore. I declare that my FYP proposal is checked by my supervisor and the
similarity index is ________% that is less than 20%, an acceptable limit by HEC. Report is attached
herewith as Appendix A.

Date: __/__/____ Name of Group Leader: ______________________Signature: ____________

Name of Supervisor: _____________________ Name of Principal: ______________________

Signature: _____________________ Signature: ______________________
 Project Proposal

ABSTRACT
An Abstract is a summary of the whole technical report. it’s also the last thing you will
write but comes first in the document. The Abstract tells the reader the main points
about your technical project. Readers may not have a technical background. The
Abstract gives them an overview and can help them decide which specific sections to
focus on. An academic abstract typically outlines four elements relevant to the
completed work: The development/research focus (i.e. statement of the
problem(s)/research issue(s) addressed), the methodology used, the results/findings of
the work done and the main conclusions and recommendations. Write at least 200
words as abstract of your report.
 Project Proposal

Table of Contents
Template Guide ............................................................................................................ 14
Project Proposal ..................................................................................................... 1
List of Figures ................................................................................................................ 6
List of Tables ................................................................................................................. 7
1. Introduction ......................................................................................................... 8
2. Objective ............................................................................................................. 8
3. Problem Description ........................................................................................... 8
4. Methodology ....................................................................................................... 9
5. Project Scope ...................................................................................................... 9
6. Feasibility Study ................................................................................................. 9
7. Solution Application Areas ............................................................................... 10
8. Requirements: ................................................................................................... 10
8.1. Hardware Requirements ................................................................................ 10
8.2. Software Requirements ................................................................................. 10
8.3. Stakeholders: ................................................................................................. 11
9. Tools/Technology ............................................................................................. 11
10. Expertise of the Team Members ................................................................... 11
11. Timeframe ..................................................................................................... 11
12. Risks & Issues ............................................................................................... 12
13. Milestones ..................................................................................................... 13
14. References ..................................................................................................... 13
 Project Proposal

List of Figures
Here list of figures will be listed down.

No table of figures entries found.

 Project Proposal

List of Tables
Here list of figures will be listed down.
 Project Proposal

1. Introduction
The blood bank application is a digital platform designed to streamline and facilitate
the process of blood donation and distribution. It allows users to find nearby blood
donation events, schedule appointments, and track their donation history. For blood
recipients, the app provides a centralized system to request specific blood types and
locate available units in real-time. Additionally, the application may include features
for donor registration, health screening, and notifications to keep users informed
about donation opportunities and urgent blood needs.

2. Objective
The blood bank aims to collect, test and distribute safe blood and its components
efficiently to meet medical needs while ensuring donor safety and compliance with
regulations.

3. Problem Description
Common problems faced by blood banks include:
1. Blood Shortages: Insufficient blood donations leading to shortages, especially
during emergencies or specific blood type demands.
2. Storage and Shelf Life: Challenges in maintaining proper storage conditions
and managing the shelf life of blood products to prevent wastage.
3. Testing and Screening: Ensuring accurate and timely testing for infections
and compatibility, with the risk of false results affecting the safety of
transfusions.
4. Donor Recruitment: Difficulty in consistently attracting and retaining
voluntary donors, impacting the overall blood supply.
5. Logistics and Distribution: Efficiently managing the logistics of blood
transportation to meet diverse and often urgent demands from healthcare
facilities.
6. Public Awareness: Limited public awareness and misconceptions about blood
donation, leading to a smaller donor pool.
7. Regulatory Compliance: Adhering to complex regulatory requirements and
quality standards, which may pose logistical and administrative challenges.
8. Emergency Preparedness: Ensuring readiness for sudden increases in
demand during emergencies or natural disasters.
9. Technological Integration: Incorporating and maintaining modern
technologies for efficient data management, communication, and donor
engagement.
10. Cost Management: Balancing the costs of blood collection, processing, and
storage while providing affordable and accessible services.
 Project Proposal

4. Methodology
The methodology of a blood bank involves several key processes:
1. Donor Recruitment and Registration: Implement strategies to attract and
register voluntary donors, including organizing blood donation drives,
partnering with community organizations, and maintaining a donor database.
2. Screening and Testing: Conduct thorough health screenings and tests on
donated blood to ensure it is safe for transfusion, including blood type
compatibility, infectious disease screening, and other relevant tests.
3. Blood Collection: Organize and carry out blood donation events, either at
fixed locations or through mobile units, using sterile and safe collection
methods.
4. Processing and Component Separation: Process donated blood into its
various components (red blood cells, plasma, platelets) using centrifugation
and other techniques, maximizing the utility of each donation.
5. Storage: Store blood and its components under controlled conditions,
including temperature and humidity, to maintain their viability and safety.
6. Inventory Management: Implement robust inventory management systems
to track available blood units, expiration dates, and ensure a balanced supply
to meet demand.
7. Distribution: Effectively distribute blood products to hospitals and healthcare
facilities based on their needs, employing efficient logistics and transportation
systems.
8. Quality Assurance: Adhere to stringent quality control measures, complying
with regulatory standards to guarantee the safety and efficacy of blood and
blood products.
9. Emergency Response: Develop and implement protocols for swift response
to emergencies, ensuring an immediate supply of blood during crises or
disasters.
10. Public Education: Conduct awareness campaigns to educate the public on the
importance of regular blood donation, dispel myths, and encourage a culture
of voluntary donation.

5. Project Scope
The scope of a blood bank application typically includes donor registration, login,
health record management, emergency request handling, term and condition,
languages, location, medical history and filter for selecting areas.

6. Feasibility Study
• Risks involved: The risks in blood banking include infection transmission,
transfusion reactions, bloodborne pathogen exposure, data security concerns,
 Project Proposal

supply shortages, regulatory compliance issues, donor eligibility challenges, and

potential disruptions during emergencies or natural disasters. Efforts to mitigate
these risks involve strict protocols, advanced testing, staff training, and adherence
to regulatory standards.
• Resource requirement: Developing a blood bank app requires a skilled technical
team, robust infrastructure, and cybersecurity measures to protect sensitive data.
Adequate resources for user support, integration with healthcare systems,
compliance, marketing, and continuous improvement ensure the app's success.
Community engagement initiatives are vital for user participation and promoting a
sense of social responsibility. Efficient allocation of these resources is crucial for
creating and maintaining an effective blood bank app.

7. Solution Application Areas

A blood bank app provides solutions across various key areas, including donor
management, inventory tracking, emergency requests, health records, notification
systems, educational resources, appointment reminders, community engagement, data
analytics, and integration with health systems. By addressing these aspects, the app
streamlines processes, enhances communication, and contributes to the overall
efficiency of blood banking operations.

8. Requirements:
Specify basic Hardware and Software requirements of your project. Detailed
Requirement specification will be performed later on in SRS.

8.1. Hardware Requirements

(List minimum hardware requirement to run your project on user’s side. Below
is the hardware requirement example for a website)
• Processor:
• Hard Disk:
• RAM:
• INPUT and OUTPUT:
• Any Other specific hardware requirement for your project.

8.2. Software Requirements

(List minimum software requirement to run your project on user’s side. Below
is the software requirement example for a website)
• Operating System:
• Browser:
• Any other software/Tool requirement.
 Project Proposal

8.3. Stakeholders:
Stakeholders are different people who would be interested in the software or
Stakeholders are all those with an interest or role in the project or who are
impacted by the project.
We need to understand that it is the actual user who will eventually use the
system and hence accept or reject the product. Therefore, ignoring the needs of
any user class may result in the system failure. Below picture depicts
involvement level of different categories of stakeholders. Identify your project’s
stakeholders carefully.

Figure 1.1 Stakeholders

9. Tools/Technology
Creating a blood bank app involves utilizing a stack of diverse tools and technologies.
The frontend typically employs HTML, CSS, and JavaScript, while the backend may
be built using Node.js, Python (Django or Flask), Ruby on Rails, or Java (Spring
Boot). Databases like MySQL, PostgreSQL, or MongoDB store donor and recipient
information, and servers such as Apache or Nginx handle web requests. Integration
with mapping APIs facilitates location-based donor searches, and authentication is
secured through OAuth or JWT. Cloud services like AWS or Azure provide scalable
hosting, while Git manages source code. Testing involves unit testing frameworks,
and security measures include SSL/TLS for data transmission. Payment integration (if
required) may use Stripe or PayPal, and push notifications rely on Firebase Cloud
Messaging or APNS. UI design tools like Sketch or Figma shape the app's interface,
and project management is often handled through tools like Jira or Trello. Continuous
integration tools automate build and deployment processes, documentation tools like
Swagger manage API documentation, and monitoring tools like New Relic track app
performance. Compliance with regulations such as GDPR or HIPAA is essential, and
regular backups and a recovery plan ensure data integrity
.

10. Expertise of the Team Members

Are all team members pre-equipped with the level of knowledge needed for the
successful completion of this project? Have you people studied the relevant
course by now? Is this project of equal interest to all team members?

11. Timeframe
The time frame for developing a blood bank app can vary based on factors such as the
app's complexity, features, team size, and development methodology. Typically, a
 Project Proposal

basic version of the app with essential features might take around 3 to 6 months to
develop. This includes planning, design, development, testing, and deployment
phases. For more complex apps with advanced features, the timeline could extend to 9
months or more. It's crucial to conduct thorough testing, ensure security measures,
and comply with relevant regulations, which might affect the overall development
time. Additionally, ongoing maintenance and updates are integral for the app's long-
term success.

Here is an example of a generic project plan:

[Include your Project Plan here]

12. Risks & Issues

Blood banks navigate various risks and challenges, encompassing supply shortages
due to limited donors or unexpected demand spikes, the meticulous storage and
monitoring of blood products to prevent expiration, and the necessity for rigorous
compatibility testing to avoid transfusion complications. Compliance with stringent
regulations, safeguarding sensitive donor data, and ensuring secure transportation are
crucial. Additionally, emergency preparedness, technological integration for efficient
management, donor recruitment strategies, and public education initiatives to dispel
misconceptions play vital roles. Successfully mitigating these risks demands a robust
framework involving strict protocols, advanced technologies, continual staff training,
and public engagement to maintain a safe and sustainable blood supply chain.

Project Risks
Risk Details Likelihood
[list here] [list here] [list here]

[list here] [list here] [list here]

[list here] [list here] [list here]

Project Issues
 Project Proposal

Issue Details Impact

[list here] [list here] [list here]

[list here] [list here] [list here]

[list here] [list here] [list here]

13. Milestones
Mention all major tasks/sub-tasks to be accomplished. You would use these
milestones while defining the project timeline.

14. References
Mention all the literature or web references here. The references should be
properly numbered and correctly used in the text.

Reference text should be written in quotes and indented and the references
marked in [square brackets]. “Reference material”[1].

The Reference section should be in the following fashion:

• Book: Last Name, First Name. “Tide of Book”. City: Publisher,
Copyright Date. Page numbers
• Magazine/ Newspaper Article: Author's last name, Author's first name.
"Title of article," Name of magazine/newspaper, date of
magazine/newspaper, page number(s).
• Internet Web page: Author. “Title of Web page”. Date on the page.
Company associated (if any). Date you last saw the page. URL.
• Online Magazine or Newspaper Articles: Author's last name, Author's
first name. "Title of article." Name of magazine, date of magazine, page
numbers. Reproduced in Name of Database. Library where database was
accessed, location of library. Date of access.
 Project Proposal

Template Guideline
[Note: this section is a guideline and should be removed in your documentation]

What is a Project Proposal?

A Project Proposal is a document that is written to kick-off a new project. It needs to convince a sponsor that a project needs to be
initiated to solve a particular problem or opportunity in the business.
It describes in depth, the basis upon which the project needs to be commenced, so that the sponsor fully understands why it’s
critical to the business and what is involved.
It also needs to outline the implications of not approving the project, so that the sponsor is forced to make a clear decision – to
approve the project, or not.

When do I use a Project Proposal?

Any time that you need to coordinate resources, tasks, equipment and raw materials within a specific timeframe to achieve a
particular business goal, then you should consider doing this as part of a formal project.
The first step when initiating a project is to document a Project Proposal. It helps you formalize the project so that it has a specific
vision that needs to be achieved in order to determine its success.
Ideally a Project Proposal will be written by the intended manager of the project. However sometimes it is written by a business
manager if the Project Manager is yet to be selected. It is always presented to senior management within the business for approval.
Once approved, the next step is usually to write a Business Case which justifies the project financially. Soon after that, a Project
Charter will be written based on this Project Proposal, to scope out the project and ensure that everyone is clear about what needs
to be done.

How to use this template

This document outlines the sections needed to complete a Project Proposal. You need to replace the content in each section with
your own. Each section includes completion instructions so that you know what you need to write, to fill the document in from start
to finish. You will want to remove these completion instructions as you go, to create your own customized Project Charter for your
business.

Formatting Guidelines
A separate formatting guideline is being provided to be followed to make the document formatting as per standards. All research
and project-based documentations are strictly followed by formatting standards.
 Project Proposal

APA Style Guidelines for Project Documentation

Formatting
Table of Contents
Order of Sections ...................................................................................................... 16
Margins & Page Numbers ........................................................................................ 16
Text Format ................................................................................................................ 16
Tables and Figures In-Text ...................................................................................... 16
Title Page.................................................................................................................... 16
Body ............................................................................................................................ 16
Headings..................................................................................................................... 17
Quotations .................................................................................................................. 17
References ................................................................................................................. 17
Appendices with Tables, Figures, & Illustrations ................................................. 17
Annotated Bibliography ............................................................................................ 18
Optional:...................................................................................................................... 18
Abstract ................................................................................................................... 18
Running Head ........................................................................................................ 18
 Project Proposal

Order of Sections
1. Title page including Title, Author, University and Department, Class, Instructor, and Date
2. Body (including introduction, literature review or background, discussion, and conclusion)
3. References
4. Appendices (including tables & figures)

Margins & Page Numbers

• 1 inch at top, bottom, and both sides
• Left aligned paragraphs and leave the right edge ragged (not "right justified")
• Indent first line of each paragraph 1/2 inch from left margin
• Use page numbers, including on the title page, 1/2 inch from top and flush with right margin

Text Format
• Use one of these highly readable fonts:
o Times New Roman, 12 point
o Calibri, 11 point
o Arial, 11 point
o Lucinda Sans Unicode, 10 point
o Georgia, 11 point
• Double-space and align text to the left
• Use active voice
• Don't overuse technical jargon
• No periods after a web address or DOI in the References list.

Tables and Figures In-Text

• Label tables and figures numerically (ex. Table 1)
• Give each table column a heading and use separating lines only when necessary
• Design the table and figure so that it can be understood on its own, i.e. it does not require
reference to the surrounding text to understand it
• Notes go below tables and figures

Title Page
• Include the title, your name, the class name, and the college's name
• Title should be 12 words or less and summarize the paper's main idea
• No periods or abbreviations
• Do not italicize or underline
• No quotation marks, all capital letters, or bold
• Center horizontally in upper half of the page

Body
• Align the text to the left with a 1/2-inch left indent on the first line
• Double-space
• As long as there is no Abstract, at the top of the first page, type the title of the paper, centered,
in bold, and in Sentence Case Capitalization
• Usually, include sections like these: introduction, literature review or background, discussion,
and conclusion -- but the specific organization will depend on the paper type
• Spell out long organization names and add the abbreviation in parenthesis, then just use the
abbreviation
• Spell out numbers one through nine and use a number for 10 or more
• Use a number for units of measurement, in tables, to represent statistical or math functions,
and dates or times
 Project Proposal

Headings
• Level 1: Center, bold, Title Case
• Level 2: Align left, bold, Title Case
• Level 3: Alight left, bold italics, Title Case
• Level 4: Indented 1/2", bold, Title Case, end with a period. Follow with text.
• Level 5: Indented 1/2", bold italics, Title Case, end with a period. Follow with text.

Quotations
• Include short quotations (40 words or less) in-text with quotation marks
• For quotes more than 40 words, indent the entire quote a half inch from the left margin and
double-space it with no quotation marks
• When quoting two or more paragraphs from an original source, indent the first line of each
paragraph a half inch from the left margin
• Use ellipsis (...) when omitting sections from a quote and use four periods (....) if omitting the
end section of a quote

References
Begins on a new page following the text of your paper and includes complete citations for the resources
you've used in your writing.

• References should be centered and bolded at the top of a new page

• Double-space and use hanging indents (where the first line is on the left margin and the
following lines are indented a half inch from the left)
• List authors' last name first followed by the first and middle initials (ex. Skinner, B. F.)
• Alphabetize the list by the first author's last name of of each citation (see sections 9.44-9.49)
• Capitalize only the first word, the first after a colon or em dash, and proper nouns
• Don't capitalize the second word of a hyphenated compound
• No quotation marks around titles of articles

Appendices with Tables, Figures, & Illustrations

• Include appendices only to help the reader understand, evaluate, or replicate the study or
argument
• Put each appendix on a separate page and align left
 Project Proposal

• For text, do not indent the first paragraph, but do indent the rest
• If you have only one appendix, label it "Appendix"
• If you have two or more appendices, label them "Appendix A", "Appendix B" and so forth as
they appear in the body of your paper
• Label tables and figures numerically (ex. Table 1, or Table B1 and Table B2 if Appendix B has
two tables) and describe them within the text of the appendix
• Give each table column a heading and use separating lines only when necessary
• Notes go below tables and figures (see samples on p. 210-226)

Annotated Bibliography
• Double-space the entire bibliography. Give each entry a hanging indent. In the following
annotation, indent the entire paragraph a half inch from the left margin and give the first line of
each paragraph a half inch indent. See the template document at the top of this page.
• Check with your professor for the length of the annotation and which elements you should
evaluate.

Optional:
These elements are optional, if your professor or field requires them, but they
are not required for student papers:
Abstract
• Abstract gets its own page
• Center "Abstract" heading and do not indent the first line of the text
• Summarize the main points and purpose of the paper in 150-250 words maximum
• Define abbreviations and acronyms used in the paper

Running Head
• Shorten title to 50 characters or less (counting spaces and punctuation) for the running head
• In the top margin, the running head is aligned left, with the page number aligned on the right
• On every page, put (without the brackets): [SHORTENED TITLE OF YOUR PAPER IN ALL
CAPS] [page number]