Generalities

This work shows the analysis for the development of a sales and
prescription control system for the “Botica la Esperanza” pharmacy. The work is
structured according to the methodology that Roger Pressman exposes in his book
“ Software Engineering, a Practical Approach”, in its seventh edition .

Beginning Stage.

The software system will be developed for the Botica la Esperanza

pharmacy, which is an establishment that is dedicated to the sale of medications of
all types. Its headquarters are located in the town of Telchac Pueblo.

Description of the problem:

Currently, the Botica la Esperanza pharmacy carries out its operations

manually in printed formats that are filled out by hand. When selling a medicine,
the information requested, such as the prescription if necessary, is stored in a
notebook to be able to give the data to the health secretary when requested. The
sales notes are made on a sheet of paper by hand and an exact inventory is not
kept of the medications that are out of stock or expired, according to Edgar Sabido,
owner of the pharmacy.

Despite being a method that has worked for them for years, the inventory
and information on the recipes is not very exact and requires many sheets and
space to store them, as well as causing discomfort to customers and the seller
himself by not knowing if They have the product or it is expired and keeping all that
documentation in order is very difficult.

Proposed Solution.
Design and develop a point-of-sale system to keep track of sales and
inventory, be able to print reports, review how many medications are expired to
remove them from inventory, and be able to keep track of customer prescription
data. to later or when necessary to be able to print them, as well as to be able to
keep track of the sellers.
 Project requirements

Below is a list of the requirements that were discovered in the first instance for the
development of the system. For a second analysis, they were simply described in
more detail and adding the requirements regarding user privileges and their
creation.

1.- The company requires consultations on medications that require a prescription for
subsequent sale.
2.- In addition, control of the sales made in the pharmacy is required.
3.- The company manages many suppliers who supply the drugs.
4.- Many drug laboratories are managed.
5.- You need to know or have stored the information of the pharmacy employees.
6.- You need to know which drugs are close to expiring or expired.
7.- It is necessary to have an inventory of all the product that exists in the warehouse.
8.- The pharmacy needs monthly reports to verify the financial situation.
9.- Proof of payment is required to be provided for customers who purchase products.
10.- When selling an antibiotic or controlled medication, the prescription needs to be
recorded, and the following information must be included, at a minimum:
- Patient identification
- Identification of the doctor (prescriber)
- Medical certificate.
- Date of issue
- Name, concentration and total amount of the drug
- Indications for use
- Route of administration
- Presentation
- Frequency and duration of treatment
11.- The company requires maintaining a record of the pharmaceutical products
purchased, acquired, or introduced into the warehouse/inventory.
12.- It is required to be able to update controlled medications.
13.- Antibiotics can only be dispensed through a legal prescription or medical order.
14.- Prescriptions for controlled substances can be filed in written version or
electronically. If the pharmacy chooses to maintain electronic files, the original copy of
the prescriptions should also be kept.
15.- The purchase date of the drug that requires a prescription must be saved.
16.- The total amount dispensed must not exceed the total prescribed amount
17.- Nothing should be dispensed after the period for which the prescription is valid.
18.- The employee must be registered in the system.
19.- Control must be kept of which employee made the sale.

When the seller or pharmacist receives the client's order, he must search
the database to see if he has the medication and if so, the system must
verify if the medicine requires a prescription, inform the seller, he will ask the
client for the prescription and will write the prescription data such as: name
of the client, date of issue of the prescription, date of expiration of the
prescription, name of the doctor, professional license of the doctor, name of
the medication, quantity dictated by the prescription, quantity sold,
chemicals , type (antibiotic or other controlled medication) and address will
then proceed to register the purchase in the system and it will save the data,
calculate the total sale price and update the warehouse quantities in the
database.

Restrictions

That pharmacies do not want to use the system

Risks

Not having the data necessary to develop the system

Not understanding pharmacy requirements

Not having enough time for development

Classification of Requirements

In the classification of requirements, all aspects provided by clients and users are considered
in order to organize them in such a way that the functional aspects that the system will have to
cover the needs of the company are considered.
Functional Requirements

1.- The system must have the following modules:

