Sie sind auf Seite 1von 7

ITE 1912 – ICT PROJECT

PROPOSAL
Level 01

Pharmacy Management System

Submitted by:
Navodya W L T
E1846002
Bachelor of Information Technology
(External Degree)
Faculty of Information Technology
University of Moratuwa
Table of content.

1. INTRODUCTION

1.1BACKGROUD AND MORTIVATION


1.2PROBLEM IN BREIF
1.3Aims and Objectives
1.4Summary

2. PROPOSED SYSTEM

2.1THE SCOPE OF THE PROJECT


2.2DEVELOPMENT TOOLS

3. FESIBILITIES IN THE SYSTEM

3.1TECHNICAL FESIBILITY
3.2ECONOMICAL FEASIBILITY
3.3SHEDULE FEASIBILTY
3.4OPERATIONAL FEASIBILTY
3.5 LEGAL FEASIBILIY

4. PROJECT PLANNING

4.1PROJECT SCHEDULE
4.2GRANTT CHART

5. REFEREENCE
1. Introduction

1.1 Background and Motivation

All of us has a time that we look for medicine. So, we go to the pharmacy to get medicine when
we are not feeling well. Once I saw a pharmacist who was jotting down the records that she had
done for the day.
So as an IT student I talked to the pharmacist and she liked to handle a system by herself.
So, I decided to make a Pharmacy management system
1.2 Problem in brief.
 In the current scenario, the client takes more than two hours to stock all the transactions.
 And misses some of the transaction that she had done in the entire day.
 Also, she doesn’t know if there’s any loss in the stocks
1.3 Aims and Objective

Aims

The aim to develop a well computerized system for the pharmacy that satisfy the
client requirements. This system will help the client a lot when it comes to check the
daily transactions.
Objectives
• New medicines can be entered.
• To check the monthly income.
• Pharmacist can check the stock easily when there’s a drop.
• Accessibility
1.4 Summary
In the end of the day the client will understand his / her daily income and, he / she
will get to know if there’s any loss in medicines

2.Proposed System
To get a solution for the above problem or the scenario, I am going to create and modify
a fully updated system. Which can display and stock the information that are relevant to
the sales done by the pharmacist by the day.
First, I will store all information about the medicines in a database, which are available at
the pharmacy. And then, I will get and store all the transactions which are done on the
certain day. So that the pharmacist can stock all those details and check how her daily
income is?
However, this system will be updated according to the arrival of new medicines.

2.1 The scope of this project

Main Functionalities.
• To store the daily transactions.
• To get the income at the end of the day.
• To check how many transactions are been made.

Non- Functionalities
•Maintainability
Users in this system
• Reception – Updates the database and the stock
• Pharmacist – The person who handles the software.

2.2 Development Tools


I am planning to use some technologies like C# language under the .net frame or Java for
this software that I am going to work
And, I am planning to use MySQL to access the database in this pharmacy.

3. Feasibilities in this project


After talking to my client, I realized that this project is not to complicated. And, the
support that I wanted to do this project already exists.

3.1 Technical Feasibility


 By visiting that place, I realized that it is possible to us hardware, software and
other technologies
 And I realized that, they are capable and properly skilled to work with my system.

3.2 Economical Feasibility


 I contemplate that this shop frugally wealthy to maintain this system.

3.3 Schedule Feasibility


 I think I will be able to deliver this software within the appropriate time frame.

3.4 Operational Feasibility


 I will be responsible that the requirement of this project meets the shop
considerably.
3.5 Legal Feasibility
The system is lawfully approved and does not have major
4.Project Planning
4.1 Project Schedule

Start & the End of the


Phase Description of the work
dates

 Create the project proposal  June 25th - July 10th


01. Planning
 Submit the Project Proposal

 Meet the client


02. Analyzing  Check how they work  July 10th – July 15th
 Identify the difficulties

 Use charts to summaries the


03. Design  July 16th – July 24th
gathered data.

04. Coding  Start to code.


 July 25th – Aug 19th
 Test whether it matches the
05. Testing
requirements.

 Deliver the system to the


06. Implementation  Aug 21st – Aug 31st
client.

4.2 Grant Chart


5. Reference

 https://www.edx.org/course/developing-international-software-4?g_acctid=926-195-
8061&g_campaign=gs-nonbrand-pc-microsoft-
softdev&g_campaignid=1012996299&g_adgroupid=52385292840&g_adid=263002199021&g_k
eyword=software%20development%20tutorial&g_keywordid=kwd-
296697872070&g_network=g

 https://www.youtube.com/watch?v=JIyW7nH5RdE

 https://www.codewithc.com/pharmacy-management-system-c-mysql/

 https://www.google.com/search?q=books+on+how+to+create+a+pharmacy+system+using+c%2
B%2B&tbm=isch&source=univ&sa=X&ved=2ahUKEwjv9bLpvITjAhX_4XMBHcLiCrUQsAR
6BAgGEAE&biw=1366&bih=608

 https://www.freelancer.com/projects/cplusplus-programming/pharmacy-management-system/

Das könnte Ihnen auch gefallen