UNIVERSIDAD PRIVADA DE TACNA

FACULTAD DE INGENIERIA
Escuela Profesional de Ingeniería de Sistemas

Proyecto Sistema de Gestión de Compras y Venta

Curso: BASE DE DATOS II

Docente: Mag. Ing. Patrick Cuadros Quiroga

Integrantes:

Chara Apaza, Edgar Diego (2017352948)

Tacna – Perú
2022
 1. INTRODUCCIÓN

1.1. Propósito

This document is the first version of the "Don Lalo Store Purchase and Sales Management System"

project, which arises in order to digitize the processes of registering inputs and outputs of the

company's products, thus achieving quick information , which will result in lower costs and better

decisions.

This document provides a vision where we will define the scope, objectives, among other things, for

the development of the new system.

The purpose of this document is to present the necessary information for the elaboration of a new

system, as well as for a good understanding between the users of the system. It will have the

detected general vision of the current system, as well as the initial proposal of the new system to

be carried out. The proposal is based on the analysis of the information collected in the interview

that was carried out with the general manager of the client company, as well as on the

documentation that the company provided us (purchase invoices, sales receipts, sales invoices,

credit).
2. DESCRIPCIÓN DE PROYECTO

2.1. Nombre del Proyecto

Sales and Purchase System Don Lalo Store

2.2. Duración del Proyecto

The project will last 3 months.

2.1. Definición del problema

El problema Currently the client company does not have a computer system
that manages the purchases and sales made by the company,
these are done manually
Afecta The sales area to carry out its work needs to access the stock of
products, to achieve this the sales manager needs to go
personally to the warehouse in order to verify product
availability, which generates a waiting time for the final
customer.
The Purchasing area does not have quick access to the
information to carry out its activities.
The warehouse area is controlled manually, which makes
warehouse status processes slow.
Consecuencia This generates a cumbersome and difficult process when
information on the economic situation of the company is
required, since these must be outsourced to the company's
accountant, who in turn must record the information document
by document in order to be able to offer the manager the
requested report.
Solución Implement a quality IT solution that automates all these
processes, that has a flexible structure and a robust
architecture.
3. OBJETIVOS DEL SISTEMA

3.1. Objetivo General

It is intended to develop a system for the control of sales and stock of the Minimarket “Tienda
Don Lalo ”.

3.2. Objetivos Específicos

 Obtain knowledge about “Tienda Don Lalo” minimarket, regarding its organization, types

of products, employees and associated suppliers.

 Implement a sales module with the help of the information obtained, to facilitate the

management of the minimarket to the owner.

 Verify with the client that the system covers and complies with the specified

requirements.
4. DISEÑO DE LA SOLUCIÓN

4.1. Casos de Uso

A use case is a sequence of transactions performed by a system in response to an event initiated by

an actor on the system itself. These types of diagrams are used to specify the functionality and
behavior of a system through its interaction with users and/or other systems.

5.1.1. Caso de Uso General

In the case of general use, the actions that can be carried out by users registered in the
system are shown. It should be noted that the administrator has more features than a common
user.

The rest of the use cases and their respective specifications can be consulted in Annex
A.

Figura 7.1 Caso de Uso Genera

Caso de Uso Realizar Venta
Actor Principal Administrador

Participantes e Administrador: Desea realizar una venta.

Intereses
Usuario: Desea Realizar una venta.
Precondiciones 1. El usuario debe estar logueado para realizar la venta.
Postcondiciones Al finalizar la venta se tendrá un listado de los productos y sus respectivos

Escenario principal 1. El Usuario ingresa al sistema

2. El Usuario selecciona la opción realizar venta.
3. El Usuario ingresa los productos que se venderán a través de un lector
Extensiones 1.1 El Usuario ingresa incorrectamente su contraseña.
1.1.1 El sistema le indica al usuario que su ingreso no ha sido exitoso.
1.1.2. El sistema manda un mensaje pidiendo que lo intente de nuevo.
3.1 El Usuario ingresa incorrectamente su contraseña.
3.1.1 El sistema le indica al usuario que su ingreso no ha sido
exitoso.
Requisitos No hay requisitos especiales.
Especiales
Frecuencia de Alta
Ocurrencia

17
5.1 Diagramas de Secuencia

5.1.1 Realizar Venta

To carry out the sale of a product, the user (seller) must scan its bar code, it is added to a list, the
product is searched, its existence is confirmed, a list of all the products to be sold is generated and
the data is displayed to the user. Then he confirms the sale, including how much money they
cancel him with. The system calculates the total of the sale and delivers the information through
the interface. The stock of the recently sold products is updated, the operation carried out is
confirmed and finally the change that must be delivered to the client is delivered to the user,
together with this a report of the sale recently made is generated.

18
 Usuario

5.2 Diagrama de Clases

A class diagram allows you to show the classes of the system and their
interrelationships. These serve both to show what the system can do (analysis) and
to show how it can be built (design). Next, the class diagram that represents the
system to be developed for the “Future” minimarket is displayed.

19
 5.3 Modelo Entidad Relación

An entity-relationship model or diagram is a tool for data modeling, which allows

representing the relevant entities of an information system, as well as their
interrelationships and properties. Next, the entity-relationship model that reflects
the “Future” minimarket system will be shown.

5.4 Modelo Relacional

In this type of model, all data is stored in relationships and since each
relationship is a set of data, there is no order in which the data is stored.
This has the considerable advantage that it is easier for a non-expert user
to understand and use. The information can be retrieved or stored
through queries that offer great flexibility and power to manage the
information. The Relational model below Reflects the relationships 20

between the data of the “Future” business.

21