- Manage Sales
- Manage Recipes
- Check expiration
- Manage Updates
- Manage Reports
- Manage Sellers
- Login
2.- In the Manage Sales module, sales and sales cancellations will be made and you
can consult or search for products, as well as print and generate sales notes.
3.- In the Manage Recipes module you can register customer recipes, edit them and
consult them.
4.- In the Check Expiration module you will see the medications that have already
expired and can be removed from the inventory.
5.- In the Manage Updates module you can Update the Warehouse or Inventory and
the medications that need a prescription.
6.- Within the Warehouse Update you can add medications, modify the medication
data and delete the medications.
7.- In the update of prescription medications, the list of medications that require a
prescription to be sold will be updated.
8.- In the Manage Reports module you can see the registered recipes and print them
as well as the sales reports made.
9.- In the Manage Sellers module you can register, modify and delete users from the
system.
10.- There will be two types of user: the administrator and the seller.
11.- The seller will only have access to the Manage Recipes, Manage Sales, Check
Expiration and Manage Updates modules.
12.- The administrator will have access to all modules.
13.- All records will be saved in a database.
14.- The system will carry out all the necessary accounts to obtain the total, subtotal,
take into account discounts, etc.
15.- When the customer makes a purchase, a note can be printed.
16.- Registered sales and recipes will be saved along with the data of the user who
made the sales.
18.- The Login module will ask for the username and password to enter the system.
19.- At the end of the sale, the system must check whether any of the medications
require a prescription. If so, the window for recording the prescription will be displayed.

Non-Functional Requirements

1.- A machine with Windows Vista or 7 operating system will be needed.

2.- You will need to have the .Net Framework version 4 installed.
3.- The database will be created in Access 2010.
4.- The language that will be used will be C# 4.0.
5.- The reports will be exported to Excel or Word to be printed.
6.- An HP inkjet printer will be used.

Use Case Diagrams

System Function Table

The functions of the system are what it will do . They must be identified and listed in
cohesive and logical groups. Functions must be classified to prioritize them and identify
those that would otherwise go unnoticed (but consume time and other resources). The
categories are:

- Obvious: It must be done, and the user should know that it has been done.

- Hidden: It must be done, although it is not visible to users. These functions are often
(wrongly) omitted during the requirements elicitation process.

Ref. # Function Category

R1.1 The user must enter an ID Evident
and password to use the
system.
R1.2 Edit Seller Evident
R1.3 Delete Seller Evident
R1.4 Register Medication Evident
R1.5 Edit Medication Evident
R1.6 Cancel Expired Medication Evident
R1.7 Consult Medication Evident
R1.8 Register Sale Evident
R1.9 Cancel Sale Evident
R1.10 Save to the DB Hidden
R1.11 Generate Note Evident
R1.12 Register Recipe Evident
R1.13 Consult Recipes Hidden
R1.14 Update Medical Prescription Hidden
Database
R1.15 Verify Data Hidden
R1.16 Display Message Evident
R1.17 Calculate Total Sale Evident
R1.18 Update Warehouse Hidden
R1.19 Deploy Forms Evident
R1.20 Display Options Evident
R1.21 Validate data Hidden
R1.22 Check User Type Hidden
R1.23 Print Report Evident
R1.24 Print Recipes Evident
R1.25 Log in Evident
R1.26 Display Information Evident
R1.27 Print Note Evident

Description of Use Cases

Below is the description of the extended use cases, which are tables that
come out of the use case diagram, in which the system processes are described in
a clearer way, that is, the steps that have to be done or the steps that must be
gone through, in order to carry out said process, in which actors intervene.

Case of use: Manage Sales

Actors: Pharmacist (Seller/Manager)
Purpose: Be able to control sales of medicines and
warehouse.
Summary: The Pharmacist may consult the
medication to verify if it is in the
warehouse, make the sale, print a sales note
or cancel the sale.
Guy: Primary
Cross-references: R1.25, R1.18, R1.7, R1.8, R1.9, R1.10,
R1.11, R1.12, R1.15, R1.16, R1.17, R1.19,
R1. 20, R1.21, R1.27
Normal Course of Events
Actor's Action System response
1.- include(Login) 2.- The system displays the options that the
Pharmacist can choose.
3.- The Pharmacist chooses an option to
perform.
3a.- If you choose Consult Medication,
see section: Consult Medication.
3b.- If you choose Make Sale, see section:
Make Sale.
3c.- If you choose Cancel Sale, see 4.- The system sends a message that the
section: Cancel Sale. operation was completed correctly.
5.- This use case ends when the
Pharmacist performs the desired
operation.

Alternative Courses
None

Section: Consult Medication

