+INTRODUCTION

According to Laura C. Rodriguez Martinez (2009), the prototyping model requires heightened involvement from

users, allowing them to witness and interact with the prototype. This leads to more detailed and superior feedback and

specifications. The presence of the prototype being assessed by the user avoids many instances of misunderstanding that

occur when both parties assume the other understands their statements. As a result, the outcome is more likely to meet the

user's preferences for appearance, tactile experience, and performance. The aim of this research is to analyze and require a

detailed analysis and design for the mentioned system. Furthermore, this prototyping procedure persists until the customer

provides no feedback and moves ahead with acquiring the client's desired preferences for the design and development.

The process of creating a prototype typically commences upon completion of the initial draft of the requirements

specification document. At this stage, there is a moderate comprehension of the system, and its demands are not yet fully

discernible or subject to change. The prototype is then constructed and presented to end users and clients for use and

evaluation. Feedback from the client is relayed to the developers, outlining areas of dissatisfaction, necessary modifications,

and redundant features. The prototype is subsequently revised to incorporate feasible suggestions, and the system is once

again made available for use by both users and clients.

In Conclusion, creating a prototype offers a powerful representation of the design, allowing for a clear understanding

of the final product's appearance and function. Additionally, it facilitates the team's overall design process and comprehension

of the purpose. Delaying changes until later stages of development necessitates significant restructuring and additional

revisions. Having an initial model readily available enables early implementation of desired changes without having to

expend significant resources on the complete product. Consequently, early modifications enable expedited goal attainment.

REQUIREMENTS GATHERING

In this process, the researcher conducts an interview to a company namely: Fresh Options which is based in

Floridablanca, Pampanga. We gather information from group of people and in some representatives, stakeholders involved

such as the Manager, Users and Staff. This would discuss and uncover the primary business pain behind the request as well as

what the project is about and its goal.

As we are examining the Condor POS, with its Customizable Front-end, Ingredients inventory, VAT and Non-VAT

item reports. Staffs and managers have their own account to open it and used to process transactions by retail customers, the
role of every user here is to find the name of the product and calculate the price purchased by the customer using POS that in

some point the process is slow. A prototype strategy would make it easy to serve customers a great service as well as the user

who use the Condor POS, this has been proposed to achieve the systems become more updated, improve service quality to all

customers and satisfied customer experience.

At last, this proposal will make the system more focused on updating business requirements analysis and help to

avoid problems, it will meet the business requirements and provide customers and stakeholders with faster service.

CONCEPTUAL MODELING
 The Condor POS business process is clearly presented in this activity diagram, which also illustrates how the point-

of-sale system responds to its users. This is to manage sales information, processing transactions and distribution of products.

It is completely necessary information to provide a quality system as well as it would be much easier to build its interactions

and activities.
 In Case Diagram of Point of Sale, this consists of processes and two users or what you called “actors” involved in the

diagram. This used to show the processes involved when users invoke the software, it depicts the structure of the system

behavior and their connections.

In Class Diagram, the Shopping Cart, Item, Customer and Purchase Order shows the simple idea of how the Point of

Sale works. This explains the system classes and relationships as well as the system’s structure in detail and part by part.

DETAILED DESIGN
Data Model

A suitable data model must be created to make it easier to scan barcodes on the products to implement Prototype. The data

model will include information about product items, scanning barcodes, customers, and other relevant topics. A flexible data

model that is easy to update in response to changing Shop requirements must be created.

System Architecture

Layer presentation

The user interface can be constructed using web-based technologies like HTML, CSS, JavaScript and Php in this layer. The

user interface, which should be easy to use and simple, should allow customers to place orders and view the menu.

Layer application

This layer will contain the code that handles user input, retrieves, and manages data, and does any crucial estimations or

processing. We use programming languages like C#, Java, C++ or Python to develop application layer.

Info layer

We use database to build a data to put information on the barcodes because typically store product information such as price

and weight, date of manufacture, expiration date, and the manufacturer's name are using database. This layer will include the

data access layer as well as any necessary caching or speed improvement.

Integration layer

integration eases the flow of data throughout complicated information and operating systems by providing a middleware layer

to act as the common interface between each individual application, system, and service.

User interface design

the product is scanned, it should appear immediately on the monitor, the computer will not be confused by the amount of

product to be scanned.

Fresh Option Meat Shop can benefit from using Prototyping to have the opportunity to test models, collect feedback and

technical feedback, and incorporate it into prototypes before the final product is manufactured.

Therefore, we need to build models that are not only functional but also have outstanding accuracy. The aim is to explore

topics such as form and function, size, or ergonomic adaptations.

CONCLUSION

Through the process of prototyping, the analysis and design phase of the proposed system for Fresh Options allowed

for the identification of the company's and its customers' needs and requirements. Furthermore, the main objective is to

ensure customer contentment, particularly in terms of the system's scalability and reliability.

The fresh options is intended to give the customer up-to-date technology that will facilitate their payment and let

them know what they will pay for the purchase. The proposed system holds significance as it eliminates any inconvenience

for the user while utilizing it and facilitates seamless access to the pricing details of the product.

In conclusion, using the Prototyping Strategy in Condor POS this proposal will make the system more focused on

updating business requirements analysis and help to avoid problems, it will meet the business requirements and provide

customers and stakeholders with faster service. Conceptual Models focus it on how they clearly understand the process or the

illustration of this system. Additionally, Data Model and System Architecture make it more detailed.