The document outlines the proposal for an online pharmacy system aiming to enhance user access, reduce paperwork, and ensure data security while addressing the inefficiencies of the existing manual system. It details the project's feasibility study, software and hardware requirements, cost estimation, and risk management strategies. The proposed system is intended to streamline processes for both users and pharmacy operators through a user-friendly platform.

1. ONLINE PHARMACY
SYSTEM
Presented By:
Ketan .M.Tapkirkar
Dhiraj Waghat
Omkar .G.Walavalkar
Guided By:
Prof.Mrs.Nilam Shaikh
SSPM’s College Of Engineering , Kankavli.
Submitted To:

2. CONTENT
 Introduction
 Existing system
 Drawbacks
 Proposed system
 Need of new System
 Feasibility Study
 Hardware And Software Requirement
 Project Proposal
 Cost Estimation
 Actively chart
 WBS
 Gantt Chart
 RMMM
 Conclusion

3. INTRODUCTION
The project OPS enables user to consume Pharmacy Portal Information
process from anywhere through online.
Reduces paper work and easily handles data.
User friendly.
This application will help user to fulfill all their requirements while Admiting
themselves and Accessing Pharmacy Information.

4. EXISTING SYSTEM
 It require more Paper work
 Less secure
 User take more efforts so process is time
consuming

5. DRAWBACKS
 Highly manual
 Data can be lost or destroyed
 It is difficult to update , delete and view data
 Maintaining and retrieving the record of Users is difficult

6. PROPOSED SYSTEM
Less time consuming
Secure process
Less paper work
Manual efforts are overcome

7. NEED OF NEW SYSTEM
 Computerization of the Pharmacy system.
 Reduce the load on the Chemist & Drugs Dealers.
 System performs all calculations .
 Chemist and Doctors list can easily be retrived & any required addition , deletion or
updation can be performed.

8. FEASIBILITY STUDY
 Operational Feasibility
 Technical Feasibility
 Schedule Feasibility
 Economic Feasibility
 Legal Feasibility
 Market Feasibility
 Resource Feasibility
 Cultural Feasibility

9. SOFTWARE REQUIREMENT
 Operating System: Windows XP
 Language: JAVA Script,PHP
 Database: MY SQL

10. HARDWARE REQUIREMENT
 Processor : Intel I3 or Above
 RAM :1GB
 Hard Disk : 2TB
 Monitor : 15"color monitor
 Keyboard :122 keys

11.  Project summary
 Technical section
 Scope of work
 Benefits
 Schedule
 Cost and payment section
 Legal section
 Management and qualification section
PROJECT PROPOSAL

12. COST ESTIMATION
Cb = 2.5
Db = 0.35
EAF = 1.2
 LOC = 50,000
 KLOC = (50,000/1000) = 50
 E = [ai(KLOC)^bi * EAF] = [3.0(50)^1.12 *1.2] = 287.8 person-Months
 Develop time(D) = [Cb(E)^ db ] = [2.5(287.8)^0.35] =18.13 months
 No. of Persons(P) = (E/D) = 287.8/18.13 =16
 Cost per person per month = 2000$
 Cost for software development = E*2000 =287.8*2000 = 5,75,600$
Software a i b i
Organic 3.2 1.05
Semi-detached 3.0 1.12
Embedded 2.8 1.20
INTERMEDIATE COCOMO

13. ACTIVITY CHART

14. WBS

15. GANTT CHART

16. RMMMRISK INFORMATION SHEET
Risk ID:001 DATE:23-02-2017 PROB:75% IMPACT:Low
Description:
Cost Overiding The Budget.
Originator:Ketan Tapkirkar Assigned: Omkar Walavalkar
Refinement/Context:
Subcondition No. 1:- When Number Of Labours are Unecessarly Involved Project Development.
Subcondition No. 2:- Expertise Cost Is More Than It Is Expected.
Subcondition No. 3:- Project Schedule Is Overriding The Deadline.
Mitigation/Monitioring: 1. The cost associated with a late delivery is critical.
2. A late delivery will result in a late delivery of a letter of acceptance from the customer.
3.Without the letter of acceptance, the group will receive a failing grade for the course.
4.Steps have been taken to ensure a timely delivery by gauging the scope of project based on the
delivery deadline
Managenent /Contigency plan/Trigger:1.Late delivery would be a catastrophic failure in the project development. If the project cannot be delivered
on time the development team will not pass the course.
2.If it becomes apparent that the project will not be completed on time, the
only course of action available would be to request an extension to the deadline
form the customer.
Current status:23-05-2017
Approval :Dhiraj Waghat Closed Date:

17. RISK INFORMATION SHEET
Risk ID:001 DATE:23-02-2017 PROB:75% IMPACT:Low
Description:
Unable To Gather Change In Requirements.
Originator:Ketan Tapkirkar. Assigned:Omkar Walavalkar.
Refinement/Context: Subcondition No. 1: Initial Requirements were Not Cleared.
Subcondition No. 2: Due New Technology Discovery.
Subcondition No. 3:Customer Additional Requirements.
Mitigation/Monitioring:1. Customer meetings (formal and informal) Should be held with the customer on a routine business.
2. Ensuring Product are producing, and the requirements of the customer are equivalent.
Managenent /Contigency plan/Trigger:1.Should the development team come to the realization that their idea of the product
requirements differs from those of the customer, the customer should be
immediately notified and whatever steps necessary to rectify this problem should be taken.
2.Preferably a meeting should be held between the development team and the customer to discuss at length this issue.
Current status:23-05-2017
Approval:Dhiraj Waghat Closed Date:

18. CONCLUSION
Thus we have Propose ONLINE PHARMACY SYSTEM
This software aims at reducing paper work & provide
multiple facilities to user with less efforts and Accessing
the Portal according to choice & availability

19. THANK YOU…