1.- The system displays a query form
asking for the name of the medication or
content.
2.- The Pharmacist fills out the fields of 3.- The system validated that all fields have
the form. been filled out.
4.- The system consults the medications in
the DB.
5.- The system displays the result
Alternative Courses
Line 3: Missing fields to fill, the system displays a
fill fields message.
Line 4: The system does not find the medication, a
message is displayed informing that the
medication was not found.

Section: Make Sale

1.- The system displays a form for capturing
medications to be sold and the option to add
medication.
2.- The Pharmacist chooses to add 3.- The system displays a field to search for
medication the medication.
4.- The Pharmacist writes the name of the 5.- The system consults the DB.
medication.
6.- The system displays the information
corresponding to the product, including the
price.
7.- The Pharmacist adds the medication. 8.- The system reviews the database of
medications that need a prescription.
9.- The system displays a message saying
that a prescription is needed to sell the
medication.
10.- The Pharmacist chooses Register
Prescription, include (Manage
Prescriptions).
11.- The Pharmacist finalizes the sale. 12.- The system performs all the necessary
calculations for the total sale.
13.- The system updates the warehouse
database by discounting the quantity of
medications sold.
14.- The system generates the note and
displays it on the screen.

15.- Include(Print Receipt). 16.- The system saves the record of the sale
in the DB.
17.- This use case ends when the user has
made the sale and registers in the system.
Alternative Courses
Line 5: The system does not find the data, an
information message is displayed.
Line 10: The medication does not need a
prescription, the sale is registered.

Section: Cancel Sale

1.- The system displays a search form for sales
records.
2.- The Pharmacist fills in the 3.- The system consults the data in the DB.
corresponding data (date or id).
4.- The sale information is displayed.
5.- The Pharmacist chooses to cancel. 6.- The system sends a message to confirm
the elimination of the sale.
7.- The Pharmacist chooses to Accept. 8.- The system eliminates the sale of the
DB.
9.- The warehouse is modified
10.- The system displays a successful
cancellation message.
Alternative Courses
Line 4: The system does not find the data, the
system displays a message informing that
the sale was not found.
Line 5: The deletion is cancelled, the system sends
a deletion canceled message.
Extended Use Case

Case of use: Manage Recipes

Actors: Pharmacist (Seller/Manager)
Purpose: Be able to keep track of medical
prescriptions.
Summary: The Pharmacist records the prescriptions
 given by the client when they are
necessary, and may also consult the
prescriptions that have been registered.
Guy: Primary
Cross-references: R1.12, R1.13, R1.14, R1.15, R1.16, R1.19,
R1.21, R1.25, R1.26.
Normal Course of Events
Actor's Action System response
1.- include(Login) 2.- The system displays the options that the
administrator can choose.
3.- The Pharmacist chooses an option to
perform.
3a.- If you choose Register Recipe, see
section: Register Recipe.
3b.- If you choose Consult Recipes, see
section: Consult Recipes.
3c.- If you choose Edit Recipe 4.- The system sends a message that the
operation was completed correctly.
5.- This use case ends when the
Pharmacist performs the desired
operation.

Alternative Courses
None

Section: Consult Recipe

1.- The system displays a query form
requesting the registration date of the
recipe or the name of the client.
2.- The Pharmacist fills out the fields of 3.- The system validates that all fields have
the form. been filled out.
4.- The system consults the medical
prescriptions in the DB.
5.- The system displays the result.
Alternative Courses
Line 3: Missing fields to fill, the system displays a
fill fields message.
Line 4: The system does not find the records, a
message is displayed informing that the
recipe was not found.

Section: Register Recipe

1.- The system displays a recipe data capture
form.
2.- The Pharmacist fills out the 3.- The system validated that the data has
corresponding data been filled out correctly.
 4.- The system saves the data in the recipe
records database.
6.- The system displays a message
informing you that the recipe has been
saved and that you do not forget to stamp
and put a consecutive number behind the
customer's recipe.
Alternative Courses
Line 3: The data was not filled in correctly, the
system displays a message asking that the
data be filled in correctly.
Section: Edit Recipes
1.- The system displays a form with a field
to choose the recipe registration date.
2.- The Pharmacist chooses a date. 3.- The system displays the recipes
registered on that date.
4.- The pharmacist chooses a prescription. 5.- The system displays the recipe data.
6.- The Pharmacist modifies the 7.- The system modifies the data in the
prescription and saves the changes. database and displays a message of
changes made.
Alternative Courses

Extended Use Case

Case of use: Check Expiration

