SRS Pharmacy Management System
A pharmacy management system is specially designed for the purpose of adding pharmacy item details. The system elaborates the basic concept for storing and generating pharmacy items detail. These items will be distributed in different categories, for example, there are a different type of items in the Pharmacy i.e. tablets, capsules, syrups, etc. so we can search them easily under the appropriate label and inform the customer about their price, quantity, and quality if needed. In this system, owner can sign up as a system admin, and he/she can have full access to the system for maintaining daily records. It will be a windows-based application that has been developed to make all the operations fast and easy. The design of the pharmacy Management system is easy to use for every type of user because a lot of shops have salespersons which are not well qualified. The main objective of developing this system is to help inventory operators of pharmacy to manage their inventory in a systematic and efficient way.
Â
Scope of Project Pharmacy Management System:
Project scope is the part of project planning that involves determining and documenting a list of specific project goals, deliverables, tasks, costs and deadlines. Defining the project scope involves adopting a clear vision and an agreement on the outcomes of the project. This allows each milestone of the project to stay on target
Functional and Non Functional Requirements of Pharmacy Management System:
Functional Requirements :
A functional requirement shows that what the system must do what services the system present to users. It describes a software system or its component. A function is nothing but inputs to the software system, its behavior, and outputs
Functional Requirements of Pharmacy Management System:
1. Registration
The administrator can create a new user (Workers at pharmacy).
New user can login and logout.
2. Pharmacy Items
Admin add, delete or modify the pharmacy items and its details.
3. Add expired Items
Admin add, delete or modify the expired items and its details.
4. Search
User can search for the required pharmacy items based on name, id etc.
5. Sell pharmacy items
The sold pharmacy items need to be deducted from the available stock.
6. Purchase pharmacy items
The purchased pharmacy items need to be added to the available stock.
NON-FUNCTIONAL REQUIREMENTS Pharmacy Management System:
- Application is user friendly.
- Application Perform fast manipulation and calculations.
- Application is adaptable.
- Application will be able to work on all types of operating systems.
- Application will be capable to handle multi user activities simultaneously.
- There will be back up system to face any problem in system
- All the options should be learning friendly I.e. member could easily understand what that option will do if he clicked on it.
- Response Time is very awesome.
Some others are:
- Accessibility
- Maintainability
- Â Fault Tolerance.
- Security
- Robustnes
Use Case Diagram of Pharmacy Management System
a use case diagram can summarize the details of your system’s users   and their interactions with the system. Scenarios in which your system or application interacts with organizations, people, or external systems. Goals that your system or application helps those entities achieve
Usage Scenarios Pharmacy Management System:
A brief user story explaining who is using the system and what they are trying to accomplish. A Scenario is made up of a number of simple, discrete steps that are designated as being performed by either the System or a  User.
ADOPTED METHODOLOGY for Pharmacy Management System:
The adopted methodology for this project is vu process model. Vu process model is a combination of water-fall model and spiral model. This combination has many advantages. This model has high risk analysis so avoidance of risk would be achieved. This model is easy to understand and use. Now first we will discuss the Water-fall model.
Work Plan of Pharmacy Management System:
Work plan
for complete srs contact us
watsapp: 03469806607