CCC 151 – Information Management

Background of the Project, Narrative Listing, Project’s Impact to the Client/Business

Organization and 1st Draft of the Project’s Database Design

Due date: Tuesday, March 21, 2023

Canoy, Nikka Shane G.

Eliodra, Rozel Hyacinth S.
Madridano, Charlyn H.
Saavedra, Cybelle L.

Name of Business: Maria Cristina Small Coconut Farmers Multi-Purpose Cooperative

Address: Purok 8 Barangay Maria Cristina, Balo-i, Lanao del Norte
Title of the Proposed Solution: Developing an Efficient Sales Management Database for Small
Coconut Farmer's Multi-Purpose Cooperative Grocery Store

2.1. Background of the Project

The project aims to address the inefficient sales management of Small Coconut Farmer's
Multi-Purpose Cooperative grocery store. Currently, the store relies on the traditional paper and
pen method to record sales, which can cause delays in the cashier's functionality. To improve this
process, the proposal suggests developing an efficient sales management database. This solution
will not only streamline the sales recording process but will also provide accurate and timely
information about the store's sales performance. The proposal may have come about through a
needs assessment or evaluation of the grocery store's current sales management system, which
identified areas of improvement and suggested a database as a viable solution.

The proposal has been developed through a process of identifying a problem in the grocery
store's operations and brainstorming potential solutions. The proponents of the proposal have
conducted research and analysis to determine the most effective and feasible solution for the store's
sales management issues. We have also consulted with experts or other stakeholders to gather
insights and perspectives on the problem and potential solutions.

2.2. Narrative Listing

Effective knowledge of the sales process and the various sales strategies is necessary for the
sales management system.
The first process will be the accommodation of the members/ employee to the customers.
Second, the customers will find some products and decide if they will be going to buy them or not.

Page 1 of 4
Once the customers decide to buy the products the third (3 rd) process will follow. The customers
will proceed to the counter to pay for all the chosen products, the cashier will then list and total all
the products using the paper and pen method. The cashier will then issue the total bill of products
in order for the customers to pay for it. Since the store doesn’t have a system, it will be hard
to issue a receipt to their customers. The process of buying and listing the sales will
continue until the grocery store closes. After closing the store, the members on duty will count the
sales manually and then remit it to the cooperative treasurer then the treasurer will write the sales
in their sales report notebook.

2.3. Project’s Impact to the Client/Business Organization

The proposed project has a significant impact on the client/business organization of Small
Coconut Farmer's Multi-Purpose Cooperative. It will help the client to have an easier and faster
transaction. As for the process that we narrate above, we can remove the 3 rd process which is the
listing of products using the paper pen method. With the help of our proposed project, we can
remove this listing method and change it to an automated process that is more suitable for their
business. It will be easier, faster, and time-saving. By that, it can accurately give the sales report for
that specific day, weekly, or monthly without manually counting the sales which is more hassle and
very exhausting for them.
The impact of our project can also improve their sales. Instead of a long time waiting for the
other turns of a customer because of a paper pen method our project will help them boost their
sales through faster transactions which are they can assist more customers in a short period of time
or much faster than waiting for a paper pen process.

2.4. The Database Design

2.4.1. List of Business Rules/Policies
● Return and exchange policy
● No debt policy
● No discount
● Price Change
2.4.2. List of End-Users and their Corresponding Functions
● Cashier
o End users who handle sales transactions
o End users who engage with customers
● Treasurer
o End-users responsible for financial transactions, managing budgets, and keeping
track of the company's financial performance.

Page 2 of 4
 2.4.3. List of the Identified Entities and their Attributes
● Members
o MemID
o MemLName
o MemName
● Invoice
o SalesID
o DateandTime
o PrdctID
o PrdctName
o Qnty
o TotalAmnt
o AmntRcvd
o Change
o MemID
o CustID
● Officers
o OfficerID
o OfficerLName
o OfficerFName
o MemID
● Customer
o CustID
o CusLName
o CusFName
o SalesID
● Product
o prdctID
o prdctName
o QntyStock
o Price
o expDate
2.4.4 The Identified Relationships among Entities

Page 3 of 4
 ● Members and Sales: The Members entity has a one-to-many relationship with the Sales
entity, where each Member ID can be associated with multiple Sales IDs.
● Customer and Invoice: The Invoice entity has a one-to-many relationship with the Customer
entity, where each Invoice ID can be associated with multiple Customer IDs.
● Invoice and Product: The Invoice entity has a one-to-many relationship with the Product
entity, where each Invoice ID can be associated with multiple Product IDs.
● Members and Officers: The Members entity has a one-to-many relationship with the
Officer’s entity, where each Member ID can be associated with multiple Officer IDs.

2.5. The 1st Draft of the Project’s Database Design using Relational Database Model
(Relational Diagram)

Page 4 of 4