Actors: Pharmacist (Seller/Manager)
Purpose: Be able to review medications that are
expired or about to expire.
Summary: The Pharmacist may consult the
medications that are about to expire or
have already expired and may cancel them.
Guy: Secondary
Cross-references: R1.6, R1.7, R1.15, R1.16, R1.18, R1.19,
R1.20, R1.21, R1.25, R1.26.
Normal Course of Events
Actor's Action System response
1.- include(Login) 2.- The system displays a form with the
medications that have already expired.
3.- The Pharmacist chooses to cancel the 4.- The system displays a message
medications, see section Canceling informing that the changes have been made
Medications.
Alternative Courses
Line 4: There are no medications that are about to
expire or are expired. The system displays
a message saying that there are no
 medications that are about to expire or are
expired.

Section: Cancellation of Medications

1.- The system displays a message asking if
you really want to cancel the medications
2.- The Pharmacist accepts. 3.- The system eliminates medications
from the BD.
4.- The system updates the warehouse
database.
5.- The system displays a message
informing that the data has been modified
correctly.
Alternative Courses
Line 2: The Pharmacist cancels, the withdrawal of
medications is cancelled.

Extended Use Case

Case of use: Manage Updates

Actors: Pharmacist (Seller/Manager)
Purpose: Be able to update the system and
warehouse.
Summary: The Pharmacist may update the warehouse
database, registering or editing medications
and the database of prescription
medications.
Guy: Primary
Cross-references: R1.14, R1.15, R1.16, R1.18, R1.19, R1.20,
R1.21, R1.25, R1.26, R1.28.
Normal Course of Events
Actor's Action System response
1.- include(Login) 2.- The system displays the options that the
administrator can choose.
3.- The Pharmacist chooses an option to
perform.
3a.- If you choose Update Warehouse, see
section: Update Warehouse.
3b.- If you choose Update Prescription
Medications, see section: Update
Prescription Medications.
4.- This use case ends when the
Pharmacist performs the desired
operation.
 Alternative Courses
None

Section: Update Warehouse

1.- The system displays the options.
2.- The Pharmacist chooses an option to
perform.
3a.- If you choose to Register Medication,
see section: Register Medication.
3b.- If you choose Edit Medication, see 4.- The system displays a message
section: Edit Medication. informing that the operation has been
carried out correctly.
Alternative Courses
None

Section: Register Medication

1.- The system displays a medication
capture form.
2.- The Pharmacist fills out the 3.- The system verifies that all the data has
corresponding data. been filled out correctly.
4.- The system saves the data in the
warehouse database.
5.- The system displays a message
informing that the data has been saved
correctly.
Alternative Courses
Line 3: The fields were not filled out correctly, the
system displays a message asking you to
fill out the data correctly.

Section: Edit Medication

1.- The system displays a search form for the
medication.
2.- The Pharmacist fills out the 3.- The system consults the data in the DB.
corresponding data.
4.- The medication information is
displayed.
5.- The Pharmacist modifies the data. 6.- The system verifies that the fields are
correctly filled out.
7.- The system displays a message asking if
you really want to save the changes.
8.- The Pharmacist accepts. 9.- The system saves the changes.
10.- The system displays a message
informing that the data has been correctly
saved.
Alternative Courses
Line 4: The system does not find the data, the
system displays a message informing that
the medication was not found.
Line 6: The data was not filled out correctly, the
system displays a message asking you to
fill out all the fields correctly.
Line 8: The Pharmacist cancels, the editing of the
medication data is cancelled.
Section: Eliminate Medication
1.- The system displays a form with the
medication search option.
2.- The Pharmacist finds the medication to 3.- The system displays a message asking if
be deleted and chooses the delete option. you really want to delete it from the
database.
4.- The Pharmacist chooses to accept. 5.- The system deletes the medication from
the database and displays a message that
the medication has been deleted.

Alternative Courses
Line 4: The Pharmacist chooses to cancel, the
deletion is cancelled.

Section: Update Prescription Drug List

1.- The system displays the Update option.
2.- The pharmacist gives you the update. 3.- The system connects via the Internet to
the Internet server.
4.- The system verifies that there is an
update.
5.- The system downloads the new
database.
6.- The previous database is deleted.
7.- A message is displayed informing that
the database has been updated.

Alternative Courses
Line 3: Cannot connect to the server, a message is
displayed informing that it cannot connect
to the server.
Line 4: There are no new updates, a message is
displayed informing you that you have the
most current database.
Extended Use Case

Case of use: Log in

Actors: Pharmacist (Seller/Manager)
Purpose: That the Pharmacist can enter his respective
session.
Summary: The Manager or Pharmacist's account will
be validated to open their respective session
in the system.
Guy: Primary
Cross-references: R1.25, R1.22, R1.26, R1.20, R1.19, R1.16,
R1.15.
Normal Course of Events
Actor's Action System response
1.- This use case begins when the Manager 2.- The system displays a message with two
or Seller enters the system. options.
3.- The Manager or Seller chooses one of
the options.
3a.- If you choose to log in as a Manager,
see section: Log in as a Manager.
3b.- If you choose to log in as a Seller, see 4.- The system displays a welcome
section: Start a Seller Session. message.
5.- This use case ends when the Manager or
Seller has entered their respective session in
the system.
Alternative Courses
None

Section: Login Manager

1.- The system displays a form requesting
the Manager ID and password.
2.- The Manager provides the data. 3.- The system validates the data provided.
4.- The system displays a welcome
message.
5.- The system displays the Manager
section.
Alternative Courses
Line 3: The data provided does not exist, a message
is displayed informing that the data is not
correct.

Section: Start Seller Session

1.- The system displays a form asking for
the username and password.
2.- The Seller provides the data. 3.- The system consults the database and
validates the data provided.
4.- The system displays a welcome
message.
5.- The system displays the Seller section.
Alternative Courses
Line 3: The data provided does not exist, a message
is displayed informing that the data is
incorrect.
Extended Use Case

Case of use: Manage Reports

Actors: Manager
Purpose: Be able to keep track or manage reports.
Summary: The Pharmacist may print reports of sales
made on a certain date as well as print
medical prescriptions that have been
recorded.
Guy: Secondary
Cross-references: R1.13, R1.15, R1.16, R1.17, R1.19, R1.20,
R1.21, R1.23, R1.24, R1.25, R1.26.
Normal Course of Events
Actor's Action System response
1.- include(Login) 2.- The system displays the options that the
Manager can choose.
3.- The Manager chooses an option to
carry out.
3a.- If you choose Print Sales Report, see
section: Print Sales Report.
3b.- If you choose Print Recipes, see 4.- The system sends a message that the
section: Print Recipes. operation was completed correctly.
5.- This use case ends when the Manager
performs the desired operation.

Alternative Courses
None

Section: Print Sales Report

1.- The system displays a query form
requesting a date range.
2.- The Pharmacist fills out the fields of 3.- The system validates that all fields have
the form. been filled out.
4.- The system consults the registered sales
in the DB.
5.- The system displays the result.
6.- The Manager gives print. 7.- The system orders the information to be
printed.
Alternative Courses
Line 3: Missing fields to fill, the system displays a
fill fields message.
Line 4: The system does not find the records, a
 message is displayed informing it.
Line 7: The Manager cancels the printing, leaves
the section.

Section: Print Recipes

1.- The system displays a query form
requesting a date range.
2.- The Pharmacist fills out the 3.- The system validates that the data has
corresponding data been filled out correctly.
4.- The system consults the registered
recipes in the DB.
5.- The system displays the information on
the recipes to print.
6.- The manager chooses to print. 7.- The system orders the information to be
printed.

Alternative Courses
Line 3: Missing fields to fill, the system displays a
fill fields message.
Line 4: The system does not find the records, a
message is displayed informing it.
Line 7: The Manager cancels the printing, leaves
the section.
Extended Use Case

Case of use: Manage Sellers

Actors: Administrator(Manager)
Purpose: Add, Edit or Delete employee data.
Summary: The Manager can register a seller, edit their
data or delete them.
Guy: Primary
Cross-references: R1.1, R1.2, R1.3, R1.10, R1.15, R1.16,
R1.19, R1.20, R1.21, R1.25, R1.26.
Normal Course of Events
Actor's Action System response
1.- include(Login) 2.- The system displays the options that the
administrator can choose.
3.- The administrator chooses an option to
carry out.
3a.- If you choose to add a seller, see
section: Seller Registration.
3b.- If you choose to edit seller data, see
section: Edit Seller Data.
3c.- If you choose Delete seller data, see 4.- The system sends a message that the
section: Delete Seller Data. operation was completed correctly.
5.- This use case ends when the
administrator performs the desired
operation.

Alternative Courses
None

Section: High Seller

1.- The system displays a query form
requesting the seller's information.
2.- The administrator fills out the form 3.- The system validates that all fields have
fields. been filled out.
4.- The system saves the data in the DB.

Alternative Courses
Line 3: Missing fields to fill, the system displays a
fill fields message.

Section: Edit Seller Data

1.- The system displays a form to enter the
name of the seller to modify.
2.- The Administrator fills out the 3.- The system validates the name of the
corresponding data client entered.
4.- The system extracts the data from the
DB.
5.- The system displays the information
corresponding to the seller.
6.- The Administrator makes the 7.- The system validates the data.
necessary modifications.
8.- The Pharmacist finalizes the sale. 9.- The system saves in the DB.
Alternative Courses
Line 3: The system does not find the data, an
information message is displayed.
Line 7: Choose cancel, the editing is cancelled.

Section: Delete Seller Data

1.- The system displays a form to enter the
name of the seller to be deleted.
2.- The Administrator fills in the 3.- The system validates the data.
corresponding data.
4.- The data is consulted in the DB.
5.- The system sends a confirmation
message.
6.- The Administrator confirms the 7.- The system deletes the data from the
deletion. DB.
Alternative Courses
Line 3: The data is not correct, you are asked to fill
out the form data correctly.
Line 5: The data is not found, the system displays a
message informing that the seller does not
exist.
Line 7: The deletion is cancelled, the system
displays a deleted deletion message.
Extended Use Case

Prioritization of Requirements and Negotiation

The prioritization of the requirements helps to define which requirement is most

relevant to be met and which are not so essential. The client is the one who defines
this process at the time of negotiation, but due to time issues, their priorities will only
be defined through criteria. developer's own.
First, the requirements are listed and in the right column their importance is placed
according to:

1 very important 2 important 3 unimportant

1.- The system must have the following modules: (1)

- Manage Sales
- Manage Recipes
- Check expiration
- Manage Updates
- Manage Reports
 - Manage Sellers
- Login
2.- In the Manage Sales module, sales and sales cancellations will be made and you
can consult or search for products, as well as print and generate sales notes.
(1)
3.- In the Manage Recipes module you can register customer recipes, edit them and
consult them. (1)
4.- In the Check Expiration module you will see the medications that have already
expired and can be removed from the inventory. (1)
5.- In the Manage Updates module you can Update the Warehouse or Inventory and
the medications that need a prescription. (1)
6.- Within the Warehouse Update you can add medications, modify the medication
data and delete the medications. (1)
7.- In the update of prescription medications, the list of medications that require a
prescription to be sold will be updated. (1)
8.- In the Manage Reports module you can see the registered recipes and print them
as well as the sales reports made. (2)
9.- In the Manage Sellers module you can register, modify and delete users from the
system. (1)
10.- There will be two types of user: the administrator and the seller. (1)
11.- The seller will only have access to the Manage Recipes, Manage Sales, Check
Expiration and Manage Updates modules. (2)
12.- The administrator will have access to all modules. (2)
13.- All records will be saved in a database. (1)
14.- The system will carry out all the necessary accounts to obtain the total, subtotal,
take into account discounts, etc. (2)
15.- When the customer makes a purchase, a note can be printed. (2)
16.- Registered sales and recipes will be saved along with the data of the user who
made the sales. (2)
18.- The Login module will ask for the username and password to enter the system.
(2)
19.- At the end of the sale, the system must check whether any of the medications
require a prescription. If so, the window for recording the prescription will be displayed.
(1)
Conceptual Diagram

Genera
Report
te

Genera
Employee te Note

Register
Manage

Recipe
Medicine Reques
t
Purchase notification

Bill

Add

Inventory
Glossary

Purpose of the Information: Place an Order Object of Information: Medication information

Attributes Attributes

Drug name Medication Name

Route of administration Laboratory
Route of administration
Quantity in warehouse
Price
Requires Recipe
Presentation

Restrictions Restrictions
It must have the name of the medication You must say if it is a controlled medication
It must have the route of administration
Domain Class Domain class
Pending to specify Pending to specify

Object of Information: Sales note

Attributes

Pharmacy name and address

Dispensing date
Expiration Date (the date the prescription
expires)
Recipe number (a unique number must be
issued on each prescription)
Name of patient
Doctor's name
Drug name and quantity dispensed
Price
VAT
Name of the employee
Date of purchase
Restrictions
That the client confirms the purchase of the
drug and the prescription has been
validated.
Domain class
Pending to specify
Purpose of the Information